Mattew Spence, en ITNEXT, a contracorriente de la enorme ola de bombo sobre microservicios, desarrolla un consistente conjunto de argumentos de relativización de la importancia y necesidad de microservicios (You don't need microservices) . Sólo destaco el argumento acerca de la simplicidad de los microservicios, y de sus ventajas derivadas:
"Simpler, Easier to Understand Code"
This benefit is at best disingenuous, at worse, a bald-faced lie.
Each service is simpler and easier to understand. Sure. The system as a whole is far more complex and harder to understand. You haven’t removed the complexity; you’ve increased it and then transplanted it somewhere else.
(...) Although microservices enforce modularization, there is no guarantee it is good modularization. Microservices can easily become a tightly coupled “distributed monolith” if the design isn’t fully considered.
(...) The choice between monolith and microservices is often presented as two mutually exclusive modes of thought. Old school vs. new school. Right or wrong. One or the other.
The truth is they are both valid approaches with different trade-offs. The correct choice is highly context-specific and must include a broad range of considerations.
The choice itself is a false dichotomy and, in certain circumstances, should be made on a feature-by-feature basis rather than a single approach for an entire organization’s engineering team.
Should you consider microservices?
As is often the case, it depends. You might genuinely benefit from a microservices architecture.
There are certainly situations where they can pay their dues, but if you are a small to medium-sized team or an early-stage project:
No, you probably don’t need microservices.
No hay comentarios.:
Publicar un comentario