Understanding when denormalized NoSQL document models beat normalized relational schemas.
A team stores each user's profile plus their recent activity feed as a single JSON document in a document database, duplicating some data instead of using joins. Which tradeoff BEST describes why this modeling choice is reasonable for a read-heavy feed?