IdeaWell

Project ideas from Hacker News discussions.

Turso is an in-process SQL database, compatible with SQLite

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

1. Skepticism Over Turso's Value Proposition and Stability

Many commenters question the fundamental need for a Rust rewrite of SQLite, arguing that SQLite's decades of battle-testing, reliability, and simplicity are superior to Turso's unproven "experimental" features. They express concern about its VC backing, potential for future license changes, and lack of SQLite's extensive test suite. - bawolff: "SQLite is some of the most battle tested software in the world. Turso seems like relatively new software that is still a bit experimental. You do not want your databases to be new or trendy. You want your databases to be solid as a rock." - maxpert: "I have been asked multiple times on why I chose SQLite and not Turso. I've always responded people that I don't trust an open-source project once it's backed by a VC firm." - dgroshev: "This style of development does not inspire confidence. They develop features, sure. But I want my database to be rock-solid and completely covered by tests, not just move fast and break things."

2. Perceived Marketing Misalignment and Lack of Technical Merit

A prevalent theme is that Turso's marketing—as "the next evolution of SQLite"—is offensive, dishonest, or a "marketing spin" that overshadows its actual technical offerings. Commenters feel it overpromises, especially regarding compatibility (e.g., breaking ecosystem tools if extensions are used) and fails to clearly justify its existence over SQLite. - blibble: "the description as 'the next evolution of sqlite' is offensive... I bet this VC funded knockoff won't see 5 [years]." - gpm: "That marketing is really the one thing that keeps me from considering this as a serious option. It's a signal of dishonest intent... why in the world would I use the alternative built by apparently dishonest people?" - rendaw: "They bluntly say you should use it instead of SQLite: 'The next evolution of SQLite'... This not only implies that SQLite has some significant design issues... but it also implies that they, not the SQLite author, are the ones who are capable of doing this. My guess is this is what's rubbing so many people the wrong way."

3. Potential Benefits of Rust Features and Concurrency

Despite the skepticism, there is acknowledgment of specific technical advantages that Turso offers, particularly for modern, asynchronous applications. These include native async support, potential for better concurrent writes (using MVCC), and easier embedding in non-C languages (like Go) without CGO. Some users highlight these as compelling reasons to consider it over SQLite for specific use cases. - loktarogar: "Turso Database is a project to build the next evolution of SQLite in Rust... with features like native async support, vector search, and more." - mattrighetti: "One quick thing I can think of is multiple writers." - gpm: "MVCC is a non-locking algorithm for concurrent writers that the big databases like postgres use... It's not a matter of pushing locks around but allowing multiple threads to operate on the data concurrently." - ako: "I've been using a sqlite alternative to avoid dependencies on a native library. It's go application that uses a native go sqlite reimplementation so i can create platform specific binaries that include all dependencies. Makes installation easier and more reliable."

🚀 Project Ideas

SQLite Vector Index Converter

Summary

  • A command-line tool that reads a standard SQLite database file and extracts any column containing vector embeddings (e.g., float[] stored as BLOB or JSON) into a format compatible with Turso's native vector search extension.
  • Allows users to leverage Turso's vector capabilities without rewriting their existing SQLite applications that store embeddings in standard formats.

Details

Key Value
Target Audience Developers using SQLite for local LLM applications or small-scale RAG who want to migrate to Turso for hosted vector search.
Core Feature Parses SQLite BLOB/JSON data and reconstructs vectors, generating a SQL script to insert data into a Turso database with a VECTOR column.
Tech Stack Rust (for consistency with Turso ecosystem) or Python; uses standard SQLite libraries.
Difficulty Low
Monetization Hobby

Notes

  • HN commenters like netghost expressed frustration with existing SQLite vector extensions: "The sqlite extensions I've tried for vector embeddings have been a challenge to get working." This tool bridges the gap between the easier local development with standard SQLite and the hosted vector features of Turso.
  • High practical utility for developers experimenting with local AI who eventually hit scaling limits but have data stored in non-optimized formats.

LibSQL Go Bindings (No CGO)

Summary

  • A pure Go implementation of the LibSQL client protocol (Turso's engine) that allows Go developers to use Turso databases without relying on CGO.
  • Solves the specific pain point of building cross-platform Go binaries that include database dependencies, which is currently difficult with CGO-reliant SQLite drivers.

Details

Key Value
Target Audience Go developers building CLI tools, serverless functions, or cross-platform applications who want to avoid CGO compilation issues.
Core Feature A Go driver implementing the LibSQL wire protocol, allowing database/sql usage of Turso without linking to C libraries.
Tech Stack Go (using net/http for protocol implementation).
Difficulty Medium
Monetization Hobby

Notes

  • User ako explicitly requested this: "I've been using a sqlite alternative to avoid dependencies on a native library. It's go application that uses a native go sqlite reimplementation so i can create platform specific binaries that include all dependencies."
  • aranw also highlighted the pain: "My biggest pain with using SQLite in Go is often the libraries and the reliance of CGO which is what puts me off using Turso." This project directly addresses that hesitation, potentially increasing Turso adoption.

SQLite Lock Page Visualizer & Validator

Summary

  • A debugging tool that scans an SQLite database file to identify usage of the "lock page" (page 262145), a documented but obscure quirk of the SQLite file format that caused issues for Turso developers.
  • Provides a visual report on page usage and flags databases that might have compatibility issues with non-standard SQLite forks or specific migration tools.

Details

Key Value
Target Audience Database engineers, tool builders, and power users working with custom SQLite VFS or managing large databases (1TB+).
Core Feature Low-level parsing of SQLite page headers to detect the lock page quirk and generate a compatibility report.
Tech Stack Rust (for memory safety and parsing speed) or C.
Difficulty Medium
Monetization Hobby

Notes

  • hiddendoom45 described the difficulty: "I stumbled on the lock page myself when I was experimenting with writing a sqlite vfs... I do recall the lockpage being one of the first things I found where I needed to skip sending page 262145."
  • Joker_vD referenced a specific Turso bug related to this. A tool to visualize this edge case would help developers avoid similar pitfalls when forking or extending SQLite.

Read Later