How to deal with changes in data over NOSQL

We are evaluating the upcoming projects of NoSQL. I tend to think about things in an RDBMS way and have difficulties in conceptualization and lack of normalization.

< /p>

I know that copying data is not considered wrong in NoSQL. What I cannot understand is to modify the data to prevent exceptions.

For example:

You are organizing a series of poker tournaments. You have players,
locations, and tournament events. As I understand it, a tournament
event might contain a location and a collection of players . It does
not need to have all the player data, but if you want to get the names
and home addresses of everyone going to the next tournament, that info
should be in the tournament collection.< /p>

Someone has gotten married and moved, changing their last name and
address. Does the application need to update the player collection and
the tournament collection? Or is my model of the collections wrong? How do
developers “keep track” of where i nformation is duplicated?

The model I have seen recently used has a constant “master” data set (in your case Down, the list of players, the “relationship” simulation with the list of players in each game, where the game records a list of player IDs), and only by running a periodic process on the “master” (master) data. The denormalized list has been updated (in your case, a list of matches with fully populated player data).

In this way, the application only needs to update the master data, and the regular update process will eventually rebuild Unnormalized results.