# SQLite

847 Hacker News commenters recommended SQLite and 220 criticized it, November 2025 to November 2026. It was recommended in 12 of 13 months; owners who said how long report a median of 2 years (13 owners). It meets the Hacker Approved badge rule.

**Verdict:** An extensively tested, zero-maintenance embedded database that handles far more load than expected for many apps, though concurrent writes and growing server apps can outgrow it.

## Why people recommend it

- Extremely well tested and reliable (7 comments): "Just by its testing and its number of installations (real world testing) you could consider SQLite being more "industrial strength" than any other DB on the market." ([source](https://news.ycombinator.com/item?id=48929806)) "Sqlite is also the only major database to receive DO-178B certification, which allows Sqlite to legally operate in avionic environments and roles." ([source](https://news.ycombinator.com/item?id=47779375)) "SQLite is a good example to bring up because its extensive closed-source tests are what’s often cited as being what keeps people from forking it." ([source](https://news.ycombinator.com/item?id=48842229))
- Simple, no server to maintain (4 comments): "I so far have gone the sqlite route for my hobby apps as it's so easy to handle and doesn't require setting up two docker containers for a single app." ([source](https://news.ycombinator.com/item?id=48329216)) "For a project where sqlite is good enough, just using it plus the amazing sqlite rsync command on a cron job gives you pretty amazing capabilities." ([source](https://news.ycombinator.com/item?id=47930502)) "No version upgrades, no connection limits, no pooler, no failover drill, no separate thing to monitor, no separate thing to pay for" ([source](https://news.ycombinator.com/item?id=48946117))
- Fast enough for most workloads (5 comments): "There are many cases where SQLite + concurrent front end (like a go net/http server) can handle all the load that a service might ever conceivably have to handle" ([source](https://news.ycombinator.com/item?id=48328167)) "Sqlite is essentially a user space queryable file system and it can be faster than writing to file system directly while working with small files." ([source](https://news.ycombinator.com/item?id=48251463)) "these writes are exceptionally fast and are serialized to the file-system anyway, so functionally equivalent to concurrent writes for p50 use case" ([source](https://news.ycombinator.com/item?id=48342943))

## What people warn about

- Outgrown as server apps scale (4 comments): "SQLite has a "lite" in the name for a reason, but it's often pushed into places where it's being asked to do things it was never really designed for." ([source](https://news.ycombinator.com/item?id=49281355)) "My experience with sqlite for server-based apps has been that as your app grows, you almost always eventually need something bigger than sqlite" ([source](https://news.ycombinator.com/item?id=47737996)) "after trying myself I think I'd never reach for it in production because it lacks a lot of power that a database like Postgres has" ([source](https://news.ycombinator.com/item?id=49095113))
- Limited concurrent multi-user writes (3 comments): "I ran into crippling file system race conditions. This was because we were hosted on a distributed file system in the cloud which I learned is very very bad for sqlite." ([source](https://news.ycombinator.com/item?id=48946143)) "ive used sqlite a couple times with WAL to try and make a small app shared between 2-3 people who all would contribute updates thru it but it wasnt ideal" ([source](https://news.ycombinator.com/item?id=46906211)) "in sqlite you need to write some app code to batch transactions in the app, so it has non-trivial development and maintenance cost" ([source](https://news.ycombinator.com/item?id=47744789))
- Needs pragmas and settings for correctness (2 comments): "It's a little frustrating that all this extra cruft is necessary to get the world's most popular RDBMS to take data correctness seriously." ([source](https://news.ycombinator.com/item?id=48875396)) "I agree that SQLite requires less maintenance, but you still need to vacuum to prevent the database file from accumulating space" ([source](https://news.ycombinator.com/item?id=46907807))
- Security and backup corruption risks (3 comments): "SQLite even had single memory write bugs that allowed code execution which lay in the code for 20 years without anyone spotting them." ([source](https://news.ycombinator.com/item?id=47032380)) "But it's timing-dependent: lose the race and you'll end up backing up a partially written transaction, making the backup corrupt." ([source](https://news.ycombinator.com/item?id=48946020)) "Battle tested and tested to hell, maybe yes. But still horrible insecure architecture, with read-only access being able to write." ([source](https://news.ycombinator.com/item?id=49519988))

## Alternatives hackers recommend

- [PGlite](https://hackerapproved.com/p/pglite.md): 49 recommend
- [DuckDB WASM](https://hackerapproved.com/p/duckdb-wasm.md): 11 recommend
- [Stoolap](https://hackerapproved.com/p/stoolap.md): 9 recommend
- [SlateDB](https://hackerapproved.com/p/slatedb.md): 6 recommend
- [SlothDB](https://hackerapproved.com/p/slothdb.md): 6 recommend

## Cite as

Hacker Approved, "SQLite", https://hackerapproved.com/p/sqlite/ (counts from 1,795,640 Hacker News comments, November 2025 to November 2026).