3 ms·
I wonder if there’s some HTTP3 style transform we can do where requests that show up in clumps get sent to the backend together after the ones that have already
by hinkley 6y ago
I wonder if there’s some HTTP3 style transform we can do where requests that show up in clumps get sent to the backend together after the ones that have already been cached are culled.
Particularly with normalized data, I’ve found it quite common that 80% of my data for some workflows is highly predictable but that last 20% that makes the interaction unique either causes the request to become whole cloth or results in very complicated code, sometimes with very bad (worse than nothing) cold cache behavior.