Microservices trade a hard problem you understand — a tangled monolith — for a set of hard problems you might not: network failure, partial outages, distributed data, and operational sprawl. This is a field guide to the patterns that make the trade survivable: how services should talk, how to stop failures cascading, how to manage data without distributed transactions, and the honest case for not splitting at all.
Saga-Pattern
-
Microservices Patterns That Work