I am stuck on cache invalidation without folklore. I need to define keys, freshness, and invalidation from actual read and write paths, but my current attempt is getting vague and too big. What would you check first?
The checklist I use for cache invalidation without folklore
The useful bit was asking for trade-offs and a smallest test before committing to a full plan.
First, shrink the decision. Do not solve the whole subject at once.
- Reproduce the failure before changing code.
- Keep the patch smaller than the diagnosis.
- Write the rollback before deployment.
Write down the result you need by the end of this session. Then choose one input you trust and make a first pass that can be checked. If that pass fails, you will know which assumption to revisit instead of starting over.
The smaller decision was the missing piece. I was asking for the whole system at once.
4 comments
Sign in to join the conversation.