The service registry I wrote (http://github.com/substack/seaport http://github.com/substack/seaport) is fundamentally version-aware to avoid this problem. You r

The service registry I wrote (http://github.com/substack/seaport http://github.com/substack/seaport) is fundamentally version-aware to avoid this problem. You register services with a semver such as `web@1.2.3` and then clients or other services query for registered services with semver query strings such as `web@1.2.x`. 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.