6 ms·
I disagree. Tying a language runtime to a specific KV interface which is tied to a specific hosted service is the opposite of forward thinking. In fact the tech
by paxys 3y ago
I disagree. Tying a language runtime to a specific KV interface which is tied to a specific hosted service is the opposite of forward thinking. In fact the tech industry has made a lot of progress away from vendor locked-in stacks, and this just reminds me of those.
What is really the difference between Deno.KV being shipped as part of the runtime vs adding an `import KV` statement at the top of the file (which could come from Deno or wherever else you want)?
And what are the chances that the Deno team is going to ship bindings for any language besides their own?
If Google started adding Google Cloud specific primitives natively to Go would you call that forward thinking as well?
- coffeebeqn 3y agoIf they want to have these primitives then I’d prefer to have a “universal” queue API that would work with SQS, Kafka, etc. with some magic. But the developer API could be just deno.Queue or whatever
- paxys 3y agoWhy try to standardize the interface at all? This isn't the job of a programming language, and there is no way it can anticipate all the possible use cases. Let each service publish their own bindings, and you can a programmer can consume whichever ones you want.
- dkn 3y agoDeno is not a programming language though. It's a JavaScript (TypeScript) runtime. Deno is basically trying to be an infrastructure framework for JavaScript.
- zoogeny 3y ago> What is really the difference between Deno.KV being shipped as a standard library vs adding an `import KVService` statement at the top of the file? The same difference between `#include "myStringMap.h"` and `map[string]string` in C vs.g Go. There is some advantage to everyone in an ecosystem using the same primitives. That kind of language-level standardization goes a long way. For example, it might increase the ecosystem of available distributed system libraries that only need KV stores. If I can compose several libraries, all of which use the same underlying KV interface and implementation - I can imagine that might result in some interesting use-cases. As for the rest of your comment, I would humbly ask if you read the entirety of my comment? We seem to agree that as long as Deno KV is locked into their cloud that people should be very wary of lock in. And I myself will likely avoid it for the time being until the dust settles. There is some chance the rest of the community will just come along and fill in the gaps on popular cloud platforms. Or maybe they won't. Time will tell.
- pests 3y ago> difference between `#include "myStringMap.h"` and `map[string]string` in C vs.g Go. Except one is a language feature with custom syntax and the other is a library that could be implmented as a library just the same. Not everyone in the ecosystem is going to use this because its not forced on them through syntax and espically because its inside deno and not node so barely anyone at all will use it.
- dsherret 3y ago> Tying a language runtime to a specific KV interface which is tied to a specific hosted service is the opposite of forward thinking. This is not the case. The Deno runtime itself is not tied to the Deno Deploy hosting service. The KV feature in the Deno runtime can be used without the hosting service. You can read the details about how Deno KV works in the Deno runtime here: https://til.simonwillison.net/deno/deno-kv https://til.simonwillison.net/deno/deno-kv (as has been posted in other comments)
- zja 3y ago> The KV feature in the Deno runtime can be used without the hosting service. But one writes to foundation, and the other writes to a sqlite file. You wouldn’t be able to self host an app written for Deno Deploy and have it work out of the box. Are there any plans to open source the KV backend so that people could host their own KV databases? Now that you can connect to remote Kv databases, I suppose someone could implement their own?
- andyferris 3y agoSelf-hosting should work with a change of configuration, no? As someone mentioned elsewhere, they have documented the protocol, so yes you could reimplement your own remote KV store.
- coding123 3y agoThis is what Java did - JCP created, APIs invented to be implemented by Tomcat, JBoss, fill in your favorite here. Configure your actual instance - in the past this was done with beautiful UIs - total waste of time considering we're in the era of Yaml (FBFW?) configuration.
- endisneigh 3y agoThis is not true, you cannot run your own foundationdb server and use the kv service without reimplementing yourself in fdb
- BoorishBears 3y ago
- paulddraper 3y ago> Tying a language runtime to a specific KV interface which is tied to a specific hosted service is the opposite of forward thinking. Yeah, I'm hella confused. Isn't Deno the Node.js replacement? But now it's a database as well? It's jumped the shark for sure.
- giraffe_lady 3y agoI think people are hung up on a distinction between language and runtime that isn't that valuable and maybe doesn't even reflect normal use. For example erlang ships a persistent KV store, queue, relational database and much more as part of its standard library. I've never heard anyone complain about this or wish it were otherwise.
- 59nadir 3y agoOTP isn't part of a cloud solution and there is zero lock-in to any kind of commercial offering as part of the batteries that are included in it.
- realPubkey 3y agoThis. It could have been a npm package, why build it directly into Deno?
- vineyardmike 3y ago> If Google started adding Google Cloud specific primitives natively to Go would you call that forward thinking as well? Go actually ships with a quite forward thinking SQL interface. It's an abstract interface over a DB, and you just import the "driver" that powers it. The driver conforms to a standard interface, so all of them behave roughly the same. I think this is what everyone wants from Deno/etc - why can't there also be a KV interface that's universal, or a Queue interface that's universal? People attempted this w/ go [1], where it attempts to use the same nice experience of the SQL logic, but it never seemed to gain traction. https://gocloud.dev https://gocloud.dev
- hueho 3y ago> Go actually ships with a quite forward thinking SQL interface SQL is low hanging fruit in this regard, because you just need to standardize the lowest common denominator flavors of SQL types for deserialization and then it's just juggling SQL queries around. JDBC for Java does the same as database/sql and it's from 1997. ODBC is from 1992.
- 59nadir 3y agoI don't think GP is saying that this is forward thinking, revolutionary level stuff, but rather that it's generally speaking a better thing to do than ship specific implementations that wall people into your solutions.