Clarity on KV limits/pricing
🔑KV
Workers
Workers- Get supports single/multiple keys. Does fetching 100 keys at once cost less or the same as doing it individually? I'm guessing it's the same since limits specify "reads" while get states "read one/multiple keys", however aside from performance timing, what would be the benefit to prefer one over the other?
- KV pricing shows lists/deletes separate from reads/writes, but limits doesn't show lists/deletes at all. Are they limited at all, part of reads/writes, or an additional group that was missed? I would think they're part of reads/writes (respectively), but it could go either way.
- I assume the API is also limited the same as workers in regards to time/quantity constraints, and that the API can't do bulk read/write as "one" transaction?
- KV pricing shows lists/deletes separate from reads/writes, but limits doesn't show lists/deletes at all. Are they limited at all, part of reads/writes, or an additional group that was missed? I would think they're part of reads/writes (respectively), but it could go either way.
- I assume the API is also limited the same as workers in regards to time/quantity constraints, and that the API can't do bulk read/write as "one" transaction?
Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news
85,042Members
Resources
Similar Threads
Was this page helpful?
