Distributed Transactions & Saga¶
π Resources¶
- Sairyss/distributed-systems-topics - Topics and resources related to distributed systems, system design, microservices, scalability and performance, etc
π Articles¶
- Life Beyond Distributed Transactions: An Apostate’s Implementation - A Primer
- Itβs Time to Move on from Two Phase Commit
- Saga Pattern for Microservices Distributed Transactions
- Microservices Distributed Transactions
- A MICROSERVICES SAGA CHOREOGRAPHY EXAMPLE
- MICROSERVICES SAGA PATTERN
- Event-driven distributed processes by example
- Saga and Process Manager - distributed processes in practice
- How to deal with back-pressure on message queues with .NET Core
- Using Channels In C# .NET β Part 3 β Understanding Back Pressure
- Four Strategies to Handle Backpressure - Jay Phelps at ReactiveConf 2019
- Coordination in the distributed systems
- Choreography
- Orchestration
- Saga and Process Manager - distributed processes in practice
- Saga patterns: wrap up - Jimmy Bogard
- Handling Complexity: Using Sagas to Provide Transactional Support for Distributed Systems β
- Implementation of Choreography-based Saga in .NET Microservices
- Sagas: When a Distributed Transaction Is The Right Thing For You
- How to handle multiple commands in the same transaction
- Combining the To-Do List and the Passage Of Time patterns for resilient business workflows
- Low Ceremony Sagas with Wolverine
- Saga Orchestration for Microservices Using the Outbox Pattern β
πΊ Videos¶
- Life Beyond Distributed Transactions: An Apostate’s Implementation - Jimmy Bogard
- Fixing Distributed Systems Fail with Jimmy Bogard
- Saga pattern within Masstransit
- Distributed Sagas: A Protocol for Coordinating Microservices - Caitie McCaffrey
- Solving distributed data problems in a microservice architecture | Microservices.io
- Backpressure in Reactive System
- Avoiding Distributed Transactions with the Reservation Pattern
- At Least Once - Ian Cooper - NDC Oslo 2022
Library¶
- event-driven-dotnet/EventDriven.Sagas - Abstractions and reference architecture for atomic operations that span multiple services.