We're Building Postgres in Rust. Using the LLVM of Databases
turso.tech44 points by polyrand 7 hours ago
44 points by polyrand 7 hours ago
Would be interested in strategic value add versus cedardb (although cedar is closed source in a way that at the moment I think may kill it)
I'm already quite excited about Turso being SQLite-compatible, but adding many features on top.
And when a feature is not directly compatible with SQLite (ie: you can't directly read the file with `sqlite3`, it's straightforward to convert). This is great because you know you'll always be able to continue working with that database. Even if Turso stopped working, it's still a valid SQLite database.
A combination I would be excited about is:
- Full support for Postgres protocol/wire format (ie: Postgres, but in-process, backed by a single file). - Optional: Client/server architecture for further scaling and remote management using existing Postgres tooling - All backed by a SQLite-compatible file
They are already adding MVCC to SQLite anyway. So their effort seems doable, and I hope they succeed.
As someone who doesn't follow databases that closely, how is this different from Amazon Aurora (other than being open source)?
Sounds cool but also why? Is it so it's possible to have 1 database and then switch from sqlite to postgres without data migration?
Author also discussing it on their Twitter [0]. I’m reserving judgement for now, but this has lots of potential usecases even apart from replacing postgres.
People said same thing about sqlite, but I love turso sqlite and haven't faced any issues.
There is no turso sqlite
I don't know if you were being pedantic or confused, but turso is a sqlite3 remake in rust (with some additional features).
The llvm of databases is not turso, it's datafusion.
Will it have fast COUNT-s?