From the article: “A microservice is an isolated, loosely-coupled unit of development that works on a single concern.” … “ if one microservice has a hard requirement for other microservices, then you should ask yourself if it makes sense to make them all part of the same unit”
I think the implication is that two microservices that are tightly coupled are actually acting on the same concern, so making them two microservices was premature.
From the article: “A microservice is an isolated, loosely-coupled unit of development that works on a single concern.” … “ if one microservice has a hard requirement for other microservices, then you should ask yourself if it makes sense to make them all part of the same unit”
Aren’t these two aspects potentially conflicting?
I think the implication is that two microservices that are tightly coupled are actually acting on the same concern, so making them two microservices was premature.