Re:Goodbye Microservices: From 100s of problem children to 1...
by artpepper2 on Tuesday July 10, 2018 @02:55PM
(#17501072)
Or use versioning and a package manager. You should be able to introduce vNext and then have each service update at its own pace, with a deprecation strategy so that service owners are responsible to get off the old version by such-and-such time. But as others mentioned, part of the problem seems to be too many services given the size of the team.
[ Parent
| on HN ]
There are no comments on this comment yet.