This is a great illustration of why the naive belief that a microservice architecture will solve all the things is so ill-conceived. When developers fail to pro

This is a great illustration of why the naive belief that a microservice architecture will solve all the things is so ill-conceived. When developers fail to properly assess how deeply coupled microservices are to their dependencies, the result is cascading failure scenarios that take down the whole ecosystem. Perhaps we should aim for 'services' architecture that are just right. When two concerns are deeply coupled/dependent on one another, the ecosystem will likely be more robust if these are left together in a single service. In addition, this adheres to good old fashioned software design principles of striving for good coupling/cohesion relationships.