I have multiple games I want to store data for. The data for each player is stored in a single document with a UUID to identify it. The two options I have thought of so far is:. The problem with option 1 is that I do not know how I would get all stats for all games per player while having good performance. Sending a query to each collection simultaneously to get all their stats seems wrong, although I think this is the best option so far. For option 2, I would not be able to create indexes on the fields that needs to be indexed because the number of games and fields per game could be expanded at any time.
It would also be very many read and write operations on a single collection which seems very wrong. We have a known antipatterns of having to many collections and indexes and we should avoid it as much as possible. The MongoDB locking is per document so writing similar objects to the same collection should not interfere with concurrency as long as you hit different documents. Now if you have a large number of attributes that you need to index for search you may consider the attribute pattern for each game.
Thanks for the good reference to Henriks problem. I have bit similar, and did some research about patterns. I have a followup question and thought perhaps it would be ok to continue in this thread, feel free to move or ask me to create a new topic.
User has few paths to complete. Paths have few stages to complete that are basically different games. The data is used to give feedback to the user and also for analytical purposes and exported to olap bq. Different games amount would be less than fifty.
I was thinking something like following, but started thinking that maybe all the stage data should be as key-value pairs? Also if want at some point more detailed data about gameplay for analytical purposes, maybe that data should be in its own collection to prevent not to fill 15 mb limit and because it is not accessed by the app?
