5 ms·
This is interesting. How er the true cost of inter service discovery is in maintenance. Adding a new service is trivial. Deprecating a service, or an API major
by donavanm 14y ago
This is interesting. How er the true cost of inter service discovery is in maintenance. Adding a new service is trivial. Deprecating a service, or an API major rev, is a PITA. Eventually you just end up with an unmaintainable morass of "deprecated" services and dead ends.
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.
- substack 14y agoThe 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.