We have come pretty far in our Saga Pattern Implementation in our last post. We have completed all the services that form a part of our Order Management Saga. Also, we have managed to start up an instance of the Axon Server and connect all our services to it. Now Read more…
This is the Part 3 of our Saga Pattern Implementation with Axon and Spring Boot series. We started to implement Saga Pattern in the previous post. To recap, below is the high-level plan we have been going through. In case you have directly come to this post, I strongly recommend Read more…
In the previous post in this series, we understood what is Saga Pattern. We also looked at the types of Saga Pattern implementation. Lastly, we also described the scenario we will implement using Saga Pattern. Below is our high-level plan for this series about Saga Pattern implementation. In Part 1, Read more…
Saga Pattern is a direct result of Database-per-service pattern. In Database-per-service pattern, each service has its own database. In other words, each service is responsible only for its own data. This leads to a tricky situation. Some business transactions require data from multiple services. Such transactions may also need to Read more…