MongoDB × Bazaarvoice
MongoDB x Bazaarvoice, sharding a billion-document catalog with zero downtime
Zero downtime migration of a billion-document catalog
Capacity crisis to safe, invisible migration
Members read free
Unlock the full breakdown
Enter your email to open every case study in the library: the full screenshot, why it works, and the one thing worth stealing. One email unlocks all of them.
Free. No spam. Unsubscribe anytime.
You're in — enjoy the library.
Why it works
The platform had real demand and data volume already in place, but a hard ceiling (the 2.1 billion document Lucene index limit plus exhausted vertical scaling) was about to choke it entirely. Removing that constraint through sharding unlocked what the system could already handle, producing a direct step-change: 3x faster workload processing and replication lag dropping from hours to near zero. The Black Friday deadline forced a live stress test, and holding up under that load made the result concrete rather than theoretical.
Steal this
The 'nothing changed for clients, but in reality everything had' quote frames a technically disruptive migration as invisible to end users, which directly neutralizes the fear of downtime risk that stalls infrastructure decisions.
Click to enlarge ↗ This is editorial commentary and curation. The case study, screenshot, and all metrics are MongoDB's published work; we link to the source and lead with our analysis.