Microservices Architecture Patterns | SAGA Design Pattern| Project Creation| Distributed Transaction

Microservices Architecture Patterns | SAGA Design Pattern| Project Creation| Distributed Transaction

In this tutorial we will discuss what is saga design pattern and its internal work flow with a business use case also we will create project for demonstrating the how distributed transaction will work.

#javatechsolutions #SpringBoot #java #distributedsystems #transactionmanagement

GitHub:

If you guys like this video please do subscribe now and press the bell icon to not miss any update from Java Tech Solutions

Below 2 kafka command is used for running zookeeper and kafka server

Its developed using spring boot3, Java17, H2 in memory database and Kafka

Your Quires
saga design pattern
transaction management in microservice
distributed transaction management in microservice
How distributed transactions works in Microservices
Saga Design Pattern for managing Distributed Transactions
Managing Transactions in Your Microservice Architecture
What is Distributed or Microservices Transaction Management
spring boot
java
java 17
spring boot 3
How to do Distributed Transactions in microservices
Spring Boot + Transaction Management
Microservices architecture patterns
SAGA design pattern
Distributed transactions in microservices
Project creation in microservices
Best practices for microservices architecture
Implementing SAGA pattern in microservices
Handling distributed transactions
Building scalable microservices architecture
Microservices orchestration
Event-driven architecture in microservices
saga choreography

[raghavh]

Clearly explained the SAGA pattern with implementation. Thanks 🙏

[nihalgajbhiye]

Thank you for explaining the SAGA choreography pattern in such a lucid way👍

[sudheerkumar-tpmg]

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.

[karamjitsinghsehdev]

Excellent explanation and example. Please keep making such videos.

[kanikagoyal]

Nice explanation about chorography design pattern. Thanks for such great content 👍

[arundhwajiiith]

Nice explanation and example for Saga pattern. Thanks.

[dipalitusharvlogs]

To the point explanation... Thank you for this tutorial... Cheers to your efforts..

[sudheerkumar-tpmg]

Very nice explanation best example and easy explanation

[abhishekpandey]

Very good explanation, just one question - In Reverse Order, how Object mapper can convert String into OrderEvent?

[officemac]

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?

[jj_pog_champ]

🎆🎆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.

[sagarshekhar]

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?

[AshishAshish-fppo]

Sir, Which design pattern you have used here - orchestration OR choreography ?

[prabhuelangovan]

What happens when the data is stored in Db and during the pbulishing of event to message broker if it fails??

[besooab]

Thanks alot!! one more question how to apply cqrs pattern on this ?

[kakshaye]

What if network failure happened and your microservice could not put message to roll back your transaction?

[rpiisenh]

When to use @Service or when to use @Component annotation? Is there any clear guideline?

[SiiitiiFreelancing-jlty]

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.

[magadiflo-dev]

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! 😊