We’re slowly moving our backend functionalities into nakama, one of the thing that we already use is a config json file stored on s3, with version on its storage path
say that
s3://storage/game/1.1.0/config/onlineConfig.json
would have different contents with
s3://storage/game/1.2.0/config/onlineConfig.json
the json itself is roughly 11kb size.
With contents roughly similar to this
{
"generalConfig": {"startingMoney":10000, ..omitted },
"boostersConfig": [{"name":"Blade","power":1, .. omitted}, {"name":"Spear","power":2, .. omitted }],
.. omitted
}
We’re planning to break the json itself into storage collections based on version like this
[
{
"collection": "1.1.0config",
"key": "generalConfig",
"value": "{\"startingMoney\":10000, ..omitted }",
},
{
"collection": "1.1.0config",
"key": "boostersConfig",
"value": "[{\"name\":\"Blade\",\"power\":1, .. omitted}, {\"name\":\"Spear\",\"power\":2, .. omitted }],",
}
]
While on client side, we could just easily read storage by collection, this looks like it’s going to be trouble managing it in the long run, since the amount of collection would grow each subsequent version release
We tried condensing it into only one collection, storing all the contents of 11kb json on the value field, but on nakama dashboard we got http: request body too large error
Any suggestion on how to properly design online config with storage nakama?