2 ms·
You won't find anyone because it would mean that you have a single service talking to SQLite which most webservices won't do for HA reasons, you have a few of t
by Thaxll 4y ago
You won't find anyone because it would mean that you have a single service talking to SQLite which most webservices won't do for HA reasons, you have a few of them behind a loadbalancer.
Using SQLite for any serious webservices is bad thing because you can only have a single app. Then you have other tools on top of SQLite for those shortcoming.
- tptacek 4y agoHaving a single database service as a write master is already commonplace in HA Postgres.
- Thaxll 4y agoRight but they do that over the network not using the filesystem.
- tptacek 4y agoI'm not sure what's complicated about this. Instead of exposing a database instance as the write master, you expose a service as the write master. You can even do it transparently, if your load balancing fabric cooperates: just arrange to have read replicas redirect write requests to the write master.
- avl999 4y agoWith that setup you have essentially lost any benefits that SQLite provides, specifically any performance benefits by making a DB read/write a network call instead of a local call in the same process that manipulates some file on the same machine. You are closer to a postgres/mysql patterne except now your writes don't scale as well. What are we actually gaining with this setup other than perhaps easier administration of the "db service" compared to a mysql/postgres deployment?
- tptacek 4y agoObviously, you have not lost those benefits: reads are satisfied from an in-process database, and, for most applications, most requests are reads.