
Sagas, Eventual Consistency, and Eventuate

#53 - Principles for Adopting Microservices Successfully - Chris Richardson
Topic 8 of 10
Published Aug 30, 2021 · Clip 33:24–43:54 (10:30)
Chris explains the Saga pattern using the customers-and-orders credit limit example: the order service creates a pending order, asks the customer service to reserve credit, and approves or rejects the order based on the response. He then describes Eventuate, his framework/platform implementing the Saga and foundational patterns like transactional outbox (atomically updating a database and publishing a message via the transaction log) and idempotent consumer. He covers compensating transactions and the lack of isolation in sagas, which causes anomalies like dirty reads, addressed by countermeasures such as semantic locks (e.g., the pending order state).