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.

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:

Do you know that too? You are working on Project A, which is still running on Java 11 LTS, while at the same time you are developing a new feature for Project B, which is already based on the current Java 21. And then there is this legacy system that, for some unknown reason, requires Java 8.