Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

github.com

Post reply on HN
Print view View original

31–40 of 109 posts

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

#31

Post by doodlesdev »

tonyhart7 wrote: post #30
blibble wrote: 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]

SQLite is public-domain software and one of the best well-maintained pieces of software around today. You absolutely have to be very careful before saying things like these, as they bring lots of implications. I wouldn't call it offensive _per se_, but I'd say it's in bad faith at least. I'd just remove that if I were the devs, because everything else there makes me find the project at least interesting.

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

#32

Post by deaux »

Didn't have a good experience with them. One day we suddenly started to experience severe latency spikes, lasting for more than a day, causing timeouts. Unrelated to our DB which was small, even happened on trivial queries - a networking thing on their side. Google showed this to have happened before with certain regions of theirs. If you can't offer a certain region in a stable manner as a DB vendor, don't offer it. The whole point of outsourcing DB mangement is to take care of these things.

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

#34

Post by maxpert »

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 ends up in that state, but chances are pretty high. At this point the "compatible with SQLite" has become a marketing term IMO, we all know how easy it is to break compatibility here or SQLite to break compatibility.

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

#35

Post by cortesoft »

deaux wrote: post #32

Didn't have a good experience with them. One day we suddenly started to experience severe latency spikes, lasting for more than a day, causing timeouts. Unrelated to our DB which was small, even happened on trivial queries - a networking thing on their side. Google showed this to have happened before with certain regions of theirs. If you can't offer a certain region in a stable manner as a DB vendor, don't offer it.…

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

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

#36

Post by memothon »

cortesoft wrote: post #35
deaux wrote: post #32

Didn't have a good experience with them. One day we suddenly started to experience severe latency spikes, lasting for more than a day, causing timeouts. Unrelated to our DB which was small, even happened on trivial queries - a networking thing on their side. Google showed this to have happened before with certain regions of theirs. If you can't offer a certain region in a stable manner as a DB vendor, don't offer it.…

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)

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

#40

Post by doanbactam »

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 support vector columns soon, or is that strictly off-roadmap for now?
Post reply on HN