Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: