Cache API vs KV
Which is better for server-side caching of database (d1) calls (aka direct data responses from the backend) - Cache API or KV Storage? The API is quite similar, but the Cache API relies directly on the CDN. This is a CRM-like application with users, roles, etc., so the usual
cache-control cannot be applied here, as we need a way to programmatically invalidate on some CRUD operations (e.g. display a list of users while invalidate the cache when adding new ones to the database, with routes like /users/students, /users/students/new).