This is a continuation of this issue on GitHub:
To give a summery, there are some JSON data stored in
storage table. Clients need to have the latest version of these data to start the game. Let’s call these data definitions.
A couple of questions arise when dealing with definitions.
1- What is the most efficient way to store definitions? Should everything be in one entry, or we should separate them as much as possible?
2- How much data in bytes should we have to even start worrying about database read performance? (i.e., if there is only 1 KB of definitions, it doesn’t really matter what you do. It’s going to be fine)
Also, in the GitHub issue, it was mentioned that we should look which game screen needs definitions at game start. In my use case, we prefer to get all definitions for every game screen at startup to avoid any unnecessary loading time when traveling between game screens.