@eniko@gnomon I'm not by any means discouraging you to go for this, but on top of that, anyone with such a server really needs proper frequent backups. It probably also makes sense to ensure whatever system you pick is compatible with making incremental backups so they can be done continuously rather than at long intervals.
@gnomon yeah, this is why i extremely don't want to reinvent this particular wheel. acid compliance is extremely finicky in the details and just as hard to get right and i just don't have the time to do a proper job of that
and i don't want to be the cause of a community server's save file going corrupt after people collectively put in a 1000 hours of play
@eniko those articles by @danluu lay out how difficult it is for filesystems to get robustness guarantees correct while maintaining performance, and as kind of a footnote they also mention how sqlite3 works so hard so maintain robustness that it can sometimes eclipse the guarantees of the underlying filesystem - that is, its coping strategies can be more effective than the FS implementation. (Which feels counterintuitive at first, but makes sense after some pondering.)
hey fedi programmer folks, this isn't urgent but i'm going to have to store my block game's world data in some kind of acid compliant database at some point. do you have any recommendations? it must be a file-based database, obviously. and game data doesn't usually neatly conform to the boring numbered rows with named columns table design of traditional databases for websites and stuff
i think ideally i'd just be able to store raw binary data