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.
Wish this was clarified. One thought would be to choose a stable component to in turn hash, such as the source coordinate hexagon, but then why not just put that in the hashtag
Naively (and naive is often fine), you can query each node in parallel. The number of nodes is usually very small relative to the amount of data per node and reading is usually much faster than writing.
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.
"You sound like a robot m" has a whole new meaning for me.
How'd I guess on the article itself?
I see them pretty frequently.