risinglight
turso
| risinglight | turso | |
|---|---|---|
| 4 | 33 | |
| 1,836 | 19,150 | |
| 0.2% | 3.7% | |
| 5.8 | 10.0 | |
| 10 months ago | 3 days ago | |
| Rust | Rust | |
| Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
risinglight
turso
-
Modern SQLite: Features You Didn't Know It Had
I believe the full docs are here: https://github.com/tursodatabase/turso/blob/main/docs/manual...
-
Deep dive into Turso, the "SQLite rewrite in Rust"
I understand worries about 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
-
How it feels to write a GPKG library in 2026 (in Rust!)
However, this also means we need an SQLite library as a dependency. At least, I cannot imagine writing a full SQLite reader (and a writer) from scratch. This makes build harder especially in case of Rust; Turso is a promising pure-Rust implementation of SQLite, but it's not ready at the moment. As explained above, rusqlite is ready to use. But, as it depends on libsqlite and needs to bundle it in many cases.
- Turso is an in-process SQL database, compatible with SQLite
- Turso: The Next Evolution of SQLite
-
C Is Best
Like this? https://github.com/tursodatabase/turso
Disclaimer: Credit goes to whoever mentioned this in this discussion before me.
-
Stoolap: High-performance embedded SQL database in pure Rust
In the same area, I am tracking the Rust rewrite of sqlite by Turso [1]. The big advantage is the file format compatibility.
[1] https://github.com/tursodatabase/turso
- Apt Rust requirement raises questions
-
Beyond the SQLite Single-Writer Limitation with Concurrent Writes
One ugly thing that stuck with me was the insinuation that SQLite was somehow immoral. Glauber Costa originally attacked SQLite's maintainer with lines like:
> We take our code of conduct seriously, and unlike SQLite, we do not substitute it with an unclear alternative. We strive to foster a community that values diversity, equity, and inclusion. We encourage others to speak up if they feel uncomfortable. https://web.archive.org/web/20221004144141/https://glauberco...
This paragraph was later deleted sometime after the backlash https://itnext.io/sqlite-qemu-all-over-again-aedad19c9a1c Eventually, Turso would release their own Limbo without a code of conduct at all, which it still lacks to this day https://github.com/tursodatabase/turso
The really sad part of that affair is that Richard Hipp and Glauber are both Christians. But in this situation, only one of them seemed to act like one.
-
Why Is SQLite Coded in C
fwiw there's a project doing just that: https://github.com/tursodatabase/turso
they have a blog hinting at some answers as to "why": https://turso.tech/blog/introducing-limbo-a-complete-rewrite...
What are some alternatives?
tonbo - Tonbo is an embedded database for serverless and edge runtimes.
libsql - libSQL is a fork of SQLite that is both Open Source, and Open Contributions.
glaredb - GlareDB: A light and fast SQL database for analytics
limbo - Limbo is a work-in-progress, in-process OLTP database management system, compatible with SQLite. [Moved to: https://github.com/tursodatabase/limbo]
Raphtory - Scalable graph analytics database powered by a multithreaded, vectorized temporal engine, written in Rust
level - Team communication optimized for deep work