3 ms·
You're getting charged for the replication of deno kv across all regions when you use deno.deploy. KV is free to use locally as I assume this will be too.
by vorticalbox 3y ago
You're getting charged for the replication of deno kv across all regions when you use deno.deploy.
KV is free to use locally as I assume this will be too.
- shafyy 3y agoSure, but genuine question: How easy it is to run my own infrastructure for Deno Queue, and, crucially, how can I know that it will still be as easy and transparent in 5 years from now when the VCs want to see some $$$. That the company developing Deno and the services that monetize Deno is the same is a major conflict of interest. And if history is of any guide, in the end economic incentives always win, no matter how good-hearted people are.
- LostLocalMan 3y agoIf Deno doesn't get adequate funding, the company developing Deno will not exist 5 years from now.
- skybrian 3y agoWhen imagining future scenarios, maybe don't get too fixated on one? Another possibility is that competitive service providers will implement the same services. (It didn't really happen with App Engine, but this seems like a cleaner API?)
- skybrian 3y agoI guess I remembered it incorrectly? This looks pretty good: > Deno KV databases are replicated across at least 6 data centers, spanning 3 regions (US, Europe, and Asia). Once a write operation is committed, its mutations are persistently stored in a minimum of two data centers within the primary region. Asynchronous replication typically transfers these mutations to the other two regions in under 10 seconds. https://docs.deno.com/kv/manual/on_deploy https://docs.deno.com/kv/manual/on_deploy