Choreography Design Pattern | Distributed Transaction Management| MicroService Design Patterns

[@aryakdeshpande2952]

Was waiting for you to start a series on Design patterns since a long time, & here it is...thanks a lot sir!

[@rakeshyedlappalli2088]

Your explanation was really helpful. I had been going through several blogs trying to grasp this design pattern, but I finally got a clear understanding from your explanation. I sincerely appreciate your help.

[@ashok55-v1h]

In very short period of time you explained each and every concept very well thanks a lot sir.

[@SumiKushwaha-yk9rh]

excellent explanation in easy way

[@themiltonator]

Very nice video my friend! very cleear explanation of a difficult design concept/strategy. I have seen systems that follow the orchestration design but they also have an event broker like the one we saw in this video. Great content, can't wait to see more! Subscribed!

[@01cybrain]

, Great explanation 😊

[@balajik8561]

Thank you Its great explanation

[@pulkitrathore2447]

excellent explanation sir.

[@hossemhrichi6570]

Thanks great explanation

[@jovangrgur3266]

Great explanation of Saga pattern

[@RicardoSilvaTripcall]

Great Explanation !!

[@PrashantZombade]

Very nice video, thanks! Quick question, how do you choose between Orchestration and Choreography? Are there any standard criterias that we should consider while choosing one over another?

[@vaibhavgarg4267]

amazing explanation

[@saranthoughts9826]

great explanations

[@pranavmahajan4190]

Thanks for this video.

[@bibekdas3592]

Sir, Do you have a java project on these explanations. As these events are dynamically generated how a service will subscribe to it.

[@dsdivya]

in the failed event, again event will be published to same topic or different topic, can you pls clarify.

[@SagguUK]

It totally depends on your business logic. You can publish on the same topic or different one.

[@caffeinejavacode1475]

How to subscribe to particular Event (NEW_ORDER f.e). How Kafka listener should be trigeret by NEW_ORDER and not UPDATE_ORDER