Choreography Design Pattern | Distributed Transaction Management| MicroService Design Patterns

แชร์
ฝัง
  • เผยแพร่เมื่อ 23 ม.ค. 2025

ความคิดเห็น • 22

  • @NoxThreads
    @NoxThreads 26 วันที่ผ่านมา +1

    Sir, you’re amazing! Watching your videos helped me pass my semester successfully 😭

    • @SagguUK
      @SagguUK  25 วันที่ผ่านมา

      Glad to hear. Best wishes.

  • @aryakdeshpande2952
    @aryakdeshpande2952 2 ปีที่แล้ว +2

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

  • @rakeshyedlappalli2088
    @rakeshyedlappalli2088 ปีที่แล้ว +1

    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
    @ashok55-v1h 7 หลายเดือนก่อน +1

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

  • @themiltonator
    @themiltonator ปีที่แล้ว +1

    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
    @01cybrain ปีที่แล้ว +1

    ,
    Great explanation
    😊

  • @SumiKushwaha-yk9rh
    @SumiKushwaha-yk9rh 11 หลายเดือนก่อน +1

    excellent explanation in easy way

  • @balajik8561
    @balajik8561 11 หลายเดือนก่อน +1

    Thank you Its great explanation

  • @pulkitrathore2447
    @pulkitrathore2447 ปีที่แล้ว +1

    excellent explanation sir.

  • @RicardoSilvaTripcall
    @RicardoSilvaTripcall 2 ปีที่แล้ว +1

    Great Explanation !!

  • @jovangrgur3266
    @jovangrgur3266 9 หลายเดือนก่อน +1

    Great explanation of Saga pattern

  • @hossemhrichi6570
    @hossemhrichi6570 ปีที่แล้ว +1

    Thanks great explanation

  • @vaibhavgarg4267
    @vaibhavgarg4267 9 หลายเดือนก่อน +1

    amazing explanation

  • @saranthoughts9826
    @saranthoughts9826 10 หลายเดือนก่อน +1

    great explanations

  • @PrashantZombade
    @PrashantZombade 2 ปีที่แล้ว

    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?

  • @pranavmahajan4190
    @pranavmahajan4190 ปีที่แล้ว

    Thanks for this video.

  • @bibekdas3592
    @bibekdas3592 2 ปีที่แล้ว

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

  • @dsdivya
    @dsdivya 7 หลายเดือนก่อน

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

    • @SagguUK
      @SagguUK  5 หลายเดือนก่อน +1

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

  • @prashantranjan4859
    @prashantranjan4859 5 วันที่ผ่านมา

    thanks

  • @caffeinejavacode1475
    @caffeinejavacode1475 ปีที่แล้ว

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