The service registry I wrote (http://github.com/substack/seaport) is fundamentally version-aware to avoid this problem. You register services with a semver such as `[email protected]` and then clients or other services query for registered services with semver query strings such as `[email protected]`. This way you can specify your breaking changes much more explicitly and not need to port over the clients to the new service all at once.
Speaking of, what's the work flow around service API revs? New config knob then query on the client side? Create a new service instance.