I was curious how long it takes for global players to get updated title data and if it only applies at launch/start.
What I'm trying to do is to have a simple patching system for game data so that I can tweak values on the fly. Would you suggest that I use title data or have a separate DB and download from it?
It depends upon the size of the data. Title Data, generally speaking, will be up-to-date on all shards within a few seconds. But if the data is particularly large, a) it could take a bit longer, and b) it would be faster to serve that data from our Content service, which is a CDN (and so, has globally distributed caches). The way to manage your updates in that context would be to include the version in the name of the file, so that you don't have to wait on the file's TTL for it to be updated. You could then store just the filename (the Key) of the latest update in Title Data, so that the client could look it up there, then download the actual content from the CDN service.
Hi Brendan, do the few seconds of waiting time also apply to the "player" title data or is the player title data as fast as the CDN?
Player title data is simply the data for a single user, in a single title. It is not a sharded or cached resource, so it has high consistency (so there isn't a delay to it being updated). But for the scenario described in the original question, it wouldn't be the right thing to use. Title Data (not player title data) is where you write data that you want all players to use the same way - configuration data for the title, for example. Player title data is where you have things like savedata for the player.
3 People are following this question.
