Query memory limits and disk spilling

An unindexed join field turns one million customers into one million collection scans

MongoDB caps each aggregation stage at 100MB of RAM. How many documents reach the first blocking stage decides whether a pipeline streams or spills, and that count depends on where $match sits and whether the join field is indexed.