3 ms·
the reality is very few workloads have access patterns that SQLite can't support. I would much rather start with a strategy like 1. use sqlite for my beta / sin
by skeeter2020 1y ago
the reality is very few workloads have access patterns that SQLite can't support. I would much rather start with a strategy like 1. use sqlite for my beta / single client, 2. duplicate the entire environment for the next n clients, 3. solve the "my application is wildly successful" and SQLite is no longer appropriate problem at a future date. Spoiler: you're never going to get to step #3.
- crazygringo 1y ago> 2. duplicate the entire environment for the next n clients That becomes an instant problem if users ever write to your database. You can't duplicate the environment unless it's read-only. And even if the database is read-only for users, the fact that every time you update it you need to redeploy the database to every client, is pretty annoying. That's why it's usually better to start with Postgres or MySQL. A single source of truth for data makes everything vastly easier.