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 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)

System Design Interview Basics Playlist:

AWS Certification:

#sagas #2pc #distributed

[VictorAug]

Best Saga explanation I've ever seen.

[krzysztof]

An underrated channel. Keep going and it's definitely gonna be a popular channel

[sfsadfsadfasdf]

You deserve more views.. this is gold..

[nuthankamera]

Very interesting and informative video. Please keep sharing such videos where a non technical people can understand it.

[ronaksiddhpura]

Explanation is giving real time project experience and very interesting and informative video.

[sathishd]

Explanation is giving real time project experience. Thanks a lot

[pedromiotti]

How have I never seen a video from this channel? Amazing content my friend. Subscribed.

[ujjwalaggarwal]

great video, always love your animations and explanations

[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?

[java-aws-techie]

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

[yravi]

@ByteMonk How do you edit/create content ?

[Ar-rpjo]

Hi, I have a doubt in SAGA. Consider service1 and service2. When service1 passes, service2 will be initiated. When the service2 is failed, and if the service1's value is changed in the meantime, what will happen? Will it lead to data inconsistency? Correct me if I am wrong.

[liangtianzhang]

how is an orchestrated saga async if it makes serial requests and requests depend on each other? Isn't it the same as a central coordinator ?

[pravee]

Still in Orchestrator SAGA there is single point of failure if orchestrator goes down rite?

[zummotv]

can we have multiple instances of a Saga orchestrator to ensure high availability, scalability, and fault tolerance, by ensuring that only one orchestrator instance handles a particular Saga at any given time.

[pradeepbisht]

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

[metaltoad]

i can do but actually i dink din din din