3 ms·
That is a good list. At an even simpler level, perhaps we can summarize: Microservices necessitate the application of a more rigorous set of engineering practi
by contingencies 10y ago
That is a good list. At an even simpler level, perhaps we can summarize:
Microservices necessitate the application of a more rigorous set of engineering practices to all service infrastructure components and therefore carry a greater overhead than traditional development methodologies - rigorous engineering does not come free. Whether that trade-off makes sense for any given project is a question of resources and requirements.
I feel two salient points were not mentioned: (1) Popular microservice orchestration/infrastructure management approaches are not universally applicable; their limitations should be recognized before assuming applicability. (2) The webhost is currently down; perhaps the author should have used a scalable or distributed cluster of microservices ;)