Caching options in Cloudflare Workers
When you get into systems design, eventually you are going to have to deal with caching. I am currently writing my serverless MUD and part of that system requires an automatic registration of users hitting the API. This means that every single API call reads from Cloudflare D1 in the hot path. Reading from D1 is incredibly fast, but it’s not latency-free, particularly during periods of high load. This got me thinking about caching the read “somewhere cheaper”. By cheaper, I mean lower la...