Imagine our SAGA Orchestrator (Saga Pattern Part 3) running at full speed. Customers are ordering like crazy. Suddenly the Inventory Service becomes slow. Maybe it’s due to a database lock or poor deployment.

1. Get out of the event chaos

Welcome to Part 3 of our series on the SAGA Pattern. In Part 2 we implemented a choreography-based saga. The services communicated loosely coupled via events, which appeared elegant and decentralized.

Part 2 – The Architecture: Services and Event Brokers

Welcome to Part 2 of our series on the SAGA Pattern! In Part 1 we clarified the theoretical basis of why we need sagas in microservice architectures and learned the difference between choreography and orchestration.