System Design
[EN] Why you (probably) …
The fallacy of “scalability from day 1”
Imagine you are starting a new project. The team is motivated, the whiteboard has been wiped clean, and the first question in the room is: “Which microservices do we need?”
[EN] Microservices …
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.
[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] Why you (probably) don't need microservices: A case for the modular monolith](/images/ModularerMonolith-BlogHeader.jpeg)
![[EN] Microservices Resilience: The Circuit Breaker Pattern with Spring Boot & Resilience4j](/images/Curcuit-Breaker-Pattern-BlogHeader.jpeg)
![[EN] SAGA in practice (Part 3): State management and compensation via orchestrator](/images/SAGA-Pattern-Teil3-BlogHeader.png)