I've started using SQLite for all new Apps a couple of years ago and haven't looked back. It was the catalyst for us to get off AWS (and RDS) where we now deplo

I've started using SQLite for all new Apps a couple of years ago and haven't looked back. It was the catalyst for us to get off AWS (and RDS) where we now deploy (.NET) Docker Apps with Kamal to a shared Hetzner Linux VM which uses Litestream for replication to Cloudflare R2. We've adopted several ways to workaround SQLite's single concurrent writer [1] including: splitting system functionality in multiple databases, separate locks per db, performing writes within a single worker thread for each db, etc. Despite being significantly cheaper, its next to zero latency actually performs better than our Apps using RDS. We also benefit from monthly rolling databases for request logs and db jobs and make use of SQLite's Application defined SQL Functions (i.e. calling C# functions in SQL queries) for some features which isn't really possible with other networked RDBMs. [1] https://servicestack.net/posts/scalable-sqlite https://servicestack.net/posts/scalable-sqlite