Episode

How MongoDB Rebuilt Its Document Store for Multi-Terabyte Workloads

Podcast
The CTO Podcast with Fexingo: Technical Leadership, Architecture, and Engineering Org
Published
Jun 23, 2026
Duration seconds
589
Processing state
not_requested
Canonical source
https://audio.fexingo.com/business/the-cto-podcast/episode-0069.mp3
Audio
https://audio.fexingo.com/business/the-cto-podcast/episode-0069.mp3
JSON
/v1/public/podcasts/the-cto-podcast-with-fexingo-technical-leadership-architecture-and-engineering-org-7871807/episodes/how-mongodb-rebuilt-its-document-store-for-multi-terabyte-workloads
Markdown
/podcast/the-cto-podcast-with-fexingo-technical-leadership-architecture-and-engineering-org-7871807/how-mongodb-rebuilt-its-document-store-for-multi-terabyte-workloads.md

Actions

  • POST https://stenobird.com/v1/public/podcasts/the-cto-podcast-with-fexingo-technical-leadership-architecture-and-engineering-org-7871807/episodes/how-mongodb-rebuilt-its-document-store-for-multi-terabyte-workloads/transcription-requests
    Idempotently request low-priority transcript generation for this episode.
  • GET https://stenobird.com/podcast/the-cto-podcast-with-fexingo-technical-leadership-architecture-and-engineering-org-7871807/how-mongodb-rebuilt-its-document-store-for-multi-terabyte-workloads.md
    Read the agent-friendly Markdown representation of this episode resource.

Summary

Episode 69 of The CTO Podcast. Lucas and Luna dive into how MongoDB's engineering team redesigned their core storage engine to handle multi-terabyte workloads without sacrificing developer velocity. They break down the specific challenge: a single customer complaint about a 12-terabyte shard that took 47 hours to rebalance. That complaint triggered a two-year effort to rewrite the WiredTiger storage engine's write-ahead log and compression layer. Lucas explains why the old architecture hit a wall at around 8 terabytes per node, and how the team's decision to switch from per-document compression to page-level compression made rebalancing 40x faster. Luna brings in a parallel from her own experience at a fintech startup that hit similar scaling pains. They discuss the trade-offs the MongoDB team made—accepting a 15 percent increase in storage cost per gigabyte in exchange for predictable rebalance times. A concrete look at how one of the most popular NoSQL databases evolved to meet the demands of modern workloads. #MongoDB #WiredTiger #NoSQL #StorageEngine #DatabaseArchitecture #CTOPodcast #TechnicalLeadership #EngineeringOrgs #Scaling #Compression #WriteAheadLog #Rebalancing #MultiTerabyte #FexingoBusiness #BusinessPodcast #BackendEngineering #DatabaseInternals #ProductionEngineering Keep every episode free: buymeacoffee.com/fexingo