B
DSave on your Workers bill by "manually" caching every response, without having to lift a finger!
BD
, as now everything would be double-cached to cache at KV-level, and at Worker-level. From what I remember, the argument against was that it would result in less predictable billing, but the counter-argument to that is while less predictable, still bounded by the current number of reads.DBBBD
U
UU
D
, end billing when stream response returned, etc) to now say ok, cached reads are now freeD
lru-cache (https://www.npmjs.com/package/lru-cache) usage 
HDBUHUHHD
HDHD
DHDBBD
sudo rm -rf nooo how else do I stop thisBA web application with 50,000 map loads using the Google Maps API will cost $350 per month.
A similar amount of traffic running through a Protomaps CDN install on Cloudflare, with an average of 20 tiles per session, costs fifty cents in Cloudflare Workers request fees.
BHHBH
K
put will want the full file but you can make ranged reads against matchKH
put a 60 GB file in every requested colo…KKput just doesn't like the status code of 206 - but if you store a ranged response w/ a body of 200 then you'll be matching any ranged read against that unless you store the requested range as apart of the cache key.KHBlru-cachesudo rm -rfGET https://maps.goalastair.com/planet - Ok @ 3/10/2023, 6:38:19 PM
✘ [ERROR] TypeError: Cannot cache response to a range request (206 Partial Content).putputputmatch200