Im looking at protobuf to save app data. Its not small amount of data, however its nature doesnt fit sql nicely, i.e. like 20 types of 1 object, so naively 20 tables of 1 rows didnt make much sense
In essence it looks like this
AppData {
Config
List<StaticDetails>
List<Texts>
UserData {
User
List<Services>
List<Games>
List<Leaderboards>
...
}
}
Does this make sense to model into a single AppData.proto, since protobuf is supposed to be so much smaller and faster?
Currently its lets say 4 json files (config, details, texts, userdata -- appData as such does not exist), because of the fact that there is quite a lot of Texts for example, and if I were to change a single boolean property on a User (not in the sample), that would mean I'd have to serialize unnecessarily lots of Texts data
