Comment by asher_

A cache seems like a particularly odd example to choose for this. If you are changing the way a cache functions, then presumably you either have fairly short expiration times (problem will fix itself) or you would have some form of cache invalidation as part of the deployment process.

Additionally, it would have been nice to see some mention of patterns that solve this issue more completely, like CQRS, where state is disposable.