2 ms·

If you have this problem, you don't have microservices -- you have a distributed monolith. If each service can talk to each other, the number of possible commu

If you have this problem, you don't have microservices -- you have a distributed monolith. If each service can talk to each other, the number of possible communication paths grows exponentially -- this is manageable up to a point, but even the largest teams will have to start investing into orchestration sooner or later. There are many orchestration patterns and mechanisms, and this is not the place to list them all -- which one is the right choice will depend on the complexity and needs of the system.

taleodor 7y ago
This is not about microservices talking to each other, but rather about seeing customer-facing product as a whole with all its different components and their versions. And yes we can agree that there are various (usually "greedy") strategies to simplify this - but this problem is a fact of life and it makes thinking process easier to accept it as such. Same as accepting that it is impossible to solve consensus in async system, but there are algorithms that perform fairly well. + I summed this up in more details in the comments down below.