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.
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.
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
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?
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.
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.
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
How much of the tools you use every day stays unnoticed...
I actually do a quarterly “read the docs” day for my major tools. It always pay off…
What do they use to make those visualizations?
I see them pretty frequently.