All blogs / Distributed systems / cloud
It Depends
Kislay's personal blog and newsletter
Distributed systems / cloudSoftware / engineering practiceEngineering management / careers
- Posts
- 186 from 8 Jul 1996 to 22 Aug 2026
- Posting
- now and then (3 in the last year)
- Kind
- personal blog
- Feed
- https://kislayverma.com/rss/
2026 3
2023 8
2022 13
- Evolving Software: SOLID principles as a continuum
- Building robust distributed systems
- On building scalable systems
- Mini Essay #4 - The other side
- Mini Essay #3 - Say "no"
- Architecture Patterns: Caching (Part-2)
- Architecture Patterns: Caching (Part-1)
- Mini Essay #2 - Failure is a Feature
- Mini Essay #1: Mindful Actions
- The pentagon of entity models
- The Mechanics of Software Evolution
- The crypto-web's fatal flaw
- The Marketplace Scam (sellers beware!)
2021 24
- Guidelines for writing useful libraries
- Competitive programming is useless
- The Rise of Edge Computing
- Uncertainty and Learning as Tech Debt
- Book Review and Highlights: "Accelerate"
- The sense of purpose in a complex system
- Summary: Lectures by Dr. Russell Ackoff
- So you want to privatize a bank?
- System design from one level up
- Combining rule-systems and machine learning
- The problem is not the problem
- How to organize your code?
- How big should a method be?
- Ditch the Urgency
- Why programmers don't write documentation
- External Programmability: The second law of building platforms
- Testing strategies for agile teams
- How to write self-documenting code
- Reduce collaboration by good design
- Architecture Pattern: CQRS
- Book Review: 10% Human by Alanna Collen
- Preventing "go-around" with Platform Thinking
- Perhaps we shouldn't be so well connected?
- Hindsight in 2020
2020 67
- Why and How to use Feature Toggles
- Architecture Pattern: Orchestration via Workflows
- Managing developer identities in autonomous teams
- How to speed up software delivery
- Book Review : Wardley Mapping
- Working around the CAP Theorem with Eric Brewer
- Observing is not Debugging (and other misnomers)
- The Revolution will be Unsupervised
- Publish events, not logs
- For the Layman (Ep. 3) - What is programming?
- Book Review : The Great Mental Models (General Thinking Concepts)
- More than testing - writing unit tests for better design
- A case against "Platform Teams"
- For the Layman (Ep. 2) - What is the Cloud?
- The Golden Rule of Platforms
- Book Review : Thinking in Systems - A Primer
- Layering domains and microservices using API Gateways
- Independence, autonomy, and too many small teams
- Book Review : Atomic Habits
- For the Layman (Ep. 1) - What is a Distributed System?
- Adios Uber, and ideas in the afterglow
- A Narrative Approach to Software Design
- Book Highlights: 97 things every software architect should know
- Design review checklist for Distributed Systems
- Code review checklist for distributed systems
- Launch Announcement: Rulette Home, Rulette Server, and more!!!
- Platforms (and dogfood) everywhere
- Scope of Business Rule Management Systems
- Gearing up for the big Rulette release
- APIs are not platforms
- Modelling tax rules with Rulette : Part Two
- Modelling tax rules with Rulette : Part One
- Platform Nuts & Bolts : Enforcing Constraints in Platform Architectures
- Platform Nuts & Bolts : Extendable Data Models
- Learning React in 24 hours
- Control and Chaos in Platform Systems
- Book Review : Wool by Hugh Howey
- Platform Nuts & Bolts : Flexible decision-making with Rule Engines
- Why I like the Vert.x Framework
- Learning Golang in 24 hours
- Defining messaging terms precisely
- Saving the day with Continuous Refactoring
- Distributed Systems as Data Pipelines : Throughput, Capacity, and BackPressure
- The full-stack team of this decade
- Book Review : The Innovator's Dilemma
- Sidestep architectural "-ilities" and deliver business value
- Book Review: Zero To One
- Book Review : The Hard Thing About Hard Things
- Marketplaces are not Platforms
- Domain Events versus Change Data Capture
- Rulette : A pragmatic rule engine
- The Children of Hurin
- Asynchronous Programming : A Cautionary tale
- Event-Based Asynchronous Programming
- Asynchronous Programming with Thread Pools
- Overcoming IO overhead in micro-services
- Being Fast or Getting Faster? (aka Build Momentum, not Velocity)
- Working in the seams of code with Resource Locator
- Agile for Innovation - Going Beyond Execution Excellence
- Choosing a service framework
- How to build a technology platform
- Using Events to build evolutionary architectures
- Why you should build a platform
- Make it better, every day of the week
- Explicitly Yours
- Products are not Platforms
- Distilled : Steve Yegge's platform rant
1996 1
Undated 70
- It Depends #59: Supercharge your reading with 4Later
- It Depends #58: Evolving software using all SOLID principles at once
- It Depends #57: Critiquing crypto, trunk-based development, and Paxos made simple
- It Depends #56: Building robust distributed systems
- It Depends #55: On building scalable systems
- It Depends #54: An introduction to Caching (Part-2)
- It Depends #53: An introduction to Caching (Part-1)
- It Depends #52: The Pentagon of Entity Models
- It Depends #51: The Mechanics of Software Evolution
- It Depends #50: The crypto-web's fatal flaw
- It Depends #49: The Marketplace Scam (seller beware!)
- It Depends #48: Theory building, visual probability, index while read, and hiring a manager
- It Depends #47: Guidelines for writing useful libraries
- It Depends #46: Competitive programming is useless
- It Depends #45: The rise of Edge Computing
- It Depends #44: Uncertainty and learning as tech debt
- It Depends #43: Book review and Highlights from "Accelerate"
- It Depends #42: The sense of purpose in system design
- It Depends #41: Systems Thinking with Dr. Russell Ackoff
- It Depends #40: So you want to privatize a bank?
- It Depends #39: System design from one level up
- It Depends #38: Combining rule systems and machine learning
- It Depends #37: The problem is not the problem
- It Depends #36: How to organize your code
- It Depends #35: How big should a method be?
- It Depends #34: Ditch the Urgency
- It Depends #33: Flink, Start with why, Pace layer, Snowflake
- It Depends #32: Why don't programmers write documentation?
- It Depends #31: The second law of building software platforms
- It Depends #30: Eliminating the QA bottleneck
- It Depends #29: On self documenting code
- It Depends #28
- Kislay's Newsletter #27: CQRS, internal platforms, complexity, and AWS
- Kislay's Newsletter #26: Tech debt, moving to IC, regulation of innovation, and architecture principles
- Kislay's Newsletter #8
- New post by Kislay Verma
- Kislay's Newsletter #25: We are only 10% human
- Kislay's Newsletter #24: Semantic web, Kubernetes, Agile, and anti-network effects
- Kislay's Newsletter #23 - On bypassing central systems (aka when good abstraction is bad)
- New Post by Kisla Verma
- New post by Kislay Verma
- Kislay's Newsletter #9
- Kislay's Newsletter #21
- Kislay's Newsletter #20
- Kislay's Newsletter #7
- Kislay's Newsletter #19
- Kislay's Newsletter #18
- Kislay's Newsletter #17
- Kislay's Newsletter #16
- Kislay s newsletter 15
- Kislay s newsletter 10
- Kislay s newsletter 14
- Kislay s newsletter 13
- Kislay s newsletter 12
- Kislay s newsletter 11
- New post by kislay verma 6
- Kislay s newsletter 6
- Kislay s newsletter 5
- Kislay s newsletter 4
- New post by kislay verma 5
- Kislay s newsletter 3
- New post by kislay verma 4
- New post by kislay verma 3 2
- Kislay s newsletter 2
- New post by kislay verma
- New post by kislay verma 3
- Kislay s newsletter 1
- Kislay s newsletter 1 2
- New post by kislay verma 2
- New post by kislay verma 2 2