That’s a bit overzealous. SQLite is great, but it’s not a replacement for a hosted database. Not all data can live on the client. Use SQLite when you have the right use case for it (offline desktop app, etc.)
That’s a bit overzealous. SQLite is great, but it’s not a replacement for a hosted database. Not all data can live on the client. Use SQLite when you have the right use case for it (offline desktop app, etc.)
When you say "client" are you referring to the end user's machine, or the server hosting the application they are talking to?
I only advocate for using SQLite on the server, integrated with the hosting application (i.e. your back-end systems).
Redundant SQLite is not impossible [0] but it is definitely less mature and well-known than replicated MySQL or Postgres.
I personally haven't used it.
What I am curious about is if "Many Small Queries Are Efficient in SQLite" when using the various hosted flavors of SQLite.