Great video! Good to see you choosing the right tool for the job and great job explaining the underlying tech (sqlite) instead of just making this a Turso video. It is good for everyone to understand what underpins their cloud solutions. You are right about sqlite performance as well. Sqlite can be very performant, especially in WAL mode. If you are using Turso, you could potentially spin up a separate sqlite db/file for each user. This has added benefit of both performance and the ability to truly delete a person's data from your service if they request it without having to do some kind of crazy query to find and remove the data from a single db. Ty for the video. :)
What are your thoughts on the write performance of SQLite? We have used SQLite in the past in many projects and the read performance is amazing fast but the biggest roadblock was for us the write performance. Unfortunately, the implementation of b*-trees can play against you.
I think sqlite is great, but for a development/staging environment. I wouldn't use it in production. I'll stick with postgres for that, which is installed on my vps and not some service I have to pay for.
So does this allow concurrent writes by different users of is it just basically single user update with multiple concurrent readers? So you would still have to use MySQL or PostgreSQL if you want to have concurrent writes by different users, is that correct?
Really? I use Cloudflare Pages (and love them), but never considered their "database" solutions, thinking they were just for caching or smth like that. Is D1 any good as a primary database for an app? And is it easy to move out to something else if needed (is it just SQL or proprietary?)
It looks promising, but I really like libsql and how open source the turso stuff is, and its not really baked into anything like cloudflare seems to be
Great video! Good to see you choosing the right tool for the job and great job explaining the underlying tech (sqlite) instead of just making this a Turso video. It is good for everyone to understand what underpins their cloud solutions. You are right about sqlite performance as well. Sqlite can be very performant, especially in WAL mode. If you are using Turso, you could potentially spin up a separate sqlite db/file for each user. This has added benefit of both performance and the ability to truly delete a person's data from your service if they request it without having to do some kind of crazy query to find and remove the data from a single db. Ty for the video. :)
Also, at 3min in you made me feel so old lol. "This is the way a lot of OLD APPs work" :P
Yea per user DB is a crazy feature I definitely should have mentioned!
bro is quickly turning into my favorite software youtuber, man i just love your content keep going.
Turso seems to have an insane free tier compared to the other ‘big’ db hosts
yea its absurd, almost made me nervous but if you look at their infra it actually makes sense
for now...
Lemme ask, using Bun and still processing env traditionally? Whiy is that?
Because I'm dumb, good call lol I did not know it could do that
I just use a persistent volume + file system
What are your thoughts on the write performance of SQLite? We have used SQLite in the past in many projects and the read performance is amazing fast but the biggest roadblock was for us the write performance. Unfortunately, the implementation of b*-trees can play against you.
What are your thoughts on Solidjs as a framework?
Pocketbase?
Interested in the comparison as well
The big thing pocketbase gives is a client SDK, which I personally don't need or want. I really like having a server
Any reason why you switched from clerk / turso to supabase in your weights-ai app?
honestly I just wanted to try more stuff lol, I like both
@@bmdavis419 cool, thanks for responding
I think sqlite is great, but for a development/staging environment. I wouldn't use it in production. I'll stick with postgres for that, which is installed on my vps and not some service I have to pay for.
What is your current setup?
VPS > Docker > Postgres?
So does this allow concurrent writes by different users of is it just basically single user update with multiple concurrent readers? So you would still have to use MySQL or PostgreSQL if you want to have concurrent writes by different users, is that correct?
I host all my db with a usb key and a raspberry pi. No free tier, no update on paying plan and I own my data.
Based
This will be the solution... until the next solution
🫡
Cloudflare d1 > turso
Really? I use Cloudflare Pages (and love them), but never considered their "database" solutions, thinking they were just for caching or smth like that.
Is D1 any good as a primary database for an app? And is it easy to move out to something else if needed (is it just SQL or proprietary?)
It looks promising, but I really like libsql and how open source the turso stuff is, and its not really baked into anything like cloudflare seems to be
Still can’t be used outside of workers can it?
SQLite always wins