If you follow the current hype cycle, you'd think 'distributed SQLite' was a trend born around 2021. You'll see venture-backed platforms and edge-computing startups pitching it as the next big thing. But the reality is far older. The journey actually started twelve years ago with a project called rqlite, which launched in 2014 to a modest reception of just nine upvotes on Hacker News.
From Raft Logs to Venture Capital
Philip O'Toole, the creator of rqlite, essentially pioneered this category by wrapping SQLite—the world's most used local database—inside a Raft consensus log. This transformed a single-file database into a fault-tolerant, distributed system. Over the last decade, this architectural seed has grown into a diverse ecosystem. We've moved from simple self-hosted clusters to complex managed services and edge-hosted forks like Turso, where the goal is to push data as close to the user as possible.
The Trade-off Tug-of-War
As the category matured, it split into distinct philosophies. On one side, you have the 'CP' (Consistency and Partition tolerance) approach favored by rqlite, prioritizing strict reliability and simple self-hosting. On the other, newer commercial platforms focus on streaming recovery and massive scalability to capture the managed-service market.
This evolution highlights a larger industry shift. For years, we chased 'scalability theater'—over-engineering with microservices and NoSQL just because we could. Now, there is a renewed appreciation for the simplicity of SQLite, provided it can be distributed effectively.
What's Next?
Whether it's through open-source tools or venture-funded clouds, the 'distributed SQLite' movement proves that local-first architecture isn't a limitation—it's a foundation. As we move further into the edge-computing era, the tension between centralized simplicity and distributed power will continue to define how we build the modern web.
Sources
Media
