DuckDB vs SQLite
People think DuckDB is just SQLite. Both run inside your program, with no server. SQLite is built for an app's own data, with many small reads and writes. DuckDB is built for sums and counts over millions of rows. Many teams use both, each for its own job.
DuckDB
A small database for sums and counts. It runs inside your own program.
DuckDB is a free, open source database for crunching numbers, and it runs inside your own program. There is no server to install or start. It stores data in columns. So sums and group-bys over millions of rows are fast, even on a laptop. It can query CSV and Parquet files directly, and work with pandas or Polars data in Python. People often call it the SQLite of data work.
SQLite
A tiny SQL database in one file. There is no server to run.
SQLite is a small SQL database that lives in one file, with no server to run. The app reads and writes that file directly. It is built into phones, web browsers and Python, which makes it one of the most used programs in the world. It is perfect for apps, tests and small sites. It is less suited to many users writing at the same moment.
In one line
- DuckDB
- A small database for sums and counts. It runs inside your own program.
- SQLite
- A tiny SQL database in one file. There is no server to run.
These live in different corners of the glossary (Data and Development), which is exactly why they get confused.