Building Without Databases: SQLite, Litestream, and Why Local-First AI Won

The Cloud Database Dogma

For two decades, every backend engineering bootcamp, university syllabus, and cloud architecture guide preached the exact same sermon: your web server must be stateless, and all application state must live in a remote, distributed database cluster connected over a network socket.

In theory, it sounded like enterprise resilience. In practice, it meant that every single page render or agent turn spent 15 to 45 milliseconds waiting on TCP handshakes, TLS negotiation, connection pooling queues, and cloud VPC routing. For high-frequency agent loops, that network latency was an invisible anchor dragging down performance.

The Local-First Alternative: SQLite at 0.04ms

What happens when you eliminate the network socket entirely and keep your database in the exact same memory space as your application code? Query latency drops from 20 milliseconds to 0.04 milliseconds. That is not a marginal upgrade; it is a 500x speedup.