Referencing often updated parts of document instead of including for performance?

Working with Data
,
2

Hi @Michael_Niemand ,

We usually stand clearly that data that is accessed together should be stored together. So if when you query the data you need all the other fields, regardless of thier update frequency they should be stored together.

Now we have another known antipattern which is dont frequently query large documents and try to avoid getting close to the 16mb limit per document.

Now let me ask you the following :

  1. What is the average size of those large documents? You can see it on the Atlas data explorer when standing on that collection.
  2. Will you need only those frequently updated fields in your access pattern? Then it make sense to seprate them …

Timeseries collection make sense for time series data, I would not assume it is good for other types…

Read here more about what is time series data and why to use timeseries collections…

Thanks
Pavel