Saga Pattern
The Saga Pattern is a way of managing data consistency across multiple services in a distributed transaction by breaking it into a sequence of local transactions, each with a corresponding compensating action to undo it if a later step fails.
15 resources across 2 libraries
Glossary Terms(5)
Microservices
Microservices is an architectural style that structures an application as a collection of small, independently deployable services, each owning a single busine…
Event-Driven Architecture
Event-driven architecture (EDA) is a software design pattern in which components communicate by producing and consuming events — notifications that something h…
CQRS
CQRS (Command Query Responsibility Segregation) is an architectural pattern that separates the operations that change data (commands) from the operations that…
Saga Pattern
The Saga Pattern is a way of managing data consistency across multiple services in a distributed transaction by breaking it into a sequence of local transactio…
Circuit Breaker Pattern
The Circuit Breaker Pattern is a resilience design pattern that stops an application from repeatedly calling a service that is likely to fail, allowing it to r…
Interview Questions(10)
What is the Saga Pattern in Microservices?
The Saga pattern manages a business transaction that spans multiple microservices by breaking it into a sequence of local transactions, where each step publish…
What is the Database-per-Service Pattern in Microservices?
The database-per-service pattern means each microservice owns its own private database that no other service is allowed to access directly, so services communi…
How Would You Design a Payment System?
A payment system is designed around an idempotent, append-only ledger where every state transition (authorize, capture, settle, refund) is recorded as an immut…
How to Design an Airline Reservation System?
An airline reservation system is designed around a strongly consistent seat-inventory service that uses optimistic locking or short-lived holds to prevent doub…
What is Two-Phase Commit (2PC)?
Two-phase commit (2PC) is a distributed transaction protocol where a coordinator asks every participant to vote on whether it can commit a transaction (the pre…
What is the Saga Pattern?
The saga pattern breaks a distributed transaction into a sequence of local transactions, each owned by a different service, where every step has a correspondin…
What are Distributed Transactions and How Do They Work?
A distributed transaction is a set of operations spanning multiple independent services or databases that must all succeed or all fail together, typically coor…
What is the Database-per-Service Pattern?
The database-per-service pattern means each microservice owns and exclusively accesses its own private database, so no other service can read or write its data…
Orchestration vs Choreography in Microservices: What is the Difference?
Orchestration coordinates a multi-service workflow through a central controller that explicitly tells each service what to do and in what order, while choreogr…
What Is the Saga Pattern in Distributed Transactions?
The saga pattern manages a business transaction that spans multiple services by breaking it into a sequence of local transactions, each with a corresponding co…