SQLite: The Database in Your Pocket

I once called SQLite the database in your pocket. If you are reading this on a phone, that description is almost literal: every Android device and iPhone contains SQLite. So do Chrome, Firefox, Safari, and many televisions and car entertainment systems.

SQLite’s developers call it the most widely deployed database engine in the world. The “Lite” in its name does not mean that it is a tutorial toy. This is mature, full-featured software that quietly does useful work on billions of devices.

What SQLite actually is

Imagine that a notes app saves a new note. It can ask SQLite to organize the note and write it to storage. The software doing that work is called a database engine.

SQLite itself is not the database file. It is a library inside another program. Our future lending.db file holds the stored data.

Lending program  →  SQLite engine  →  lending.db

The lending program asks SQLite to do some work, and SQLite reads from or writes to the file.

Many database systems run as a separate server that programs contact. SQLite runs inside the program that uses it. That is what embedded database means here, and it leaves us without a database server to install and maintain.

Why SQLite fits this course

Python’s standard library gives us SQLite through the sqlite3 module. We can use a real SQL database without creating an account or starting an online service.

SQLite is compact and economical with memory, storage, and setup. Keeping its engine beside local data also avoids a network trip for every question. It can run efficiently on a phone while remaining useful in serious software.

SQLite is not right for every job. A database that many computers must write to at once may need a system such as PostgreSQL. That is a different setting, not the dividing line between a toy database and a real one.

Now you know what will manage the lending catalog and where its data can live. Next, let us look at how the item facts are arranged inside that database.