The best video on saga pattern also please add the failure scenarios like one of the service is down and other services keep on pushing the datat to kafka, please enhance the video which will be great help for all of us.
@@JavaTechSolutions Yes. If say payment-ms is down and order-ms send orderEvent over topic new-orders. Once the payment-ms is up, I believe it will consume the orderEvent?
Question: here upon success we are always publishing a new event to the next step, what if we have to send data back on Success ? In this example Deliver order is the last step, hence we are just saving data on success, how to return some data to stock on success ? do we need to have a success topic and put an even there and consume it in Stock service ?? the way we are consuming reverse stock on failure? or is there a better standard way?
Is it necessay to take two different kafkaTemplate objects? Can't we use the same kafkaTemplate object and create different topics and put messages in those?
🎆🎆Happy New Year Sir 🎆🎆, thank you for your help. As I have learned from comments that this is choreography pattern, so to relate that order done then next step payment and in this way states are being changed. I am still skeptical about something that in this case even a rabbitMQ would do the job, then why consider kafka.
@@JavaTechSolutions what I observed is that even though orchestration is a better decoupled approach, almost no one use it in real life. any reason? or simply the application does not grow complex enough to migrate to orchestration pattern? Please reply sir.
@@JavaTechSolutions I’m not sure if it with Microservices , cuz, most of the RU-vid videos explained the CQRS General info . I’m looking for deep idea and implementation as you have done in this video . Plz share the link thanks!!!! 🙏
Component is the very generic annotation. It can be used anywhere like service layer or dao layer. But spring provide specific annotation for service and repository level. So component can be used in dao layer as we are having service annotation for service layer
you should not create simple classes from scratch. just explain the code written by you. focus on important points. Till 1.02.00 you are coding just the CRUD part.
@@JavaTechSolutions can you explain where in your video you have explained distributed transaction? how will you handle transactions that were not successful? What is there in this video that you are saying its easy to understand?
@@SiiitiiFreelancing-jl3ty Actually this is just for explaining the concept. Not possible to cover all the point. Still I am trying to understand what you need basically? Please let me know in detail so that I will create another tutorial for that
@@JavaTechSolutions I was looking for the specific code that takes care of rolling back data in other microservice when one failed or it retried say 5 times and then it was success or failed. This is 2PC or 3PC. This video is a simple one without transaction management
Hi, I have a question, I see that in the @KafkaListener() annotation the groupId attribute is repeated for some topics, for example: In the microservice payment-ms you have @KafkaListener(topics = "new-orders", groupId = "orders-group") and in the microservice order-ms you have @KafkaListener(topics = "reversed-orders", groupId = "orders-group"), i.e. both topics, both "new-orders" and "reversed-orders" point to the same groupId="orders-group". In that sense, why the groupId="orders-group" is repeated in both topics? shouldn't the groupId be unique for each topic?.... I would be very grateful if you could help me to understand this question. Note: Excellent tutorial, I enjoyed watching the whole video, best regards! 😊
Thank you for asking such nice questions. The question you asked is related to kafka . Like how kafka is working. Can you please go through kafka related tutorial. I hope you can clear your most of the doubts from that tutorial. ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-RYUlF-8IYsI.html ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-F3f9kekI4Q4.html