The encyclopedia · Software & IT · Technical decision · 2000–2015
SQLite made the database a file, and became the world's most deployed database
Serverless and zero-config, SQLite embedded SQL into billions of apps instead of asking for an install
SQLite Consortium
the move
In 2000 D. Richard Hipp wanted a SQL engine for a US Navy contract that could not run a database server. He built SQLite as an in-process library: no server process, no configuration, no installation — the entire database is one cross-platform file that applications read and write directly.
The design traded the multi-user concurrency of a server database for radical simplicity: a complete SQL database with tables, indexes, triggers, and views in a single file, with ACID transactions that survive power loss and a test suite that exercises the code under simulated failures.
That shape made SQLite the default embedded database of phones, browsers, cars, appliances, and desktop apps, and the US Library of Congress recommends it as a storage format. The project reports it as the most widely deployed database in the world, with billions of copies in the wild.
why it works
- Zero configuration meant the database worked on first run in any app, with no DBA
- A single cross-platform file is portable across machines, OSes, and endianness
- Public-domain licensing removed every legal and procurement obstacle
- Aviation-grade testing made reliability a feature rivals could not casually claim
what transfers
The lowest-friction version of a technology wins distribution: delete the server, install, and config, and SQL reaches places a full database never could.
what came after
SQLite became the storage engine behind iOS and Android apps, browsers, and countless embedded systems, and its file format is recommended by the Library of Congress for archival. The 'database as a file' idea also shaped newer embedded engines and the industry's default answer to local persistence.
references
spotted an error? The archive wants to know.