0:00 / 0:00
Will Turso Be The Better SQLite? (with Glauber Costa)
Developer Voices
35K subscribers • 14 videos on Hallway
- Recommended by 1 person: 1 on Lobsters.
- Presented by Glauber Costa, co-founder of Turso
- Linked in the descriptiontursodatabase/tursotursodatabase/libsql
Intermediate. Assumes working knowledge.
20K views10 months ago1 recommendation
Databases and dataSystems programmingSQLiteRustDatabase internals
Glauber Costa discusses rewriting SQLite in Rust to build Turso, covering concurrent writes, vector search, and deterministic simulation testing.
SQLite is embedded everywhere - phones, browsers, IoT devices. It's reliable, battle-tested, and feature-rich. But what if you want concurrent writes? Or CDC for streaming changes? Or vector indexes for AI workloads? The SQLite codebase isn't accepting new contributors, and the test suite that makes it so reliable is proprietary. So how do you evolve an embedded database that's effectively frozen? Glauber Costa spent a decade contributing to the Linux kernel at Red Hat, then helped build Scylla, a high-performance rewrite of Cassandra. Now he's applying those lessons to SQLite. After initially forking SQLite (which produced a working business but failed to attract contributors), his team is taking the bolder path: a complete rewrite in Rust called Turso. The project already has features SQLite lacks - vector search, CDC, browser-native async operation - and is using deterministic simulation testing (inspired by TigerBeetle) to match SQLite's legendary reliability without access to its test suite. The conversation covers why rewrites attract contributors where forks don't, how the Linux kernel maintains quality with thousands of contributors, why Pekka's "pet project" jumped from 32 to 64 contributors in a month, and what it takes to build concurrent writes into an embedded database from scratch. -- Support Developer Voices on Patreon: patreon.com/DeveloperVoices Support Developer Voices on YouTube: youtube.com/@DeveloperVoices/join Turso: turso.tech/ Turso GitHub: github.com/tursodatabase/turso libSQL (SQLite fork): github.com/tursodatabase/libsql SQLite: sqlite.org/ Rust: rust-lang.org/ ScyllaDB (Cassandra rewrite): scylladb.com/ Apache Cassandra: cassandra.apache.org/ DuckDB (analytical embedded database): duckdb.org/ MotherDuck (DuckDB cloud): motherduck.com/ dqlite (Canonical distributed SQLite): canonical.com/dqlite TigerBeetle (deterministic simulation testing): tigerbeetle.com/ Redpanda (Kafka alternative): redpanda.com/ Linux Kernel: kernel.org/ Datadog: datadoghq.com/ Glauber Costa on X: x.com/glcst Glauber Costa on GitHub: github.com/glommer Kris on Bluesky: bsky.app/profile/krisajenkins.bsky.social Kris on Mastodon: mastodon.social/@krisajenkins Kris on LinkedIn: linkedin.com/in/krisjenkins/ -- Intro Ten Years Contributing to the Linux Kernel From Linux to Startups: OSv and Scylla Lessons from Scylla: The Power of Ecosystem Compatibility Why SQLite Needs More Open Source But Not Open Contribution Why a Rewrite Attracted Contributors When a Fork Didn't How Deterministic Simulation Testing Works 70% of SQLite in Six Months Features Beyond SQLite: Vector Search, CDC, and Browser Support The Challenge of Adding Concurrent Writes Building a Self-Sustaining Open SourWhy it's here
1 person recommends thisWhat people say. Recommended for its deep dive into the architectural challenges of SQLite and the motivations behind Turso.