<- back

# The Most Impressive Database Is Just a File, SQLite

Posted on Jun 15, 2026

Let's go through a hypothetical scenario, imagine that you are building the next cutting edge trillion dollar vibecoded masterpiece web app for mobile, now lets assume that you collect and store user data locally on the device.

Now imagine how you can store this data, maybe you could use text files or .csv files, well this is technically okay but this prevents us from being able to query it, expensive deletion and searching.

If you want to query your data, then you could use SQL servers such as mysql, this is inefficent as you would have to spin up a server and then provide connections on the device, what if you could use SQL without the server, that is SQLite

## History/Origin

SQLite began in 2000 when Richard Hipp was working on software for the U.S Navy's DDG-79 destroyer program. The application needed as datavase but the options where complex and couldn't fit the environment constraints

So Hipp decided to build his own solution

The idea was simple, a database that doesn't need a server

## Where is it used?

It's everywhere, you are probably using it right now...

Android uses it extensively, many desktop applications use it, apple platforms ship with SQLite. The browser relies on SQLite for local storage and internal data management. Apps such as Notion use WASM implementation of SQLite as a client side DB and caching layer to store and query data directly on the user's device

The SQLite website describes it as,

- the most used database engine in the world. SQLite is built into all mobile phones and most computers and comes bundled inside countless other applications that people use every day.

## Three's Company

This massive project that runs on possibly trillions of instances is maintained by just three people.

All of the SQLite source code is public domain, meaning that the authors have dedicated it to the public rather than using a license such as MIT, Apache or GPL (more on that later). You are allowed to modify, distribute and embed it inot commercial products without any licensing requirements

The codebase only has three developers due to their extreme emphasis on testing edge cases, narrow scope and design philosphy of "don't break anything"

Backward compatability is extremely important and having fewer developers reduces complexity

## Too Much Internal Tooling?

Richard Hipp wrote much of his own tooling, the most notable example is Fossil, which is a version control and project management system used to develop SQLite. Fossil includes a built-in wiki, bug tracker, and a web interface.

Richard also wrote his own text editor, reportadly called 'E'

## ACID Compliant

For anyone wondering, yes, SQLite is ACID compliant

## My Favourite License

The license isnt a text of legal slop, its simply:

    /* ** 2005 February 15 **
    ** The author disclaims copyright to this source code. In place of
    ** a legal notice, here is a blessing:
    **
    ** May you do good and not evil.
    ** May you find forgiveness for yourself
    ** and forgive others.
    ** May you share freely, never taking more than
    ** you give.
    **
    *************************************************************************
    ** This file contains C code routines that used to generate VDBE code
    ** that implements the ALTER TABLE command.
    */
    

## Further Reading

SQLite Official Website

Official documentation, source code, architecture notes, and design papers.

SQLite and its weird new fork “libSQL”

How SQLite is structured internally. Why it matters, whats the fork like

SQLite Is ULTIMATE Choice For 99% of Projects

Why SQLite is like a swiss army knife for most projects

SQLite is a masterclass in library design

A deep dive into the SQLite source code and how to design libraries

The Code Inside Everything (That Gets Zero Credit)

Covers everything from the origins to how the company was saved by motorola