Why didn't anybody tell me about Redis hash slots?
A backend engineer at a gig-economy delivery service hit a wall caching route estimates in Redis. Their keys, built from H3 hexagon IDs, never landed in the same hash slot, so every MGET exploded into dozens of round trips. Redis hash tags, brute-forced integer anchors, slot-aware batching, EVAL for expiry, and dropping JSON for CSV fixed it. The lesson: build the benchmark harness first.
I think in the post-Claude era of programming, where such a benchmarking harness is a matter of providing a spec and waiting 10 minutes, this is no longer acceptable.
- lesam
I'm confused how you find the data again in this cache? It seems like you're randomly salting your cache keys, so I don't understand how subsequent requests find cached data.
- HeavyStorm
I can see how the author put some work in this article. But I can't handle any more AI speak, even more after spending the whole day talking to Claude. It's too bad - blogging has been dying (well, at least in decline) for half a decade, and AI might be the final nail in the coffin.
"You sound like a robot m" has a whole new meaning for me.
- abofh
Because you inherited it from someone who built it before that was a thing, and discovered it when you went serverless.
How'd I guess on the article itself?