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

Deep dive into Turso, the “SQLite rewrite in Rust”

kerkour.com

Post reply on HN
Print view View original

121–130 of 154 posts

Re: Deep dive into Turso, the “SQLite rewrite in Rust”

#121

Post by duped »

9rx wrote: post #82
duped wrote: post #76

Earlier quoted context omitted.

I'm not sure I follow what that has to do with embedding a database into your application

In a networked environment, which includes the web, it is typical to expose your database over the network. In the olden days clients started speaking SQL over the network, but there are a number of pitfalls to this approach. SQL was designed for use on mainframes, which, understandably, does not translate to the constraints of the network very well. To alleviate the pressure of those pitfalls, we started adding midd…

Are you an AI?

Re: Deep dive into Turso, the “SQLite rewrite in Rust”

#122

Post by dullcrisp »

einsteinx2 wrote: post #77
CharlesW wrote: post #73

Earlier quoted context omitted.

> IMHO breaking free of SQLite's proprietary test suite is a bigger driver than C vs Rust. I don't understand this claim, given the breadth and depth of SQLite's public domain TCL Tests. Can someone explain to me how this isn't pure FUD? "There are 51445 distinct test cases, but many of the test cases are parameterized and run multiple times (with different parameters) so that on a full test run millions of separate…

The irony is if they only had the public domain tests, no one would complain even though it would mean the exact same number of open source tests.

That’s like if I gave you half the dictionary and then said it’s ironic that if there really weren’t any letters after “M” you wouldn’t be complaining.

Re: Deep dive into Turso, the “SQLite rewrite in Rust”

#123

Post by gizzlon »

IshKebab wrote: post #70
MobiusHorizons wrote: post #43

Earlier quoted context omitted.

> 2) They have a paid cloud option to drive income from: I’ve been confused by this for a while. What is it competing with? Surely not SQLite, being client server defeats all the latency benefits. I feel it would be considered as an alternative to cloud Postgres offerings, and it seems unlikely they could compete on features. Genuinely curious, but is there any sensible use case for this product, or do they just catc…

The article talks about this. If you have a project that starts small and an in-process DB is fine, but you end up needing to scale up then you don't have to switch DBs.

So the usecase is: I started with SQLite, but now I have too many terrabytes to fit on one server? That seems.. very uncommon.

And since moving it out of process, and even to another network, is going to make it much much much slower. You're going to need a rewrite anyway

Re: Deep dive into Turso, the “SQLite rewrite in Rust”

#124

Post by pelasaco »

So the idea is to rewrite it in Rust and drop SQLite? I mean, maybe that’s just how things evolve. But it feels like every project is only a few vibe-coding sessions away from getting rewritten in $LANGUAGE. And I can’t help wondering whether that’s hurting a sustainable open-source ecosystem.

SQLite is a good example: the author built a small ecosystem around it and managed to make a living from open source. Thanks to author's effort, we have a small surface area, extreme stability, relentless focus on correctness.

If we keep rewarding novelty over stewardship, we’ll lose more “SQLite-like” projects—stable cores that entire ecosystems depend on.

Re: Deep dive into Turso, the “SQLite rewrite in Rust”

#126

Post by pelasaco »

yunohn wrote: post #7

What a breath of fresh air to read a blog not written by AI, with actual human learnings and opinions. Thanks for the write up!

a blog not written by AI, about a project written in AI. It is just matter of time. We just need AI to read the article, and then the full circle is complete.

Re: Deep dive into Turso, the “SQLite rewrite in Rust”

#128

Post by IshKebab »

gizzlon wrote: post #123
IshKebab wrote: post #70

Earlier quoted context omitted.

The article talks about this. If you have a project that starts small and an in-process DB is fine, but you end up needing to scale up then you don't have to switch DBs.

So the usecase is: I started with SQLite, but now I have too many terrabytes to fit on one server? That seems.. very uncommon. And since moving it out of process, and even to another network, is going to make it much much much slower. You're going to need a rewrite anyway

I think it's more like you started with SQLite and now you need concurrent writes, replication, sharding, etc. etc. - all the stuff that the "big" databases like PostgreSQL provide.

Re: Deep dive into Turso, the “SQLite rewrite in Rust”

#130

Post by lelanthran »

MobiusHorizons wrote: post #43
hu3 wrote: post #38

Earlier quoted context omitted.

I too am weary of VC incentives but: 1) It's MIT licensed. Including the test suite which is something lacking in SQLite: https://github.com/tursodatabase/turso 2) They have a paid cloud option to drive income from: https://turso.tech/pricing

> 2) They have a paid cloud option to drive income from: I’ve been confused by this for a while. What is it competing with? Surely not SQLite, being client server defeats all the latency benefits. I feel it would be considered as an alternative to cloud Postgres offerings, and it seems unlikely they could compete on features. Genuinely curious, but is there any sensible use case for this product, or do they just catc…

> Genuinely curious, but is there any sensible use case for this product

Looking at the comments each time this product comes up, Rust is apparently the selling point for many, including the dev team themselves.

Post reply on HN