You've broken the microservice abstraction if this a problem.
A team should own a microservice, you release as soon as the team able to.
You version your apis, so you don't break any services which rely on yours.
A team should own a microservice, you release as soon as the team able to.
You version your apis, so you don't break any services which rely on yours.
I agree, but in practice it seems more companies break it rather than follow it.
We may make the occasional announcement that v5 our api is coming soon which has x features based on feedback from other teams. Then announce when we've released it.
Its a product, and we own it.
That's called the "distributed monolith" and it's worse than a monolith.
It's a totally impractical standard for modern software development, but the developers themselves have no choice in the matter until the customers change.