Saga Pattern | Distributed Transactions | Microservices

Sagas are an essential concept in microservices and distributed systems design, and they often come up in system design interviews. In microservice architectures, transactions often span multiple services. Sagas provide a way to manage these long-running transactions, ensuring that either all operations are executed successfully or the entire transaction is rolled back. Understanding Sagas demonstrate your ability to understand and design complex distributed systems. In this video we will discuss
1. Distributed Transactions
2. Two Phase Commit
3. Orchestration
4. Choreography
LinkedIn: / bytemonk
System Design Interview Basics Playlist:
► • System Design Intervie...
AWS Certification:
►AWS Certified Cloud Practioner: • How to Pass AWS Certif...
►AWS Certified Solution Architect Associate: • How to Pass AWS Certif...
►AWS Certified Solution Architect Professional: • How to Pass AWS Certif...

[@KrishDholeria]

as you said we can use zookeeper to implement 2 phase commit. Similarly, is there any framework which can be used to implement orchestrated saga?

[@Zmey5656]

Very simple about Saga, thanks

[@ujjwalaggarwal7065]

great video, always love your animations and explanations

[@java-aws-techie]

Great video. Might help if you could also discuss about some tools or frameworks to implement saga.

[@vivek.tiwary]

You can use Azure durable function to implement an orchestrator saga. For choreography, you can use Azure Sb.

[@java-aws-techie]

So Aws step functions as orchestrator and SQS for choreography. Clear. Thanks.

[@ByteMonk]

Thank you for suggestions and replies, will cover them up in my upcoming videos. I try to keep my videos under 10 mins, but this one turned out to become too long because of the context I had to provide in the beginning.

[@pradeepbisht3397]

Nice video ! can you share article you talking about in video?

[@ByteMonk]

Thank you. This is from my experience, I did not made it into an article, but will consider in future.