3 ms·
If the change is in a shared library (and not a service shared over the network), it's fine to change all usages at once. Deploying a service wouldn't affect th
by rohitpaulk 5y ago
If the change is in a shared library (and not a service shared over the network), it's fine to change all usages at once. Deploying a service wouldn't affect the others.
If the change affects the public interface of a service, then there's no option but to make your changes backward-compatible.
- tantalor 5y ago> no option but to... Not necessarily; you can accept downtime/breakage instead. That is always an option!
- bluGill 5y agoYou must not work on safety critical code where downtime/breakage mean people die.
- ralmeida 5y agoMost people don't, to be fair. The case where zero-downtime strategies are adopted for (at least) a questionable ROI is far more common.
- closeparen 5y agoI hope you're not doing anything "safety critical" with general purpose computers, let alone microservices.
- bluGill 5y agoWell the arm CPUs we use are in general purpose computers as well. Though you are correct, we don't follow the same practices as general purpose computers.
- marcosdumay 5y agoI hope nobody's life depends on the uptime of a web-based distributed system. But, well, I also expect nobody's life to depend on it. There would be a short window between people getting into that situation and they not have any life to depend on anything.
- tantalor 5y agoI was thinking more like bank/govt websites that go down for "scheduled maintenance".