3 ms·
Meanwhile here I am wondering why everyone isn’t using SQLite.
by User23 1y ago
Meanwhile here I am wondering why everyone isn’t using SQLite.
- HWR_14 1y agoI thought SQLite's use case was for a single-user local database.
- 0x6c6f6c 1y agoMore like "single process application's database". There are interesting use cases for DB-per-user which can be server or client side, or litestream's continuous backup/sync that can extend it beyond this use case a bit too. You _can_ use SQLite as your service's sole database, if you vertically scale it up and the load isn't too much. It'll handle a reasonable amount of traffic. Once you hit that ceiling though, you'll have to rethink your architecture, and undergo some kind of migration. The common argument for SQLite is deferring complexity of hosting until you've actually reached the type of load you have to use a more complex stack for.
- jimbokun 1y agoIf you can serve all your traffic by a single instance running Sqlite in same process as your application, have at it. If you need to serve your dats across a network to many clients, managing that with SQLite is much trickier.