Search

Lessons (9)

• Data in Microservices: Sagas & the Outbox Pattern

  … So microservices accept eventual consistency and use sagas. The saga pattern A saga is a series of local …

• Time, Consistency and Distributed Transactions

  … clocks order observations, fencing protects ownership, and sagas compensate cross-service work](/img/system-design-l6/time-transactions …

• Which Pattern Do I Need?

  … corruption layer Command Message queues, CQRS commands Mediator Saga orchestrator Chain of Responsibility Middleware pipelines, API gateway filters …

• Monolith vs Microservices

  … unreliable network calls Transactions ✅ One ACID database transaction ❌ Sagas, eventual consistency Testing end to end ✅ Easy ❌ Hard Ops …

• Kafka Producers

  … to a database and Kafka together (see Microservices → Sagas & Outbox ) Key takeaways - Producers serialise, partition (by key), batch …

• Event-Driven Architecture

  … and Microservices topics cover delivery guarantees, the outbox, sagas and CQRS in depth.) EDA inside a single application …

• Database Indexing & Transactions

  … for that, see Sagas & the Outbox Pattern in the Microservices lessons. Key takeaways - Indexes turn O(n) scans …

• Vertical Slice Architecture & the Modular Monolith

  … can fail) Transactions ✅ Easy ✅ Easy within a module ❌ Sagas Operational complexity ✅ Low ✅ Low ❌ High Independent deploy and scale …

• Behavioral Patterns II: Chain, Template, Iterator, Mediator, Memento, Visitor

  … an API gateway, an orchestrator in a microservice saga. --- 5. Memento 💾 Analogy: Save points in a video game …