Our solution was to just create a unique hash of the known fields and adding that to our cache key (e.g. Foo:96f8148eb2b7:123). Whenever a field is added, renamed or deleted, the hash changes effectively invalidate the cache.
Tips for Building High-Quality Django Apps at Scale

Another solution is to utilize the VERSION for a cache. That allows you to increment the version when doing a deploy and have “no downtime” experiencing when fetching values from a cache that can’t be hydrated back into your model.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.