Developer Voices · 2025-12-11 · 1h 51m
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.
What's Worth Knowing In AI Right Now? (with Henry Garner)80 / 100Asciinema: Terminal Recording Done Right (with Marcin Kulik)Building the SpacetimeDB Database, Game-First (with Tyler Cloutier)Can Google's ADK Replace LangChain and MCP? (with Christina Lin)Building Observable Systems with eBPF and Linux (with Mohammed Aboullaite)