@jgrahamc what a great service. It might be great to have cloudflare credits like aws/google/azure credits for CL Workers for startups.
Introducing Workers KV
41–50 of 103 posts
Re: Introducing Workers KV
#42@jgrahamc what a great service. It might be great to have cloudflare credits like aws/google/azure credits for CL Workers for startups.
Take a look at the pricing.
$5/month for
- 1 GB of KV storage and up to 10 million KV reads
- 10 million requests
- per million requests
- per GB of storage
- per million KV reads
Re: Introducing Workers KV
#43@jgrahamc what a great service. It might be great to have cloudflare credits like aws/google/azure credits for CL Workers for startups.
Take a look at the pricing. $5/month for - 1 GB of KV storage and up to 10 million KV reads - 10 million requests After that it's $0.50/month - per million requests - per GB of storage - per million KV reads I think that's well within startup money. I mean, if a company has to give out credits perhaps it's just too expensive :-)
Heck, I think that's well within hobbyist budgets. Thanks for pricing it out nicely :).
Re: Introducing Workers KV
#44Earlier quoted context omitted.
Last write wins. There are several features for controlling consistency that we have been prototyping. Based on how storage is used we will enable those as the product matures.
So, with a global consistency window of 10s, and 1 write per second, would consistency ever be reached if a key is written to every second? What value would be visible? One great example of why this would matter to me - could workers ever institute a coordinated rate limiting function using this KV store?
Rate limiting doesn't have to be coordinated to work. But you do need a PN-Counter, which they are only considering at this point.
Re: Introducing Workers KV
#45[deleted]
Re: Introducing Workers KV
#46Earlier quoted context omitted.
Last write wins. There are several features for controlling consistency that we have been prototyping. Based on how storage is used we will enable those as the product matures.
So, with a global consistency window of 10s, and 1 write per second, would consistency ever be reached if a key is written to every second? What value would be visible? One great example of why this would matter to me - could workers ever institute a coordinated rate limiting function using this KV store?
One thing to remember is you have at least two other ways of storing values. Each worker has global memory which persists between invocations (local, atomic), and you have access to the Cache API (per-data center, ephemeral).
By combining those with KV to do global coordination on a more course time scale, I think you could.
Re: Introducing Workers KV
#47Earlier quoted context omitted.
So, with a global consistency window of 10s, and 1 write per second, would consistency ever be reached if a key is written to every second? What value would be visible? One great example of why this would matter to me - could workers ever institute a coordinated rate limiting function using this KV store?
Rate limiting doesn't have to be coordinated to work. But you do need a PN-Counter, which they are only considering at this point.
A PN-Counter is a method of coordination. And if the writes were coordinated with the consistency time, that would be sufficient to implement consistent counters (or even a naive counter in a store given atomic operatons).
Re: Introducing Workers KV
#48Re: Introducing Workers KV
#49Earlier quoted context omitted.
Best link is probably the blog: http://blog.plan28.org/
Any reason it doesn't serve HTTPS?
Turns out I never enabled HTTPS in Blogger. Just clicked the button... https://blog.plan28.org/
Re: Introducing Workers KV
#50@jgrahamc could you link to the technical post near the top, and maybe copy in that table 'Limits and Pricing' on this post? Because it would be really helpful to have that info in the general post, otherwise it's not clear what the details are (like write rate). Great posts BTW!