Comment by avinassh
1 year ago
disclosure: I work here. I am happy to answer any questions
tl;dr We are rewriting SQLite in Rust. It uses Asynchronous I/O, considers WASM as first class, and has Deterministic Simulation Testing support from the beginning.
Will you release the code into the public domain, like SQLite?
absolutely not.
We're not fans of public domain, which is one of the things that led us to create libSQL in the first place.
It is MIT.
Why not do both? Release as public domain or MIT license. Take your pick.
1 reply →
What's wrong with public domain?
3 replies →
Is your company a member of the SQLite Consortium? https://www.sqlite.org/consortium.html
> It uses Asynchronous I/O
Can it have more than 1 writer?
As of now it has a single writer, same like SQLite. But we plan to add MVCC with multiple writers in the future. Pekka has experimented with MVCC earlier: https://github.com/penberg/tihku
I assume this will need to change the shared memory header protocol so either SQLite comes along for the ride or this is an incompatible ABI?
So a hard fork?
5 replies →
How much has Turso raised so far? Rewriting SQLite sounds like it may cost a sum.
Crunchbase says 7M seed: https://www.crunchbase.com/organization/chiselstrike