Microservice architecture honestly — when to split, when to merge, gRPC vs REST trade-offs, service boundaries that respect data ownership, and the patterns that prevent a distributed monolith.
3 articles · updated regularly
You split the monolith into ten services and somehow got slower, more fragile, and harder to deploy. That's a distributed monolith — the worst of both worlds. Here's how to spot and avoid it.
The hardest design question in microservices isn't 'how do they talk?'. It's 'what is the right thing to be its own service?'
Both are fine choices. Picking wrong costs you debugging, observability, and a year of regret.