3 ms·
For me, the concern about SQLite has never been if the database engine itself is “reliable for real data”, but that storing data on a single node is not “reliab
by beoberha 5mo ago
For me, the concern about SQLite has never been if the database engine itself is “reliable for real data”, but that storing data on a single node is not “reliable for real data”. Performance aside, what you are positing is no different than dumping everything to a text file on disk. What happens if that VM dies?
- aperrien 5mo agoIf the file is that important, it shouldn't be stored in the VM, but on some sort of more robust storage system.
- ohnei 5mo agoThe standard for pretty much any multiuser app of a reasonable size is a quorum of SQL or noSQL DBs preferably as a single source of truth for all retainable state. Personally, I think foundationDB is the closest to an attempt to make the minimal viable base layer that I've encountered. But C/C++ based and then owned by apple make it not suitable for the role.
- hellcow 5mo agoIt's trivial to set up WAL-based streaming backups. Same thing as you'd have with Postgres on GCP. Restore from your latest backup.
- ramblurr 5mo agoPostgres, MySQL, all of them, they write to files (binary, not text) on your disk. What happens if your postgres VM dies? (Hint: whatever your answer is it'll apply to SQLite too)