How Event-Driven Architecture based applications works ? (Demo)

Поділитися
Вставка
  • Опубліковано 12 гру 2024

КОМЕНТАРІ • 9

  • @hjhgjghjjh
    @hjhgjghjjh 3 роки тому +1

    Informative, Thanks Karthik 👍

  • @muthukumarkamatchi1895
    @muthukumarkamatchi1895 2 роки тому +1

    It’s really amazing and interested on your teaching. Kindly Is it possible to get the code for best understanding the event driven and it’s helpful for understanding.

  • @s1h2r345
    @s1h2r345 2 роки тому +1

    Hi Karthik, its a really informative. Can you share details related to the Testing of Event-Driven Architecture, Tools Stack, Strategy, etc..

  • @ignaciogonzalez2619
    @ignaciogonzalez2619 2 роки тому

    Amazing Video, BTW does anyone know the tool to build the graphs I Can see is from azure but do not know the name ?

  • @m3kbeatz
    @m3kbeatz Рік тому

    Can u explain who is updating database? How many db are in this example?

    • @ExecuteAutomation
      @ExecuteAutomation  Рік тому

      It’s almost all the services to store on their domain level
      I have a complete course explain these details www.udemy.com/course/testing-eda-microservices/

    • @m3kbeatz
      @m3kbeatz Рік тому

      @@ExecuteAutomation do u explain in that course what kind of challenges we are facing when something for example goes wrong and datastores are not in sync?

    • @ExecuteAutomation
      @ExecuteAutomation  Рік тому

      @@m3kbeatz Not atleast the outbox patterns but, will show how the Dataset stores data by fetching the message from Service broker

  • @TheDibyendusarkar
    @TheDibyendusarkar 3 роки тому

    I don't thing queue is a good fit for event driven system, instead we need immutable logs, such as kafka topic of kinesis shards. Queue implicitly means that the data is deleted once read by one service. That actually avoids one major benefit of ED system that you can plug n number of application to the echo system at any point of time whose input(s) is/are one/more of the existing topics.