Summary

We started by reviewing the traditional monolithic approach to developing an application. We established that this approach has worked for years and is not inherently incorrect. We also acknowledged its shortfalls and explained why there might be better ways to build a project.

We then explored how microservices will change an application’s implementation and development style. The idea here is to make the code and components as loosely coupled as possible, making it easier to manage the different parts independently and increasing the ability to manage various parts of the application without affecting others. While this approach has its benefits, it does introduce complexities where the monolith does not and requires more expertise in implementations.

To properly implement a microservices architecture-based application, we must appreciate the cross-cutting concerns that must be addressed and the different approaches, or design patterns, that help us to do...