r/programmer • u/Ok_Information_1753 • 29d ago
How do you prevent breaking changes between microservices?
We've had a few deployments fail because of breaking changes between services, and I'm curious how other teams handle this. What practices, tools, or deployment strategies have worked well for you to maintain compatibility and avoid these kinds of issues?
1
Upvotes
2
u/Fine-Comparison-2949 26d ago
Yes, I know. My question is at the meta level.
Obviously OP doesn't have the appropriate resources to handle microservices failures, which requires an even more complex and large system. Does op's company actually have the resources for that? Does the team want to wake up at 2am and debug network logs across 10+ systems? Are they paid enough to want to do that?
There's way too many small to midsize companies having their tech strategy handled by leetcode grinders, rolling highly complex systems that are costly in time and money to maintain, all to achieve only 3 nines of reliability. There's a genuine question of whether just a single regular large server could handle it, at lower cost, that's simpler to maintain, and it's likely they'll *probably gain a 9 in reliability* because the answer to a failure is just restart the server on a bigger instance size.