Question

You are modeling a blogging platform in Azure Cosmos DB for NoSQL. Each Post can have many Tags, and each Tag applies to many Posts (a many-to-many relationship). Tag metadata (name, description, color) is edited rarely but read constantly. Users frequently query 'all posts for a given tag' and 'all tags on a given post'. Tag descriptions must stay reasonably current across the site. Which modeling approach best balances read performance and update maintainability?

Accepted Answer

Store Tags in their own container as the source of truth, and embed only lightweight tag references (tag id plus denormalized name) in each Post.

Answer

Embed the full Tag document (name, description, color) inside every Post that uses it, with no separate Tag container.

Answer

Embed the full list of Post documents inside each Tag document so a tag lookup returns all its posts in one read.

Answer

Create a single container where every Post-Tag combination is stored as a separate item duplicating both the full post body and full tag metadata.