SAGA 2 | Compensating Transaction Pattern | Zomato System Design Primer

Sdílet
Vložit
  • čas přidán 27. 07. 2024
  • This video covers compensating transaction pattern in microservices using Zomato System design as an example for explaining failure handing in SAGAs.
    📌 Chapter Timestamps
    ===================
    00:00 - Introduction
    00:20 - Agenda
    01:17 - Zomato System Design - Distributed Microservices Architecture
    06:53 - Why do we need to compensate a transaction?
    10:13 - Self Compensating Transaction
    📌 Related Links
    =============
    🔗 SAGA Part 1 • SAGA | Microservices A...
    📌 Related Playlist
    ================
    🔗Spring Boot Primer - • Spring Boot Primer
    🔗Spring Cloud Primer - • Spring Cloud Primer
    🔗Spring Microservices Primer - • Spring Microservices P...
    🔗Spring JPA Primer - • Spring JPA Primer
    🔗Java 8 Streams - • Java 8 Streams
    🔗Spring Security Primer - • Spring Security Primer
    💪 Join TechPrimers Slack Community: bit.ly/JoinTechPrimers
    📟 Telegram: t.me/TechPrimers
    🧮 TechPrimer HindSight (Blog): / techprimers
    ☁️ Website: techprimers.com
    💪 Slack Community: techprimers.slack.com
    🐦 Twitter: / techprimers
    📱 Facebook: TechPrimers
    💻 GitHub: github.com/TechPrimers or techprimers.github.io/
    🎬 Video Editing: FCP
    ---------------------------------------------------------------
    🔥 Disclaimer/Policy:
    The content/views/opinions posted here are solely mine and the code samples created by me are open sourced.
    You are free to use the code samples in Github after forking and you can modify it for your own use.
    All the videos posted here are copyrighted. You cannot re-distribute videos on this channel in other channels or platforms.
    #SAGA #SystemDesignPrimer #TechPrimers
  • Jak na to + styl

Komentáře • 23

  • @ganpatinatrajan5890
    @ganpatinatrajan5890 Před rokem +1

    Very Well Explained...

  • @benneighbour7339
    @benneighbour7339 Před 3 lety +6

    The systems design is all well and good. But actually implementing it in an enterprise microservices architecture without using serverless and it being a mess; is a different thing.... Nice video!

    • @TechPrimers
      @TechPrimers  Před 3 lety +2

      Yesh Ben. Cannot agree more. Thats another reason why many companies does not use SAGAs for majority of their usecase. I'm going to create a hands-on series. Before that lots of people wanted to know how to handle exception scenarios in SAGAs, so created this one. Thanks for the feedback.

  • @trinathtalluri
    @trinathtalluri Před 3 lety +1

    Excellent 👍

  • @saratchandra4689
    @saratchandra4689 Před 3 lety +2

    Really helpful, great explanation, thanks for the video.. 👍

  • @sbshshendkar
    @sbshshendkar Před 3 lety +2

    Good content ajay... ❤️❤️❤️

  • @JameS00989
    @JameS00989 Před 3 lety +1

    Cool very useful Ajay

  • @asjjain191183
    @asjjain191183 Před 3 lety +3

    It's very basic explanation of saga pattern. Concept is very easy but when you are going to implement its very hard. Specifically which one to choose choreography or orchestration?? could you please make another video about how saga pattetn implement in the particular application.

    • @Jsr10008
      @Jsr10008 Před 3 lety +2

      Hi Ashish
      I have done a basic implementation of saga pattern. It might be helpful for you.
      github shobhit-bhardwaj saga-pattern

    • @TechPrimers
      @TechPrimers  Před 3 lety

      Yesh Ashish. Thats next. I'm going to create a series. Before that lots of people wanted to know how to handle exception scenarios in SAGAs, so created this one. Thanks for the feedback.

  • @weitanglau162
    @weitanglau162 Před 3 lety +3

    Would appreciate an implementation. This is because the concepts are known, but the implementation that is difficult

    • @asjjain191183
      @asjjain191183 Před 3 lety

      Totally agree, concept is very easy but when you are going to implement its very hard. Specifically which one to choose choreography or orchestration??

    • @TechPrimers
      @TechPrimers  Před 3 lety +1

      Yesh Lau. Thats next. I'm going to create a series. Before that lots of people wanted to know how to handle exception scenarios in SAGAs, so created this one. Thanks for the feedback.

    • @weitanglau162
      @weitanglau162 Před 3 lety

      @@TechPrimers that's great news! Can't wait for the video :)

    • @Videoorchard
      @Videoorchard Před 2 lety

      Please create a implementation in spring boot

  • @Priyam_Gupta
    @Priyam_Gupta Před 3 lety +1

    I believe the Order service will only generate an order id and respond back to the app and now its app responsibility to call the payment service separately, on which the app page gets redirected through the payment gateway and the order is marked as payed after payment service again calls the order service with the order id and transaction id.

  • @chandanbhosle
    @chandanbhosle Před 3 lety +1

    Ajay, can you make a video on feature flags and canary deployments

  • @Gaurav-op7ez
    @Gaurav-op7ez Před 3 lety +1

    Hi, i don't think cart service's database will be populated the minute we add something to the cart, i think it will stored locally in phone. To confirm this assumption i added something on my cart on website and then opened my app, the cart contents were not updated in the app.
    I don't think based on login we can assume this because i also uninstalled the app, if it was stored in cart DB i would seen my items after installing again, which wasn't the case. Did i miss something?

    • @TechPrimers
      @TechPrimers  Před 3 lety

      I have done the same with Amazon. However the items stayed in web though i added in Mobile.
      I guess everyone has their own implementation. So it's fair to say it's up to the product feature team to decide😉

    • @mmgtechm
      @mmgtechm Před 2 lety

      @@TechPrimers agree, major players do the same like Zealand on, Walmart, adidas does preserve the dat across app or web.