MongoDB Builder Blog
Deep dives into technical concepts, architectures, and innovations with MongoDB.
Practical Guide: CPU Utilization and Network Compression in MongoDB
When operating at scale, even a highly optimized MongoDB deployment can face pressures during peak traffic. In this controlled exercise, we set out to systematically evaluate how different network compression algorithms impact CPU utilization, throughput, and bandwidth consumption under realistic production workloads.
How Auto-Generating Terraform Improved Our APIs and Customer Experience
Enterprise infrastructure increasingly runs declaratively. If a new capability is not available through the Infrastructure as Code (IaC) tool a customer has standardized on, it does not exist for the part of their organization responsible for shipping it to production. For the MongoDB Atlas customers we serve, that tool is overwhelmingly Terraform. And the gap between an Atlas API shipping and the matching resource appearing in the MongoDB Atlas Terraform Provider was four to ten weeks, a function of both the code development required per resource and the bandwidth our team had to maintain the provider alongside competing priorities. Given how central Terraform is to how customers consume Atlas, we wanted it to be a first-class delivery target for new features.
Beyond Benchmarks: Selecting the Best Architecture for Vector Search In Production Workloads
Vector search needs more than similarity matching. AI engineering now demands context and memory engineering with complex infrastructure requirements. At a moderate scale (under 10 million vectors), the performance differences between well-tuned algorithm implementations are often marginal, because index configuration, hardware, and memory allocation tend to matter more than algorithm choice (ANN-Benchmarks). The performance gap between specialized and general-purpose databases has largely closed at moderate scale. The best vector database for production is usually the one that already holds the rest of your data.
Evolving APIs with Confidence at MongoDB Atlas
Delivering a great API experience requires more than just exposing functionality. It requires a consistent design and a scalable process for ongoing improvement. With teams relying more heavily on automation and programmatic integrations, the way an API is designed can make the difference between workflows that “just work” and workflows that are fragile or surprising. For MongoDB Atlas, our unified data platform, the programmatic interface is the Atlas Administration API. This API provides developers with programmatic access to the features across the Atlas platform to deploy, manage, and scale their databases in the cloud.
From Prompt to Production: MongoDB Atlas for Agentic Dev
Vibe coding and LLM-generated code have emerged as a new way for developers to build code. This trend is expected to accelerate over the next few years. With tools like GitHub Copilot, Claude Code, Emergent, Base44, Codex, and other Agentic coding platforms, we're moving into a new era of software development. Instead of just writing code line-by-line, we're guiding, prompting, and iterating with AI partners. According to the Stack Overflow 2025 Survey, 51% of professional developers use AI tools daily.
Why Every AI Workflow Is Really a Data Problem in Disguise
88% of enterprises are using AI in at least one business function. Fewer than 10% are seeing meaningful business impact. That gap isn't explained by model selection. It isn't explained by prompt quality. It's explained by what's underneath.
The Case Against Building Your Own Agent Platform
You know the meeting. The board wants an AI agent strategy by the end of the quarter. Someone on the leadership team has read a McKinsey report. You've been voluntold to build the platform. The slide deck says "AI-native." The acceptance criteria are vague. Somebody mentions LangGraph, and somebody else says, "We'll just wrap it ourselves."
Modernizing Enterprise Content Management with MongoDB
Enterprise Content Management (ECM) is mission-critical to almost every large organization. It underpins how contracts are signed, invoices are archived, citizen records are retained, and how billions of documents are searched and governed every day. Yet most ECM platforms still run on architectures designed decades ago, struggling to keep up with today’s scale, agility, and AI expectations.
Fighting Tool Sprawl: The Case for AI Tool Registries
As enterprise AI agent adoption scales, the absence of centralized, organization-level tool infrastructure is producing compounding costs. When adoption is built around optimizing for deployment speed, enterprises expose themselves to a combination of risks: duplicated engineering effort, security exposure, and operational opacity.