Comment by rmbyrro
4 years ago
SQLite is not meant to compete directly with MySQL or Postgres. It's meant for local usage only, where you don't need high concurrency, managing multiple connections, replication, etc.
I mean, you could probably use SQLite in many simple cases which currently use Postgres (personal servers, small apps), but advocating it as default solution is inadequate at best, if not misleading to people starting out in the field.
This view is the view I was talking about in the op.
Inadequate for what? Most persistence layers I've ever seen did not need MySQL, postgres or MongoDB.
> high concurrency, managing multiple connections, replication
In the grand scheme of things, basically nobody needs these things. Sorry, your app is overengineered.
Your app actually suffered in areas such as performance, security, portability, complexity and cost.
Developers love to prematurely optimise everything. Most SaaS products today don't need a dedicated database server. Most apps that require a database server backend would be better with sqlite, most Dev/test/staging/prod pipelines would be better served with sqlite files.