“But SQLite is just for toys, right?” No. Here's why it's the right choice for most content sites.

There's a stubborn myth that SQLite is a “test” database. In reality it's one of the most deployed databases in the world, and a perfect fit for content sites.

What SQLite actually is

A full SQL engine in a single file, with no separate server. It doesn't run as a process; it lives inside your app. For a read-heavy, write-light site — i.e. almost any marketing site or blog — it's fast and solid.

Why it works so well for a CMS

  • Reads are very fast — exactly what a visitor does: read pages.
  • WAL mode allows reads alongside writes.
  • Backup = file copy. No dump, no maintenance window.
  • Zero config on hosting: no database to request.

Haloo enables WAL and foreign_keys on every connection and applies migrations idempotently from PHP, so the schema is always current with no manual steps.

Where it is NOT the right fit

If you have hundreds of concurrent writes per second — a huge shop, a platform with thousands of users writing at once — then yes, move to PostgreSQL or MySQL.

The bottom line

For 9 out of 10 real sites, SQLite isn't a compromise. It's the smart choice: fewer moving parts, trivial backups and excellent performance exactly where it counts.