3 ms·
Version your cache keys to survive rolling deployments
- orrbenyamini 9mo agoAuthor here. This came from a production incident where renaming a field broke our rolling deployment. The cache became a shared contract between versions we hadn't versioned. The solution: automatically derive version identifiers from model structure at startup, prefix cache keys with them. Schema changes naturally map to new cache namespaces. Happy to discuss tradeoffs or alternative approaches!