Tag Distributed Data

When Kafka Became a Second Database

We originally introduced Kafka for a simple reason. We needed asynchronous communication. A service would publish an event. Another service would consume it. The producer didn’t need to wait. The consumer could process the event independently. It looked straightforward. Kafka…

When Every Service Wanted Its Own Database

One of the first principles we adopted after decomposing the system was simple: Every service should own its own data. It sounded right. The architecture became cleaner. Teams could deploy independently. Services no longer needed direct access to another service’s…