When designing data for MongoDB ita not enough to just mentioned the data the user stores but we need to understand how the application uses and present the data.
When a user login to the app what data should he see?
A calendar with the meals.placed on dates in the month?
A list of his meals and the details?
his personal information and summary?
Based on this data it will be easier to determine what data should be stored together, reference or duplicated for ease of queries and updates.
Well it’s not really a calendar. In the frontend it would be a table that represents an entire week of meals separated by user and daytime. For example:
So it sounds like a weekly document storing that information with user meals as a subdocument/array of subdocuments is beneficial for the application presenting layer.