We've been using SQLite in production (B2B setting) for almost a decade. Concurrent, multi-user systems too. Sometimes thousands of concurrent users will be hit

We've been using SQLite in production (B2B setting) for almost a decade. Concurrent, multi-user systems too. Sometimes thousands of concurrent users will be hitting the same databases all at the same time. Literally not once have we had an incident related to SQLite/IO corruption or performance. SQLite could handle a billion daily users with just one decent NVMe drive. You don't even have to do anything crazy to make this work. Just pick one of the top 10 techempower web frontends, tack on SQLite and set journal mode to WAL. Oh - try to use the same connection throughout as well. That one trips up a lot of developers used to the hosted SQL patterns. Oh but what about high availability? DQLite, RQLite, et. al. are now ready to take you to the next level. You can also address this in your application logic instead of deferring to your RDBMS vendor (this is our path).