Explaining when to use microservices architecture
Taking into account the characteristics of an application based on the architecture of microservices, we can establish some criteria of when to use microservices architecture, as shown in the following bullet list:
- When a system grows in its amount of requirements and functionalities, meaning that it has evolved quickly. In this case, the system begins to mix the responsibilities between its modules.
- When we need to reuse services.
- When the centralization of the APIs begins to block the evolution of the system.
- When there is a need for new features, APIs, libraries, and frameworks, and we do not want to rewrite all of the software for this.
Imagine that we have a sensational and innovative business model, and we must quickly make an application available for customers to enjoy this business. The adoption of a monolithic model, in principle, would make the application develop quickly, with quick tests and deployments as well. At this point, we...
