The post explores the use of the Saga pattern in Elixir to manage complex, multi-step transactions that must either fully complete or be entirely rolled back. It details the problem of ensuring atomicity in transactions separated by time or space, and introduces two approaches to implementing the Saga patternβ€”choreography-based

β€’11m read timeβ€’From peterullrich.com
Post cover image
Table of contents
Hey! I recorded two video courses!πŸ”— The ProblemπŸ”— The SolutionπŸ”— Choreography-basedπŸ”— Orchestration-basedπŸ”— Short-lived TransactionsπŸ”— Sage libraryπŸ”— Synchronous vs Asynchronous Communication in SagasπŸ”— Conclusion

Sort: