Don't Use SQLite in Production!

Terreateam shares their experiences using Fly.io and SQLite. While Fly.io heavily promotes server-side SQLite, the author argues against using it as a primary data store in production unless there's a compelling reason. This adds complexity with backups, high availability configurations (like LiteFS and Consul), and migration to other databases (like PostgreSQL) becomes challenging. The post uses the Atlantis project as an example, highlighting the high-availability challenges of using database-as-a-library solutions (like BoltDB and SQLite), ultimately recommending a traditional database architecture for production unless there's a very clear need to diverge for better scalability and reliability.