Backend
![[EN] SAGA in practice (Part 3): State management and compensation via orchestrator](/images/SAGA-Pattern-Teil3-BlogHeader.png)
[EN] SAGA in practice …
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.
![[EN] SAGA Pattern in Practice: Choreography with Spring Boot & RabbitMQ (Part 2)](/images/SAGA-Choreographie-BlogHeader.png)
[EN] SAGA Pattern in …
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.
![[EN] SAGA Pattern for Beginners: Consistency in Microservice Architectures Explained Part 1](/images/SAGA-Pattern-Part1-BlogHeader.png)
[EN] SAGA Pattern for …
Introduction – The Dilemma of Distributed Transactions
Imagine you are developing a classic e-commerce application. A customer clicks “Buy” and a process is initiated in the background that consists of several steps: