I am building a game where many players will be able join publicly available worlds, where the game state would need to be stored in a persistent manner.
Use-case is very similar to Minecraft: An authoritative server model where players do not have direct access to the world state. Only parts of it are sent to each player, and they alter it as they play. (Eg, mining blocks etc.) No player necessarily 'owns' the world. When the last player leaves, before the server would shut down, it would save the last world state, so if players would like to visit it again, it could be restored to how it last was.
There were a few similar, older threads a few years back about similar questions. However, I would like to know what is the current best practice to accomplish something like this?
