| I think Deno KV is a great tool with a nice API, it's great to see how it works. Really well designed. I used it a couple of times locally with Sqlite for CLI apps, if you want to do some data manipulation stuff with TS from the CLI and need a db, don't look further. I also used it in Production with FoundationDB on Deno Deploy. It does not replace your postgres/mysql database but a different beast entirely for many reasons. One is pricing. You pay per read and write. An issue I had is that it's hard to migrate from using KV with Deno Deploy. You can migrate to a local SQLite backed instance but will need to develop your own solutions on how you migrate and it will cost more the larger your database gets because you pay for reads. I do think it's great, but I would recommend using Deno Deploy only if your reads and writes produce value that offset the costs, else you can find yourself in the issue of needing to migrate. For example, use it for features you offer to authenticated users, but don't use it for things available in the open, else you open up yourself to high fees from DDOS. |
Are any of the these tools open source? Would love to look at what you're doing