SQLite & Turso/libSQL — decide, connect, operate

SQLite is an in-process, single-file, single-writer relational engine. Turso/libSQL is the fork that adds a remote edge database and — the part people actually want — embedded replicas: a local SQLite file that syncs to a remote primary, so reads are microsecond-local and writes still land durably in the cloud.

This skill is decide + connect + operate. It owns the engine truths (WAL, single writer, pragmas), the three deployment shapes, and wiring the current @libsql/client. It does NOT own schema modeling or type-safe queries (that is drizzle-orm), versioned migration files (that is db-migrations), or backup strategy as a primary task (that is backups).

Is SQLite/Turso the right tool?

Decide first. Picking SQLite for a high-write multi-writer workload is the mistake that wastes a week.