Live data from Hacker News

Turso is an in-process SQL database, compatible with SQLite

github.com

41–50 of 109 posts

Re: Turso is an in-process SQL database, compatible with SQLite

#42

We switched our main API from Postgres to Turso last month and haven't looked back. The automatic schema migrations are a nice touch, but I wish the documentation on vector embeddings was a bit more robust. It's wild how much of the modern web is moving back to file-based databases. We switched our main API from Postgres to Turso last month and the cold start times are basically zero now. Are there any plans to suppo…

How do you scale your front end horizontally with a file based database? Do you put the files on a shared file system that the app layer all mounts and lock when writing? Or do you shard and route by user? Or do you build a big vertically scaled API server with the database in it?

Re: Turso is an in-process SQL database, compatible with SQLite

#43
post #16

the description as "the next evolution of sqlite" is offensive D. Richard Hipp has done a universal good for the world by releasing sqlite into the public domain and maintaining it for 25 years I bet this VC funded knockoff won't see 5

[flagged]

Re: Turso is an in-process SQL database, compatible with SQLite

#44
post #16

the description as "the next evolution of sqlite" is offensive D. Richard Hipp has done a universal good for the world by releasing sqlite into the public domain and maintaining it for 25 years I bet this VC funded knockoff won't see 5

[flagged]

Ohhh is that why their logo is a bull?

Re: Turso is an in-process SQL database, compatible with SQLite

#45

Earlier quoted context omitted.

I am confused, this product appears to be an in-process DB, so what does "networking thing in their side" even mean?

Turso offers a cloud-hosted sqlite product. The idea is you can easily spin up per-tenant databases and have a "serverless" sqlite interface. It feels like it has a lot of the same downsides of hosted databases so I'm not sure what the specific value is. From their site they really emphasize local first syncing (so mobile apps and electron/tauri apps) and multi tenancy (hard database boundaries)

Huh. That sucks but also isn’t surprising. Seems like putting this in the cloud eliminates most of its benefits though. If you’re going to wait for that much latency you might as well use a “real” (traditional big complicated) rdbms.

Re: Turso is an in-process SQL database, compatible with SQLite

#47

We switched our main API from Postgres to Turso last month and haven't looked back. The automatic schema migrations are a nice touch, but I wish the documentation on vector embeddings was a bit more robust. It's wild how much of the modern web is moving back to file-based databases. We switched our main API from Postgres to Turso last month and the cold start times are basically zero now. Are there any plans to suppo…

You only run a single instance of your API? How many monthly customers do you have

Re: Turso is an in-process SQL database, compatible with SQLite

#48
post #34

Disclaimer: I am author of Marmot https://github.com/maxpert/marmot so I will sound extremely bias. I have been asked multiple times on why I chose SQLite and not Turso. I've always responded people that I don't trust an open-source project once it's backed by a VC firm. I've moved away from Redis to Val-Key for same reason, and we have seen the Redis train-wreck in slow-mo. I hope at no point in future Turso ever en…

I find it crazy that people would ask you in that direction. I would wonder why anyone would chose Turso over SQLite.

SQLite is some of the most battle tested software in the world. Turso seems like relatively new software that is still a bit experimental.

You do not want your databases to be new or trendy. You want your databases to be solid as a rock.

Re: Turso is an in-process SQL database, compatible with SQLite

#49
post #29
post #28

A gotcha, if you are expecting compatibility with sqlite. You can't set PRAGMA journal_mode=WAL and expect to be able to read database state from another process. Turso will report exclusive lock

I thought the point of Turso was to offer better concurrency than SQLite currently does. A la https://turso.tech/blog/beyond-the-single-writer-limitation-... and https://penberg.org/papers/penberg-edgesys24.pdf Would be great if one of the Turso developers can clarify :)

Honestly, if you care about that level of concurrency, it begs the question of why are you using an in process database in the first place?

Re: Turso is an in-process SQL database, compatible with SQLite

#50
post #46

Without SQLite's full test suit, I don't think it's as safe. Rust may have better memory safety, but that's just part of the issue.

They can probably use most of SQLite test suite.

Except the most critical of them are close-sourced.
Post reply on HN