Live data from Hacker News

Deno KV Is in Open Beta

deno.com

41–50 of 60 posts

Re: Deno KV Is in Open Beta

#42
post #4

I poked around with this a few months ago to figure out how it works locally. The answer is SQLite: https://til.simonwillison.net/deno/deno-kv I'm finding the business model aspect of Deno KV absolutely fascinating. const kv = await Deno.openKv(); That's a Deno core API. It works fine in the open source version of Deno using a local SQLite database file. But as soon as you deploy your application to their proprietary…

Why does a KV store need SQLite? Does it provide transactionality?

SQLite is superb choice as a local storage solution, you don't need a transactionality requirement to use it as a KV store.

People choose NoSQL databases primarily for scaling reasons, which is not the problem here.

Re: Deno KV Is in Open Beta

#43
post #4

I poked around with this a few months ago to figure out how it works locally. The answer is SQLite: https://til.simonwillison.net/deno/deno-kv I'm finding the business model aspect of Deno KV absolutely fascinating. const kv = await Deno.openKv(); That's a Deno core API. It works fine in the open source version of Deno using a local SQLite database file. But as soon as you deploy your application to their proprietary…

Cloudflare KV is basically the exact same. Even the same name. Cloudflare’s pricing seems more reasonable, though a 1:1 comparison is impossible. Cloudflare reads and writes in every region for the same price, Deno scales price with number of replica regions. Also CF is billed per read/write operation (and supports listing), this is billed per kB read/written. That all said, if your values are bigger than ~2kB Cloudf…

Yes, Deno KV is much closer to D1 than to Cloudflare KV.

Re: Deno KV Is in Open Beta

#45

I continue to watch Deno with excitement. I haven't had a good use case to play with it yet (all my free programming time has gone into my side business and I'm not ready to chance it on Deno yet) but I'll keep looking. I find the way they handle secondary indexes very interesting. I mean under the hood I think DynamoDB does pretty much the same thing (stores the data multiple times) but instead of explicitly writing…

Deno gives me hope for web development. The security model, no bundler and general pace of progress is great. They've drastically improved node interop but if they could close the gaps (and sort out extension/less imports) so many more projects could finally jump ship over to Deno.

Re: Deno KV Is in Open Beta

#47
post #36

Earlier quoted context omitted.

Why does a KV store need SQLite? Does it provide transactionality?

What would you use instead? By the time you've implemented even a basic key-value store with on-disk storage you've probably written a bunch of code that would be unnecessary if you had used SQLite.

[deleted]

Re: Deno KV Is in Open Beta

#48
post #25

Earlier quoted context omitted.

What syntax would you suggest for importing a specific version of a library?

import ... from "dino@1.1/utils" idk i just think there's many options besides a full url in your code

In Deno you can load your code from any URL on the Internet, instead of relying on a namespace within a single package manager.

Re: Deno KV Is in Open Beta

#49

Earlier quoted context omitted.

Cloudflare KV is basically the exact same. Even the same name. Cloudflare’s pricing seems more reasonable, though a 1:1 comparison is impossible. Cloudflare reads and writes in every region for the same price, Deno scales price with number of replica regions. Also CF is billed per read/write operation (and supports listing), this is billed per kB read/written. That all said, if your values are bigger than ~2kB Cloudf…

Yes, Deno KV is much closer to D1 than to Cloudflare KV.

Except D1 gives you a full powered SQL interface and DKV gives you “get”, “set”, and transactions.

D1 is also faaaaaar cheaper. Like 3+ orders of magnitude cheaper.

Re: Deno KV Is in Open Beta

#50
post #4

I poked around with this a few months ago to figure out how it works locally. The answer is SQLite: https://til.simonwillison.net/deno/deno-kv I'm finding the business model aspect of Deno KV absolutely fascinating. const kv = await Deno.openKv(); That's a Deno core API. It works fine in the open source version of Deno using a local SQLite database file. But as soon as you deploy your application to their proprietary…

This is the enshittification of open source. It has been happening for a while with a bunch of startups like Supabase claiming to be "open source" and marketing themselves as such but making it really hard to self host for a long time. It wasn't just them either. I would see with disgust a bunch of startups use "open source" as their marketing tactic, no matter how hard it was to setup or run without their hosted ser…

Stallman was right and he provided an alternative. Go use it. Stick to GPLd software safely nested under the auspices of a foundation.

Don't expect Deno or any other corporate entity solely focused on profit seeking to give a single shit about anything other than profit.

It's all marketing, it's all spin, and it can't be any other way, that's how the system is structured.

Post reply on HN