An under-rated solution to this problem is saying No and having quality retrospectives.
Microservices adoption has largely become a cargo cult thing. It is a part of being cool like FAANG.
Instead of being cool, focus on solving your problems.
Microservices adoption has largely become a cargo cult thing. It is a part of being cool like FAANG.
Instead of being cool, focus on solving your problems.
Unfortunately, I don't see a wealth of other ready-made practices for companies to copy when they grow and need to solve this problem. I once worked on an enormous Rails monolith that was very well organized and had layered on several additional patterns to improve modularity and maintainability. Still, a SEV in a minor product area could (and did) bring down the whole system, and they were in the process of dismantling it.
One of the troubling practices is tightly-coupled containerized services, though, which only gives us all of the problems of microservices at the same time as we have all of the problems of monoliths.
This needs repeating to every dev every week. Myself included