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 provides 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 demonstrates 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
FOLLOW ME ON:
▶️ Main Channel: /bytemonk
Timestamps -
00:00 - Introduction
00:34 - Distributed Transactions Part 1
01:38 - Two-Phase Commit (2PC)
05:08 - Distributed Transactions Part 2
05:52 - Sagas
07:41 - Orchestrated Saga
08:55 - Choreographed Saga
09:20 - Orchestrated Saga vs. Choreographed Saga
10:25 - High-Level System Design
13:10 - Sagas vs. Two-Phase Commit (2PC)
15:20 - Orchestrated Saga vs. Two-Phase Commit (2PC)
LinkedIn: https://www.linkedin.com/in/bytemonk/
System Design Interview Basics Playlist:
►https://www.youtube.com/playlist?list=PLJq-63ZRPdBt423WbyAD1YZO0Ljo1pzvY
AWS Certification:
►AWS Certified Cloud Practioner: https://youtu.be/wF1pldkQrOY
►AWS Certified Solution Architect Associate: https://youtu.be/GzomXNLFgkk
►AWS Certified Solution Architect Professional: https://youtu.be/KFZrBxSA9tI
#sagas #2pc #distributed