Summary
In almost every section of this book, we have shown that, besides being solutions to recurrent problems, patterns aim at the reuse of and low coupling between application components. Following this principle, the decomposition of an application into small independent parts that perform intelligent and specific tasks allows this application to evolve in a natural and organized way. These small parts with specific tasks are called microservices, and the method of developing a system based on the decomposition of the application into these small parts is called microservices architecture.
However, like any technology, there are pros and cons to this. Developing an application and thinking about the control of the various microservices is a complex task, but once the microservices are well defined, the application is able to evolve much better than a monolithic application. In this way, the maintenance of the application is done more quickly, with the addition of new functionalities...
