3 ms·
Realistic applications can be mostly per-user data, but with a residue of global data (e.g. the tables that list all those beautifully segregated users). Even i
by HelloNurse 2y ago
Realistic applications can be mostly per-user data, but with a residue of global data (e.g. the tables that list all those beautifully segregated users). Even if per-user databases work well and can be managed simply (e.g. doing backups by briefly taking them offline when idle and copying entire files) the global part usually has more requirements (e.g. cannot be shut down for maintenance, requiring "live" backups) and requires greater complexity (for example sharing it through a traditional DBMS network server or through application-layer services).
- vidarh 2y agoThere's rarely any reason for not being able to shut them down, because you can trivially replicate. E.g. I've built systems where the only global piece of data was which backend held which user, and that data was trivially lazily updated via gossip-style protocols. Login requests were broadcast, and the backends responded, and the central services acted only as "backups" storing the most up to date info seen in case a backend happened to be unavailable. The whole thing was trivial to set up. (And you can back up sqlite "live" just fine with some care if you want to, or things like litestream).