Microservices Topic

Microservices

Microservices are an organizational pattern with a technical cost. These posts are about when the cost is worth paying, when a well-structured monolith is the smarter choice, and how distributed transactions actually fail in practice.

Backend

Posted on May 15, 2026

Sagas Are Not Transactions

Sagas replace ACID transactions with compensation actions, not rollbacks. Intermediate states are visible to other services, and compensations can fail too.

Distributed Transactions Are a Lie

Why two-phase commit fails in production distributed systems, and what engineers actually use instead: sagas, the outbox pattern, and eventual consistency.

The Monolith That Works Fine, Thanks

Monoliths aren't a sign of technical immaturity. Most teams don't need microservices. Here's why a well-structured monolith is often the smarter choice.