What is SAGA Design Pattern in Microservices Architecture and how to handle distributed transactions

Dear Friends,

This video will help you to understand basics of Distributed transaction handling using SAGA Design Pattern in Microservices Architecture. This tutorial is in Hindi.

#saga
#sagapattern
#microservices
#distributedtransaction
#transaction
#event
#choreography
#orchestrator
#stock
#reallifeexample
#hindi
#hinditutorial

You can connect with me via
Whatsapp - [phone]

Thanks
Amit Goyal

[sushilroy]

च च चा लाजवाब और बहुत ही सरल तरीक़े से समझाया आपने 🙏👨🏻‍💻 | ये टॉपिक हर माइक्रोसर्विसेज़ के इंटर्व्यू में पूछा ही जाता है

[gokulaher]

The MySQL, PostgresSQL, MariaDB and ORacle XE are all freely available and we can do that coding in our personal machines hence suggested these 4 databases for 4 microservices
Thanks for such useful videos with explanation in a very simple and easy to understand way.

[ratunawartejas]

Sahi explain kiya.. mast laga sunne ko

[jaihindjaibharat]

Amit ji bahut badiya samzhaya hain apne.. pls iska practical video bhi bana dijiye.😊😊

[lal_]

thanks, for explaining the concept in such a simple way. :)

[ashok-vh]

thank you and all the very best sir...

[sanjayg]

Woa Amit, you made so simple to understand this SAGA patterns with 2 examples, thank you so much.. as i was waiting for this kind of video, great jobs sir.

[Mantukumar-ivgb]

Very important questions and Amit bhaiya you explained very nice.

Can you please explain orchestration choreography design patterns.

[movieclimax]

Please make videos on how will mange transaction if some failure happened on certain point, how can we perform rollback in distributed transaction in event base and other approaches

[shivamgupta]

Suggestion, Make videos on optimizing db performance using micro services design pattern

[kailashkarki]

Nice, but the important this is to explain how to handle the failure in SAGA. Plz make videos on that.

[gokulaher]

Requesting you to pl. create a video on Distributed Transaction in Microservices using different databases.
For example there are 4 microservices say MS-1, MS-2, MS-3, MS-4 and each one is having there own database.
like MS-1 will be storing data in MySQL, MS-2 will be storing data in PostgresSQL, MS-3 will be storing data in MariaDB and MS-4 will be storing data in Oracle(11g or XE)
By using 2PC and or SAGA design pattern. (Handling different scenarios for commit and rollback)

[videolounge]

where is the second part of it? can you please share the link here?

[truthreveal]

Main importance बटाया ही नहीं sir But how the rolls back happens if order is failed then how payment will be refund

[AdarshMaverick]

Bhai pls made quick hands-on videos on MS. Practical knowledge sharing gives perfect knowledge and garners more views

[atuldhariwal]

Saga can be implemented by simple rest api call only?

[vinaypandey]

Well explained. Even a Layman or nonexpert can get a clear picture of it's execution... Thanks...

[rahimkhan-fhdd]

Hi sir,
Is Saga choreography or CQRS design pattern are same ?

[rahul]

Amit sir when will the videos on confluence and git will be uploaded.

[gokulaher]

I have Few Question
Q1) How to incorporate "old endpoints" with "new endpoints" without affecting the existing functionality of the microservices using spring boot? in other words when you are doing code refactoring or enhancing the existing feature or functionality?How to incorporate "old endpoints" with "new endpoints"?

Q2) Another interview question that I faced was in microservices using spring boot how will you initialize microservice instance without using "application.properties" file

Q3) How will you create multiple instance of a microservice having very heavy workload
(I said creating new instances of that microservice by changing the port number) then he asked How will you do it in real life scenario how will you create multiple instances of the microservice for load balancing of millions of hits in an hour or so ?