4 ms·
This is ignoring the elephant in the room: SQLite is being rewritten in Rust and it's going quite well. https://github.com/tursodatabase/turso https://github.co
by slashdev 1y ago
This is ignoring the elephant in the room: SQLite is being rewritten in Rust and it's going quite well. https://github.com/tursodatabase/turso https://github.com/tursodatabase/turso
It has async I/O support on Linux with io_uring, vector support, BEGIN CONCURRENT for improved write throughput using multi-version concurrency control (MVCC),
Encryption at rest, incremental computation using DBSP for incremental view maintenance and query subscriptions.
Time will tell, but this may well be the future of SQLite.
- zvmaz 1y agoIn the link you provided, this is what I read: "An in-process SQL database, compatible with SQLite." Compatible with SQLite. So it's another database?
- simonw 1y agoYeah, I don't think it even counts as a fork - it's a ground-up re-implementation which is already adding features that go beyond the original.
- ForHackernews 1y agoIt's a fork and a rewrite.
- tonyhart7 1y agoso its sqlite++ since they added bunch of things on top of that
- metaltyphoon 1y agoThe moment turso becomes stable , SQLite will inevitably fade away with time if they don’t rethink how contributions should be taken. I honestly believe the Linux philosophy of software development will be what catapults turso forward.
- assimpleaspossi 1y ago>>SQLite is being rewritten in Rust SQLite is NOT being rewritten in Rust! >>Turso Database is an in-process SQL database written in Rust, compatible with SQLite.
- slashdev 1y agoIt's a ground up rewrite. It's not an official rewrite, if that's what you mean. Words are hard.
- stoltzmann 1y agoSo a reimplementation, not a rewrite.
- lionkor 1y agoSo they have much worse test coverage than sqlite
- blibble 1y ago> Time will tell, but this may well be the future of SQLite. turdso is VC funded so will probably be defunct in 2 years
- 3eb7988a1663 1y agoIt should be noted that project has no affiliation with the SQLite project. They just use the name for promotional/aspirational purposes. Which feels incredibly icky. Also, this is a VC backed project. Everyone has to eat, but I suspect that Turso will not go out of its way to offer a Public Domain offering or 50 year support in the way that SQLite has.
- slashdev 1y ago> They just use the name for promotional/aspirational purposes. Which feels incredibly icky. The aim is to be compatible with sqlite, and a drop-in replacement for it, so I think it's fair use. > Also, this is a VC backed project. Everyone has to eat, but I suspect that Turso will not go out of its way to offer a Public Domain offering or 50 year support in the way that SQLite has. It's MIT license open-source. And unlike sqlite, encourages outside contribution. For this reason, I think it can "win".
- frumplestlatz 1y agoCalling it “SQLite-compatible” would be one thing. That’s not what they do. They describe it as “the evolution of SQLite”. It’s absolutely inappropriate and appropriative. They’ve been poor community members from the start when they publicized their one-sided spat with SQLite over their contribution policy. The reality is that they are a VC-funded company focused on the “edge database” hypetrain that’s already dying out as it becomes clear that CAP theorem isn’t something you can just pretend doesn’t exist. It’ll very likely be dead in a few years, but even if it’s not, a VC-funded project isn’t a replacement for SQLite. It would take incredibly unique advantages to shift literally the entire world away from SQLite. It’s a new thing, not the next evolution of SQLite.
- slashdev 1y agoThe founders came from ScyllaDb, I wouldn't be so quick to count them out. The repo has a lot of contributors and traction. As long as the company survives, I think it has a bright future.