Making collections is cheap. Having one or two extra collections and joining data manually when needed isn't too bad. Then business requirements change and mana

Making collections is cheap. Having one or two extra collections and joining data manually when needed isn't too bad. Then business requirements change and management makes you add new features, so you add more collections. One morning you show up to work and realize you're doing all of your joins and aggregates manually. You start devising a plan to switch back to a relational database...