← всС Π²ΠΈΠ΄Π΅ΠΎ

How Saga Pattern Solves Distributed Transactions in Microservices

Visualcoders Β· 2026-06-21 Β· 12ΠΌ 21с Β· 92 просмотров Β· YouTube β†—

Π’ΠΎΠΏΠΈΠΊΠΈ: durable-execution

Аудио Π΅Ρ‰Ρ‘ Π½Π΅ скачано.

πŸ“ Summary

Summary Π΅Ρ‰Ρ‘ Π½Π΅ сгСнСрён.

πŸ“œ Transcript

Transcript Π΅Ρ‰Ρ‘ Π½Π΅ сдСлан.

βš™οΈ Pipeline jobs

НСт job'ΠΎΠ² Π² ΠΎΡ‡Π΅Ρ€Π΅Π΄ΠΈ.

πŸ“„ ОписаниС YouTube

ΠŸΠΎΠΊΠ°Π·Π°Ρ‚ΡŒ
On Black Friday, inventory vanished. Revenue flatlined. 
The order existed. The stock was locked. But the payment had failed.

And here's the worst part β€” you can't just type ROLLBACK. 
The moment that transaction crossed a service boundary, your rollback button stopped existing.

That is the Distributed Transaction Problem. And the Saga Pattern is the fix.

In this video I break down exactly how Saga works β€” from the monolith's ACID guarantee 
all the way to Choreography vs Orchestration, with fully animated diagrams and real 
system design walkthroughs.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
πŸ• TIMESTAMPS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
0:00  The Black Friday incident
1:45  How the monolith solved this (ACID transactions)
3:15  Database-Per-Service β€” why we broke the safety net
4:20  The Distributed Transaction Problem (step by step)
6:10  What is the Saga Pattern?
7:10  Compensating Transactions β€” not rollback, compensation
9:10  Saga Approach 1: Choreography (the wedding dance)
11:00 Saga Approach 2: Orchestration (the conductor)
12:50 Choreography vs Orchestration β€” which one should you pick?
13:10 The new problem Saga quietly creates (and what's next)

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
πŸ“Œ WHAT YOU'LL LEARN
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
βœ… Why distributed transactions are impossible in microservices
βœ… What a compensating transaction is (and how it differs from rollback)
βœ… How Choreography coordinates services without a central boss
βœ… How Orchestration uses one brain to control the entire flow
βœ… When to use each β€” and why large orgs reach for Orchestration

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
πŸ”— SERIES β€” System Design Patterns
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
β–Ά Next: API Composition Pattern (coming soon)
β–Ά Database-Per-Service Pattern
β–Ά Event-Driven Architecture

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

If this finally made Saga click for you β€” subscribe and hit the bell πŸ”” 
so you don't miss the API Composition Pattern next.

Connect with  us on: 

Instagram: https://www.instagram.com/visualcoders
website: https://visualcoders.in/
facebook: https://www.facebook.com/people/Visualcoders/61587693743021


Playlists:

Microservices Design Patterns: https://www.youtube.com/playlist?list=PL2MKEvl7Sd7mPNjJ-JFu04kt-e1SRB93w

Tree Data Structure: https://www.youtube.com/playlist?list=PL2MKEvl7Sd7nEG9CZ6Q4uxz8NO6K0Q3aN

Linked List: https://www.youtube.com/playlist?list=PL2MKEvl7Sd7kiZnlk1cxRuzRluekdntFy

Time Complexities: https://www.youtube.com/playlist?list=PL2MKEvl7Sd7leuFfXExK3V8vdy37LutSJ


#sagapattern #systemdesign #microservices #softwaredevelopment #designpatterns