redis

Mass-deleting Redis keys felt right until I read the docs. Versioned keys with INCR bumps make stale chat answers unreachable instead.

TL;DR: Editing an article left the Redis-cached AI answers stale, and the author's first fix—scanning and deleting every ask: key—turned out to solve the wrong problem. SCAN is non-blocking; the real pain is tracking key families across workers forever. Versioned keys fix it: bake versions into key names, bump with INCR on edits, and let TTL clean up.

A security audit uncovered 11 findings in the chat AI pipeline, from cache keys to prompt injection.

The blog's AI chat now answers 'what are you working on' from local commit history: a narrow port, a version namespace bump, and term mining.

When the LLM router died, a meta fallback event arrived and the visitor still got an answer. Here's the three-part chain behind it.