The Saga Pattern in Microservices (EDA - part 2)

Learn about the Saga Pattern in Microservices in order to do distributed transactions, comparing Orchestration vs Choreography. In this video, the second in the series of Event Driven Architecture, I explain the complexity of doing transactions in distributed systems, specifically in Microservices. Throughout the video I explain how we move from a single system (monolith) to a distributed architecture using Microservices, how to deal with transaction, explain the Saga Pattern with its two variants: Orchestration and Choreography and how they are closely related with Event Driven Architecture (EDA). For more information on Event Driven Architecture, watch the series: #Microservices #SagaPattern ----------------------- 📘 Recommended books (incentivized): - Microservices Patterns: - Building Microservices: 🔖 Relevant resources: - The many meanings of Event Driven Architecture: - Microservices: - Saga Pattern: -- Orchestration vs Choreography () -- Pros and Cons: 🤓 If you are preparing for a technical interview, don’t miss my playlist: 📚 I have also prepared FREE study guides available here (no subscription needed): ----------------------- Remember you can reach me here: #️⃣ Twitter: ⌨️ Github: ----------------------- In A Dev’ Story I explain Software Development related topics from my point of view. I’ll be explaining different topics in “Chapters“ according to the stage of the story I think they belong. Hope is as entertaining for you as it’s fun for me to create these videos Thanks again for watching! Feel free to like, comment, share and subscribe, it means a lot to me and helps the channel grow.