Adding fields or methods is easy. You can do it at any time.
Removing them is difficult. You must first go through a long deprecation cycle and ensure ALL clients are updated.
You need good logging AND good monitoring and analysis of the logs in both client and server to be able to detect access to removed features.
Alternatively you could provide different API versions at the same time and keep the old ones running, as long as they are called.
And, in general, don't focus on generic methods.
The more specific a service method, the better. The less it does, the better. Don't have an "order pizza" api. Have a "start order", "add to order", and "complete order" api. If it helps, have multiple add methods. The parameters to add a pizza can and should be different from a salad. Even the pizza may be better served with partial service calls to start and complete.
This sounds crazy, but it's essential if you can't guarantee that you can atomically deploy a new service version AND any other services that call it.
Creating backwards compatible releases means sticking to some rules, things like:
- you can add fields but you can never delete them
- you can add new methods but you can't remove old ones
Having really detailed logging helps a lot. If you want to deprecate a method you can remove it from calling clients first and then use the logs to confirm it isn't being called any more before removing it from the service.
It's a lot if work, and teaching a large engineering team how to be productive in this kind of environment is decidedly non trivial.