If you've ever worked with distributed databases, you've probably heard the phrase "CAP theorem: Pick two." It's one of those principles that sounds simple but drives the design of almost every distributed system we use today. In this post, I'll break down what it really means, how different database systems fit into it, and why configuration choices can sometimes push a system from one category t... [read more]

To build a building, you first need to know at least what kind of construction it will be. (skyscraper? datacenter? or someone's summer house?) Then, with the architecture and construction calculations, you begin with the foundation and structure. You can't start the project from the penthouse! And you can't add "Burj Khalifa's feature" on top of someone's summerhouse! 😉 Surprise surprise: The sa... [read more]

Are you Google or anything close to the size of FAANG/MAMAA?Do you have 10+ tech teams in your company?Do you have multiple products?Do you have a bottleneck in your system?Do you need multiple types of databases to handle different behaviors/purposes? If your answer to all (or most of) these questions is yes, then Microservice architecture might help you split your solution into simpler blocks so... [read more]

Note: All the names and events in this story are fictional, and any resemblance to real people or events is purely coincidental. The story is completely made-up but is inspired by a mix of a few common patterns I have either seen myself or heard from others in the past few years. The purpose of this story is to share a common trending scenario and a few mistakes that can cause IT-based startups to... [read more]