3 ms·
> Sometimes new code creates and persists state that the old code can't handle and rolling back would just make the old version blow up because of it. Sometimes
by ryandrake 7y ago
> Sometimes new code creates and persists state that the old code can't handle and rolling back would just make the old version blow up because of it. Sometimes clients can't talk to the old code after talking to new code and expecting new protocol.
These are both severe bugs that should have blocked deployment of the old version. Software should gracefully ignore state or data file content it doesn’t expect—not blow up. Well known techniques like fuzzing can help catch this kind of defect. Clients should be able to probe which version they are talking to and negotiate the protocol. This is kind of basic versioning cleanliness.