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.

Hello everyone,

In modern, microservices-oriented architectures, we want to keep components as independent as possible. When service A performs an action (e.g. registers a user), service B should respond to it (e.g. send a welcome email) without A needing to know from B directly.

Hello everyone,

As developers, we know that writing an application is only half the battle. The other half is packaging, rolling out and operating them reliably. This is where the microservice stack with Spring Boot, Docker and Kubernetes comes into play.