Is there a best practice on how to structure player data. The limit for player data single value is 300k bytes, so is it better to store all info about a character in a single player data key value pair or split them up.
The downside would be needing to rewrite the entire value when making updates, but if I split them up into multiple key-value then I can have more granular control.
I am having trouble understanding whats a good approach here from a design pov, should I be treating a single key value pair as a row in a sql table. And when we get multiple key value pairs, the time complexity is almost the same as getting a single key-value? Or does it matter if I store in a single key value and just rewrite the entire value again when making updates(which feels odd if i want to update a small part of the value but i need to rewrite the entire value)..