In this chapter, we added the aspect of reactive programming to our microservice-based architecture. There are trade-offs with this message-driven approach of microservices communicating with each other. However, at the same time, this approach tends to solve some of the fundamental problems when we advance our microservice architecture further. The event sourcing pattern comes to our rescue and lets us get past the limitation of an ACID transaction or a two-phase commit option. This topic requires a separate book altogether, and restricting it to a single chapter does not do it justice. We used our sample application to understand how to restructure our initial microservice in a reactive way.
In the next chapter, we will have the entire application ready for us to explore, and we will put together everything that we have discussed so far in this book.
