Databases are a field that didn't have a lot of competition, but a lot of room for profit. There is a lot of competition now for several different cases, which is amazing for us Developers.
Hey! I think the main benefit is an integrated system. You don't only have the cloud environment with Deno, but seamless integration with a database AND access to the Deno language and all the Deno packages.
The main difference that comes to mind is that KV has first class support in the Deno language and in Deno deploy. It is a solution maintained by the actual Deno team, so you can always expect a seamless integration in the ecosystem.
Haha! It is old tech, but integrations are becoming easier by the day. For instance, sure, I can use Redis, but is there a service which allows me to deploy and scale all that automatically?
Kinda. I have used foundation db before and is not the same experience if you set it up manually. You should take care of the connections, data storage, distribution and shit which is not pleasant to say the least EDIT: Deno KV is just there ready for you to use which automatically scales to your needs
@@dyto2287 Yes they do but distributed auto scaling is different. Your data is stored where your users are but something like redis exists in one region only. Yes distributed data stores exist too like turso but they are not part of the runtime
I don't see a reason for allowing a vendor lock. All this "edge" and "serverless" stuff is just a very clever commercial made by cloud/hardware providers. That "ease" will cost you 10 times more in future, compared to classical "own servers cluster + devops specialist to set up all the automation".😊
I sqw the demo in jsconf, trully amazing. How does the data looks in the filesystem? How do you backup the data? Are any tools (maybe too soon for that)? I'm sold on this.
I believe KV is already available in Deno Deploy as a closed beta. I expect they'll provide backup tools in that interface for certain since regular backups and redundancy are prerequisites for production environments. I think we are just a couple of months away from getting full access to this!
it is so unclear still, some say it is prod some say it primary db others say no only cookies, session mgmt, small data...then the docs say the least of all, storage capacity?I DUNNO. Rate limits? I DUNNO. backups story? I DUNNO
it's kind of confusing seeing only the first line of imports. I'm looking at like 5 functions here that I have zero context for, so the code may as well be obfuscated assembly :\
Thanks for the feedback! I'm trying to squeeze as much as possible in a single view as possible, but I get it might be confusing. I'll fix it in the next videos!
I don't understand why does a interpreter (that's what i would call it. if it's more than that they should've delivered a ONLY interpreter as the core of the runtime) needs to have a kv?
Because the Deno Runtime is just one small piece of the Deno platform offering. When you consider Deno Deploy and running at the edge support, a storage solution would actually make sense.
I don't think KV is a real replacement for firestore database; i really like building SPA where the browser talks directly to the database. Then i don't need any app server at all!
Web Dev is on a course to become the easiest thing on the planet (not that it is was ever that hard anyway). You don't need to know anything anymore, just use bunch of services as black box and voila. In few years a monkey with 6 months of training will be able to do it.
It was already the case with rails + heroku and those "bunch of services" years ago. The difference is when you need to understand your stack when unique problem arrives, if you're trying to do something a little bit different or even when those services become too limiting or vendor lock you. That's ultimately the difference between someone who doesn't know what he's doing and someone who does, otherwise you could already use Back end as a service solutions and "website builders" for the frontend or even just use those builders for everything and accept the limitations. This whole JS ecosystem thing is a shitshow tho, people are just getting excited about things that existed long before, but I guess that's also emphasized by the social media effect, this RUclipsr for example saw the announcement and decided it was "a game changer", next time he'll see a new JS framework, spend an hour playing with the hello example of the README and call it "the Framework we have all been waiting for", that's RUclips for you, it's just not worth watching tbh.
I was looking for a video about this subject yesterday 😅
Very informative indeed, I'm excited to see what ppl will build with KV.
Ha! Good timing!
Played around with it a bit locally, pretty neat indeed
I see you took our advice. Nice one!
Lately everyone is trying to make a new database for some reason.
Thank you for the help and your suggestions! They are always welcomed!
Databases are a field that didn't have a lot of competition, but a lot of room for profit. There is a lot of competition now for several different cases, which is amazing for us Developers.
"new"
Deno seems to be amazing... Have you also tried Workers or Workers KV in any manner?
I did not played around with Workers yet, but it might be a good subject for a future video! ✌️
nice vid :) But why does your highlighting flicker so much (at around 01:00)?
Thanks!
That's vscode being weird - whenever I'm typing it believes I'm going to use those unused imports :)
what makes cloudflare and deno so different, for example cloudflare pages, what is so beneficial by using deno? call database locally?
Hey! I think the main benefit is an integrated system. You don't only have the cloud environment with Deno, but seamless integration with a database AND access to the Deno language and all the Deno packages.
I saw it earlier in the Dahl's speech. Still don't get, what's the benefit compared to Redis for example?
The main difference that comes to mind is that KV has first class support in the Deno language and in Deno deploy. It is a solution maintained by the actual Deno team, so you can always expect a seamless integration in the ecosystem.
@@awesome-coding yeah, that's obviously good. If we use Deno in prod, that KV storage will be used for sure.
I got a feeling that JS devs will go on a hypetrain for any old tech.
Haha! It is old tech, but integrations are becoming easier by the day. For instance, sure, I can use Redis, but is there a service which allows me to deploy and scale all that automatically?
Kinda. I have used foundation db before and is not the same experience if you set it up manually. You should take care of the connections, data storage, distribution and shit which is not pleasant to say the least
EDIT: Deno KV is just there ready for you to use which automatically scales to your needs
@@awesome-coding Auto-scaling most KVs solutions existed for ages.
@@TechBuddy_ Exactly!
@@dyto2287 Yes they do but distributed auto scaling is different. Your data is stored where your users are but something like redis exists in one region only.
Yes distributed data stores exist too like turso but they are not part of the runtime
ry said they'll add queues as well.
won't be surprised if they'll add a websockets service... lots of things
Yep... the options are infinite. Deno is going to be an amazing platform!
I don't see a reason for allowing a vendor lock. All this "edge" and "serverless" stuff is just a very clever commercial made by cloud/hardware providers. That "ease" will cost you 10 times more in future, compared to classical "own servers cluster + devops specialist to set up all the automation".😊
I sqw the demo in jsconf, trully amazing. How does the data looks in the filesystem? How do you backup the data? Are any tools (maybe too soon for that)? I'm sold on this.
I believe KV is already available in Deno Deploy as a closed beta. I expect they'll provide backup tools in that interface for certain since regular backups and redundancy are prerequisites for production environments. I think we are just a couple of months away from getting full access to this!
it is so unclear still, some say it is prod some say it primary db others say no only cookies, session mgmt, small data...then the docs say the least of all, storage capacity?I DUNNO. Rate limits? I DUNNO. backups story? I DUNNO
wait, what is that? 1:47
why are you writing await like that? my ocd will not let me do that.
Sometimes I like to see the world burn...
I guess it can be used in a JS repo
I mean, if you want to keep living in the past, sure. What are you, a FinTech CTO?
Next you’ll tell me you build brand new micro services in Java 7.
Wait.. what's wrong with Java 7?!
@@awesome-coding it isn’t Java that’s the problem, it’s fintech.
it's kind of confusing seeing only the first line of imports. I'm looking at like 5 functions here that I have zero context for, so the code may as well be obfuscated assembly :\
Thanks for the feedback! I'm trying to squeeze as much as possible in a single view as possible, but I get it might be confusing. I'll fix it in the next videos!
Cant wait
Ever heard of redis?
I've heard of the color Red if that helps 😅
I don't understand why does a interpreter (that's what i would call it. if it's more than that they should've delivered a ONLY interpreter as the core of the runtime) needs to have a kv?
Because the Deno Runtime is just one small piece of the Deno platform offering. When you consider Deno Deploy and running at the edge support, a storage solution would actually make sense.
Helping you to break RUclips algorithm
Thank you! I really appreciate it!
@@awesome-coding yaa
explanation about bun js😄
Will do soon!
I don't think KV is a real replacement for firestore database; i really like building SPA where the browser talks directly to the database. Then i don't need any app server at all!
You are right, it is not a replacement, but it is a really nice convenience!
Nice 👍
Thanks!
There are new game changers every week … 😢
😅✌️
no it won't
noted 😅
Web Dev is on a course to become the easiest thing on the planet (not that it is was ever that hard anyway). You don't need to know anything anymore, just use bunch of services as black box and voila. In few years a monkey with 6 months of training will be able to do it.
Haha! Monkey see monkey do is how I got through 15 years of development!
It was already the case with rails + heroku and those "bunch of services" years ago.
The difference is when you need to understand your stack when unique problem arrives, if you're trying to do something a little bit different or even when those services become too limiting or vendor lock you.
That's ultimately the difference between someone who doesn't know what he's doing and someone who does, otherwise you could already use Back end as a service solutions and "website builders" for the frontend or even just use those builders for everything and accept the limitations.
This whole JS ecosystem thing is a shitshow tho, people are just getting excited about things that existed long before, but I guess that's also emphasized by the social media effect, this RUclipsr for example saw the announcement and decided it was "a game changer", next time he'll see a new JS framework, spend an hour playing with the hello example of the README and call it "the Framework we have all been waiting for", that's RUclips for you, it's just not worth watching tbh.
Too much code
You might be right. Thanks for the feedback!
I disagree! The code kept me here.