Chapter 4. Managing transactions with sagas

This chapter covers

  • Why distributed transactions aren’t a good fit for modern applications
  • Using the Saga pattern to maintain data consistency in a microservice architecture
  • Coordinating sagas using choreography and orchestration
  • Using countermeasures to deal with the lack of isolation

When Mary started investigating the microservice architecture, one of her biggest concerns was how to implement transactions that span multiple services. Transactions are an essential ingredient of every enterprise application. Without transactions it would be impossible to maintain data consistency.

ACID (Atomicity, Consistency, Isolation, Durability) transactions greatly simplify the job of the developer by providing ...

Get Microservices Patterns now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.