The issue is when you have multiple teams working on a monolith.
I haven't seen a configuration of teams that doesn't screw up the monolith by creating "spaghetti" dependencies between the pieces. Hence making the transition to microservices a multi year journey.
Re:Enough with the microservices
by marcosdumay on Thursday May 25, 2017 @10:49AM
(#14417646)
That's because you need a configuration of the boundary, not of the teams.
And that, coincidentally, is also what you need to not write spaghetti service interactions.
You can do that inside a monolith too. Microservice as a solution points to architectural problems, we try to build systems that are too vertical, our architecture should be horizontal. Microservices enforce this horizontalness, but it's not the only way to achieve it.