<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0">
<channel>
<title>MongoDB | Blog</title>
<description>MongoDB news and information.</description>
<link>https://www.mongodb.com/blog</link><item>
      <title>MongoDB Named a Leader in Gartner® Magic Quadrant™ for Cloud Operational Database Management Systems 2026</title>
      <description><![CDATA[<p>I’m thrilled to share that MongoDB has been named a Leader in the new <a href="https://www.mongodb.com/resources/solutions/use-cases/gartner-magic-quadrant-leader">Gartner Magic Quadrant for Cloud Operational Database Management Systems</a>. </p><p>We believe our placement as a Leader in a brand-new category reflects the investments MongoDB has made in our data platform and the strength of our product offerings. We also believe it reflects the trust our more than 70,000 customers, including ~75% of the Fortune 100, have placed in MongoDB.</p><p>Agents are changing what an operational database has to do: absorb spiky demand, keep context fresh, and keep cost per task down. Here’s how we see MongoDB doing that, and what it means for your next architecture decision.</p><h2>What is the operational database category?</h2><p>This year, the former Gartner Magic Quadrant for Cloud Database Management Systems has been split into separate Magic Quadrant reports for Operational Database and Lakehouse, because we believe the buying criteria and decision-makers associated with each differ. If you’re choosing the database that runs your apps and agents, you now have a report written for that decision.</p><p>Gartner defines the market for cloud operational database management systems (DBMS) as software designed to store and manipulate data and delivered primarily as platform as a service (PaaS) in the cloud. These systems primarily optimize routine business transactions, data writes, and application state management. They prioritize high concurrency and low latency while enforcing transactional guarantees to ensure data integrity.¹</p><p>Put plainly, these systems power the services that the world depends on, from healthcare and telecommunications to card payments and banking, to retail solutions that touch millions of people.</p><h2>Why your data platform is important to AI success</h2><p>I traveled a lot<em> </em>in 2026, meeting with scores of MongoDB customers and partners across dozens of cities (in multiple countries!). One theme kept coming up: the data platform decides whether AI works. A few threads connect what I’ve been hearing:</p><ul><li><p>Agents make demand spikier. Where a person might click a button or two to accomplish a task, an agent will make dozens of calls (and might even spawn other agents). That&#39;s why elasticity matters more than another point of peak throughput.</p></li><li><p>Cost per task, not cost per token or cost per seat, is what organizations looking to control AI spending should focus on. As my colleague Pete Johnson has written, <a href="https://www.cio.com/article/4226223/the-wrong-million-tokens.html">the goal of every org should be spending the right 200K tokens instead of the wrong million</a>. When your operational data, vector search, and reranking live in the same platform, you can filter, retrieve, and rerank in one pipeline—saving money and improving results.</p></li><li><p>One data foundation is simpler to run. Teams build AI applications directly on MongoDB’s intelligent data platform instead of governing separate components. <a href="https://www.mongodb.com/solutions/customer-case-studies/relevance-ai">As Jacky Koh, Co-founder of Relevance AI, put it</a>, “Having both the operational and vector database in the same platform makes managing scale much simpler and managing performance much more effective.” </p></li></ul><p>In our opinion, AI success depends on having the right data platform. MongoDB combines a state-of-the-art operational database with search, vector search, hybrid search, and built-in embedding models that keep context fresh (giving agents the information they need to act reliably). MongoDB also gives customers <a href="https://www.mongodb.com/products/capabilities/run-anywhere">the freedom to run anywhere</a>, helping them move quickly today while enabling them to change deployment postures later.</p><h2>How MongoDB enables (AI) innovation</h2><p>2026 was another big year for MongoDB. Everything we do aims to help organizations move faster, build smarter, and to simplify complex architectures, and 2026 was no different. </p><p>The product releases and capabilities we shared this year reinforce the importance of data to AI success, and underscore how MongoDB is the intelligent data platform for the AI era. Here are some highlights:</p><ul><li><p><strong>MongoDB 9.0 </strong></p></li><ul><li><p><a href="https://www.mongodb.com/products/updates/version-release">9.0 is the fastest</a>, most performant version of MongoDB we’ve ever built, and it’s designed for applications and agents that act on live data. Compared to MongoDB 8.0, transactional workloads in 9.0 achieve up to 20% higher throughput, enabling applications to process more business-critical operations more efficiently. Find-one queries are up to 35% faster, and update-one queries are up to 30% faster. That means more users, transactions, and AI activity before you add infrastructure or re-architect applications. Also now generally available as part of MongoDB 9.0 are <a href="https://www.mongodb.com/company/blog/product-release-announcements/intelligent-workload-management-keeping-your-clusters-available-when-it-matters">Intelligent Workload Management</a>, expanded <a href="https://www.mongodb.com/company/blog/product-release-announcements/queryable-encryption-prefix-suffix-substring-queries-are-now-ga">Queryable Encryption capabilities</a>, and the <a href="https://www.mongodb.com/company/blog/product-release-announcements/extension-for-hibernate-orm-now-ga">MongoDB Extension for Hibernate ORM</a>.</p></li></ul><li><p><strong>Atlas Infinite </strong></p></li><ul><li><p><a href="https://www.mongodb.com/products/platform/atlas-database/deployment-options#atlas-infinite">Atlas Infinite</a> is the largest architectural innovation for MongoDB Atlas ever. It was built for the reality of the agentic era, <a href="https://www.mongodb.com/company/blog/product-release-announcements/ai-demand-constant-unpredictable-extreme-mongodb-is-built-for-it">when demand is constant, unpredictable, and extreme</a>. It absorbs bursts of traffic and scales from prototype to petabyte on the same high-performance foundation, so organizations never outgrow it.</p></li></ul><li><p><strong>Atlas Agent Engine</strong></p></li><ul><li><p><a href="https://www.mongodb.com/products/platform/atlas-agent-engine">Atlas Agent Engine</a> lets developers build, deploy, and govern agents with persistent memory, context, built-in guardrails, and state management. Teams move from prototype to production without stitching together custom state stores, guardrails, and data pipelines.</p></li></ul><li><p><strong>New Voyage AI models and capabilities</strong></p></li><ul><li><p>Voyage AI by MongoDB embedding models and rerankers run next to your operational data, so agents retrieve accurate context in one pipeline instead of several. Recent Voyage AI releases include the <a href="https://blog.voyageai.com/2026/09/30/rerank-3/">Rerank 3 series</a>, <a href="https://blog.voyageai.com/2026/08/13/voyage-code-4/">voyage-code-4</a>, a retrieval model tuned specifically for coding agents, and <a href="https://www.mongodb.com/products/updates/now-ga-automated-embedding-in-atlas-vector-search/">automated embedding in Atlas Vector Search</a>. </p></li></ul></ul><p>And that only scratches the surface; for everything MongoDB has released, and for the latest product news and ways we’ve innovated on behalf of customers, see our <a href="https://www.mongodb.com/products/updates/">What’s New page</a>.</p><h2>Building (for) the road ahead</h2><p><a href="https://www.mongodb.com/company/blog/product-release-announcements/intelligent-data-platform-for-ai-era">To paraphrase MongoDB CEO Dev Ittycheria</a>, we expect that the data layer will eventually become an integral part of every organization’s control plane. As software moves from systems of record to systems that act on their own, the data layer of the tech stack will become ever more important. </p><p>The customers I’ve been meeting say they no longer want software that explains what happened. They need software, and the technology they rely on, to keep pace with what&#39;s happening right now. MongoDB was built for this reality, and we can’t wait to see what’s next. </p><h2>Footnotes</h2><p>Gartner and Magic Quadrant are trademarks of Gartner, Inc. and/or its affiliates.</p><p>Gartner does not endorse any company, vendor, product, or service depicted in its publications, and does not advise technology users to select only those vendors with the highest ratings or other designation. Gartner publications consist of the opinions of Gartner’s business and technology insights organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this publication, including any warranties of merchantability or fitness for a particular purpose. </p><ol><li><a href="https://www.gartner.com/document-reader/document/8622033?ref=TypeAheadSearch&amp;toggle=1&amp;viewType=Full">Gartner, Magic Quadrant for Cloud Operational Database Management Systems, 12 November 2026, Masud Miraz Et Al</a>.</li></ol>]]></description>
      <pubDate>Tue, 17 Nov 2026 18:07:13 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/news/mongodb-named-leader-gartner-magic-quadrant-for-cloud-operational-database-management-systems-2026</link>
      <guid>https://www.mongodb.com/company/blog/news/mongodb-named-leader-gartner-magic-quadrant-for-cloud-operational-database-management-systems-2026</guid>
    </item><item>
      <title>AI Demand is Constant, Unpredictable, and Extreme. MongoDB is Built for It.</title>
      <description><![CDATA[<p>When a huge surge in demand meets limited resources, an awful experience usually isn’t far behind. Fans feel it when trying to compete for concert tickets with bots and scalpers. Diners feel it when they try to get a reservation at a trendy restaurant that’s fully booked for months. Websites and applications feel it when they go viral and get an accidental DDoS from a “Reddit Hug of Death.” </p><p>Unpredictable spikes in demand are only becoming more common, and scaling resources to meet them is hard. In my lifetime, I’ve seen big shifts in the amount of demand systems need to handle. First, the internet era, then the cloud era, we saw increased demand that was often predictable. Think of an annual flash sale or regular seasonality. Things might speed up, with more frequent spikes, but they were still spikes you could plan around.</p><p>Then AI happened. And this is where we live now: demand that’s constant, unpredictable, and extreme, increasing in frequency and intensity at the same time. If the internet era taught customers to expect an instant response, then the AI era is teaching them to expect something else: instant value. You can snap a photo of something you want, and an agent can identify it, buy it, and have it on your doorstep tomorrow. Those capabilities cut both ways. Change now hits every layer underneath faster and harder than before. The user isn&#39;t only human anymore. Agents are in the product too.</p><p>Agents don’t ease in. The second they’re on, they hit your system with massive, simultaneous reads and writes. They also take in and act on more information at once than any team of people ever could. Enterprises need a data layer built for that reality, where the only predictable thing is how unpredictable the load will be. Teams that can scale into those spikes will be the ones that last.</p><h2>Introducing Atlas Infinite</h2><p>Today, we&#39;re announcing Atlas Infinite, the largest architectural innovation for MongoDB Atlas ever. Atlas Infinite is purpose-built to handle the speed of development and unpredictable demand of applications that customers expect, with independent scaling of compute and storage to absorb sudden bursts of traffic.</p><p><a href="https://www.mongodb.com/docs/atlas/infinite/atlas-infinite-landing/">Atlas Infinite</a> is not a new database. It&#39;s a new deployment option within Atlas. Same document model, same drivers and APIs, no code changes required. Also, the current deployment option you know and love as MongoDB Atlas is not going anywhere. It just has a new name, MongoDB Atlas Core. Atlas Core and Atlas Infinite are the two database deployment options within the Atlas platform. You pick the right one for each workload.</p><p>How does Atlas Infinite deal with four key scaling and future-proofing problems organizations are dealing with today? </p><ol><li><p><strong>Scaling delay:</strong> Gone. Atlas Infinite cuts read scaling time by more than 96% compared to Atlas Core. Compute and storage automatically scale independently within minutes, not hours.</p></li><li><p><strong>Storage ceiling:</strong> 10x higher. Atlas Infinite grows with you, from prototype to a petabyte, on the same foundation. You scale on your terms, when you need more performance, not when you run out of room. Atlas Infinite supports replica sets that hold 10x the data of replica sets in Atlas Core. </p></li><li><p><strong>Capacity planning:</strong> No more guesswork. Atlas Infinite meets your needs in real time as you scale up and down. Atlas Infinite also runs more efficiently on the same hardware compared to Atlas Core, so you get nearly triple the performance per dollar.</p></li><li><p><strong>Re-architecture:</strong> Not required. Zero application changes required. Enjoy more elasticity and scalability on literally the same database.</p></li></ol><p>This isn&#39;t only a scalability story. It&#39;s a more capable, more performant engine. Internal tests* using MongoDB 9.0 have shown that Atlas Infinite provides <strong>189% more throughput per dollar </strong>compared with Atlas Core. And customers like Icon Solutions are using it to drive more growth. </p><p>&quot;Atlas Infinite let us process 55% more transactions per second than our equivalent previous setup on MongoDB 8.0, with zero application changes. In payments, that kind of headroom without a re-architecture means faster, more reliable experiences for the customers on the other end of every transaction,&quot; said Mike Wallis, Head of DevOps at Icon Solutions.</p><p>Atlas Infinite is available as a public preview, and I can’t wait for you to try out the next generation of MongoDB Atlas.</p><h2>MongoDB 9.0: The best version of MongoDB ever</h2><p>In addition, we just released the best version of MongoDB ever, <a href="https://www.mongodb.com/products/updates/version-release">MongoDB 9.0</a>. We’ve hardened the core to ensure a rock-solid foundation for the most demanding enterprises, and we’re setting a new bar for security, durability, availability, and performance. </p><p>That bar was already high. <a href="https://www.mongodb.com/company/blog/product-release-announcements/top-4-reasons-to-use-mongodb-8-0">MongoDB 8.0</a> was released just two years ago, and today, nearly 80% of our Atlas fleet has adopted it, with higher customer satisfaction and stronger retention among these customers.</p><p>We are proud of what 8.0 delivered, and 9.0 pushes further still. Here are some of my favorite enhancements in MongoDB 9.0.</p><p>Performance*:  </p><ul><li><p>In our internal tests against MongoDB 8.0, MongoDB 9.0 delivers:</p></li><ul><li><p>Up to 35% faster find-one queries</p></li><li><p>Up to 30% faster update-one queries</p></li><li><p>Up to 2x throughput on large instances</p></li><li><p>Up to 20% higher throughput for transactional workloads</p></li></ul></ul><p>Security:</p><ul><li><p><a href="https://www.mongodb.com/docs/manual/core/queryable-encryption/">Queryable Encryption</a> now supports prefix, suffix, and substring searches, allowing organizations to query sensitive information without ever decrypting it. </p></li><li><p>Expanded private networking capabilities make it easier to deploy MongoDB Atlas securely across complex enterprise environments. </p></li></ul><p>Durability and Availability:</p><ul><li><p><a href="https://www.mongodb.com/docs/atlas/intelligent-workload-management/?interface=atlas-ui#std-label-intelligent-workload-management">Intelligent Workload Management</a> automatically protects clusters when they are overloaded with requests and ensures short-running operations continue when demand is unpredictable.</p></li><li><p>Enhanced backup, restore, and recovery capabilities help organizations to maintain application availability and speed recovery when disruptions occur. </p></li></ul><p>Observability &amp; Developer Productivity:</p><ul><li><p>Expanded observability into application and database performance</p></li><li><p>New developer productivity features that make it easier to modernize applications with familiar tools and frameworks, without costly rewrites.</p></li></ul><p>MongoDB 9.0 continues to give you the freedom to run anywhere. MongoDB 9.0 is available in MongoDB Atlas and in self-managed environments through <a href="https://www.mongodb.com/products/self-managed/enterprise-advanced">MongoDB Enterprise Advanced</a> and <a href="https://www.mongodb.com/products/self-managed/community-edition">MongoDB Community Edition</a>. </p><p>MongoDB 9.0 on Atlas Infinite changes the calculus on scale. It&#39;s not something you plan around anymore, it&#39;s just there when you need it. There&#39;s never been a better time to build on MongoDB.</p><p><em>*Performance results are based on internal MongoDB testing comparing MongoDB 9.0 and MongoDB 8.0 using public benchmark methodologies. Results may vary by workload, deployment, hardware, and configuration.</em></p>]]></description>
      <pubDate>Tue, 17 Nov 2026 16:36:12 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/product-release-announcements/ai-demand-constant-unpredictable-extreme-mongodb-is-built-for-it</link>
      <guid>https://www.mongodb.com/company/blog/product-release-announcements/ai-demand-constant-unpredictable-extreme-mongodb-is-built-for-it</guid>
    </item><item>
      <title>Agentic Treasury: How AI Agents Turn Cash Blind Spots Into Real-Time, Governed Action</title>
      <description><![CDATA[<p>At 8 a.m., a $4 million payroll is due, but an expected customer payment hasn’t arrived. Leafy International’s treasury agent spots the gap in live payment data. It checks current balances and recommends a cash sweep from an overnight deposit. It’s enough to fund payroll while keeping Leafy’s $1 million minimum cash buffer intact.</p><p>Just as the treasurer reviews the proposal, an approved, time-stamped market feed flags a material EUR/USD move after a central bank announcement. The agent connects the signal to Leafy’s upcoming euro payment, refreshes the exposure, and flags it for review. A market alert is a reason to reassess, not permission to trade.</p><p>The treasurer views the rationale, data source, and update time, and then approves or delegates within the agreed mandate. If a balance, payment status, or foreign exchange (FX) rate changes before execution, the agent checks again. This is agentic treasury: Monitoring relevant conditions, recommending next steps, and helping carry them out only when authorized.</p><p>Leafy International is fictional, but the pressures and actions are real. Treasury teams are exploring how AI can improve decisions across payments, cash, working capital, and financial risk—and how to govern these systems.</p><p>Agentic treasury has two key requirements: </p><ul><li><p>Context that stays current as balances, payments, and markets move</p></li><li><p>An independent check that confirms each action is authorized before it runs. </p></li></ul><p>MongoDB provides the data layer for both, keeping the agent&#39;s context fresh as conditions change, and holding the controls and audit log that decide what the agent is allowed to do.</p><h2>The industry shift to AI action</h2><p>Cash and liquidity optimization remain persistent challenges for treasury teams. Nearly two-thirds of people <a href="https://finance.yahoo.com/technology/ai/articles/afp-survey-ai-priorities-rise-143300675.html">surveyed by AFP</a> cite cash management and forecasting as a top priority, while nearly 50% say they’re concerned about liquidity and cash planning. For the first time, AI and automation also ranked among the top five priorities, cited by 30% of respondents.</p><p><a href="https://www.citigroup.com/global/insights/mea-treasury-a-shift-in-how-transformation-is-delivered">Similarly, Citi’s 2026 MEA treasury survey</a> highlights that half of those surveyed point to cash visibility and forecasting and liquidity optimization as their biggest concerns. </p><p>Interest is already turning into practice. According to Strategic Treasurer&#39;s<a href="https://strategictreasurer.com/2025-ai-survey/"> 2025 AI in Treasury &amp; Finance Survey</a>, 22% of companies already use agentic AI, with 18% reporting active use within their own treasury or finance department. Beyond current use, 25% are actively testing agentic tools, 32% have experimented with them, and 72% say they understand the technology.</p><p>Adoption is early, but agentic AI is no longer hypothetical. The opportunity lies in delivering timely, consolidated context that surfaces liquidity gaps earlier. This frees treasurers to focus on judgment and exceptions rather than monitoring out-of-date dashboards.</p><h2>From batch snapshots to continuous operations</h2><p>Traditional treasury workflows rely on batch processing of morning balance files and end-of-day reporting. This lag exposes teams to intraday liquidity risks and unhedged FX volatility. A continuous, real-time view of cash positioning and market data enables proactive liquidity management and dynamic risk mitigation.</p><p>Treasury agents need current, decision-ready context across authorized balances, payment and receipt status, deposit terms, FX rates, and relevant events. Not every signal update calls for action. The agents reassess only when a material signal could change a decision. Freshness should match urgency since payroll cutoffs need tighter checks than overnight-surplus reviews.</p><p>A continuous operating model runs on a repeatable loop:</p><ol><li><p><strong>Sense:</strong> Gather the current context (e.g., authorized balances, payment and receipt status, market signals) with each source and update time visible.</p></li><li><p><strong>Plan:</strong> Compare the projected cash position with what must be funded, such as payroll and the required buffer. Identify any surplus available to deploy.</p></li><li><p><strong>Propose:</strong> Explain a specific action, its rationale, and its expected effect on cash or exposure.</p></li><li><p><strong>Check and act:</strong> Confirm that the action is authorized and the data is fresh enough for the decision’s urgency. Then execute, request approval, or stop.</p></li></ol><h2>The contextual layer: 4 data capabilities an agent needs</h2><p>An agent is only as trustworthy as its context: balances, payments, market signals, policy, and memory, each with its source and age visible. Four data capabilities keep that context current and useful.</p><h3>1. Detect relevant changes</h3><p>Relevant events can include an overdue payment, a payment-status change, or an authorized FX or news feed. After the application ingests an external update into MongoDB,<a href="https://www.mongodb.com/docs/manual/change-streams/"> change streams</a> can notify an agent of the change. The agent then refreshes its context and reassesses. <a href="https://www.mongodb.com/docs/atlas/atlas-ui/triggers/">Atlas Database Triggers</a> build on change streams and automatically run a function when a matching change occurs, such as a payment-status update.</p><h3>2. Absorb new shapes of information</h3><p>Suppose an ISO 20022 feed adds a <em>remittancePurpose</em> field. Teams can validate and map it without reshaping historical payment information. MongoDB’s flexible document model lets new payments include the field while older ones retain their shape.</p><p>With <a href="https://www.mongodb.com/docs/manual/core/schema-validation/">schema validation</a>, teams can require the <em>remittancePurpose</em> field on every new payment and block writes that break the rules at the database level. <a href="https://www.mongodb.com/docs/manual/core/schema-validation/specify-validation-level/">Validation levels</a> and actions control how strictly those rules apply, so teams can roll out enforcement gradually without rewriting historical payments.</p><h3>3. Retrieve by meaning, not just keywords</h3><p>Explaining a recommendation may require market events, FX trends, invoice or remittance details, and the policy governing the decision.<a href="https://www.mongodb.com/docs/vector-search/"> MongoDB Vector Search</a> retrieves by semantic meaning and can rank candidates by relevance.<a href="https://www.mongodb.com/docs/vector-search/#automated-embedding"> Automated Embedding</a> generates embeddings inside MongoDB, reducing the need for a separate pipeline. Keeping context alongside balances and payments helps connect relevant evidence to a decision.</p><h3>4. Remember with agent memory</h3><p>Short-term memory tracks the current payroll run, balances, and pending approvals. Long-term memory preserves reusable context, such as payroll calendars and target buffers. Time-sensitive details can expire while useful context carries forward. Proposed actions, checks, and outcomes remain in the audit log. These are among the approaches for <a href="https://www.mongodb.com/resources/basics/artificial-intelligence/agent-memory">managing agent memory with MongoDB</a>.</p><h2>Make delegation safe by design</h2><p>Dependable agentic treasury requires decision-ready context and an independent, governed check before action. Timely data does not authorize action.</p><p>The Monetary Authority of Singapore’s<a href="https://www.mas.gov.sg/publications/monographs-or-information-paper/2026/safeguards-for-agentic-finance-at-runtime"> Safeguards for Agentic Finance at Runtime (SAFR)</a> offers what law firm <a href="https://www.ashurstperkinscoie.com/en/insights/mas-safr-explained-singapores-runtime-governance-standard-for-agentic-ai-in-finance/">Ashurst Perkins Coie</a> calls the first reference framework of its kind for governing AI agents in financial services at runtime. It is not a regulatory compliance checklist.</p><p>In this framework, the agent submits a governance envelope containing the proposed action, its action trace, and relevant context. Four components work through that envelope:</p><ul><li><p><strong>Agent identity:</strong> Verifies the registered agent.</p></li><li><p><strong>Controls repository:</strong> Supplies the policy, regulatory, and delegated-authority controls that the disposition engine applies.</p></li><li><p><strong>Disposition engine:</strong> Evaluates each proposal against those controls and decides the outcome.</p></li><li><p><strong>Audit log:</strong> Keeps a tamper-evident, append-only record of the envelope, mandate, checks, and outcome.</p></li></ul><p>In the cash sweep example, the agent first assembles the context it needs: its authority, the deposit terms, the current balance, pending payments, and the freshness of the data. If a material input is stale, the agent refreshes it or pauses before submitting the action for governance. The check returns one of four outcomes:</p><ul><li><p><strong>Auto-execute:</strong> The action is routine, within mandate, and passes all checks.</p></li><li><p><strong>Observe:</strong> The action proceeds, but is flagged for monitoring and later review.</p></li><li><p><strong>Escalate:</strong> The action may be appropriate, but needs an authorized approver.</p></li><li><p><strong>Deny:</strong> The action conflicts with a hard limit, customer instruction, or restriction.</p></li></ul><p>Governance data also varies in shape. Policies, delegated-authority limits, action traces, and check results differ by product, jurisdiction, and mandate. This variety suits MongoDB’s flexible document model. </p><p>An FX hedge and a cash sweep, for example, have different structures yet both belong in the same governance envelope. A document can take the shape each action needs and can change as execution unfolds. No rigid, predefined table design is required.</p><p><strong>Figure 1.</strong> One collection, different document structures: An FX hedge and a cash sweep each carry the fields their action needs, side by side as part of the governance envelope.</p><p>Hosting the controls repository, governance envelopes, and audit log in MongoDB puts the controls alongside the data they govern. The disposition engine then decides each outcome on current data rather than a copy, and the audit log shows what the engine relied on.</p><p>Independence also matters. The agent can submit an envelope, but it should not be able to change the controls it is judged against or rewrite the audit log. An insert-only audit role is a practical baseline against changes by the application. For higher assurance, safeguards such as application-level hash chaining or replication to immutable storage add independent tamper evidence.</p><p><strong>Figure 2.</strong> From real-time data to governed action: One data layer keeps the agent’s context current, and an independent check decides whether each proposal proceeds.</p><h2>Governed agents across treasury</h2><p>The same governed approach applies to other recurring decisions:</p><ul><li><p><strong>Invest surplus cash:</strong> Once obligations are covered, the agent can propose an overnight placement with an approved institution within concentration and maturity limits. The agent can compare options—such as dynamic discounting or supply-chain finance—on effective return, funding cost, supplier participation, and fees, and not just the headline rate.</p></li><li><p><strong>Hedge a foreign-currency payable:</strong> Leafy owes €2 million in 60 days, but holds U.S. dollars. A material FX move or credible news-sentiment shift prompts a fresh exposure check rather than an automatic trade. If policy calls for hedging 60% to 90% of the exposure, the agent could propose buying €1.5 million through a forward contract (75% of the exposure). The proposal shows the source, time stamp, and rationale for the treasurer&#39;s review.</p></li><li><p><strong>Pool cash across subsidiaries:</strong> Before proposing an intercompany transfer, the agent checks the authorized route, timing, local restrictions, and cutoffs. If the route is not permitted or the information is stale, the agent pauses or blocks the proposal and explains why.</p></li></ul><h2>Start small, build confidence</h2><p>Agentic AI in treasury doesn’t have to begin with autonomous execution. Choose one recurring, measurable use case, such as monitoring liquidity ahead of payroll. Compare recommendations with outcomes, strengthen the data and controls, and learn from implementation. Expand to approval-based actions, then automate only routine decisions that stay within mandate.</p><p>The next 8 a.m. liquidity surprise is coming. Have your treasury’s answer ready before the surprise becomes a problem.</p>]]></description>
      <pubDate>Tue, 17 Nov 2026 15:00:03 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/agentic-treasury-how-ai-agents-turn-cash-blind-spots-into-real-time-governed-action</link>
      <guid>https://www.mongodb.com/company/blog/innovation/agentic-treasury-how-ai-agents-turn-cash-blind-spots-into-real-time-governed-action</guid>
    </item><item>
      <title>Build Once, Grow Freely: Search and Vector Search on Atlas Infinite</title>
      <description><![CDATA[<p>Enterprise workloads are getting bigger, more variable, and harder to predict, especially as agentic applications introduce spiky, unpredictable demand. Most data platforms weren&#39;t built for this reality—to cope with demand, they bolt AI services onto aging architecture, leaving customers to manage, monitor, and pay for multiple systems to get the job done. That fragmentation slows your teams down and limits how fast and how far your agentic applications can run.</p><p>In a traditional database architecture, storage is tied to the machine that runs your queries. Scaling up, adding a replica, or restoring a backup comes down to copying data from one machine to another, and the bigger the database, the longer that takes. My colleague Abhishek Chauhan calls this “storage gravity.” “Data doesn’t want to move,” he wrote for the <a href="https://www.mongodb.com/company/blog/engineering/ground-beneath-database">MongoDB Engineering Blog</a>. The bigger the data gets, the harder it pulls.</p><p>MongoDB built <a href="https://www.mongodb.com/docs/atlas/infinite/atlas-infinite-landing/">Atlas Infinite</a> precisely for this reality; purpose-built to absorb spikes in demand with flexible, elastic scaling. Whether you’re launching a first prototype or running at petabyte-scale in production, Atlas Infinite enables you to build on a foundation that scales with you and never forces re-architecture. <strong>With </strong><a href="https://www.mongodb.com/products/platform/atlas-search"><strong>MongoDB Search </strong></a><strong>and </strong><a href="https://www.mongodb.com/products/platform/atlas-vector-search"><strong>Vector Search</strong></a><strong> supported on Atlas Infinite in public preview</strong>, your database and retrieval live in one platform, with nothing to stitch together.</p><h2>How Atlas Infinite works</h2><p>A new deployment option within MongoDB Atlas, Atlas Infinite separates compute from storage so each scales independently and rapidly. Storage moves into a fully managed layer that handles replication, durability, and backup across availability zones, so compute no longer has to carry the data with it. </p><p>The impact is dramatic. Read replicas come online in minutes because there&#39;s no data to copy. A single shard holds up to 128 TB, so you no longer shard just to add disk space. You only pay for the data you store, not capacity provisioned in advance, so a small team never has to buy a bigger compute tier just to get more disk. And it’s all driven by the same MongoDB API, drivers, and tooling, so your application doesn’t need to change.</p><p>The separation of storage and compute matters most where agentic applications grow fastest: the retrieval layer. Every answer an assistant gives and every step an agent takes starts with a search over your data, and the data behind that search, especially vector embeddings, can grow large quickly. With MongoDB Search and Vector Search running natively on Atlas Infinite, that data lives on the same foundation as the rest of your application and can grow without re-architecture. Build your agentic workload once and keep scaling it on the same foundation as demand grows.</p><p><strong>Figure 1.</strong> Compute and storage as independent layers in Atlas Infinite.</p><h2>Retrieval, built into the database</h2><p>Many retrieval stacks are cobbled together from disconnected components—a database, a search engine, and a vector database—which means running all of those separate parts, plus managing the pipelines that keep everything in sync. On Atlas Infinite, retrieval is part of the platform, so there are fewer pieces to build, secure, and maintain. Here is what that looks like:</p><ul><li><strong>One platform, nothing to stitch together:</strong> On Atlas Infinite, your database and retrieval work together seamlessly, with no separate search engine or vector database to stand up, sync, or monitor. MongoDB Atlas keeps your indexes in sync with your data automatically, so there is no pipeline for your team to build or maintain, and no extra systems to copy sensitive data into or secure. With Atlas Infinite, retrieval is built in, alongside the ability to scale to absorb unpredictable demand with zero waste.</li><li><strong>Start small, never outgrow your data platform:</strong> A team can start with a 5GB prototype that includes semantic search and keep building on the same foundation. Rather than sizing and maintaining two infrastructures, storage grows automatically with your data, billed only for what you store. The operational data behind your search has room to grow to petabyte scale on Atlas Infinite, with no re-platforming when the application takes off.</li><li><strong>Agent memory and context retrieval: </strong>Give agents one place to store and retrieve context, history, and state alongside your operational data. Support thousands of agents hitting your retrieval layer while also persisting agent memory and context within a single, durable system that scales when they need it.</li></ul><p><strong>Figure 2. </strong>Search and Vector Search run alongside the database on Atlas Infinite, with indexes kept in sync automatically and data stored once in Atlas-managed storage.</p><h2>How Atlas Infinite handles your largest text and vector workloads</h2><p>Separating compute from storage in the database also changes the scaling behavior and economics of large retrieval workloads. Text and vector data lives in the database first, where it drives storage requirements. Because Atlas Infinite manages that storage separately from compute, the economics come down to one property of the data: how well it compresses.</p><p>Databases shrink data on disk with compression, which works by finding repetition. Text is full of repetition: common words, repeated field names, predictable structure. Text in MongoDB typically compresses to about 40% of its original size. An embedding is an array of decimal values with almost no repetition, so it shrinks by only about 13%. In practice, a vector takes up as much space on disk as it does in your application.</p><h3>How each deployment option stores that data</h3><p><a href="https://www.mongodb.com/products/platform/atlas-database/deployment-options">Atlas Core</a> uses attached storage volumes. Each node in a replica set keeps a full copy of the data on its own disk, provisioned ahead of time with room to grow, and compute and storage come in matched tiers. That gives every node complete isolation and predictable performance, and it&#39;s the right fit for many workloads, especially ones where data and query load grow together.</p><p>Vector workloads tend to be storage-driven because high-dimension embeddings are so large. A <a href="https://www.mongodb.com/docs/vector-search/tutorials/rag/?embedding=auto&amp;language-no-interface=python&amp;embedding-model=voyage&amp;llm=openai">RAG</a> knowledge base can hold hundreds of gigabytes of embeddings, which drives up storage needs relative to query volume. On Atlas Core, storage can drive scaling decisions: once you outgrow a tier’s maximum disk size, you have to move up a tier to get more storage, even if you don’t need more compute, and very large datasets eventually call for sharding.</p><p>On Atlas Infinite, compute and storage scale independently. Storage is billed per logical (uncompressed) GB of data you store, metered hourly. Replication across availability zones happens inside the storage layer and isn&#39;t billed separately. There&#39;s no headroom to provision, and because a shard holds up to 128 TB, a growing dataset doesn&#39;t push you to a larger compute tier or to more shards. Because embeddings barely compress, their logical size and their size on disk are nearly the same, so you pay only for the data you store and nothing for the copies and headroom underneath it. As vector collections grow to hundreds of millions of documents, that billing model becomes an advantage.</p><p>Here is an example. For a collection with 100 million documents, each with a 1,024-dimension float32 embedding and about 1 KB of other fields, storage is roughly 500 GB uncompressed.  Assuming moderate query traffic, an M30 cluster tier’s compute is sufficient.</p><p>On Atlas Core, since embeddings barely compress, the data shrinks to ~435GB on disk. Each node also needs space for the oplog and room for the collection to grow. At 1.3× headroom, that comes to about 565 GB per node, more than the 512 GB an M30 supports, so the cluster has to move up to an M40 for the disk. On Atlas Infinite, the cluster stays at the compute tier its queries need, and storage is billed once on the 500 GB it holds. With storage billed once and no tier-up for disk, the total monthly cost of this deployment, Search Nodes included, comes out about 25% lower than on Core. At 1 billion vectors (about 5 TB), it is about 30% lower, and the gap keeps widening as vector data grows. These figures are modeled on list prices in US East, with Search Nodes sized to the smallest tier that fits the index, so your results will vary.</p><h3>Where the difference is smaller</h3><p>Text-heavy search workloads also see a TCO benefit on Atlas Infinite, around 5% to 10% cost reduction at multi-terabyte scale. Text compresses well, so Core&#39;s storage cost per GB is already low. The advantage of Atlas Infinite comes from deferring early tier-ups and delaying sharding for disk. Under 500 GB, the two deployment options are roughly even on cost, so a smaller workload gets Atlas Infinite’s room to grow without paying more for it. Choose the deployment option based on the elasticity and growth you expect.</p><h2>Get started with Search and Vector Search on Atlas Infinite</h2><p>MongoDB Search and Vector Search are available on Atlas Infinite in public preview on AWS. Choose Atlas Infinite as the deployment option for your next workload, add a search index the way you would on Atlas Core, and keep building on the same foundation as your application grows. Whether you’re prototyping an AI feature or running a large production application, you can start small and keep going. Start with the <a href="https://www.mongodb.com/docs/atlas/infinite/atlas-infinite-landing/">Atlas Infinite documentation</a>.</p>]]></description>
      <pubDate>Tue, 17 Nov 2026 15:00:03 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/product-release-announcements/build-once-grow-freely-search-vector-search-on-atlas-infinite</link>
      <guid>https://www.mongodb.com/company/blog/product-release-announcements/build-once-grow-freely-search-vector-search-on-atlas-infinite</guid>
    </item><item>
      <title>MongoDB Acquires Firebolt to Bring Lightning-Fast Real-Time Analytics Into Its Intelligent Data Platform</title>
      <description><![CDATA[<p><em><strong>Real-time analytics on live operational data, built so applications and AI agents can act on what’s happening now.</strong></em></p><p>The most valuable analytics no longer live in a dashboard. They live inside the application. A logistics app reroutes a shipment around a delay. A retail system reorders inventory before the shelf goes empty. A payments platform flags unusual behavior before the transaction clears.</p><p>Each of these decisions requires comparing live operational data against historical patterns. Which routes are backing up, and is that normal? What’s selling faster than usual, and should we restock? Is this login typical for this account at this time of day? Enterprises that can answer these questions in the moment adapt as conditions change. Those that can’t are reacting to yesterday.</p><p>Data infrastructure has long been split into two worlds: operational databases that run applications, and data warehouses that analyze what already happened. That paradigm was built for humans looking at morning dashboards, where data a few hours or days old was fine. As analytics moved into applications, real-time analytics emerged as a category of its own, combining complex queries over massive datasets with the speed, freshness, and concurrency that live applications demand. Agents raise the bar on all three. They act continuously, can drive thousands of concurrent queries, and need sub-second answers on fresh data. As businesses rely more on agents, real-time analytics becomes a core part of their data infrastructure.</p><h2>Eliminate the data-movement tax</h2><p>Running analytics on operational data often means copying it into a separate system, forcing organizations to build and maintain data pipelines, keep systems in sync, and run yet another platform. Even once the data is flowing, the added complexity, operational overhead, infrastructure cost, and risk of stale answers remain. This is the data-movement tax, and it compounds as agents drive more decisions.</p><p>Systems that require customers to move and synchronize data across separate platforms often struggle to deliver fresh answers at the speed and scale that live applications need. For MongoDB customers, the operational data their applications and agents rely on is already in MongoDB, so analytics should be able to run there too, at the source. That&#39;s why MongoDB acquired Firebolt.</p><h2>One platform for operational data and real-time analytics</h2><p>By integrating Firebolt into MongoDB’s Intelligent Data Platform, we’re bringing a high-performance analytics engine to where your operational data already lives. Firebolt’s engine will run right alongside your database, and we’ll keep it in sync automatically, so there’s no pipeline to build or manage. You’ll get one platform for operational and real-time analytical workloads, so teams can ship faster, with fewer systems to operate and secure.</p><p>Our Intelligent Data Platform already brings together operational data, search and vector search, Voyage AI models, stream processing, and the ability to build and run agents in production. Real-time analytics will extend that foundation, enabling applications and agents to analyze live data and act on it in the moment. Over time, customers will also be able to analyze data from other sources and formats alongside their MongoDB data.</p><p>When analytics powers a live application, an outage no longer just delays a report. It breaks the customer experience or stalls an agent mid-decision. MongoDB operates in this mission-critical world: today, approximately 75% of the Fortune 100 trust MongoDB with applications that require the highest levels of security, durability, and availability. We’re bringing that same level of reliability and operational excellence to real-time analytics.</p><h2>Why Firebolt, and what’s next</h2><p>Firebolt’s analytics engine is proven in production. It was built from the start for the high concurrency required by live applications and agents, not just internal dashboards and reports. Similarweb, for example, uses Firebolt to power complex, customer-facing analytics over more than a trillion rows at petabyte scale, with dynamic queries delivering sub-second performance without extensive pre-aggregation.</p><p>Firebolt’s team has tackled some of the hardest problems in analytical engines. CEO Benjamin Wagner’s background is in analytical database research at the Technical University of Munich. He built the Munich engineering team behind Firebolt’s engine and led engineering before becoming CEO. CTO Mosha Pasumansky was an architect of Microsoft Analysis Services, co-invented the MDX query language, and led the technical development of Dremel and BigQuery at Google.</p><p>“Firebolt was designed for the cloud to do what many people believed was impossible: low-latency, high-QPS analytics with fast-changing data on object storage,” says Mosha Pasumansky, Firebolt’s CTO. “We also knew that today’s applications deal with complex and flexible schemas, the kind MongoDB’s document model supports natively. So we made sure to keep the benefits of columnar storage and vectorized processing on those schemas through smart automatic column shredding.”</p><p>“Firebolt and MongoDB share the same DNA,” says Benjamin Wagner, Firebolt’s CEO. “We both build mission-critical data infrastructure for engineers. We spent the last several years building an analytics engine for what live applications and agents demand: high-concurrency, sub-second answers on fresh data. Joining MongoDB puts our engine where millions of developers already build. We can’t wait to bring real-time analytics to MongoDB customers.”</p><p>We’re thrilled to welcome the Firebolt team to MongoDB, and our teams are already working together to bring Firebolt’s engine into MongoDB. In the coming months, customers will be able to turn on real-time analytics for their MongoDB data, so their applications and agents can act on what’s happening now. </p><p>More to come soon. <a href="https://www.mongodb.com/products/platform/real-time-analytics">Join the waitlist</a> to be among the first to try real-time analytics on MongoDB.</p><h2>FAQ</h2><h3>What is Firebolt?</h3><p>Firebolt is a high-performance analytical database designed for low-latency queries and high-concurrency applications.</p><h3>Do Firebolt and real-time analytics replace a data warehouse?</h3><p>No. Traditional data warehouses and data lakes remain the right fit for internal BI, reporting, and data science. Real-time analytics is for application-facing analytics, which has a different set of requirements: complex queries over massive datasets, sub-second responses, high concurrency, and fresh data for live applications and AI agents.</p><h3>What happens to existing Firebolt customers?</h3><p>Nothing changes for existing Firebolt customers. They can continue using the product with the same support and service. Firebolt’s customers are a big reason we wanted to bring this team and engine into MongoDB. They’ve shown what the technology can do under real production load.</p><h2>Forward-Looking Statements</h2><p>This post includes certain &quot;forward-looking statements&quot; within the meaning of Section 27A of the Securities Act of 1933, as amended, and Section 21E of the Securities Exchange Act of 1934, as amended, including statements concerning MongoDB&#39;s acquisition of Firebolt and the anticipated benefits, integration, and future development of Firebolt&#39;s technology within MongoDB&#39;s intelligent data platform. These forward-looking statements include, but are not limited to, plans, objectives, expectations and intentions and other statements contained in this post that are not historical facts and statements identified by words such as &quot;anticipate,&quot; &quot;believe,&quot; &quot;continue,&quot; &quot;could,&quot; &quot;estimate,&quot; &quot;expect,&quot; &quot;intend,&quot; &quot;may,&quot; &quot;plan,&quot; &quot;project,&quot; &quot;will,&quot; &quot;would&quot; or the negative or plural of these words or similar expressions or variations. These forward-looking statements reflect our current views about our plans, intentions, expectations, strategies and prospects, which are based on the information currently available to us and on assumptions we have made. Although we believe that our plans, intentions, expectations, strategies and prospects as reflected in or suggested by those forward-looking statements are reasonable, we can give no assurance that the plans, intentions, expectations or strategies will be attained or achieved. Furthermore, actual results may differ materially from those described in the forward-looking statements and are subject to a variety of assumptions, uncertainties, risks and factors that are beyond our control including, without limitation: our customers renewing their subscriptions with us and expanding their usage of software and related services; global political changes; the effects of the ongoing geopolitical instability resulting from the conflict in Iran, the unrest in Mexico, the conflicts between Russia and Ukraine, Israel and Hamas and recent events in Venezuela on our business and future operating results; economic downturns and/or the effects of rising interest rates, inflation and volatility in the global economy and financial markets on our business and future operating results; our ability to remain profitable and grow in a constantly changing market; our potential failure to meet publicly announced guidance or other expectations about our business and future operating results; reputational harm or other adverse consequences resulting from use of artificial intelligence (“AI”) and machine learning (“ML”) in our product offerings and internal operations if they don&#39;t produce the desired benefits; our limited operating history; our history of losses; our potential failure to repurchase shares of our common stock at favorable prices, if at all; failure of our platform to satisfy customer demands; the effects of increased competition; our investments in new products and our ability to introduce new features, services or enhancements, including AI and ML, for both traditional and emerging use cases; our ability to effectively expand our sales and marketing organization; our ability to continue to build and maintain credibility with the developer community; our ability to add new customers or increase sales to our existing customers; our ability to maintain, protect, enforce and enhance our intellectual property; our ability to continue to increase revenue from our Atlas platform; the effects of social, ethical, security and regulatory issues relating to the use of new and evolving technologies, such as AI and ML, in our offerings or partnerships; the possibility that the market for AI-related data infrastructure may not develop as we expect or may favor alternative architectures or competitors; the growth and expansion of the market for database products and our ability to penetrate that market; our ability to integrate acquired businesses and technologies successfully or achieve the expected benefits of such acquisitions, including the acquisition of Firebolt; the risk of any unexpected costs or expenses resulting from the acquisition of Firebolt; the risk of any litigation relating to such acquisition; the risk that such acquisition and the announcement of it could have an adverse effect on our operating results and business generally; our ability to maintain the security of our software and adequately address privacy concerns; our ability to manage our growth effectively and successfully recruit and retain additional highly-qualified personnel; and the price volatility of our common stock. These and other risks and uncertainties are more fully described in our filings with the Securities and Exchange Commission (&quot;SEC&quot;), including under the caption &quot;Risk Factors&quot; in our Quarterly Report on Form 10-Q for the quarter ended July 31, 2026, filed with the SEC on September 1, 2026, and other filings and reports that we may file from time to time with the SEC. Except as required by law, we undertake no duty or obligation to update any forward-looking statements contained in this post as a result of new information, future events, changes in expectations or otherwise.</p>]]></description>
      <pubDate>Tue, 17 Nov 2026 13:59:01 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/news/mongodb-acquires-firebolt</link>
      <guid>https://www.mongodb.com/company/blog/news/mongodb-acquires-firebolt</guid>
    </item><item>
      <title>How to Model an Insurance Policy Without Joining Dozens of Tables</title>
      <description><![CDATA[<p>Ask an underwriter to describe a policy, and you’ll get a coherent answer: A contract, for a customer, covering a car or a house, with a handful of coverages, each with a limit and a deductible, plus a history of every change since it was issued. One policy—with parts. Many parts.</p><p>Now ask your database the same question. In most insurance core systems, that single policy is sliced across dozens of relational tables: one each for coverages, vehicles, named parties, endorsements, and billing schedules. Every time a screen loads, the system reassembles the policy by joining those tables back together. Every time a product changes, several of the tables need altering. When Manulife(1) rebuilt its policy servicing platform, its chief architect described replacing more than 500 core tables with one document per policy and reported that the new system won overwhelming approval from its developers.</p><p>That gap—between how the business thinks about a policy and how the database stores it—is the central problem a document database like MongoDB solves. This blog post explains the one design decision that matters most when you make that move and why it’s an insurance decision as much as a technical one.</p><h2>One rule drives everything</h2><p>A document database stores records as nested structures, closer to a folder than a spreadsheet row. A policy document can hold its coverages, its vehicles, its parties, and its event history all within itself. The temptation is to simply pour the old table diagram into this new shape. That’s the wrong instinct.</p><p>The core idea is to model the data around what the business does with it, not around how the entities look on a diagram. Concretely, that means designing for the policy lifecycle (quote, underwrite, issue, bill, endorse, renew, cancel, claim) and asking, at each step, what gets read and written together.</p><p>Once you ask that question, every design choice reduces to one decision: whether to embed or reference.</p><h2>Embed or reference: The decision that matters</h2><p>For any two related pieces of data, you have two options. Embed one inside the other, so they live in a single document. Or reference one from the other, storing just an identifier that points to a separate document, the way a relational foreign key does.</p><p>The test can be reduced to two very simple statements: </p><ul><li><p>Embed data that is part of something and is always read alongside it.</p></li><li><p>Reference data that has its own lifecycle or is shared across many records.</p></li></ul><p>Apply that to a policy and the answers fall out naturally. Coverages belong inside the policy. Nobody ever looks up collision coverage without the policy it sits within. The insured vehicle belongs inside the policy—as does the event history, because an endorsement or a cancellation is meaningless apart from the contract it changed. In document form, that looks like this:</p><p>Anyone in the business can read that. It looks like the policy.</p><p>The claim follows the same logic, with a payoff that finance teams will appreciate. A claim’s reserves and payments belong inside the claim document. Because a single document is always written atomically, posting a reserve and updating the claim’s total becomes one operation that either fully succeeds or doesn’t happen at all. There’s no window where the ledger and the claim disagree.</p><p>Now let’s look at the other side of the test. A customer’s policies should not be embedded inside the customer record. Policies are large, they change constantly, and they’re almost always looked up by policy number rather than through the customer record. Instead, store policies in their own collection and have each policy reference its customer by ID. Claims should not be embedded inside policies either, because a claim can outlive the policy that spawned it: a canceled policy can still have open claims. Store claims separately, with each claim referencing the policy it belongs to.</p><p>The agent who sold the policy and the product it was written on should also be referenced, not embedded, and here the reasoning is operational. Thousands of policies share one agent and one product. Embed the agent’s details, and a change to their license number becomes a write across every policy in their book. Keep the product catalog as the single, versioned source of truth, and let the policy store only a point-in-time snapshot of the coverage terms it was bound against.</p><h2>Two storms that test the design</h2><p>Insurance also stress-tests data models in a way few other industries do: catastrophes.</p><h3>The hurricane claim </h3><p>Most auto and property claims carry fewer than 10 supporting attachments (photos, estimates, or a police report, for example). Embedding them in the claim is fine. But a major-loss claim after a hurricane can accumulate 60 or more attachments. MongoDB has a hard 16 MB size limit per document, but even well below that, a bloated minority of claims slows down every screen that loads them.</p><p>The wrong fix is to move all claim documents into a separate collection “just in case,” penalizing the 99% for the 1%. The right fix is what MongoDB’s engineers call the outlier pattern: embed by default, and when a claim crosses a threshold, flip an overflow flag and store the excess in a side collection. The design serves the common case and handles the exception explicitly.</p><p>Here’s what that looks like for a hurricane claim. Once the claim crosses the threshold, the application sets the flag and moves the extra documents to the side collection, so the claim record stays small:</p><h3>The wildfire intake surge</h3><p>When a database outgrows one server, MongoDB splits it across several, and a field called the shard key decides which server each record lands on. It seems sensible to shard claims by catastrophe (CAT) event code, since the CAT dashboard queries by it. It’s a trap. During an active wildfire, nearly every new claim for days shares one CAT code, so every new claim routes to one server—precisely when intake throughput matters most. Use a hashed shard key on the claim number to spread new claims evenly, and keep the CAT code as an ordinary index for the dashboard.</p><p>Both examples carry the same lesson: The data model is where operational resilience is decided, long before the storm arrives.</p><h2>Three patterns to adopt on day one</h2><p>Beyond the embed-versus-reference rule, there are three more design patterns to adopt:</p><ol><li><p><strong>Computed totals</strong>. Store “total incurred” and “total paid” on the claim rather than re-summing reserves and payments on every read. Claim detail is among the busiest screens in the company; don’t make it do math.</p></li><li><p><strong>Schema versioning</strong>. Stamp every policy and claim with a version number. Insurance records survive for decades under regulatory retention and litigation discovery, and your document shape will change over that time. Without a version marker, that drift becomes an audit problem, not just a technical one. Travelers Insurance(2) is reported to have eliminated a three-day wait for schema changes after moving off a rigid relational model; versioning is what makes that agility safe.</p></li><li><p><strong>Append-only history</strong>. Policy events, claim activity, and increasingly, the step-by-step decision trace of any automated underwriting or fraud-screening agent should only ever be added to, never edited or deleted. In most industries, that’s good hygiene. In insurance, it’s compliance. As regulators turn their attention to AI-driven decisions, an auditable trace of what an automated system decided and why will be the difference between a quick review and a drawn-out one.</p></li></ol><h2>What this means for you</h2><p>None of this requires your engineers to abandon what they know. Multi-document transactions still exist for the moments that need them, such as binding a submission into a policy. The shift is in the starting question. Instead of “What are the entities and how do they relate?” it becomes, “What does the business read and write together, and what changes on its own?”</p><p>Keep what’s always read together, well, together. Separate what lives its own life. Plan explicitly for the outlier and the surge. Get those right, and the database finally describes a policy the way your underwriters do.</p><p><strong>References:</strong>
1. <a href="https://www.mongodb.com/company/blog/why-leading-insurer-manulife-ditched-sql-for-mongodb">Why Leading Insurer Manulife Ditched SQL For MongoDB
</a>2. <a href="https://diginomica.com/travelers-insurance-speeds-up-business-ask-to-production-process-with-mongodb">Travelers Insurance speeds up business ask-to-production process with MongoDB</a></p>]]></description>
      <pubDate>Fri, 13 Nov 2026 12:30:27 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/how-model-insurance-policy-without-joining-dozens-tables</link>
      <guid>https://www.mongodb.com/company/blog/innovation/how-model-insurance-policy-without-joining-dozens-tables</guid>
    </item><item>
      <title>Optimizing Document Lookup: Making Atlas Search and Vector Search Up to 5x Faster</title>
      <description><![CDATA[<p>Sometimes the biggest performance gains come not from making core operations faster, but from eliminating unnecessary work surrounding them. That is exactly what we discovered while optimizing document lookup in MongoDB Atlas Search and Vector Search. By removing redundant query planning and execution overhead, we made search queries up to 5x faster without changing the underlying search algorithms.</p><p>When you run a <em>$search</em> or <em>$vectorSearch</em> query in MongoDB, two key stages work together to deliver the results. First, <a href="https://www.mongodb.com/docs/search/self-managed/current/"><strong>mongot</strong></a>, MongoDB&#39;s search process powered by Apache Lucene, executes the search query to identify and rank the most relevant documents. Then, <a href="https://www.mongodb.com/docs/manual/tutorial/manage-mongodb-processes/"><strong>mongod</strong></a> joins the search results with the corresponding BSON documents from the underlying collection using their _ids. The resulting documents can be further processed by additional aggregation pipeline stages before being returned to the application. Figure 1 illustrates this two-stage process:</p><p><strong>Figure 1.</strong> Search execution in mongot and document materialization in mongod.</p><p>This second stage, known as document materialization, is handled by an internal aggregation stage called <em>$_internalSearchIdLookup</em>. While search execution has been extensively optimized, we discovered that document lookup had become a significant performance bottleneck. For every matching document, the stage repeatedly constructed a new query plan and acquired collection resources, introducing substantial overhead for queries returning hundreds or thousands of results. In our profiling, approximately 30% of <em>mongod</em> CPU time was spent on query planning and collection acquisition, rather than retrieving documents.</p><p>To address this, we redesigned the document lookup execution path to eliminate redundant query planning, reuse execution plans, and amortize resource acquisition across multiple lookups. The result: up to 4.9x faster <em>$search</em> queries, 5.5x faster <em>$vectorSearch</em> queries, and approximately 2.75x higher throughput under concurrency.</p><p>These optimizations shipped in MongoDB 9.0, are enabled by default, and require no application changes. In this post, we&#39;ll explore how we identified the bottleneck, redesigned the execution path, and achieved these performance improvements.</p><h2>The hidden cost of repeated query planning</h2><p>Looking up a document by its <em>_id</em> is typically a fast operation in MongoDB, thanks to its efficient _id index. However, the original <em>$_internalSearchIdLookup</em> implementation constructed and executed a new aggregation sub-pipeline for every document returned by <em>mongot</em>, even though only the <em>_id</em> value changed:</p><p>For each document, MongoDB parsed the query, optimized the pipeline, constructed an execution plan, acquired collection resources, attached a cursor, executed the lookup, and released resources.</p><p><strong>The problem was not the indexed document retrieval, but the repeated preparation work surrounding it.</strong> Even though the query structure was identical across lookups, MongoDB rebuilt the execution plan and reacquired collection resources for every document instead of reusing them. This overhead accumulated linearly with the number of results. For example, a search query returning 1,000 documents could trigger 1,000 separate cycles of query planning, collection acquisition, and resource cleanup. As result sets grew, the repeated preparation work became a substantial contributor to end-to-end search latency. Figure 2 illustrates this repeated execution overhead.</p><p><strong>Figure 2.</strong> Repeated query planning and resource acquisition for each document lookup.</p><p>To quantify this overhead, we profiled representative Vector Search workloads. The results revealed that approximately 30% of mongod CPU time was spent on query plan construction and collection acquisition, rather than retrieving documents. This confirmed that the bottleneck was not primarily the underlying document reads, but the redundant work surrounding them.</p><h2>Redesigning the document lookup execution path</h2><p>To eliminate redundant lookup overhead, we redesigned <em>$_internalSearchIdLookup</em> around two key optimizations: reusing parameterized execution plans and batching document lookups to minimize resource acquisition overhead. Together, these changes allow MongoDB to retrieve thousands of documents without repeatedly rebuilding query plans or acquiring collection resources.</p><h3>1. Reusing a parameterized SBE execution plan</h3><p>The first major optimization was introducing <em>SbeSingleDocumentLookupExecutor</em>, built on MongoDB&#39;s Slot-Based Execution (SBE) engine. The key observation was simple: every document lookup follows the same query structure, and only the <em>_id</em> value changes. Instead of constructing a new execution plan for each document, the optimized executor builds the lookup plan once, caches it, and reuses it by rebinding the <em>_id</em> parameter for subsequent lookups.</p><p>For example, when retrieving 1,000 documents, the original implementation could construct 1,000 separate query plans. With the optimized executor, all 1,000 lookups can reuse a single parameterized plan.</p><p>This eliminates redundant query parsing, optimization, and plan construction, significantly reducing per-document execution overhead.</p><h3>2. Batching document lookups to reuse collection resources</h3><p>While plan reuse eliminates repeated query planning, acquiring and releasing collection resources for every document can still introduce substantial overhead. To address this, we introduced a reusable <em>BatchedEnrichmentStage</em> that buffers incoming search results and processes them within a shared resource scope. Instead of independently acquiring and releasing collection resources for every document, the optimized execution path reuses collection resources across multiple lookups within a batch, amortizing the acquisition and cleanup costs. For example, with 1,000 documents and a batch size of 100, collection resources can be acquired just 10 times instead of 1,000 times, i.e., once per batch rather than once per document. Although the number of document lookups still grows linearly with the result set size, batching significantly reduces the repeated resource management overhead.</p><p>Combined with SBE plan caching, this allows thousands of document lookups to share both an execution plan and collection resources, substantially reducing CPU overhead. The result is a more efficient document lookup architecture: build the execution plan once, reuse it across documents, and minimize repeated resource acquisition. </p><p>Figure 3 illustrates how the optimized approach eliminates redundant work by reusing execution plans and collection resources across document lookups.</p><p><strong>Figure 3.</strong> Original per-document lookup vs. optimized batched lookup with shared execution plans.</p><h2>Performance results: End-to-end latency and throughput</h2><p>As shown in Figure 4, both Atlas Search ($search) and Atlas Vector Search ($vectorSearch) achieved substantial reductions in end-to-end query latency across all evaluated result-set sizes (100, 1,000, and 10,000 documents). At 10,000 results, median latency dropped from approximately 2.6 seconds to 527 milliseconds for Atlas Search (<strong>4.9× faster</strong>) and from 3.1 seconds to 561 milliseconds for Atlas Vector Search (<strong>5.5× faster</strong>).</p><p>An important pattern emerges: <strong>the larger the result set, the greater the speedup</strong>. This is consistent with the underlying optimization. While search execution still incurs its own costs, eliminating repeated query planning and resource acquisition overhead becomes increasingly valuable as more documents are materialized.</p><p><strong>Figure 4.</strong> End-to-end query latency improvements for Atlas Search and Atlas Vector Search in MongoDB 9.0.</p><h3>Higher throughput under concurrency</h3><p>Lower latency is only part of the story. We also evaluated performance under concurrent query execution. With 16 concurrent clients running a <em>$search</em> workload, the optimized implementation delivered:</p><ul><li><p>Approximately 2.75x higher throughput</p></li><li><p>Approximately 3x lower median latency</p></li></ul><p>These results demonstrate that the optimization does more than accelerate individual queries. By eliminating repeated query planning and resource acquisition, it reduces unnecessary CPU work per document lookup, allowing <em>mongod</em> to process more concurrent search requests with the same execution resources. The approximately 30% CPU overhead identified in our earlier profiling and the nearly 80% latency reduction observed in our benchmarks represent different measurements and workloads, rather than directly proportional improvements.</p><h2>Real-world customer impact</h2><p>To understand the potential impact on real-world workloads, we analyzed 163.8 million Atlas Vector Search executions across 610 customer clusters over 90 days. The analysis shows that larger result-set limits are used across a meaningful portion of the customer fleet. At least 40% of clusters execute queries with limits between 21 and 50, and at least 17% execute queries with limits above 100.</p><p>These workloads are particularly well-positioned to benefit from the document lookup optimizations, as eliminating repeated query planning and resource acquisition becomes increasingly valuable when more documents are retrieved.</p><p>Importantly, these improvements require no application changes. The optimized document lookup path is enabled by default in MongoDB 9.0.7. Applications do not need to rewrite queries, rebuild search indexes, or adopt new syntax. Existing <em>$search</em> and <em>$vectorSearch</em> pipelines can automatically benefit when running on supported configurations.</p><h2>Faster search, without the extra work</h2><p>This optimization began with a surprising observation: a simple <em>_id</em> lookup was spending a significant portion of its CPU budget preparing to execute rather than retrieving data. By replacing repeated aggregation planning with lightweight execution, introducing reusable batching infrastructure, and caching parameterized SBE plans, we removed a major source of overhead from Atlas Search and Vector Search. The result is up to <strong>5.5× faster end-to-end queries</strong> in our benchmarks, along with substantial throughput improvements under concurrency.</p><p>More broadly, this work illustrates an important database engineering principle: sometimes the biggest performance gains come not from making the core operation faster, but from eliminating the unnecessary work surrounding it. This effort was made possible through collaboration across MongoDB’s Atlas Search Query, Query Execution, Query Integration, Database Integration and Observability, and Server Triage &amp; Release teams. Special thanks to <strong>Denis Grebennicov</strong> from the Database Integration and Observability team for his significant contributions to this optimization effort.</p>]]></description>
      <pubDate>Thu, 12 Nov 2026 23:34:15 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/engineering/optimizing-document-lookup-making-atlas-search-vector-search-up-to-5x-faster</link>
      <guid>https://www.mongodb.com/company/blog/engineering/optimizing-document-lookup-making-atlas-search-vector-search-up-to-5x-faster</guid>
    </item><item>
      <title>The $5 Trillion Shift: Preparing Retail Backends for the Age of AI Agents</title>
      <description><![CDATA[<p>Retail is entering the era of the multi-agent shopping assistant. Instead of a single, stateless chatbot following a rigid script, retailers are building systems where multiple agents collaborate behind the scenes, drawing on preferences and customer purchase history to deliver recommendations that improve with every interaction. More retailers are reconfiguring their backends to reflect the rise in agentic usage, as this is no small trend: McKinsey estimates AI agents could mediate $3 trillion to $5 trillion of global consumer commerce by 2030.(1) </p><p>The need is real, as the race is heating up to quickly respond to customer searches and take service to another level. A customer searching for a pair of running shoes for an upcoming marathon no longer triggers a keyword search. The query kicks off a coordinated reasoning process across multiple specialized agents. This has to happen rapidly and seamlessly to keep consumers&#39; attention and needs met.</p><p>The promise of this shift is real, but the real architectural question has nothing to do with which LLM or orchestration framework a team chooses. It has everything to do with where the data lives and whether every agent can see the same version of the truth simultaneously. Increasingly, retailers are finding that solution in MongoDB.</p><h2>The technology challenge behind multi-agent AI</h2><p>Building a single AI agent is straightforward with modern LLMs and orchestration frameworks. Building a production multi-agent system is not. Why? Agentic AI has five distinct data needs: </p><ul><li><p>Semantic search over vector embeddings </p></li><li><p>Flexible user context </p></li><li><p>Conversation state across sessions </p></li><li><p>Long-term memory that evolves over time </p></li><li><p>Observability through audit logs </p></li></ul><p>Engineering teams pay a heavy ‘siloed database tax’ to meet these needs, standing up five distinct, single-purpose datastores: a vector store for product discovery, a session store for chat history, a short-term memory store for session context, a long-term memory store for accumulated preferences, and an audit log for compliance and debugging.</p><p>That fragmentation comes at a cost. Every additional datastore adds its own SDK, its own operational overhead, and its own failure mode. If the profile agent writes a new preference to one store while the product agent reads from another, the two are only as consistent as the ETL job connecting them. In a real-time conversation, that gap shows up as an agent recommending a product the customer already ruled out, or forgetting a preference captured moments earlier.</p><p>Retail makes the problem concrete. Carol asks for running shoes for a road marathon. Her profile has her static preference on file: She wears a size eight. Earlier in this conversation, she mentioned wanting maximum cushioning; that&#39;s short-term session context. John asks for running shoes, too. His profile puts him at a size 11, but long-term memory holds something neither his profile nor this conversation does: He needs a waterproof build, a fact learned from a past return after a pair let water soak in. Serving both well, consistently, and across every channel requires holding all three—static preferences, session context, and long-term memory—as one coherent view. This is what we’ve built to make this all happen fluidly </p><h2>Giving every agent the same context</h2><p>Retailers building a multi-agent system need specialized agents—including planner agents, profile agents, product agents, and eventually others—to discover and invoke each other&#39;s capabilities regardless of which team built them. This is what an open protocol like Agent2Agent (A2A) (2) provides. The Multi Agent Retail Advisor (MARA) is a reference implementation. Here, a planner agent delegates to a profile agent and a product agent, coordinating through A2A. The orchestration framework and LLM are both swappable; MongoDB, the data layer underneath every agent, is not.</p><p><strong>Figure 1.</strong> Reference architecture for the MARA, showing how the planner, profile, and product agents interact through the A2A protocol, with <a href="https://www.mongodb.com/products/platform/atlas-database">MongoDB Atlas</a> unifying operational and agentic data via Vector Search, text search, and auto-embeddings.</p><p>MongoDB Atlas handles all five agentic data needs natively in one platform, as shown in Figure 2 below. <a href="https://www.mongodb.com/products/platform/atlas-vector-search">Atlas Vector Search</a> stores product embeddings alongside the catalog data itself, so semantic search runs directly against operational data instead of a separate index to remain in sync. The same flexible document model holds customer context and preferences without a schema migration every time a field changes. Short-term memory lives as a nested array inside each session document, allowing the planner agent to fetch an entire conversation in one read. Long-term memory accumulates in its own collection, capturing facts an agent learns about a customer, like a preference for polyester base layers because they dry faster, independent of any single session. Observability runs through the same platform, too, logging every tool call&#39;s inputs, outputs, and latency so a request&#39;s full execution path can be reconstructed instantly.</p><p><strong>Figure 2. </strong>MongoDB Atlas consolidates all single-purpose datastores to meet agentic AI’s data needs into one platform.</p><p>For product discovery, retailers build directly on Atlas Vector Search. They embed queries with Voyage AI and match them semantically against the catalog, falling back automatically to Atlas full-text search on the same collection when a query needs it, with no extra infrastructure. Because Voyage AI&#39;s newer models share a common embedding space, retailers can embed the catalog once with a larger, accurate model, and then run live queries with a smaller, faster model without ever re-indexing.</p><h2>A simpler, more resilient stack for IT teams</h2><p>For retailers, the payoff is architectural simplicity that compounds into speed and cost savings. Teams no longer manage four or five separate systems; they manage one. Schema flexibility, shown in Figure 3, lets agent state and user profiles, each varying by shopper or task, evolve without disruptive migrations. Because MongoDB Atlas scales horizontally, it supports the bursty, unpredictable request patterns of autonomous agents without becoming a bottleneck. Full observability works the same way: A single aggregation pipeline query joins the tool_invocations log, agent_state history, and session record for a request, reconstructing what each agent did, in what order, and how long each step took. That gives IT teams a queryable execution trace for every agent decision, shortening the path from a production issue to a root cause.</p><p><strong>Figure 3.</strong> Two documents from the agent_state collection and two from the users collection. This shows the same collection, different shape, depending on which agent ran or which shopper it describes.</p><p>This consolidation also changes how fast a team can move. The product catalog, user profiles, session history, long-term memory, and tool-invocation logs all live as collections in one MongoDB cluster, not four separate systems linked together. That&#39;s the difference between a proof of concept shipping in weeks and one spending its first quarter wiring systems together before a single agent runs.  This setup lowers total cost of ownership the same way: one licensing agreement, one scaling model, and one team. Governance benefits too. Fine-grained access controls, encryption, and audit logging apply consistently across every agent&#39;s data, instead of system-by-system configuration. Because the architecture is not tied to a specific framework or model provider, retailers can add new agents, inventory, loyalty, and fulfillment onto the same data plane without replatforming. That matters most for agents no one can name yet. Any future agent built on the same document model plugs into the same unified context, turning what would otherwise be a multi-quarter integration effort into a schema extension.</p><h2>An experience that feels seamless for customers</h2><p>For customers, this translates into an experience that feels genuinely continuous. Because every agent reads from and writes to the same unified context, a preference shared in one conversation carries into the next. A question that starts in a chat can hand off cleanly to an inventory agent checking store stock or a loyalty agent applying a reward without the customer repeating themselves. This results in recommendations that get sharper the more a customer interacts with the system and a shopping experience that feels like one relationship rather than a series of disconnected sessions.</p><p><strong>Figure 4. </strong>Any multi-agent retail architecture needs a swappable layer for orchestration and the LLM, but every agent still needs one constant data layer underneath it. Here, that&#39;s MongoDB Atlas beneath MARA&#39;s planner, profile, and product agents.</p><p>That continuity holds up across channels, not just across conversation turns. A preference a customer states while browsing on mobile is available the next time they open a chat window, walk into a store, or call support because it lives in the same unified profile every agent reads from rather than in a channel-specific cache. Customers also benefit from recommendations that account for their actual history rather than generic popularity signals. This happens since the product agent&#39;s semantic search runs against a catalog informed by what a shopper has already bought, browsed, and rejected. For the business, that precision compounds directly into commerce metrics: higher conversion, larger basket sizes, and fewer costly returns from recommendations that miss the mark.</p><h2>Building for what comes next</h2><p>The orchestration framework and LLM a retailer chooses today will likely change more than once. What shouldn&#39;t change is the data layer holding the system together. MongoDB gives retailers a single, flexible foundation for the knowledge, context, memory, and observability multi-agent retail experiences depend on, so the architecture underneath doesn&#39;t have to be rebuilt as frameworks and models evolve. Retailers that consolidate this layer now will be the ones ready to add the next agent—and the next protocol—without starting over.</p><h2>References</h2><ol><li><p>The automation curve in agentic commerce. McKinsey. January 28th, 2026.
<a href="https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-automation-curve-in-agentic-commerce">https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-automation-curve-in-agentic-commerce</a></p></li><li><p>Getting Started with Agent2Agent (A2A) Protocol <a href="https://codelabs.developers.google.com/intro-a2a-purchasing-concierge#0">https://codelabs.developers.google.com/intro-a2a-purchasing-concierge#0</a></p></li></ol>]]></description>
      <pubDate>Thu, 12 Nov 2026 15:25:40 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/5-trillion-shift-preparing-retail-backends-for-age-of-ai-agents</link>
      <guid>https://www.mongodb.com/company/blog/innovation/5-trillion-shift-preparing-retail-backends-for-age-of-ai-agents</guid>
    </item><item>
      <title>How Observe.AI Used MongoDB Resharding to Scale Its AI Platform</title>
      <description><![CDATA[<p>Launched in 2017, Observe.AI was originally known for its expertise in conversation intelligence and contact center analytics. In recent years, however, the company has grown into a comprehensive agentic AI platform, and now has three core offerings:</p><ul><li><p>AI agents for customers that resolve customer requests across voice and chat.</p></li><li><p>AI agents for frontline teams. These include Observe.AI’s recently launched Companion Agent, which provides human team members real-time guidance and automates work before, during, and after customer interactions.</p></li><li><p>AI agents for operations that evaluate interactions, generate coaching, uncover operational insights, and drive continuous improvement across contact centers.</p></li></ul><p>Observe.AI uses <a href="https://www.mongodb.com/products/platform/atlas-database">MongoDB Atlas</a> as the foundational data layer for its AI platform and relies on it to store raw customer conversations, AI-generated enrichments, model configurations, and agent metadata. </p><p><a href="https://www.mongodb.com/resources/basics/flexible-data-model">MongoDB&#39;s flexible document model</a> enables rapid iteration as AI models evolve, while its scalability—supporting over 100 clusters and 50+ TB of data—has made it the trusted system of record powering our platform&#39;s intelligence layer.</p><p>Recently, the team wanted to continue scaling with MongoDB in a way that preserved application availability, reduced operational risk, and created a predictable runway for continued data growth.</p><p>The team partnered with <a href="https://www.mongodb.com/services/consulting">MongoDB Consulting</a>’s professional services to scale a production-critical <a href="https://www.mongodb.com/products/platform/atlas-database">MongoDB Atlas</a> deployment to support Observe.AI’s conversation intelligence platform. The project was a joint engineering effort between Observe.AI and MongoDB that used MongoDB resharding as a practical, online mechanism for redistributing large collections across a broader shard footprint.</p><h2>Expanding a constrained shard footprint</h2><p>At the time of the project, the cluster had the following characteristics:</p><ul><li><p>A sharded MongoDB Atlas deployment with<strong> </strong>two data shards plus config servers.</p></li><li><p>Approximately 13 TB of compressed data per data shard, representing roughly 50 TB of uncompressed data overall.</p></li><li><p>Each shard runs on the M140 tier with a disk limit of approximately 14 TB, leaving limited available headroom.</p></li><li><p>A sustained ingest rate of roughly 50 GB per day, making proactive capacity expansion important for safe long-term operations.</p></li><li><p>Several multi-TB collections with significant index footprint and production traffic. This setup had worked at an early stage in the company&#39;s cycle, but was no longer fit for purpose and could lead to performance issues or service degradation that would directly impact customers. </p></li></ul><p>The engineering objective of the MongoDB–Observe.AI effort was clear: to expand a constrained shard footprint to a healthier horizontal layout, while also keeping the application online and minimizing disruption to production workloads.</p><h2>Beyond balancer: a faster redistribution for large-scale data movements </h2><p>After adding new shard capacity, the team evaluated the default balancer-driven redistribution path. They determined that the balancer was the right tool for ongoing incremental balancing, but the volume of data to be redistributed was large enough that relying on chunk migrations alone would have extended the migration window and kept the original shards under elevated pressure for longer than desired.</p><p>The team also tackled a number of other constraints. First, the new shard capacity could receive data, but the pace of redistribution was bounded by balancer and range-deletion throughput; range deletion<strong> </strong>also created additional background load on shards that were already carrying production traffic. Secondly, existing shards periodically experienced high WiredTiger cache pressure, making it important to avoid prolonged competition between application traffic, balancing, and cleanup activity. Finally, the team wanted a controlled, predictable migration path rather than an extended background redistribution process.</p><p>They concluded that the balancer should continue to handle incremental corrections, but a faster and more explicit redistribution mechanism was needed for the initial large-scale data movement.</p><h2>The four-step resharding plan</h2><p>Instead of relying solely on balancer migrations, the MongoDB–Observe.AI team designed a controlled resharding plan:</p><ol><li><p><strong>Scale out the cluster</strong></p></li><ul><li><p>Increase capacity by adding multiple new shards (not just one) so that, after redistribution, each shard would hold a manageable share of the ~50 TB dataset.</p></li></ul><li><p><strong>Prepare the cluster for resharding</strong></p></li><ul><li><p>Ensure no ongoing migrations or resharding jobs.</p></li><li><p>Pin the config servers to remain embedded/dedicated as appropriate for this topology.</p></li><li><p>Disable range deletions and disallow chunk migrations for critical collections so that resharding traffic does not compete with the balancer and range deleter for IOPS.</p></li></ul><li><p><strong>Run resharding on the largest collections</strong></p></li><ul><li><p>For each large collection (<em>collection6</em>, <em>collection7</em>, <em>collection8,</em> etc.), run <em>reshardCollection</em> to redistribute data across the new shard set, keeping the same shard key but changing the ownership distribution.</p></li><li><p>Execute resharding sequentially per collection to avoid overloading donors, recipients, or the config server.</p></li></ul></ol><p><strong>Table 1.</strong> Resharding performance metrics.</p><p>4.<strong> Clean up and return to normal operations</strong></p><ul><li>Once data has been redistributed:</li><ul><li>Remove old empty shards from the cluster.</li><li>Remove temporary zone configurations that were only needed during the migration.</li><li>Re‑enable balancing and range deletions for the now‑healthy collections.</li></ul></ul><h2>Resharding driving greater optimization, performance, and reliability </h2><p>The joint effort gave Observe.AI a safer and more scalable data foundation for continued platform growth.</p><p>Thanks to resharding, the cluster moved from a limited disk runway to a healthier multi-month capacity position, while large multi-TB collections were redistributed across the expanded shard footprint using online resharding rather than relying only on extended balancer-driven chunk migration.</p><p>Production reads and writes continued during the clone and catch-up phases, with only the final commit phase requiring a brief write-blocking critical section. The team reduced sustained pressure on the original shards and created more room for future ingest growth, maintenance, and operational flexibility.</p><p>Finally, after the migration, the MongoDB balancer returned to its normal role of incremental rebalancing, while the heavy data movement was handled through the more appropriate resharding workflow.</p><p>The project highlighted how sharding and resharding can be used proactively as part of ongoing capacity management, helping optimize storage utilization, manage growing data volumes, and maintain platform performance and reliability as workloads scale.</p><h2>Combining horizontal scale-out and resharding: A winning combo</h2><p>The key idea behind MongoDB’s resharding capability is simple—<strong>sharding should not be the last‑resort, once‑in‑a‑lifetime operation you dread. </strong>It should be a practical, fast tool you can use whenever your workload outgrows its current shape.</p><p>If you treat sharding as “too expensive” and delay it until your primary is holding tens of TBs, you pay that cost back many times in:</p><ul><li><p>Oversized single replica sets,</p></li><li><p>Operational risk,</p></li><li><p>And slow, painful balancing when you finally add shards.</p></li></ul><p>By combining horizontal scale-out with resharding,<strong> </strong>which has been available since <a href="https://www.mongodb.com/products/updates/version-release">MongoDB 8.0</a> launched in 2024, you can start small, grow organically, and still have a <strong>predictable, efficient path</strong> to redistribute data when your cluster—and your business—takes off.</p><p>Observe.AI’s  platform processes billions of customer interactions each year, so the infrastructure has to scale as seamlessly as the business. Working alongside the MongoDB team enabled Observe.AI to redistribute more than 50 TB of production data with virtually no disruption to customers. MongoDB 8.0 resharding provided  the operational confidence to expand capacity proactively instead of reacting to infrastructure limits, allowing Observe.AI’s engineering teams to stay focused on delivering innovation for customers. </p>]]></description>
      <pubDate>Thu, 12 Nov 2026 12:34:46 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/how-observe-ai-used-mongodb-resharding-scale-ai-platform</link>
      <guid>https://www.mongodb.com/company/blog/innovation/how-observe-ai-used-mongodb-resharding-scale-ai-platform</guid>
    </item><item>
      <title>Introducing the MongoDB Vercel AI SDK Integration: Persistent Memory for AI Applications</title>
      <description><![CDATA[<p>We are excited to announce the release of the MongoDB Vercel AI SDK integration, which provides AI applications and agents built with Vercel’s SDK with a persistent memory store in MongoDB Atlas. It&#39;s now open source and generally available on <a href="https://www.npmjs.com/package/@mongodb-developer/vercel-ai-memory">npm.</a></p><p>This integration adds <a href="https://www.mongodb.com/products/platform/atlas-database">MongoDB Atlas</a> as the memory store in the existing Vercel AI SDK code. Once installed, the package connects Vercel AI SDK applications to MongoDB Atlas and automatically stores the application&#39;s memories in documents. This allows the application to retain memories about conversations, user facts, and past events that persist across sessions, users, and restarts.</p><h2>What is the Vercel AI SDK?</h2><p>The Vercel AI SDK is a TypeScript toolkit for building AI applications. It handles calling models, streaming responses, using tools, and running agents that work through multi-step tasks. The SDK doesn&#39;t include a database to persist memories between runs. Without memory, an AI application starts every conversation with no knowledge of the last one. It doesn&#39;t know who the user is, what they asked yesterday, or what it learned along the way. It doesn’t have any context.</p><p>Today, developers have to build their own tooling to store memories in a layer. That usually means designing a database schema, writing jobs to clear out old data, and setting up vector search so the application can find relevant past information by semantic meaning instead of just keywords. It&#39;s a lot of work to build an AI application that can remember context.</p><h2>What types of memory does an AI application need? </h2><p>An AI application needs five kinds of memory, each kept for a different length of time and retrieved differently. This integration automatically categorizes each type of memory and stores it in MongoDB Atlas; here are short definitions of the five memory types:</p><ul><li><p><strong>Session:</strong> The conversation an application or agent has in each session. This helps the application follow what the user just said.</p></li><li><p><strong>Semantic:</strong> Facts about people, entities, and preferences, so users don&#39;t have to repeat themselves.</p></li><li><p><strong>Procedural:</strong> Workflows and instructions, so the application carries out tasks the way you&#39;ve defined them.</p></li><li><p><strong>Episodic:</strong> Key events and outcomes, so the application can recall what happened before. Kept for one year of inactivity by default.</p></li><li><p><strong>Scratchpad:</strong> Temporary notes for work in progress. They expire after an hour and can be promoted to episodic memory if they turn out to matter.</p></li></ul><p>Semantic and procedural memories are versioned, so history is preserved when a fact changes. The semantic, procedural, and episodic tiers use <a href="https://www.mongodb.com/products/platform/atlas-vector-search">MongoDB Vector Search</a>, which finds stored memories by semantic meaning rather than by exact keywords. </p><p>This integration automatically creates the vector indexes and detects embedding dimensions at startup. Developers can use any AI SDK embedding model to create vector indexes, including Voyage AI, OpenAI, Cohere, or Google.</p><p><strong>Figure 1.</strong> How the integration works with MongoDB Atlas and the Vercel SDK interface.</p><h2>How should memory age?</h2><p>Each category of memory has its own retention policy, so short-lived notes expire quickly, and long-term facts are stored for longer. The MongoDB Vercel AI SDK integration ships with defaults for every category, which developers can customize if they desire.</p><p>Effective memory retention requires a balance. Keeping memories indefinitely can decrease retrieval performance and increase costs, while deleting them too early can cause applications to forget important context. This integration includes features to help developers easily set the right balance:</p><ul><li><strong>Retention modes:</strong> Choose <em>none</em> (never expire), <em>ttl</em><em> </em>(expire after a set time), <em>ttl+importance</em> (expire after a set time unless the memory is marked important), or <em>dynamic</em>, where you define your own forgetting time period.</li><li><strong>Model-driven forgetting:</strong> With <em>memory_forget</em>, the model can delete a specific memory when a user says &quot;forget that.&quot; Removal usually happens within about 60 seconds.</li></ul><p>Because the memory is stored in MongoDB Atlas, application operational data, its memory, and the vector search that retrieves it run on one platform. Developers can secure, monitor, and scale a single database without bolting on a separate vector store or memory service alongside it.</p><h2>What changes when you run the MongoDB Vercel AI SDK Integration in production?</h2><p>This production release gives developers greater controls over their data and flexibility in how they use the integration:</p><ul><li><p><strong>Reliable session history:</strong> By default, the model decides when to save and read conversation turns, so it can occasionally skip one. For production, you can use the AI SDK hooks so that the application’s own code loads and saves the transcript at every turn. Every user, assistant, and tool message is saved exactly once.</p></li><li><p><strong>Separate data per customer:</strong> Developers can add a filter field, such as tenant_id, to the application’s vector indexes to limit each search to a single customer&#39;s memories.</p></li><li><p><strong>Application names and layout:</strong> Developers can rename collections and indexes to match the existing application schema or turn off indexing for unused categories. </p></li><li><p><strong>Open source:</strong> The package is licensed under Apache 2.0 and works with any AI SDK model.</p></li></ul><h2>Get started today</h2><p>Developers can add memory to an existing Vercel AI SDK project in three steps. This integration works with AI SDK v6 and v7 and requires a MongoDB Atlas cluster.</p><ol><li><p>Install the package and its peer dependencies: npm install @mongodb-developer/vercel-ai-memory ai mongodb</p></li><li><p>Create a memory instance with an Atlas connection string and an embedding model.</p></li><li><p>Pass the memory tools to the application, scoped to a user and session.</p></li></ol><p>From there, the model decides when to save and when to search for memories.</p>]]></description>
      <pubDate>Thu, 12 Nov 2026 00:44:22 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/product-release-announcements/introducing-mongodb-vercel-ai-sdk-integration-persistent-memory-applications</link>
      <guid>https://www.mongodb.com/company/blog/product-release-announcements/introducing-mongodb-vercel-ai-sdk-integration-persistent-memory-applications</guid>
    </item><item>
      <title>Introducing the MongoDB Claude SDK Session Adapter: Durable Session Storage for Agents</title>
      <description><![CDATA[<p>The <a href="https://code.claude.com/docs/en/agent-sdk/overview">Claude Agent SDK</a> is a package that lets you embed Claude Code&#39;s own agent loop directly into your application: web search, file search, file editing, MCP server connections, and more, all without having to define those tools or manage the agent loop yourself. The SDK also automatically persists session transcripts to the local file system by default. Claude calls it the Agent SessionStore. </p><p>Today, we are excited to announce the MongoDB Claude SDK Session Adapter, available in Python (with TypeScript coming in January 2027). </p><h2>What is the Claude Agent SessionStore?</h2><p>But first, let&#39;s understand what a SessionStore actually is. It is the extension point in the Claude Agent SDK for saving an agent&#39;s session outside the machine where it ran. Configure one, and the SDK mirrors every conversation turn and action as the agent works, so the session can pick back up exactly where it left off, on any instance that has access to that store.</p><p>That matters most once an agent stops running on a single, persistent machine. Say a team deploys their Claude agent as a Lambda function, callable as an internal service by teams across the company. Every invocation is a disposable instance; there&#39;s no local disk to store anything between calls. Without a SessionStore, each request is stateless by default; the agent has no memory of what came before. With a configured SessionStore, any invocation can pick up a session&#39;s full history, regardless of which instance handled the last turn.</p><p>That is the gap the MongoDB Session Adapter closes.</p><p>This is especially useful for enterprises that have multiple teams developing agents across many machines, who need session storage that survives host failures, scales as the agent fleet increases, and enforces the same access controls and retention rules as the rest of their data estate, not a bolt-on system built solely for agent memory.</p><h2>The MongoDB Claude SDK Session Adapter</h2><p>The MongoDB Claude SDK Session Adapter gives Claude agents durable session storage: a record of the conversation and its action history that lets an agent pick back up exactly where it left off, whether that&#39;s on the same laptop, a different server, or any server in a distributed deployment.</p><p>The adapter helps cover three crucial areas:</p><ul><li><p><strong>Cross-environment continuity:</strong> Whether a different backend instance picks up a conversation after a restart or a user resumes on a different device, session state doesn&#39;t live on the machine that started it. Because every step is mirrored to MongoDB as it happens, any instance in your deployment can resume exactly where the last one left off.</p></li><li><p><strong>Resilience to failure:</strong> If a host crashes or a container gets rescheduled mid-conversation, nothing is lost. Entries are written to MongoDB as they occur, not batched or cached locally, so whichever instance picks the session back up sees the same state as the failed one, up to the last completed step.</p></li><li><p><strong>Retention and auditability:</strong> Many teams need to retain agent transcripts to meet internal data-retention or audit requirements. Instead of standing up a separate system just for that, session data lives in the MongoDB cluster you&#39;re already operating, under the same access controls and backup policies as the rest of your data.</p></li></ul><h2>How it works</h2><p>This adapter implements the Claude Agent SDK&#39;s session storage interface directly, so you can mirror session transcripts to MongoDB in a few lines in <a href="https://code.claude.com/docs/en/agent-sdk/configuration#pass-options-to-a-session">ClaudeAgentOptions</a>:</p><p>That&#39;s it. Every session started with these <em>options</em> is stored in MongoDB and can be resumed across machines. Each agent writes locally; MongoDB makes the conversation portable between app instances.</p><p><strong>Figure 1.</strong> How the adapter allows you to access agent session transcripts mirrored in MongoDB.</p><h2>Get started today!</h2><p>Simply run the following command to start with session storage for your Claude agents:</p><p>Check out the <a href="https://www.mongodb.com/docs/atlas/ai-integrations/claude-agent-sdk/">documentation</a> to explore the source, open issues, and contribute. We&#39;d love to hear what you build!</p><p><strong>Additional resources:</strong></p><ul><li><p><a href="https://www.mongodb.com/docs/atlas/ai-integrations/claude-agent-sdk/">Claude Agent SDK documentation</a></p></li><li><p><a href="https://github.com/mongodb-developer/claude-agent-sdk-mongodb-session-store">MongoDB Session Adapter repo on Github</a></p></li><li><p><a href="https://code.claude.com/docs/en/agent-sdk/overview">Agent SDK overview - Claude Code Docs</a></p></li></ul>]]></description>
      <pubDate>Wed, 11 Nov 2026 20:54:41 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/product-release-announcements/introducing-claude-sdk-session-adapter-durable-session-storage-for-agents</link>
      <guid>https://www.mongodb.com/company/blog/product-release-announcements/introducing-claude-sdk-session-adapter-durable-session-storage-for-agents</guid>
    </item><item>
      <title>Introducing the MongoDB Google ADK Integration: Durable Memory for Agent State</title>
      <description><![CDATA[<p>We’re excited to announce the <a href="https://github.com/google/adk-python/blob/main/src/google/adk/integrations/mongodb/README.md">MongoDB Google ADK Integration</a>, which provides developers with the building blocks they need to create durable memory for agent state. </p><p>As agents move from prototypes to real-world applications, they need secure, dependable access to data and the ability to retain context over a long time. However, developers still need to build their own tooling for a data store that provides durable agent memory for agent state. </p><p>This integration gives developers a cohesive, ADK-native experience for using MongoDB as the data platform for agents.</p><h2>What is the Google ADK?</h2><p><a href="https://docs.cloud.google.com/gemini-enterprise-agent-platform/build/adk">The Google Agent Development Kit (ADK)</a> is an open source agent development framework that lets you build, debug, and deploy reliable AI agents at enterprise scale. It is available in Python, TypeScript, Go, Java, and Kotlin.</p><p>Google ADK offers developers an extensive set of tools for creating, deploying, assessing, and scaling agents, enabling developers to build anything from personal AI assistants to mission-critical business workflows.</p><h2>How does the MongoDB Google ADK Integration help?</h2><p>Developers can prototype an agent that searches a product catalog or knowledge base, then evolve it into a production experience that preserves user context across conversations and recalls relevant prior interactions. With MongoDB as the data layer, developers can keep the data their agents search over, the conversation state that needs to survive a restart or a scaled-out instance, and the memories agents build over time, all in the same place as the rest of their application data. That means no separate database to stand up for retrieval, no pipeline syncing app data into a different memory index, and no added latency pulling context from another system before the agent can respond.</p><p>ADK supplies the agent framework and tool interface; this integration provides the data and persistence layer beneath it, so developers can easily take an agent from prototype to production. These agents can maintain conversation and session memory independent of any single machine, and carry a user&#39;s history across sessions.</p><h2>Providing a unified agent architecture</h2><p>At the core of this integration is Google ADK 2.0, which serves as the code-first orchestration layer for multi-agent systems. ADK 2.0 provides the deployment framework, while MongoDB provides session and memory storage for agents.</p><p>Integrating directly with the Gemini Enterprise Agent Platform, ADK 2.0 eliminates the need for custom routing logic by providing standardized tool-calling interfaces, native telemetry, and enterprise access controls out of the box. Developers can use Gemini 4 Argon for multi-step reasoning and Gemini 3.8 Flash for low-latency execution. </p><p><strong>Figure 1.</strong> The MongoDB Google ADK Integration adds session and memory storage for single or multi-agent workflows.</p><h2>How do Sessions and Memory storage work?</h2><p>Great agent experiences improve with context. This integration introduces <em>MongoDbSessionService</em> to persist sessions, events, and application-, user-, and session-scoped state to MongoDB.</p><p>This means developers can build agents that retain the context needed for longer-running and multi-turn interactions. The session service includes optimistic concurrency control to help applications safely manage concurrent updates, while configurable collections make it easier to fit the service into existing data architectures.</p><p>The following Python code shows how you can add <em>MongoDbSessionService</em> to your agent:</p><p>For agents that need memory beyond a single session, <em>MongoDBMemoryService</em> ingests session events into MongoDB collections and recalls relevant memories through keyword matching. Memory ingestion is idempotent, which prevents duplicates when a session is added again.</p><p>Together, these services help agents become more useful over time without requiring developers to stitch together separate systems for retrieval, state, and memory.</p><h2>How does MongoDB Search help agents with data retrieval?</h2><p>Having memory for agent state is essential, but agents also need fast access to the operational data they search over, the same product catalogs, documents, and records your application already queries. This is where MongoDB&#39;s built-in search capabilities come in. <a href="https://www.mongodb.com/products/platform/atlas-vector-search">MongoDB Vector Search</a> leverages <a href="https://www.mongodb.com/products/platform/ai-search-and-retrieval">Voyage AI&#39;s embedding models</a>, which are the same engine backing MemoryService&#39;s semantic retrieval in this integration. </p><p>Developers can also perform hybrid search by combining vector search with full-text search using the <em>$rankFusion</em> aggregation stage.</p><p>This gives agents access to the right information and context at the right time, delivering better responses in production. Whether you are building product discovery, knowledge assistants, support experiences, or domain-specific copilots, agents can automatically leverage semantic and hybrid retrieval to ground their responses in your data.</p><p>The application owns the database connection, database name, and search configuration. The agent gets focused tools to call, without exposing those operational details in its context.</p><p>The following Python code shows how to add MongoDB Search to your agents:</p><p>Using MongoDB as the operational data store, the memory layer for agent state, and the search engine over both, developers get one platform instead of three, on whatever deployment they run it on. There&#39;s no separate vector database to stand up, no search engine to sync against a second copy of the data, and no added latency from hopping between systems before the agent can respond.</p><h2>Which deployment versions does this integration support?</h2><p>The integration supports <a href="https://www.mongodb.com/products/platform/atlas-database">MongoDB Atlas</a> and self-managed MongoDB 8.0+ deployments for vector and hybrid search. Developers can provide a connection string or bring an existing PyMongo client, and configure search behavior through <em>MongoDbToolSettings</em>, including index names, embedding fields, limits, and candidate counts.</p><p>That flexibility makes it possible to align the integration with existing data models, deployment choices, and performance requirements.</p><h2>Get started today!</h2><p>Install the MongoDB Google ADK Integration by running the command below:</p><p>You can learn more about the integration in the <a href="https://www.mongodb.com/docs/atlas/ai-integrations/google-adk/get-started/">documentation</a>.</p>]]></description>
      <pubDate>Wed, 11 Nov 2026 20:14:25 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/product-release-announcements/introducing-mongodb-google-adk-integration-durable-memory-agent-state</link>
      <guid>https://www.mongodb.com/company/blog/product-release-announcements/introducing-mongodb-google-adk-integration-durable-memory-agent-state</guid>
    </item><item>
      <title>Atlas Data Federation and Online Archive Can Now Be Deployed in Azure</title>
      <description><![CDATA[<p></p><p>Exciting developments are on the horizon for users of Microsoft Azure, marking a significant leap in data management capabilities. First off, <a href="https://www.mongodb.com/products/platform/atlas-data-federation">Atlas Data Federation</a> is now Generally Available on Azure. Atlas Data Federation is now generally available for deployment in Azure. An Azure deployment can query data in Microsoft Azure Blob Storage, alongside other supported sources. And that&#39;s not all. We&#39;ve also launched the General Availability of Atlas <a href="https://www.mongodb.com/products/platform/atlas-online-archive">Online Archive</a> on Azure. These advancements usher in a new era of efficient archiving solutions for Azure-based data solutions.</p><p>Both updates are big steps forward in making data management on Azure more powerful and flexible. Let&#39;s dive into what this means for you!</p><h2>Azure support in Atlas Data Federation (General Availability)</h2><p>Atlas Data Federation can query across multiple supported sources, including Atlas clusters and cloud object storage. It supports S3 or Azure Blob Storage as a source, but does not support querying S3 and Azure Blob Storage together in the same federated database instance/query. This feature, previously exclusive to AWS, is a game-changer, allowing direct deployment within Azure and the ability to tap into Microsoft Azure Blob Storage for data insights.</p><h2>Key features of Atlas Data Federation</h2><ul><li><strong>Cloud flexibility:</strong> Deployment choice: Deploy Atlas Data Federation in AWS or Azure. Cloud storage sources are queried within the supported provider configuration; cross-cloud queries between AWS S3 and Azure Blob Storage are not supported.</li><li><strong>Diverse data sources:</strong> For Azure deployments, query Atlas cluster data with supported Azure storage sources, including Azure Blob Storage and Azure Data Lake Storage Gen2. Atlas Data Federation does not combine Azure storage and AWS S3 in the same federated query.</li><li><strong>Advanced aggregation:</strong> Comprehensive aggregation capabilities with operators inclusive of $match, $lookup, $queryHistory, $merge, $out, etc.<ul><li>Direct $out support for Azure Blob Storage and Azure Data Lake Storage Gen2.</li></ul></li><li><strong>Atlas SQL queries on Azure:</strong> Execute SQL queries on Azure, integrating MongoDB data for a unified analysis experience.</li></ul><p>Atlas Data Federation simplifies accessing and analyzing complex data sets by combining data across multiple sources into a single, federated view, providing valuable insights for more informed business decisions.</p><p>A federated configuration supports at most one configured instance each of AWS S3, Azure Blob Storage, and Google Cloud Storage. This does not enable querying across cloud providers; S3 and Azure Blob Storage cannot be queried together in one federated database instance/query.</p><p><a href="https://account.mongodb.com/account/login">Explore Atlas Data Federation on Azure Today</a>.</p><h2>Azure support in Atlas Online Archive (General Availability)</h2><p>Atlas Online Archive&#39;s expansion to Azure ensures that data tiering is not only efficient but also integrated, keeping archival data within the Azure ecosystem. This integration addresses the previous limitation of defaulting to AWS for storage, even for Azure-hosted clusters.</p><h2>Key features of Atlas Online Archive</h2><ul><li><strong>Provider choice:</strong> Opt for AWS or Azure to align with your cloud strategy.</li><li><strong>Automatic archiving:</strong> Set rules to move older data to cost-effective cloud storage automatically, eliminating manual offloading.</li><li><strong>Unified querying endpoint:</strong> Access all data through a single endpoint, ensuring quick insights without compromising data availability.</li><li><strong>Integrated MongoDB Atlas UI management:</strong> Manage your data tiering and archiving within the familiar Atlas interface, streamlining operations and maintenance.</li></ul><p>Seamlessly manage your MongoDB Atlas data tiering at scale with Atlas Online Archive. Atlas Online Archive empowers you to manage your data lifecycle efficiently, balancing cost and accessibility with ease.</p><p>Finally, here are a few points to consider:</p><ul><li>Any newly created archive on an Azure cluster on or after 02/28 will default to Azure regions. Note that storage regions for Online Archive will default to Azure clusters only if there are no pre-existing AWS archives on that specific Azure cluster</li><li>If there are any pre-existing AWS Online Archives on Azure clusters, then all newly created archives on that specific cluster will remain on AWS.</li><li>Cloud providers or storage regions cannot be edited or modified once configured</li></ul><p><a href="https://account.mongodb.com/account/login">Embrace the Full Potential of Atlas Online Archive on Azure Today</a>.</p><p>We&#39;re thrilled to support your data management journey, offering enhanced control and flexibility over your data through these new Azure capabilities. As MongoDB Atlas continues to expand as a multi-cloud solution, we&#39;re here to ensure your data strategy is as dynamic and versatile as your business needs.</p><p>For guidance on getting started, check out our documentation on <a href="https://www.mongodb.com/docs/atlas/data-federation/tutorial/getting-started/">Atlas Data Federation</a> or <a href="https://www.mongodb.com/docs/atlas/online-archive/configure-online-archive/">Atlas Online Archive</a>.</p><p>Thank you for trusting MongoDB Atlas as your modern database. Welcome to expanded cloud deployment and storage options for Atlas Data Federation and Online Archive.</p>]]></description>
      <pubDate>Mon, 09 Nov 2026 13:22:06 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/product-release-announcements/atlas-data-federation-online-archive-can-now-be-deployed-in-azure</link>
      <guid>https://www.mongodb.com/company/blog/product-release-announcements/atlas-data-federation-online-archive-can-now-be-deployed-in-azure</guid>
    </item><item>
      <title>AI Search for Agents: Announcing Automated Embedding in MongoDB Atlas</title>
      <description><![CDATA[<p></p><p>Automated Embedding is now available in Public Preview on <a href="https://www.mongodb.com/products/platform/atlas-database">MongoDB Atlas</a>.</p><p>When we<a href="https://www.mongodb.com/company/blog/product-release-announcements/unlocking-ai-search-introducing-automated-embedding-in-mongodb-vector-search"> introduced Automated Embedding to MongoDB Vector Search in MongoDB Community Edition</a>, we started from a single principle: developers building agentic applications shouldn&#39;t have to operate a parallel embedding pipeline just to search their own data. That release proved the pattern: text in, text out, no client-side embedding code. On MongoDB Atlas, it goes further, using Voyage AI embedding models to solve the operational problems that have made vector search the most fragile part of an agent stack.</p><p><strong>Figure 1.</strong> Automated Embedding flow in MongoDB Atlas. </p><h2><strong>Your vector search index falls behind your data</strong></h2><p>A document gets edited. The vector store still has the old embedding. The agent retrieves stale context and confidently answers based on outdated information. The fix has historically been a backfill job, written by a human, scheduled by a human, and debugged by a human. The time between &quot;data changed&quot; and &quot;index reflects it&quot; is measured in hours, not seconds.</p><p><strong>Automated Embedding solves this with field-level delta detection</strong>. When a document changes, MongoDB Atlas re-embeds only when an indexed field actually changes. Sync is near real-time, not batch. There is no manual re-index path because there&#39;s no manual index to maintain. For agents, this is the difference between trustworthy memory and stale context.</p><p>The same property extends to search on views. If your embedding source is a $concat of title, cast, and year, an update to any of those underlying fields automatically propagates through the view to the index.</p><h2><strong>One inference pool can&#39;t serve every workload</strong></h2><p>Embedding inference is the throughput problem hiding inside a latency problem. A first-time backfill needs to chew through tens of millions of documents as fast as possible. A live query needs a vector back in tens of milliseconds. A change stream sits in between, bursty, sometimes idle, and sometimes hot. One inference pool serves all three workloads poorly: tune it for throughput and queries time out; tune it for latency, and backfills take a week.</p><p><strong>Automated Embedding separates inference into two mechanisms</strong>, each optimized for the workload it serves:</p><ul><li><strong>Index builds</strong> are throughput-optimized using a newly introduced Inference Flex Tier, enabling them to go from zero to fully indexed without competing with live queries. Variable but unbounded throughout.</li><li><strong>Queries</strong> are latency-optimized, completing within the time budget agents actually have. Guaranteed but bounded throughput.</li></ul><p>A backfill no longer slows your queries, and your queries no longer cap your backfill rate.</p><h2><strong>At scale, storage and indexing both break</strong></h2><p>Float32 vectors are honest but expensive. A million 1024-dimensional embeddings is roughly 4 GB before you&#39;ve stored a single byte of operational data. At a hundred million vectors, storage cost becomes <em>the</em> line item, retrieval latency suffers, and the team starts asking whether they really need 1024 dimensions or whether 512 would do. That&#39;s a guess most teams shouldn&#39;t be making.</p><p>Storage isn&#39;t the only thing that breaks at scale.</p><p>One document per inference request wastes orders of magnitude of throughput. Hand-tuned batching helps until you hit a document shape that exceeds the model&#39;s token window mid-batch, at which point the whole request fails. Errors at this scale don&#39;t fail one document; they fail a job, and you find out the next morning.</p><p><strong>Automated Embedding addresses both with configurable quantization and built-in dynamic batching, with no manual tuning required.</strong></p><p>For storage, configurable quantization gives you the right point on the accuracy/cost curve:</p><ul><li><strong>Scalar quantization (default)</strong> is roughly 4x smaller than float32, with retrieval accuracy nearly indistinguishable for most workloads.</li><li><strong>Binary quantization</strong> is roughly 32x smaller, for workloads where the corpus is large enough that the recall trade-off pays for itself many times over.</li></ul><p>For indexing, built-in dynamic batching automatically optimizes for the maximum tokens per request, adjusting batch size in real time based on document shape and size:</p><ul><li><strong>Automatic batch sizing</strong> adjusts in real time based on the actual shape and size of documents flowing through.</li><li><strong>Built-in error recovery</strong> means a single malformed or oversized document doesn&#39;t take down a multi-million-document indexing job. The system isolates, retries, and continues.</li></ul><p>Together, configurable quantization and dynamic batching mean agents can scale to hundreds of millions of documents without storage or indexing becoming a bottleneck.</p><h2><strong>Integrated feature engineering</strong></h2><p>Retrieval quality lives or dies on the quality of the input that gets embedded. Automated Embedding supports search on <strong>views</strong>, which means you can define a composite field declaratively, concatenating or transforming fields from the underlying collection. MongoDB Atlas automatically embeds and indexes the view&#39;s output, so feature engineering for retrieval becomes a query-language exercise instead of an ETL pipeline.</p><p>The simplest case is embedding a single field directly.</p><p><strong>Figure 2. </strong>Enabling AI search on a single field in your document.</p><p>When retrieval requirements grow more complex, you can combine multiple fields into a single embedding source.</p><p><strong>Figure 3.</strong> Enabling AI search on a combination of fields in your document.</p><p>For teams chasing the last 10-15% of retrieval accuracy, this is the lever that makes the difference. For everyone else, it&#39;s the reason you don&#39;t have to maintain a separate &quot;search index document&quot; alongside your operational schema.</p><h2><strong>Why this matters</strong></h2><p>The teams winning at agent applications treat search as a primitive, not an integration project. Automated Embedding provides retrieval that stays<strong> current</strong> as data changes, <strong>fast</strong> enough for agent response times, <strong>observable</strong> down to the token, <strong>affordable</strong> at any corpus size, and <strong>compliant</strong> out of the box.</p><p>Together, these qualities deliver a memory layer agents can depend on, built into the same platform where their data already lives. </p><h2><strong>Start building</strong></h2><p>Automated Embedding is now available in Public Preview on MongoDB Atlas across our supported regions. To get started:</p><ol><li>Spin up or select an Atlas cluster.</li><li>Define an Automated Embedding index on your collection or view, pick a model, and you&#39;re done.</li><li>Query with natural-language text - no client-side embedding required.</li></ol>]]></description>
      <pubDate>Mon, 09 Nov 2026 13:17:29 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/product-release-announcements/ai-search-for-agents-announcing-automated-embedding-atlas</link>
      <guid>https://www.mongodb.com/company/blog/product-release-announcements/ai-search-for-agents-announcing-automated-embedding-atlas</guid>
    </item><item>
      <title>Why Actionable Banking Is the Critical Stepping Stone to Full Autonomy</title>
      <description><![CDATA[<p>Almost nothing is as important to someone today as their financial health. Most of us want to stay on top of what&#39;s happening with our bank accounts, like when a deposit clears so we can pay bills, if we&#39;re reaching our credit card limit, or if we have finally paid off that 30-year mortgage and can free up funds for that dream vacation or paying for our kid&#39;s college tuition. But we don&#39;t always get immediate feedback when transactions happen. That information often sits on the backend within our banks, and then days or weeks later we may get an email or alert with advice on investing or creating a payment plan.</p><p>But with actionable banking, this all becomes immediate. With the help of agentic AI, banks’ customers can quickly have a better understanding of steps they can take to make an investment or curb their spending with AI-powered insights. And people have said they want this. </p><p>In fact, in a survey conducted by Personetics of 2,000 bank customers(1), 70% said they strongly want their bank to proactively analyze their financial situation and 84% said they would likely switch to a bank that offers timely, relevant advice.</p><p>Actionable banking is also the safest first step toward autonomous banking. The agents act on events, but a human still makes the decision. MongoDB Atlas makes this possible by turning banking events into real-time triggers, unifying customer context in one platform, and keeping an auditable record of every agent action.</p><h2>A three-step ladder: From passive to autonomous banking</h2><p>Actionable banking serves as the bridge between legacy banking and fully autonomous finance: </p><p><strong>Figure 1. </strong>The three-step ladder from passive to autonomous banking.</p><ul><li><strong>Passive banking</strong>: The customer initiates the interaction, most likely in response to a marketing campaign.</li><li><strong>Actionable banking</strong>: The bank takes a proactive approach based on real-time event analysis. Agents act on events, but the customer still makes the decision.</li><li><strong>Autonomous banking</strong>: A personal finance agent acts on its own, within limits the customer has set in advance and can revoke at any time.</li></ul><p>The gap between actionable and autonomous is not the model. It is evidence: A bank can only grant agents a mandate once it can show what each agent saw, decided, and did, and who authorized it. Actionable banking is how that evidence gets logged into the corresponding audit trail.</p><p>Actionable banking also imposes a behavioral change. A dedicated agent will be continuously monitoring personal banking information, so its success will depend heavily on the guardrails implemented by the bank, in line with the customer&#39;s consent. More importantly, it should comply with data protection and AI regulations. Policymakers are moving fast to propose frameworks that incentivize innovation with the right controls in place. In the end, actionable banking&#39;s goal is to recommend the &quot;best course of action&quot; based on specific triggered events, but the customer is the one who decides and has the final word, which safeguards trust.</p><p>Below are three actionable agentic workflows and a reference architecture built on MongoDB Atlas and Atlas Agent Engine.</p><h2>Three banking events, three agentic workflows</h2><p>Every workflow starts with the Personal Finance Agent, which listens to daily banking activity through event-driven notifications. When a significant event arrives—a large deposit, an overdue card balance, a new mortgage—the agent opens an agentic workflow, hands the work to specialist agents, and returns a proposal the customer can discuss.</p><p><strong>Figure 2. </strong>Actionable agentic workflow for proactive investments. </p><p><strong>Proactive investment</strong>. A large deposit is the clearest signal of idle money. McKinsey estimates(2) that $23 trillion of the $170 trillion in consumer deposits worldwide sits in accounts paying zero or close to zero interest. The risk profile is not a formality; the EU requires the MiFID II suitability assessment before investment advice. So a risk assessment agent&#39;s output must be stored as evidence, not just passed along in a prompt. While the personal finance agent is responsible for the interaction and agreement with the customer, the wealth advisory agent is specialized in private banking, bringing the right proposal to the customer.</p><p><strong>Figure 3. </strong>Actionable agentic workflow for proactive lending. </p><p><strong>Proactive lending</strong>. An overdue card balance is both a credit risk and a moment of customer stress. Moving the balance to a cheaper installment loan costs the bank card margin, but keeps the customer and lowers its credit risk. Creditworthiness assessment of individuals is a high-risk use under the EU AI Act, so this workflow needs the strictest human oversight of the three. A credit risk officer needs to review, approve, and have all the arguments at hand for situations where customers and regulators would demand an explanation. A single agent with lending expertise can handle both risk assessment and advisory. </p><p><strong>Figure 4. </strong>Actionable agentic workflow for proactive added-value services. </p><p><strong>Proactive added-value services</strong>. A new mortgage changes the terms of what the customer needs to protect. The insurance agent reads the mortgage conditions and proposes an insurance policy with the proper coverage, as an optional offer and never as a condition of the loan.</p><p>Each workflow ends in &quot;push and discuss,&quot; not &quot;execute.&quot; That is what makes it actionable rather than autonomous.</p><h2>Actionable banking reference architecture on MongoDB </h2><p><strong>Figure 5.</strong> Actionable banking reference architecture.</p><p>Systems of record write into MongoDB Atlas, which holds the operational view of each customer. <a href="https://www.mongodb.com/docs/manual/changestreams/?language-no-dependencies=shell">Change streams</a> turn business moments into events for the personal finance agent. Specialist agents run on <a href="https://www.mongodb.com/docs/agentengine/">Atlas Agent Engine</a>, sharing customer context through a common memory layer with per-agent access controls. Every agent action and tool call is recorded in a single, immutable audit trail. The customer&#39;s decision flows back as memory for the next interaction and as evidence for the regulator.</p><h3>The business case for actionable banking </h3><p>McKinsey(3) estimates that banks that fail to adapt to agentic AI could see global profit pools fall by about $170 billion, or roughly 9%, as customers&#39; own agents start moving idle money. Actionable banking is both the defense and the offense: The bank&#39;s agent makes the better offer before someone else&#39;s agent does.</p><h2>Why banking agent projects stall and what the platform must fix</h2><p>Banks are not short of agent pilots; they are short of agents in production. Gartner(4) expects over 40% of agentic AI projects to be canceled by the end of 2027 over cost, unclear value, or weak risk controls. Actionable banking runs into three engineering problems behind those numbers.</p><p><a href="https://www.mongodb.com/company/newsroom/press-releases/mongodb-launches-atlas-agent-engine-to-put-ai-agents-in-production-without-a-new-stack">Atlas Agent Engine</a>(5), in public preview since September of 2026, unifies runtime, memory, and governance in one layer, with sandboxed execution and agent identity built in. It is neutral across models and frameworks and built on open standards such as MCP and A2A, so a personal finance agent can delegate to specialist agents without tying the bank to one vendor&#39;s model or cloud. Paysafe is already exploring an agent engine-based agent so its analysts stop stitching together data from multiple systems by hand when investigating unusual payment activity.</p><h2>A change in behavior, not only in technology</h2><p>Actionable banking is largely an engineering pattern. Autonomous banking also requires a shift in trust and behavior. Customers must delegate, banks must accept accountability for agents that act, and regulators must be satisfied that both are safe.</p><p>The relationship manager becomes an agent. The attention of a private banker, someone who notices the bonus, the new mortgage, and the missed payment, has always been rationed by cost. A personal agent makes it available to every customer, around the clock, with memory of every conversation. Banks that get this right keep the relationship with the customer. Those that don’t may end up as the infrastructure for another party’s agent.</p><p>Trust is the ultimate mandate. The most critical challenge is not technical. Delegating decision-making authority to an agent—and granting it permission to act on behalf of an organization or an individual—turns machines into active economic participants. That is a disruptive behavioral change for customers, regulators, and banks alike. Banks have always sold trust; in autonomous banking, they must also prove it, action by action and mandate by mandate.</p><p>Start simply with one event, one workflow, or one governed proposal. That is the first step toward autonomous banking, and the data platform underneath decides how far you can take it.</p><p><strong>Sources:</strong></p><ul><li>(1)<a href="https://www.prnewswire.com/il/news-releases/new-research-shows-surging-consumer-demand-for-ai-banking-services-according-to-personetics-global-survey-859809061.html">New Research Shows Surging Consumer Demand for AI-Banking Services, According to Personetics Global Survey</a></li><li>(2)<a href="https://americanbanker.com/news/customer-use-of-ai-agents-will-depress-profits-mckinsey">Customer use of AI agents will depress profits: McKinsey | American Banker</a></li><li>(3)<a href="https://www.finextra.com/newsarticle/46803/bank-profits-face-170bn-hit-from-ai---mckinsey">Bank profits face $170bn hit from AI - McKinsey</a></li><li>(4)<a href="https://www.gartner.com/en/newsroom/press-releases/2025-06-25-gartner-predicts-over-40-percent-of-agentic-ai-projects-will-be-canceled-by-end-of-2027">Gartner Predicts Over 40% of Agentic AI Projects Will Be Canceled by End of 2027</a></li><li>(5)<a href="https://www.mongodb.com/company/newsroom/press-releases/mongodb-launches-atlas-agent-engine-to-put-ai-agents-in-production-without-a-new-stack">MongoDB Launches Atlas Agent Engine to Put AI Agents in Production Without a New Stack</a></li></ul>]]></description>
      <pubDate>Thu, 05 Nov 2026 15:31:37 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/why-actionable-banking-is-critical-stepping-stone-full-autonomy</link>
      <guid>https://www.mongodb.com/company/blog/innovation/why-actionable-banking-is-critical-stepping-stone-full-autonomy</guid>
    </item><item>
      <title>Building an Agentic Warehouse Management System—Part 3: Tools, Decisions, and Actions</title>
      <description><![CDATA[<p>If you haven’t read the first two parts yet, I recommend starting with <a href="https://www.mongodb.com/company/blog/technical/building-an-agentic-warehouse-management-system-part-1-where-ai-agents-add-value"><strong>Part 1: Where AI Agents Add Value</strong></a> and <a href="https://www.mongodb.com/company/blog/technical/building-an-agentic-warehouse-management-system-part-2-java-spring-ai"><strong>Part 2: Designing and Planning the Agent</strong></a>. There, we introduced the WMS scenario, discussed where an AI agent can add value, and built the first stages of the implementation with Java and Spring AI.</p><p>In this third and final part, we will build on the execution plan created in <a href="https://www.mongodb.com/company/blog/technical/building-an-agentic-warehouse-management-system-part-2-java-spring-ai">Part 2</a> and focus on the remaining stages of the agent workflow. We will see how each task is executed using controlled tools, how operational and business context is gathered, how the replenishment decision is made, and how the agent acts on that decision when necessary.</p><h2>From plan to execution</h2><p>Let’s revisit the complete agent flow. The first stages: <strong>Define the Agent, Trigger the Agent, and Plan,</strong> were covered in the previous article. Now we will focus on executing the tasks, using the available tools, gathering context, and making the replenishment decision.</p><p><strong>Figure 1.</strong> Agent Lifecycle: Execute, Decide, and Complete.</p><h2>Execute tasks with controlled tools</h2><p>With the execution plan created in Part 2, the <a href="https://github.com/mongodb-developer/mongodb-jvm-showcase/blob/ea5c87c042867a0ea0c71f9ca80c41b466bd2981/java/use-cases/agentic-wms/src/main/java/com/devrel/wms/agent/AgentRunner.java#L56">AgentRunner</a> starts processing the tasks one at a time. For each task, the runner reads its description and capability, executes it, stores the result, and then continues with the next task:</p><p>Before executing a task, the runner selects only the tools associated with its capability:</p><p>When the task is executed, the executor receives the current goal, the results produced by previous tasks, the current task, and only the tools available for its capability:</p><p>The result of each completed task becomes part of the context available to the tasks that follow. This allows the agent to progressively gather the information it needs before making the replenishment decision.</p><p>At the same time, the capability assigned to each task defines which tools are available during its execution. This preserves the boundaries we established earlier: an ANALYSIS task, for example, can inspect information from the WMS, but it does not have access to tools that create a replenishment request.</p><p><strong>Figure 2.</strong> Agent running.</p><h2>Accessing operational data</h2><p>During <em>ANALYSIS</em> tasks, the agent can use controlled tools to retrieve operational data from the WMS, such as inventory, invoice movements, stock movements, and pending replenishments.</p><p>For example, <a href="https://github.com/mongodb-developer/mongodb-jvm-showcase/blob/ea5c87c042867a0ea0c71f9ca80c41b466bd2981/java/use-cases/agentic-wms/src/main/java/com/devrel/wms/tool/InventoryAnalysisTool.java#L80">one</a> of the available tools retrieves the stock movements generated by an outbound invoice:</p><p>With Spring AI, methods like this can be exposed to the model using annotations such as <em>@Tool</em><em> </em>and <em>@ToolParam</em>. The executor can then call them when the current task requires that information.</p><p>The complete application exposes <a href="https://github.com/mongodb-developer/mongodb-jvm-showcase/tree/main/java/use-cases/agentic-wms/src/main/java/com/devrel/wms/tool">additional tools</a> for retrieving inventory, invoice movements, pending replenishments, and other operational data. We will not cover each one here, but they follow the same idea.</p><h2>Retrieving depositor policies</h2><p>The depositor policies are also accessed through a dedicated tool exposed by the POLICY capability. In our application, each depositor can register business rules through the <a href="https://agentic-wms-39763860545.southamerica-west1.run.app/#policies">Depositor Policies page</a>. For example, a policy may define a seven-day lead time or require at least 500 units per replenishment request:</p><p><strong>Figure 3.</strong> Depositor policies screen.</p><p>These policies are stored as natural-language documents, which allows us to retrieve them using semantic search instead of relying solely on exact keywords. For example:</p><p>When a policy is stored, its text is converted into an embedding using the configured <a href="https://github.com/mongodb-developer/mongodb-jvm-showcase/blob/6eb6dc81b5eb60976d198b92ff5ec2ff5e2dd165/java/use-cases/agentic-wms/src/main/java/com/devrel/wms/config/VoyageEmbeddingModel.java#L17">Voyage AI embedding</a> model and added to the vector store. During a <em>POLICY</em> task, the agent can ask a question based on the context collected so far:</p><p>This gives us a simple <a href="https://www.mongodb.com/docs/vector-search/tutorials/rag/?utm_campaign=devrel&amp;utm_source=third-party-content&amp;utm_medium=cta&amp;utm_content=agentic-wms&amp;utm_term=ricardo.mello">Retrieval-Augmented Generation (RAG</a>) flow: the question is used to retrieve the most relevant policies, which are then added to the execution:</p><p><strong>Figure 4.</strong> Retrieval-augmented generation (RAG) pipeline for policy lookup.</p><p>The retrieval uses <a href="https://github.com/mongodb-developer/mongodb-jvm-showcase/blob/6eb6dc81b5eb60976d198b92ff5ec2ff5e2dd165/java/use-cases/agentic-wms/src/main/java/com/devrel/wms/knowledge/DepositorKnowledgeStore.java#L46">semantic search</a>:</p><p>and is filtered by depositor and knowledge type:</p><p>Together with the results from the <em>ANALYSIS</em> tasks, these policies give the agent the operational and business context required to decide whether replenishment is needed.</p><h2>Decide</h2><p>After the <em>ANALYSIS</em> and <em>POLICY</em> tasks are completed, the <em>DECISION</em> task uses the collected context to determine whether replenishment is required. The result ends with one of two tokens:</p><p>This gives the <em>AgentRunner</em> a simple way to determine whether the remaining tasks should continue:</p><p>If replenishment is not required, the remaining <em>REPLENISHMENT</em> and <em>NOTIFICATION</em> tasks are marked as <em>SKIPPED</em>, and the execution is completed:</p><p><strong>Figure 5.</strong> Agent skipped task.</p><p>The runner marks those tasks as <em>SKIPPED</em> and completes the execution:</p><p>If replenishment is required, the execution continues with the next tasks in the plan.</p><h2>Act</h2><p>Once replenishment is required, the agent can use the <a href="https://github.com/mongodb-developer/mongodb-jvm-showcase/blob/ea5c87c042867a0ea0c71f9ca80c41b466bd2981/java/use-cases/agentic-wms/src/main/java/com/devrel/wms/tool/ReplenishmentTool.java#L41">action tools</a> exposed by the application.</p><p>The <em>REPLENISHMENT</em> task can create a replenishment request:</p><p><strong>Again</strong>: The tool does not replace the existing WMS logic. It gives the agent a controlled way to request the operation, while validation and persistence remain inside the application services.</p><p>Once created, the replenishment ID can be used by the <em>NOTIFICATION</em> task to prepare the depositor email draft:</p><p>At this point, the agent has made the decision and performed the actions required by it.</p><h2>Complete</h2><p>When there are no more tasks to execute, the agent run is completed, and a summary is generated:</p><p><strong>Figure 6</strong>. Agent finished process.</p><p>If a replenishment request was created, it is now available on the<a href="https://agentic-wms-39763860545.southamerica-west1.run.app/#replenishment"> Replenishments</a> page for review:</p><p><strong>Figure 7.</strong> Replenishments review dashboard.</p><p>This completes the flow: the agent gathers context through controlled tools, decides whether replenishment is necessary, and acts only when required.</p><h2>Next steps</h2><p>During a single execution, the agent uses the results of previous tasks as context for the tasks that follow. A natural next step would be to give the agent memory across different executions.</p><p>For example, before creating a new replenishment request, the agent could look at previous AgentRun records and use relevant outcomes from similar situations:</p><p><em>The last three requests for 500 units of this product were rejected. Approved requests were usually between 200 and 300 units. Based on the current consumption, I will request 250 units.</em></p><p>This would allow the agent to use not only the context of the current execution, but also relevant information from previous ones. One possible evolution would be to retrieve similar past executions and add them to the agent context before making a new decision.</p><p>There are many other directions in which this agent could evolve, but this is a good example of how the same design can gradually become more context-aware over time.</p><h2>Conclusion</h2><p>The main goal of this series was to show how an AI agent can add value in scenarios where business decisions depend on multiple sources of context and increasingly complex rules. Our replenishment example is only a small glimpse of what this approach can support in a real Warehouse Management System.</p><p>In <a href="https://www.mongodb.com/company/blog/technical/building-an-agentic-warehouse-management-system-part-1-where-ai-agents-add-value">Part 1</a>, we explored where an AI agent can add value in a WMS. In <a href="https://www.mongodb.com/company/blog/technical/building-an-agentic-warehouse-management-system-part-2-java-spring-ai">Part 2</a>, we translated that design into Java and Spring AI by defining the agent, its capabilities, and its execution plan.</p><p>In this third and final part, we completed the flow: tasks were executed through controlled tools, operational data and depositor policies were added to the context, and the agent used that information to decide whether replenishment was required and act when necessary.</p><p>The main idea remains the same: the application defines what the agent is allowed to do, while the agent decides what to do within those boundaries.</p><p>Explore our<a href="https://github.com/mongodb-developer/mongodb-jvm-showcase"> MongoDB JVM Showcase</a> repository for more Java examples and use cases. If you find it useful, consider giving it a ⭐.</p>]]></description>
      <pubDate>Thu, 05 Nov 2026 15:00:01 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/technical/building-an-agentic-warehouse-management-system-part-3-tools-decisions-actions</link>
      <guid>https://www.mongodb.com/company/blog/technical/building-an-agentic-warehouse-management-system-part-3-tools-decisions-actions</guid>
    </item><item>
      <title>Quick Start: C# and MongoDB - Starting and Setup</title>
      <description><![CDATA[<p></p><p>In the first of the C# Quick Start series, I&#39;ll show how to set up connections between C# and MongoDB.</p><p>In future parts we&#39;ll move on and work through:</p><ul><li>Database Create, Read, Update, and Delete (CRUD) operations</li><li>Map MongoDB to C# objects</li><li>Look at MongoDB aggregation</li><li>How to use LINQ with MongoDB</li></ul><p>As you already know, C# is a general-purpose language and MongoDB is a general-purpose data platform. Together, C# and MongoDB are a powerful combination.</p><p>To follow along, I&#39;ll be using Visual Studio 2019 on Windows 10 and we will be connecting to a MongoDB Atlas cluster.</p><p></p><p>If you&#39;re using a different OS, IDE, or text editor, the walkthrough might be slightly different, but the code itself should be fairly similar. Let&#39;s jump in and take a look at how nicely C# and MongoDB work together.</p><h2>Getting Setup</h2><p>For this demonstration, I’ve chosen to create a Console App (.NET Core), and I’ve named it MongoDBConnectionDemo.</p><p>Next, we need to install the MongoDB Driver for C#/.NET for a Solution. We can do that quite easily with <a href="http://bit.ly/nuget-home">NuGet</a>. Inside Visual Studio for Windows, by going to <em>Tools</em> -&gt; <em>NuGet Package Manager</em> -&gt; Manage NuGet Packages for Solution..._</p><p>We can browse for <em>MongoDB.Driver</em>. Then click on our Project and select the driver version we want. In this case, the <a href="http://bit.ly/mongodb-csharp-driver">latest stable version</a> is 2.9.1. Then click on <em>Install</em>. Accept any license agreements that pop up and head back to Program.cs to get started.</p><h2>Putting the Driver to Work</h2><p>To use the MongoDB.Driver we need to add a directive.</p><p></p><p>Inside the Main() method we’ll establish a connection to <a href="https://www.mongodb.com/products/platform/atlas-database">MongoDB Atlas</a> with a connection string and to test the connection we’ll print out a list of the databases on the server. The Atlas cluster to which we’ll be connecting has the MongoDB Atlas <a href="http://bit.ly/atlas-sample-data-blog">Sample Dataset</a> installed, so we’ll be able to see a nice database list.</p><p>The first step is to pass in the MongoDB Atlas connection string into a MongoClient object, then we can get the list of databases and print them out.</p><p></p><p>When we run the program, we get the following out showing the list of databases:</p><p></p><p>The whole program comes in at just over 20 lines of code:</p><p></p><h2>C# and MongoDB</h2><p>By developing with C# and MongoDB together one opens up a world of possibilities. Console, window, and web applications are all possible. As are cross-platform mobile applications using the <a href="http://bit.ly/home-xamarin">Xamarin</a> framework. Join me in this Quick Start series and learn how to perform CRUD operations with C# and MongoDB.</p><h4>Other articles in this Quick Start C# and MongoDB series:</h4><ul><li><a href="https://www.mongodb.com/company/blog/quick-start-c-sharp-and-mongodb-creating-documents">Quick Start: C# and MongoDB - Creating Documents</a></li><li><a href="https://www.mongodb.com/company/blog/quick-start-c-and-mongodb-read-operations">Quick Start: C# and MongoDB - Read Operations</a></li><li><a href="https://www.mongodb.com/company/blog/quick-start-csharp-and-mongodb-update-operation">Quick Start: C# and MongoDB - Update Operations</a></li><li><a href="https://www.mongodb.com/company/blog/quick-start-csharp-and-mongodb-delete-operations">Quick Start: C# and MongoDB - Delete Operations</a></li></ul><h2>Get Started with MongoDB Atlas</h2><h4>Run MongoDB in the cloud for free with MongoDB Atlas. No credit card required.</h4><a href="https://www.mongodb.com/cloud/atlas/register">Try Free</a>]]></description>
      <pubDate>Tue, 03 Nov 2026 20:09:41 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/technical/quick-start-c-sharp-and-mongodb-starting-and-setup</link>
      <guid>https://www.mongodb.com/company/blog/technical/quick-start-c-sharp-and-mongodb-starting-and-setup</guid>
    </item><item>
      <title>Introducing Atlas App Connections: Secure, One-Click Access for AI Tools</title>
      <description><![CDATA[<p>For builders using AI coding tools, speed is everything. Integrations that require generating a credential, filing an access request, or waiting on a custom build can stop momentum (and productivity) in its tracks.</p><p>Until now, connecting an external application like an AI coding assistant to a MongoDB Atlas account introduced some of that friction. The only way to do so was by sharing long-lived service account credentials, a workaround that slowed builders down and left administrators managing a security risk they were reluctant to accept. Faced with that tradeoff, some organizations avoided third-party integrations, or defaulted to whatever tool was already the default in their AI stack, whether or not it was the best fit.</p><p><a href="https://www.mongodb.com/docs/atlas/app-connections/">MongoDB Atlas App Connections</a> closes that gap. It enables builders to securely connect AI coding tools to their <a href="https://www.mongodb.com/products/platform/atlas-database">MongoDB Atlas</a> account with a single click. Built on OAuth 2.1, an industry-standard authorization framework, App Connections allows AI clients to act on the user&#39;s behalf via the <a href="https://www.mongodb.com/products/tools/mcp-server">MongoDB Atlas MCP Server</a>, without long-lived credentials to generate, share, or manage.</p><h2>Available now in Atlas App Connections</h2><p>With Atlas App Connections, builders can connect their AI coding tools to MongoDB Atlas through the Atlas MCP Server, including: </p><ul><li><p>ChatGPT</p></li><li><p>Claude</p></li><li><p>Claude Code</p></li><li><p>Codex CLI</p></li><li><p>Cursor</p></li><li><p>Devin</p></li><li><p>Devin Desktop</p></li><li><p>Grok</p></li><li><p>Grok CLI</p></li></ul><p>Once connected, these tools can provision, manage, and query MongoDB Atlas resources directly on the builder&#39;s behalf, whether that means spinning up a new cluster, checking on an existing one, or working with the data inside it, based on the access the connecting user already has. Administrators control how far that access extends, choosing between read-only and full access before any AI client can act.</p><h2>Using App Connections in practice</h2><p>Here&#39;s what that looks like for a builder, using Claude as an example. Assuming Claude is already running, connecting a MongoDB Atlas account takes three steps:</p><ol><li><p>Install the MongoDB plugin by running <em>/plugin install mongodb-atlas@claude-plugins-official</em>.</p></li><li><p>Grant Claude access by running <em>/mcp</em>, selecting <em>plugin:mongodb-atlas:mongodb-atlas</em>, and choosing Authenticate.</p></li><li><p>Approve the one-click authorization.</p></li></ol><p>Installing the plugin also adds a set of skills that teach Claude how to work with MongoDB Atlas, and installs MongoDB&#39;s remote MCP server behind the scenes. From there, the developer can simply ask Claude to provision a new database cluster, and Claude does it: translating that request into secure Atlas API calls through the Atlas MCP Server. There&#39;s no credential to generate or share to make that happen. The administrator overseeing that Atlas organization still has full visibility into the connection and can revoke it at any time.</p><h2>What you get if you’re building</h2><p>For builders, speed and security have always felt like a tradeoff. Bottlenecked by integration setup friction, many resorted to workarounds such as sharing high-risk, long-lived credentials just to keep building. </p><p>Atlas App Connections removes that tradeoff. A single click securely authorizes AI coding tools to connect to Atlas. There are no credentials to share and no manual configuration to manage. Builders stay in their flow, building at the speed of AI, without ever compromising account security to get there.</p><h2>What you get if you’re governing an organization</h2><p>For administrators, the calculus has been just as fraught. Engineering teams need modern AI coding tools to stay competitive, but granting those tools access via opaque, shared service accounts can mean losing track of who or what is actually acting on an organization&#39;s data. </p><p>Atlas App Connections eliminates that challenge. Access to connect AI clients to Atlas is disabled by default in existing organizations, and administrators must opt in. New organizations created during sign-up start with that access enabled, so first-time users get the best possible AI experience from the outset. Once approved, every action is attributed to both the application and the person who authorized it, visible in Atlas activity feeds. Administrators decide exactly how long an AI client&#39;s access can last before it requires re-approval, and can turn off AI client access for the entire organization at any time. Individual users can revoke their own connections whenever they choose. Atlas App Connections helps eliminate shadow AI without standing in the way of engineering teams doing their jobs.</p><h2>How Atlas App Connections works</h2><p>Connecting an AI coding tool to Atlas using App Connections takes five steps:</p><ol><li><p>The user installs MongoDB&#39;s plugin or connector for their AI client.</p></li><li><p>The user requests to connect their MongoDB Atlas account from within that client.</p></li><li><p>The client redirects the user to Atlas.</p></li><li><p>The user logs in and sees a consent screen naming the application and exactly what it&#39;s asking to access.</p></li><li><p>All the user has to do is click “Approve” and the application is enabled to act on their behalf through the Atlas MCP Server.</p></li></ol><p>Behind the scenes, that approval gives the AI coding tool permission to obtain a short-lived access token and a refresh token on the user&#39;s behalf, so it doesn&#39;t need to ask the user to log in again for every action. The tool uses that access to provision, manage, and query Atlas resources through the Atlas MCP Server, scoped to whatever access the connecting user already has. All of this happens automatically, invisible to both the user and the application.</p><p>A few properties of that access are worth knowing:</p><ul><li><p><strong>User-scoped:</strong> The AI client can only take actions for which the user has permissions. If a user&#39;s Atlas permissions change, the AI client&#39;s access automatically changes with them.</p></li><li><p><strong>Revocable:</strong> Users can revoke an AI client&#39;s access at any time, and it takes effect within 15 minutes.</p></li><li><p><strong>Auditable:</strong> Every delegated action is attributed to both the AI client and the user it acted on behalf of.</p></li><li><p><strong>Governed by the organization:</strong> Delegated access to AI clients is disabled by default. Atlas organization owners decide whether to turn it on, and for AI clients specifically, whether to allow read-only or full access. If an owner turns off delegation for the entire organization, that change takes effect immediately.</p></li></ul>]]></description>
      <pubDate>Tue, 03 Nov 2026 20:08:21 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/product-release-announcements/introducing-atlas-app-connections-secure-one-click-access-for-ai-tools</link>
      <guid>https://www.mongodb.com/company/blog/product-release-announcements/introducing-atlas-app-connections-secure-one-click-access-for-ai-tools</guid>
    </item><item>
      <title>Building Next-gen AI agents: The MongoDB Atlas-Microsoft Foundry Integration</title>
      <description><![CDATA[<p>Generative AI is rapidly evolving from experimenting with models to relying on intelligent, autonomous multi-agent workflows that can reason, act, and adapt in real time. Together, Microsoft and MongoDB are defining the future of AI by providing companies everywhere a robust, secure, scalable foundation for building innovative, next-generation AI agents.</p><p>Microsoft Azure Foundry provides a unified, enterprise-grade platform to build, deploy, and govern AI applications and agents, while MongoDB Atlas delivers the flexible, secure, and scalable data foundation that gives those agents real-time memory, context, and intelligence across the Azure ecosystem.</p><p>Today, we’re pleased to announce that Microsoft and MongoDB are taking that collaboration to the next level, bringing the <a href="https://www.mongodb.com/products/tools/mcp-server">MongoDB MCP Server</a> into the tools catalog in Microsoft Foundry. This integration bridges Microsoft Foundry’s Agent Service with MongoDB’s real-time data capabilities—empowering developers to build context-aware agents that can both retrieve knowledge and perform actions using MongoDB Atlas.</p><h2>MongoDB Atlas meets Microsoft Foundry </h2><p>Originally introduced by Anthropic, the Model Context Protocol (MCP) has become the de facto standard for communication between AI agents and external data systems. In essence, MCP servers bridge AI agents and live business data. </p><p>Microsoft Foundry’s MCP support extends this power to its Agent Service, enabling seamless integrations with diverse systems—whether hosted locally in Azure tenant or remotely in the provider’s cloud. Adding the MongoDB MCP Server to the Tools Catalog allows for easy access to the tools supported by the MongoDB MCP Server, broadly classified as Atlas tools and Database tools. For all MongoDB MCP Server-supported tools, <a href="https://github.com/mongodb-js/mongodb-mcp-server?tab=readme-ov-file#%EF%B8%8F-supported-tools">check out GitHub</a>. </p><p>This integration allows Microsoft customers to give their AI systems secure, contextual, and real-time access to enterprise data in MongoDB Atlas—all within a governed, scalable architecture. It also allows the agents to take actions/perform operations like inserting or updating documents, managing clusters, or creating users.</p><p></p><p>The MongoDB MCP Server translates agentic requests coming from Microsoft Foundry into structured, policy-compliant queries to MongoDB Atlas, returning context-rich results that agents can use to reason, act, and learn safely. Beyond enabling retrieval for retrieval-augmented generation (RAG) scenarios, it also enables other database operations such as update, insert, delete, create indexes, etc. It also supports Atlas operations such as creating projects, clusters, and database users. Because the MCP Server connects through MongoDB’s native APIs and security model, enterprises can control exactly what data an agent can access.</p><h2>How to deploy the MongoDB MCP Server in Microsoft Foundry</h2><p>Within the Microsoft Foundry interface:</p><p>1. Select <strong>MongoDB MCP Server</strong> from the Tools Catalog.</p><p></p><p>2. Click Connect, which provides deployment instructions, and click GitHub for a Bicep template for hosting the server on Azure Container Apps (ACA).</p><p></p><p>3. Use the ACA URL and your preferred authentication method to connect to the MCP Server.</p><p>4. Configure which tools the agent can access, and define clear usage instructions for each agent on how and when to use the tools.</p><p>This seamless integration extends across both the Microsoft Foundry UX, SDK and API, ensuring flexibility for developers building advanced agentic workflows.</p><p>With the MongoDB MCP Server, Microsoft Foundry agents can move beyond static knowledge bases or stale vector stores. They can now interact with fresh, operational data—grounding their insights, actions, and recommendations in the latest enterprise context. Agents can now autonomously do data exploration, database management, and assist in code generation—all while maintaining compliance and security.</p><h2>Enabling enterprise AI</h2><p>The MongoDB MCP Server-Microsoft Foundry integration is a major step forward in enterprise AI enablement. It delivers a secure, scalable, and governed pathway from experimentation to production—turning enterprise data into the active backbone of intelligent decision-making and workflow automation.</p><p>This collaboration paves the way for trustworthy, context-aware AI systems that align seamlessly with real-world business processes, permissions, and policies—accelerating the journey from AI prototypes to production-ready agents.</p><p></p><p></p>]]></description>
      <pubDate>Tue, 03 Nov 2026 20:02:58 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/building-next-gen-ai-agents-mongodb-atlas-integration-microsoft-foundry</link>
      <guid>https://www.mongodb.com/company/blog/innovation/building-next-gen-ai-agents-mongodb-atlas-integration-microsoft-foundry</guid>
    </item><item>
      <title>Automated, Secure, and Scalable: Reference Implementation for Atlas on Azure</title>
      <description><![CDATA[<p>Today’s cloud-driven world is characterized by the requirement to scale—and to do so massively and faster than ever. But standing up secure and compliant environments on the cloud is complex and requires huge efforts, as teams have to figure out networking, policies, identity, and governance requirements across numerous projects.</p><p>At MongoDB, we’re focused on empowering enterprise customers to build faster, smarter, and more securely. We know how important it is to developers to be able to quickly onboard and start building on a trusted platform. But to stand up secure, governed, production-ready Atlas clusters, a standardized cloud foundation is essential.</p><p>That’s where the <strong>MongoDB Atlas on Azure Reference Implementation </strong>comes in. Designed to bring the power of MongoDB Atlas to Microsoft Azure customers, this reference architecture and sample implementation enables teams to automatically deploy MongoDB Atlas clusters that align seamlessly with Microsoft Azure’s well-architected framework, avoiding inconsistent deployments, security gaps, and reduced developer productivity.</p><h2>Introducing the MongoDB Atlas on Azure reference implementation <strong> </strong></h2><p> The MongoDB Atlas on Azure reference implementation extends automation and governance to the data layer, allowing you to deploy MongoDB Atlas with confidence that your database setup is repeatable and adheres to your organization’s policies and compliance frameworks automatically.</p><p> The reference implementation (RI) is our prescriptive guidance and automation toolkit to deploy Atlas seamlessly within your enterprise-grade Azure environment.</p><p> Here’s what it delivers:</p><ul><li><p><strong>Automated deployment:</strong> We provide Infrastructure-as-Code (IaC) Terraform templates that automatically provision and configure Atlas to align perfectly with Azure and MongoDB architecture standards. This includes setting up both single-region and multi-region Atlas clusters using a DevOps Pipeline with a manual approval gate. </p></li><li><p><strong>Prescriptive security:</strong> The RI provides guidance and recommendations on security best practices. It automates the configuration of private endpoints within customer Azure VNet, NSGs, NAT Gateway, and VNet Peering between multi-region application nodes—providing for secure communication and network isolation. </p></li><li><p><strong>Scalable by design:</strong> The RI establishes a repeatable deployment pattern for MongoDB Atlas. This means every new development team can spin up a pre-configured, secure, and governed Atlas environment quickly, allowing your organization to rapidly and systematically scale.</p></li><li><p><strong>Monitoring and observability:</strong> The RI includes a monitoring component, wherein an Azure Function App periodically queries the MongoDB Atlas API to gather database health and performance metrics, which are visualized in the Application Insights dashboards. </p></li><li><p><strong>Test DB connectivity:</strong> The RI can also deploy an optional Web App to confirm the connectivity between the application and MongoDB Atlas was successful and secure.</p></li></ul><h2>MongoDB Atlas on Azure architecture overview</h2><h3>Single-region architecture</h3><p>In the single-region deployment, all core components—including the MongoDB Atlas cluster, Azure Virtual Network, monitoring, and supporting application infrastructure—are provisioned within a single Azure region. This setup is ideal for applications with regional data residency requirements or when resilience to regional failure is not a primary concern.</p><p></p><h3>Multi-region architecture</h3><p>For organizations with higher requirements for business continuity and disaster recovery, the multi-region architecture distributes MongoDB Atlas cluster nodes and supporting infrastructure across multiple Azure regions. The design leverages VNet peering and multiple private endpoints to provide seamless, secure connectivity, even in the event of a regional failure.</p><p></p><h4>Components:</h4><ol><li><p><strong>Application or service:</strong> Applications or services are deployed in the subnet with the NSG and the NAT so that they are secured and have visibility to the MongoDB Atlas clusters. These can include web apps, backend services, analytics jobs, or integration tools.</p></li><li><p><strong>MongoDB Atlas Cluster:</strong> The MongoDB Atlas clusters are visible through a private endpoint connection and can connect to the applications or services deployed in the secured Azure Virtual Network.</p></li><li><p><strong>Observability:</strong> An Azure Function App periodically queries the MongoDB Atlas API to gather database health and performance metrics, which are visualized in Application Insights dashboards.</p></li><li><p><strong>Resiliency:</strong> VNet Peering is enabled so that in case of a regional outage, all remaining regions have visibility to the rest of the MongoDB Atlas clusters.</p></li></ol><h2>Accelerating innovation</h2><p>The MongoDB Atlas on Microsoft Azure Reference Implementation helps bridge the gap between developer agility and enterprise control. It provides the automation, security, and scalability needed to deliver data-driven innovation faster—while aligning with your organization’s cloud governance model. With this accelerator, enterprises can standardize data deployments, empower teams to focus on building applications instead of managing infrastructure and confidently scale MongoDB Atlas across their Azure ecosystem.</p><p>The RI offers a unified approach that brings together the best of MongoDB’s modern data platform and Azure’s cloud foundation—enabling organizations to innovate securely and at scale.</p><p></p>]]></description>
      <pubDate>Tue, 03 Nov 2026 20:02:16 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/automated-secure-scalable-reference-implementation-mongodb-atlas-on-azure</link>
      <guid>https://www.mongodb.com/company/blog/innovation/automated-secure-scalable-reference-implementation-mongodb-atlas-on-azure</guid>
    </item><item>
      <title>Fighting Tool Sprawl: The Case for AI Tool Registries</title>
      <description><![CDATA[<p>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. </p><p>Every enterprise needs its own shared tool registry, one that reflects its specific regulatory environment, security posture, and operational conventions. To be clear, this is not an argument for a public package manager, something like npm, PyPI, or Maven. The infrastructure each enterprise needs is internal; scoped to its own teams, its own data, its own policies, its own domain. Trying to expand the scope beyond the confines of individual organizations would be premature standardization in a fast-moving, nascent space. </p><p>A shared enterprise tool registry is not an optimization or a nice-to-have. It is foundational infrastructure as agent deployments scale beyond early experiments. The case for it rests on two pillars: reducing coordination cost and enabling risk management, both for the humans building with agents and for the agents themselves. </p><p>AI agents depend on tools that retrieve data, write records, trigger workflows, and call external APIs. According to <a href="https://www.mckinsey.com/capabilities/quantumblack/our-insights/seizing-the-agentic-ai-advantage">McKinsey</a>, in most large organizations, these tools are built by individual teams in an ad hoc fashion: undocumented, ungoverned, and invisible to the rest of the organization. This pattern is familiar to most engineering leaders, and the fragmentation it creates compounds with every new agent deployment. Teams rebuild what already exists elsewhere, security reviews miss tools that were never registered, and when something breaks, no one has a complete picture of what is running or why.</p><h2>A coordination failure at infrastructure scale</h2><p>The software industry solved an analogous problem decades ago with package managers. Centralized registries gave teams a way to discover, depend on, and govern shared code. The learning was clear: preventing duplication and inconsistency is an infrastructure problem, not a discipline problem.</p><p>The agent era presents the same problem in a new domain. When <a href="https://konghq.com/company/press-room/press-release/kong-introduces-mcp-registry">Kong launched its enterprise MCP Registry</a> in February 2026, they explicitly called out the problems of manual MCP configuration, hardcoded and managed tool isolation across teams, fragmented integrations, and limited organization visibility.</p><p>Fragmented tool development is not a consequence of poor engineering practice. Rather, it is the predictable outcome of asking teams to solve an infrastructure problem at the application layer.</p><h2>The visibility problem</h2><p>Gravitee&#39;s <a href="https://www.gravitee.io/state-of-ai-agent-security">The State of AI Agent Security 2026</a> survey quantifies what happens when agent tooling is invisible to the people responsible for securing it. The survey found that only 14.4% of teams with agents beyond the planning phase have full security approval, and 88% of organizations had an agent-related security incident this year. Bad practices like shared API keys are endemic, with only 22% of organizations treating agents as independent identities. This governance gap transforms agents from productivity boosters into high-velocity liabilities capable of executing unauthorized actions or leaking sensitive data before a human can even intervene.</p><p>The story is clear: adoption is outpacing governance, and in a race for speed, old lessons are having to be retaught. The majority of deployed agents (and the MCP servers powering them!) are operating without any security sign-off. This is not primarily a resourcing failure, and it is not something a registry alone solves. Security teams cannot review what they cannot discover, and without a registry, discovery is manual, incomplete, and stale. A registry does not make tools inherently secure; rather, it makes security work possible by ensuring tools exist not as transitory, ad hoc shims, but rather as inventoried artifacts that audits and policy can attach to. </p><p>It is worth revisiting public package managers here. These registries have not been able to eliminate a number of security problems, issues such as typosquatting, malicious packages, and dependency confusion, showing clearly that centralization alone is not a security solution. But they also show the converse: a registry is a precondition for security. Numerous community responses to breaches in these ecosystems demonstrate the power centralization provides. Centralization does not guarantee security, but decentralization forfeits the means to coordinate it.</p><h2>Governance requires shared context</h2><p>The default posture in most agent deployments is permissive: tools are available unless explicitly blocked. <a href="https://agilityfeat.com/blog/layered-ai-guardrails-for-enterprise-ai-agents">AgilityFeat&#39;s analysis of enterprise AI guardrails</a> identifies the structural risk this creates, since an architecture not built on deny-by-default increases risk and creates upkeep costs.</p><p>Allow-by-default, replicated across dozens of independent agent deployments, produces an attack surface that scales with adoption. Inverting this requires a coordination point, a shared, organization-wide context. The registry itself isn’t a governance layer, but it is what makes governance possible. When every tool an agent can use is registered with ownership, version, and review status, the governance layer has something concrete to enforce against. Without that context, policy has to be reimplemented by every consuming team, and consistency becomes impossible.  </p><p>Frontegg&#39;s framework for AI agent governance describes what that policy layer looks like operationally: agent actions mapped to explicit, granular guardrails that define the operational boundaries for what any agent can attempt or execute. These guardrails live outside the registry, but they depend on it. A guardrail that references a tool the security team has never heard of cannot be written in the first place.</p><h2>What a production-grade tool catalog requires</h2><p>A mature enterprise tool registry has two core functions, discovery and versioning, and serves as the foundation for two others: certification metadata and access control. Think of it as an Internal Developer Portal (IDP) built for the agent era, solving the same coordination problem that IDPs solved for service teams, but one layer up.</p><p>Discovery allows any team building an agent to search for existing tools before writing new ones. With ownership metadata, version history, and usage metrics centralized, duplication is reduced not through mandate but through reduced friction. A well-designed catalog goes further than a flat list: tools should be grouped hierarchically by functional domain so that both humans and agents can find relevant capabilities quickly.  </p><p>Versioning closes a gap that neither discovery nor access controls address: when agent behavior changes, why did it change? A tool registry that tracks versions gives enterprises the visibility to answer that question. Was it the model? A tool prompt update? An underlying API change? Without proper versioning, finding the answer goes from a simple diff comparison to a time-consuming, manual investigation. </p><p>Certification status (things like security approval, API contract validation, PII handling checks) is metadata that the registry surfaces, not a boundary that the registry itself enforces. The actual review work happens through the security organization’s existing tooling. The registry’s contribution is making the result of that review visible at the moment a team is deciding whether to adopt a tool, ensuring the review actually informs the decision it was meant to inform. </p><p>Access control works the same way. A policy layer enforces authorization scoped to agent identity, team, environment, and action type, reading from the registry to know what tools exist and who owns them. The registry’s centralization lets access control be applied consistently, rather than forcing each team to come up with something bespoke. </p><p>None of this is achievable when each team maintains its own isolated tooling stack. Platform teams already understand why IDPs exist. The value of the paradigm in the agent context is no different.</p><h2>The compounding cost of inaction</h2><p>The cost of inaction is direct, not merely operational and security-related. Without a searchable, well-organized catalog of tools, teams continually reinvent the wheel, since it is easier to generate a tool than to find one that already exists. Duplication means redundancy and technical debt. A registry, by making tools discoverable and reusable, converts that redundant spend into capacity for actual work. </p><p>For platform engineering teams, the trajectory is clear. Agent adoption is increasing, tool duplication is increasing with it, and the shims that worked at small scale will not hold as the number of agents and tools grows. The security exposure documented in the Gravitee survey will widen, not narrow, without structural intervention.</p><p>The organizations that build centralized tool infrastructure now will be able to onboard new agents quickly, govern them consistently, and audit them when something goes wrong. Those that defer will rediscover, the hard way, what platform teams learned a decade ago: coordination problems do not resolve themselves at the application layer. They compound there. </p>]]></description>
      <pubDate>Tue, 03 Nov 2026 20:01:13 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/technical/fighting-tool-sprawl-case-for-ai-tool-registries</link>
      <guid>https://www.mongodb.com/company/blog/technical/fighting-tool-sprawl-case-for-ai-tool-registries</guid>
    </item><item>
      <title>Financial Crime Mitigation with MongoDB / Part IV: Agentic AI for Case Management</title>
      <description><![CDATA[<p>Welcome back to the last part of our series on Building a Financial Crime Mitigation Platform. We have shown how MongoDB ideally supports the technical capabilities of modern digital financial operations as a unified data platform. In case you missed it, be sure to check out <a href="https://www.mongodb.com/company/blog/innovation/building-financial-crime-mitigation-platform-with-mongodb-series-overview">the series overview</a>.</p><p>In today’s world, fraud management systems need to react in the moment. Immediacy has become a must-have characteristic of control systems. Real-time monitoring is required not only to block potential fraudulent activities, but also to fulfill customers’ expectations. Modern financial services, like instant payments, demand straight-through screening processing that executes all the corresponding checks instantaneously. Therefore, the challenge is to ensure comprehensive checks are executed without creating bottlenecks in the customer experience.</p><p>This blog explains how to operationalize enhanced due diligence with an agentic SAR investigation pipeline built with LangGraph and MongoDB. Rather than stopping at alert generation, the solution uses specialized agents to triage suspicious activity, gather evidence in parallel across entities, transaction, network, and watchlist data, analyze investigative leads, draft compliance-ready SAR narratives, and route cases through durable human-in-the-loop review.</p><p>To begin, we must put in perspective the end-to-end process for fraud management, which consists of the following stages:</p><p><strong>Figure 1. </strong>Fraud management end-to-end process.</p><h2>Fraud reaction’s due diligence</h2><p>Previously, we learned how to <a href="https://www.mongodb.com/company/blog/innovation/building-a-dynamic-customer-profile-using-mongodb">build a dynamic profile</a> for the <strong>fraud prevention</strong> stage. Then, we analyzed how <strong>fraud detection</strong> can be enhanced by <a href="https://www.mongodb.com/company/blog/financial-crime-mitigation-with-mongodb-part-ii-comprehensive-analysis">conducting a behavioural analysis and transaction monitoring</a>. Now, if an activity has been flagged as suspicious, then we have arrived at the last stage, <strong>fraud reaction</strong>: here we need to combine information from the customer profile, the anti-money laundering policies, with the transaction’s contextual information, along with the <a href="https://www.mongodb.com/company/blog/financial-crime-mitigation-with-mongodb-part-ii-comprehensive-analysis">Suspicious Activity Report</a> generated in the previous step. This last process is known as <em>due diligence</em>. </p><h2>Enhanced due diligence</h2><p>Historically, digitized anti-money laundering (AML) solutions focused on dashboarding and rule-based automation. While these improved service level agreements (SLAs), they introduced a &quot;fragmentation tax&quot; risk. Analysts must manually stitch together disparate data points, leading to high false-positive rates and significant operational latency. </p><p>Agentic AI introduces a paradigm shift: rather than relying on brittle, hard-coded rules, financial services institutions can deploy autonomous, specialized agents that synthesize disparate data points in real-time. However, for these agents to be effective in an enterprise setting, they require more than just a large language model (LLM); they require a durable, high-performance data backbone.</p><p>Digitized solutions came to the rescue to support risk analysts in their jobs. Mainly, by enabling reporting dashboards, powered by fast search engines, and automating some tasks with rule-based logic. Even though digitized solutions drastically improved SLAs, it was still error-prone. Several studies have shown that not only the rate of false positives remains high, but they are increasingly running on a costly operation with little to no return on investment (ROI). </p><h2>(Agentic AI) Enhanced due diligence<strong> </strong></h2><p>Agentic AI capabilities make the perfect fit for this scenario: Having smart agents that can automate manual checks more accurately, being able to easily combine several data points, or better yet generate synthetic data for evaluating potential scenarios, and lastly bringing natural language interactive ability, makes the perfect co-pilot to risk analyst for providing precise recommendations in complex cases, or to have the full autonomy to approve or reject evident cases that won’t require a human escalation.</p><h2>Putting into practice agentic AI-enhanced due diligence (EDD)</h2><p>Coming back to the <a href="https://github.com/mongodb-industry-solutions/fsi-aml-fraud-detection">demo prototype</a> we’ve explored in the series, we have a team of agents specialized in completing specific tasks: </p><p><strong>Figure 2.</strong> Specialized agents created for enhanced due diligence operations.</p><p>When operationalizing Agentic AI for “fraud reaction”, the architectural focus must be on state management. A common pitfall is assuming the agent itself holds the &quot;truth.&quot; In enterprise AML, the agent is merely the processor; the state must reside in a durable, persistent store. </p><p>MongoDB and LangGraph provide an ideal architectural fit: LangGraph provides the orchestration and dynamic routing, and MongoDB serves as the single source of truth. Its flexible document model handles the polymorphic nature of AML data (SARs, alerts, and entity metadata) without the need for destructive schema migrations. Leveraging <a href="https://www.mongodb.com/products/platform/atlas-vector-search">MongoDB Atlas Vector Search</a> allows financial institutions to consolidate transactional data and vector embeddings into a single store, eliminating the &quot;database sprawl&quot; associated with maintaining separate vector databases and operational stores.</p><p>For CTOs, &quot;agentic&quot; does not imply &quot;unsupervised.&quot; The true power of this architecture lies in the Human-in-the-loop (HITL) pattern as an explicit Audit Design Pattern. Using MongoDB to store the complete provenance of an agent’s decision-making process supports auditability by making every step traceable. Risk analysts do not just see a final decision; they see the chain of thought and the data sources that led to that decision, allowing for faster, more confident sign-offs.</p><p><strong>Figure 3.</strong> Stages for automating having a Human-in-the-loop as “analyst review” step.</p><h2>Agentic process workflow</h2><p>After building and configuring the specialized agents comes the agentic process workflow:</p><p><strong>Figure 4.</strong> Agentic workflow for enhanced due diligence operations.</p><ol><li>The process begins with a notification to the <strong>triage agent</strong> that a new Suspicious Activity Report (SAR) has been registered. It proceeds to launch a few sub-agents for fetching actions: gathering information from the entity, transactions, watchlists, and network.</li><li>Next, it derives all the consolidated information to a <strong>case analyst agent</strong>, which in turn orchestrates the analysis done by sub-agents. It sends all the generated output to a <strong>SAR author agent</strong>, an expert in Due Diligence terminology, which ensures that the case is documented using the organization&#39;s terminology.</li><li>The SAR is handed over to a <strong>compliance QA agent</strong> that ensures that it is following the policies, rules, and standards defined by the risk management organization. Using its natural language capabilities, it can adjust accordingly.</li><li>Lastly, the case is handed over to the risk analyst for the final human review in order to be dispatched for the corresponding compliance enforcement action. </li></ol><h2>Takeaways</h2><p>Implementing agentic AI shifts your fraud mitigation strategy from &quot;manual effort&quot; to &quot;autonomous scale.&quot; To successfully scale this architecture, keep these foundational principles in mind:</p><ul><li><strong>Design for specialization</strong>: Do not build &quot;general purpose&quot; agents. Design specialized agents with narrow scopes to simplify monitoring, governance, and model optimization.</li><li><strong>Centralize state, distribute logic</strong>: Maintain a single contextual data layer (MongoDB) as your source of truth. Allow your orchestration framework (LangGraph) to handle the logic, but offload the persistence of state to the data platform.</li><li><strong>Prioritize auditability</strong>: Ensure your agentic workflow captures not just the output, but the context and references used for each decision. This transforms &quot;AI recommendations&quot; into &quot;compliance-ready logs.&quot;</li></ul><p><em>This is the last article in this series. We would like to thank you for joining us in this journey. Feel free to revisit the series to have a full picture of building a Financial Crime Mitigation platform powered by a modern data platform like MongoDB. We also invite you to check out our prototype (</em><a href="https://github.com/mongodb-industry-solutions/fsi-aml-fraud-detection"><em>demo repo</em></a><em>) and share any feedback or suggestions. Thank you!</em></p><p>1  <a href="https://secretariat-intl.com/wp-content/uploads/2025/04/Secretariat-Global-Financial-and-Economic-Crime-Outlook-2025.pdf">Global Financial and Economic Crime Outlook 2025</a></p>]]></description>
      <pubDate>Tue, 03 Nov 2026 20:00:16 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/financial-crime-mitigation-part-iv-agentic-ai-for-case-management</link>
      <guid>https://www.mongodb.com/company/blog/innovation/financial-crime-mitigation-part-iv-agentic-ai-for-case-management</guid>
    </item><item>
      <title>Layer MongoDB Atlas Resource Policies for Defense-in-Depth</title>
      <description><![CDATA[<p><em>Editor’s note: This post is the second in a five-part series exploring how MongoDB Atlas Resource Policies help you strengthen database security and enforce consistent guardrails across your organization. </em><a href="https://www.mongodb.com/company/blog/innovation/secure-mongodb-atlas-automated-ip-access-list-policies">Read the first post on IP access list management here</a><em>. Future posts will cover topics like blocking wildcard IP access and restricting access by cloud provider or region.</em></p><p>Imagine protecting your home with only a front-door lock. No matter how good that lock is, what happens when someone breaks a window or tricks their way in? A single security control, no matter how robust, creates a single point of failure.</p><p>Database security faces the same reality. Defense-in-depth is a military strategy adapted for cybersecurity: Deploy multiple independent layers of security controls so that if one fails, others still provide protection. In database security, this means protecting multiple dimensions simultaneously. Network controls determine who can reach your database, geographic controls ensure data stays in compliant regions, and protocol controls protect data in transit. Each layer requires different knowledge and tools to bypass, making comprehensive attacks substantially more difficult.</p><p><a href="https://www.mongodb.com/docs/atlas/atlas-resource-policies/">MongoDB Atlas Resource Policies</a> enable defense-in-depth at the infrastructure layer, preventing misconfigurations before deployments happen rather than detecting problems after resources go live. Each policy addresses a different attack vector: network access, geographic restrictions, and protocol requirements. When layered together, they create synergistic protection, where the whole is greater than the sum of its parts.</p><h2>The three layers: Network, geographic, and protocol</h2><p>An effective resource policy strategy addresses three critical layers of database infrastructure security. Think of these as concentric rings of protection, each independent but mutually reinforcing.</p><h3>Layer 1: Network access control</h3><p>The network layer controls which IP addresses can even attempt to connect to your database. This is your outermost defense. If attackers can’t reach the database at the network level, authentication becomes irrelevant. Resource policies enable sophisticated network access control through multiple complementary approaches.</p><p>Some teams add “0.0.0.0/0,” the wildcard IP, to a <a href="https://www.mongodb.com/products/platform">MongoDB Atlas</a> cluster’s access list, allowing connections from anywhere on the internet. A resource policy can be created to block this, ensuring no one in the organization exposes a cluster publicly. This eliminates the most dangerous configuration mistake, but it doesn’t specify what <em>should</em> be allowed. IP allowlists build on this foundation by defining exactly which IP addresses or Classless Inter-Domain Routing (CIDR) blocks are permitted. This establishes a positive security model where everything is denied by default except explicitly approved addresses. For maximum security, requiring empty IP access lists forces all traffic through private networking solutions, such as VPC peering or AWS PrivateLink, ensuring that database traffic never traverses the public internet.</p><p>These policies can be combined or used selectively based on your security requirements and architectural maturity. Organizations often start with wildcard blocking as a quick win, transition to allowlists as they document legitimate access requirements, and ultimately migrate production workloads to private networking with empty IP access lists.</p><h3>Layer 2: Geographic and cloud platform control</h3><p>The geographic layer ensures your data stays in regions that meet your compliance, performance, and sovereignty requirements. Even with perfect network access controls, data in the wrong geographic region can lead to compliance violations and regulatory risk.</p><p>Cloud provider restrictions limit which platforms can host your clusters; perhaps you’ve standardized on AWS for operational consistency or need to avoid specific providers due to compliance requirements. Region restrictions control the specific geographic locations where clusters can be deployed. This ensures adherence to data residency regulations, such as the GDPR’s requirement that European citizen data remain in Europe, or the California Consumer Privacy Act’s California-specific requirements.</p><p>These policies become particularly powerful when combined with network controls. You might allow broader network access for clusters in your home region where data sensitivity is lower, while requiring private networking for clusters in international regions where local laws impose stricter data protection requirements. The policies work together to create a nuanced security posture that strikes a balance between protection and operational flexibility.</p><h3>Layer 3: Protocol security</h3><p>The protocol layer ensures that even authorized connections from permitted locations use secure communication standards. This addresses the reality that network-level access doesn’t guarantee that the connection itself is secure or that cluster configurations meet security baselines.</p><p>TLS version requirements establish minimum encryption standards for connections, preventing clients from negotiating down to older, vulnerable protocol versions. Specifying required cipher suites gives you fine-grained control over the cryptographic algorithms used, ensuring only approved strong ciphers are available.</p><h2>A Defense-in-depth policy suite</h2><p>Let’s explore how these layers work together through concrete examples that combine multiple policies into comprehensive security architectures.</p><h3>Example 1: Financial services compliance stack</h3><p>A financial services organization processing payment card data needs to meet PCI DSS requirements while supporting development teams across multiple time zones. Their defense-in-depth strategy layers four complementary policies.</p><h4>Cedar Policy Code</h4><h4></h4><p>This combination creates multiple independent barriers to security violations. The wildcard blocking prevents the most dangerous network misconfiguration. Region restrictions ensure data stays in specific US regions to meet data residency requirements and minimize latency to primary user populations. TLS requirements prevent protocol downgrade attacks or connections from old clients with vulnerable encryption. Cluster size limits prevent cost overruns and enforce the architecture principle that very large databases should use sharding rather than vertical scaling.</p><h3>Example 2: Healthcare privacy-first architecture</h3><p>A healthcare provider handling protected health information prioritizes privacy above all else, implementing a zero-trust network architecture combined with strict data residency enforcement.</p><h4>Cedar Policy Code</h4><h4></h4><p>This healthcare provider’s approach eliminates public internet exposure entirely through the empty IP access list requirement, forces standardization on AWS, where the provider’s VPC peering and AWS PrivateLink configurations are mature, and prevents accidental deployment to international regions that would complicate HIPAA compliance.</p><p>The layering here creates defense-in-depth through architectural constraints. It’s not enough to configure security correctly. The resource policies prevent insecure configurations from being deployed in the first place. Developers can’t accidentally expose a database to the internet, because the system prevents it. They can’t unknowingly deploy to a noncompliant region, because the guardrails prevent them from doing so. Security becomes an architectural property rather than a configuration detail.</p><p>The key insight here is that defense-in-depth doesn’t mean “maximum restrictiveness everywhere.” It means a thoughtful layering of controls that addresses real risks while supporting business requirements. Each policy solves a specific problem without creating unnecessary friction.</p><h2>Policy interaction patterns: complementary vs. overlapping</h2><p>When designing multipolicy architectures, understanding how policies interact determines whether they strengthen or contradict each other.</p><p>Complementary policies address different security domains without overlap. For example, locking wildcard IP addresses controls network access, while region restrictions control data location. These policies are independent and mutually reinforcing. Neither interferes with the other’s operation. This is the ideal pattern for defense-in-depth, as each policy provides value independently while combining for greater overall security.</p><p>Overlapping policies address the same security domain through different mechanisms. An IP allowlist policy and an empty IP access list policy both control network access, but in conflicting ways. One requires specific IPs while the other requires no IPs at all. You can’t satisfy both simultaneously. Generally, avoid overlapping policies unless you intend to create an impossible-to-satisfy condition for specific projects as a way to completely block certain actions.</p><p>Hierarchical policies create progressively tighter restrictions. You might have an organization-wide policy blocking wildcards, a division-level policy enforcing a broad allowlist, and a project-level policy requiring an even narrower allowlist. Each layer adds restrictions without contradicting the others. This pattern is particularly effective in large organizations with diverse security requirements across business units.</p><h2>Method of rolling out defense-in-depth successfully</h2><p>Implementing a defense-in-depth strategy with MongoDB Atlas Resource Policies requires balance and communication. The goal is to strengthen security without creating friction that slows teams down.</p><p>Start with quick wins that deliver high impact and low disruption—such as blocking wildcard IPs—to prevent the most serious misconfigurations right away. Then layer in additional policies over time: region restrictions to meet data residency requirements, TLS enforcement for secure connections, and finally IP allowlists or private networking for production workloads. This phased rollout helps teams adapt gradually while maintaining momentum toward full coverage.</p><p>Avoid common missteps by keeping policies practical, transparent, and flexible. Overly restrictive or poorly communicated controls can drive teams to find workarounds, undermining security. Test new policies in nonproduction environments, explain the “why” behind every change, and provide clear paths to compliance. Review and adjust regularly as your architecture and regulatory landscape evolve. </p><h2>Your path forward</h2><p>Implementing a defense-in-depth strategy using MongoDB Atlas Resource Policies transforms database security from a checklist item into a fundamental architectural property. By layering policies across network, geographic, and protocol dimensions, you create security that’s resilient to individual control failures and configuration mistakes.</p><p>The journey begins with a single policy. From there, build incrementally toward comprehensive coverage based on your specific threat model and compliance requirements. Each new policy adds an independent layer of protection that makes your entire security architecture stronger.</p><p>MongoDB Atlas Resource Policies are included with all MongoDB Atlas deployments at no additional cost. The only investment required is the time to design your policy stack thoughtfully and implement it carefully. That investment pays dividends in reduced security incidents, faster compliance certifications, lower operational overhead, and the confidence that your security controls actually prevent problems rather than just detecting them.</p><p>Start building your defense-in-depth architecture today. Your future self—the one who doesn’t have to explain a data breach to executives or auditors—will thank you.</p><h2>Additional resources</h2><ul><li><p><a href="https://www.mongodb.com/docs/atlas/atlas-resource-policies/">MongoDB Atlas Resource Policies documentation</a></p></li><li><p><a href="https://docs.cedarpolicy.com/">Cedar policy language guide</a></p></li><li><p><a href="https://www.mongodb.com/docs/atlas/architecture/current/security/">Security Best Practices for MongoDB Atlas</a></p></li><li><p><a href="https://www.mongodb.com/docs/atlas/api/atlas-admin-api/">MongoDB Atlas Administration API reference</a></p></li></ul><p></p>]]></description>
      <pubDate>Tue, 03 Nov 2026 19:56:14 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/layer-mongodb-atlas-resource-policies-for-defense-in-depth</link>
      <guid>https://www.mongodb.com/company/blog/innovation/layer-mongodb-atlas-resource-policies-for-defense-in-depth</guid>
    </item><item>
      <title>Secure MongoDB Atlas With Automated IP Access List Policies</title>
      <description><![CDATA[<p><em>Editor’s note: This post is the first in a five-part series exploring how MongoDB Atlas Resource Policies help you strengthen database security and enforce consistent guardrails across your organization. Future posts will cover topics like defense-in-depth, blocking wildcard IP access, and restricting access by cloud provider or region.</em></p><p>Picture this: Your development team spins up a new MongoDB cluster for a critical application. To get things working quickly, the team adds overly permissive IP access rules. That might mean allowing their entire office network’s /16 CIDR block, or perhaps skipping careful validation of which specific IPs truly need access. That cluster goes into production. Six months later, during a security audit, you discover your database has been accessible from far more locations than anyone realized, with no clear documentation of who added which IP addresses or why.</p><p>Scenarios like this aren’t uncommon—and highlight why customers rely on MongoDB Atlas’ IP Access Lists to enforce clear, least-privilege network boundaries. IP Access Lists are a critical defensive layer in a defense-in-depth approach to security.</p><p>What if you could define exactly which IP addresses are allowed to access your databases and make it technically impossible for anyone to deviate from that approved list, at scale? That’s exactly what <a href="https://www.mongodb.com/docs/atlas/atlas-resource-policies/">MongoDB Atlas Resource Policies</a> are designed to do. They turn security best practices into enforceable guardrails that no one can bypass.</p><h2>MongoDB Atlas IP access lists</h2><p>Before diving into enforcement, let’s establish what IP access lists are and why they&#39;re your first line of defense.</p><p>An IP access list is a security feature that controls which IP addresses or CIDR blocks can connect to your <a href="https://www.mongodb.com/products/platform">MongoDB Atlas</a> clusters. Think of it as a bouncer at an exclusive club; only addresses on the list get through the door.</p><p>Every MongoDB Atlas project maintains an IP access list that applies to all clusters within that project. You can add individual IP addresses (e.g., 203.0.113.42), CIDR-notated ranges (e.g., 198.51.100.0/24), or AWS security groups for VPC peering connections.</p><p>MongoDB Atlas supports up to 200 IP access list entries per project, giving you granular control over who can access your data.</p><h2>The problem: Human error at scale</h2><p>Manual IP access list management has inherent weaknesses that compound as organizations grow. Configuration drift becomes inevitable. What starts as a secure configuration degrades over time as teams add “just one more” convenience entry. Security teams often lack visibility into insecure IP access lists until an audit or incident forces a review, by which time the damage may already be done.</p><p>The challenge intensifies when different teams interpret security policies differently, resulting in wildly inconsistent implementations across projects. Traditional security controls detect problems after they occur rather than preventing them, creating a perpetual game of catch-up. Meanwhile, developers who feel blocked by security requirements find creative workarounds that often create even bigger security gaps than the original policy was designed to prevent.</p><p>Organizations need a way to enforce IP access list policies automatically, consistently, and across every corner of their infrastructure. And they need to implement these guardrails without creating friction that drives teams to circumvent security entirely.</p><h2>The solution: Resource policies for automated IP access list enforcement</h2><p>Enter MongoDB Atlas Resource Policies. These policies transform IP access list management from reactive to proactive. Instead of documenting best practices and hoping teams follow them, you codify security requirements as enforceable policies.</p><p>Resource policies for IP access lists operate at the <a href="https://www.mongodb.com/docs/atlas/access/orgs-create-view-edit-delete/">Atlas Organization level</a> and automatically apply to all projects and clusters. They act as intelligent guardrails that prevent insecure configurations before they’re deployed.</p><h2>IP Access list resource policies: Real-world examples</h2><p>Let’s explore the specific policies you can implement to secure your MongoDB Atlas infrastructure.</p><h3>Policy #1: Enforce an IP address allowlist</h3><p>Take a zero-trust approach by specifying exactly which IP addresses are permitted for database access.</p><h4>Cedar policy code</h4><h4></h4><p></p><p></p><h4>What it does</h4><p>This policy ensures that only the specified IP addresses can be added to the access list. Any attempt to add an IP address outside this approved list is automatically blocked.</p><h4>How it impacts your business</h4><p>An IP allowlist policy is particularly valuable for regulated industries where you must document and control all access points. It simplifies compliance audits by providing preapproved IP address documentation that’s automatically enforced. The policy prevents unauthorized access points from being added while creating a traceable security architecture that risk management teams can confidently present to auditors and regulators.</p><h4>When to use this</h4><p>This approach is ideal for production environments where you know exactly which systems need database access. Consider this policy when you have application servers with static IP addresses, corporate VPN exit points with known IPs, partner integrations from specific known networks, or ETL and analytics systems with fixed infrastructure. The allowlist model works best when your access patterns are predictable and well-documented.</p><h3>Policy #2: Require empty IP access lists (private network only)</h3><p>For maximum security, prohibit all public network access by requiring the IP access list to remain empty. This forces all traffic through private endpoints or VPC peering.</p><h4>Cedar Policy Code</h4><h4></h4><p></p><p></p><h4>What it does</h4><p>This policy prevents anyone from adding entries to the IP access list, ensuring that all cluster access must occur through private networking paths, such as VPC peering or private endpoints.</p><h4>How it impacts your business</h4><p>By requiring an empty IP access list, you eliminate public internet exposure completely and force architecture best practices where private networking takes precedence over public access. This approach meets the highest security standards for regulated data while reducing your attack surface to zero for external threats. It also simplifies network security by removing public access as an option entirely, making it impossible for teams to accidentally expose databases to the internet.</p><h4>When to use this</h4><p>This represents the gold standard for production environments handling sensitive data. Financial services systems processing payment data, healthcare applications storing protected health information or personally identifiable information, government systems with classified or controlled data, and enterprise software-as-a-service (SaaS) applications with stringent security requirements all benefit from this approach. The policy makes sense when you’ve committed to private networking as your standard architecture pattern and want to enforce it consistently across all production workloads.</p><h4>Architecture note</h4><p>Before implementing this policy, ensure you have private networking configured with VPC peering or private endpoints for your cloud provider.</p><p>The result: <strong>Zero public internet exposure</strong> for production databases, significantly reduced attack surface, and simplified compliance with PCI DSS requirements.</p><h2>Key benefits of automated IP access list enforcement</h2><p>Resource policies fundamentally shift security left in the development process. Security becomes part of the infrastructure deployment workflow rather than an afterthought that’s discovered during audits. Developers receive immediate feedback when they try to create insecure configurations, learning the rules through experience rather than documentation.</p><p>The enforcement of resource policies is absolute. Unlike documentation or training, resource policies are applied with 100% consistency across every project, cluster, and team member. There’s no variation based on who’s deploying or what time of day it happens. This consistency makes security frameworks like SOC 2, ISO 27001, and HIPAA significantly easier to achieve because resource policies provide both the control mechanism and the documentation in code form.</p><p>Resource policies help reduce security teams’ workloads dramatically. They no longer need to constantly audit IP access lists searching for violations or send emails asking teams to fix configurations. Resource policies prevent violations automatically, freeing security professionals to focus on strategic initiatives rather than tactical firefighting. MongoDB Atlas also generates activity feed events whenever policies are created, updated, or deleted, providing complete auditability for compliance purposes without additional work.</p><p>Perhaps most importantly, developer velocity actually increases within these guardrails. Teams maintain self-service capabilities for infrastructure deployment while staying within security boundaries. The dreaded cycle of deploying infrastructure, waiting for security review, making changes, and waiting again disappears entirely. Developers receive clear, immediate feedback about what’s allowed and can make compliant choices from the start.</p><h2>IP access list best practices</h2><p>When implementing IP access list policies, start with the strictest policy your architecture can support. It’s far easier to loosen restrictions later than to tighten them after teams become accustomed to more permissive controls. The initial discipline pays dividends in security posture.</p><p>Documentation plays a crucial role in long-term success. Maintain clear records of which IP addresses are in your allowlist and the business justification for each one. This documentation simplifies compliance audits and proves invaluable during troubleshooting sessions when you need to understand why specific addresses were approved.</p><p>For production workloads, the use of private networking solutions like VPC peering, AWS PrivateLink, and Azure private endpoints provides superior security compared to IP access lists alone. While IP access lists control which addresses can connect, private networking ensures traffic never traverses the public internet at all. The combination creates defense-in-depth that significantly reduces risk.</p><p>Before rolling out policies organization-wide, test them thoroughly in a separate organization or nonproduction environment. Understanding the impact on your teams and workflows prevents surprises during production rollout and helps you refine policies based on real-world feedback.</p><h2>Take control of your database security today</h2><p>IP access list misconfigurations are one of the most common—and most preventable—database security risks. MongoDB Atlas Resource Policies give you the power to eliminate this risk automatically and permanently. You don’t have to choose between security and developer productivity. With resource policies, you can enforce security requirements that are impossible to bypass while giving teams the self-service capabilities they need to move fast.</p><p>Begin by logging into MongoDB Atlas with Organization Owner privileges and navigating to Organization Settings, then Resource Policies. Implement your first IP access list policy—choose the allowlist or empty access list policy based on your architecture. Audit noncompliant resources to understand what needs remediation, then expand to comprehensive security policies as you build confidence in the approach. IP access list resource policies are included with all MongoDB Atlas deployments at no additional cost, making this a zero-friction way to dramatically improve your security posture.</p><h2>Additional resources</h2><ul><li><p><a href="https://www.mongodb.com/docs/atlas/security/ip-access-list/">Configure IP Access List Entries</a> </p></li><li><p><a href="https://www.mongodb.com/docs/atlas/atlas-resource-policies/">Atlas Resource Policies documentation</a> </p></li><li><p><a href="https://www.mongodb.com/docs/atlas/security-vpc-peering/">VPC peering setup guide</a> </p></li><li><p><a href="https://www.mongodb.com/docs/atlas/security-private-endpoint/">AWS PrivateLink configuration</a> </p></li><li><p><a href="https://www.mongodb.com/docs/atlas/api/atlas-admin-api/">MongoDB Atlas Administration API reference</a></p></li></ul><p></p>]]></description>
      <pubDate>Tue, 03 Nov 2026 19:55:16 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/secure-mongodb-atlas-automated-ip-access-list-policies</link>
      <guid>https://www.mongodb.com/company/blog/innovation/secure-mongodb-atlas-automated-ip-access-list-policies</guid>
    </item><item>
      <title>LEAF: Distillation of State‑of‑the‑Art Text Embedding Models</title>
      <description><![CDATA[<p>At MongoDB Research, we’re exploring how to make cutting‑edge AI models smaller, faster, and more flexible.</p><p>In this blog post, we present LEAF (<strong>Lightweight Embedding Alignment Framework</strong>), a new knowledge distillation framework for text embedding models.</p><p>We’re also releasing two best‑in‑class embedding models trained with LEAF:</p><ul><li><p><a href="https://huggingface.co/MongoDB/mdbr-leaf-ir">mdbr-leaf-ir</a>—23M parameter model optimized for retrieval‑focused tasks like semantic search and <a href="https://www.mongodb.com/docs/atlas/atlas-vector-search/rag/">retrieval‑augmented generation</a><strong> </strong>(RAG).</p></li><li><p><a href="https://huggingface.co/MongoDB/mdbr-leaf-mt">mdbr-leaf-mt</a>—23M parameter model tailored for broader NLP applications such as classification, clustering, and sentence similarity.</p></li></ul><p>These models are suitable for CPU-only deployments (no GPU), as well as IoT and mobile devices, with no internet connection required.</p><p><em><strong>Note:</strong></em><em> </em><em>We</em><em> </em><em>are</em><em> </em><em>publishing</em><em> </em><em>these</em><em> </em><em>models</em><em> </em><em>and</em><em> </em><em>the</em><em> </em><em>recipe</em><em> </em><em>used</em><em> </em><em>to</em><em> </em><em>train</em><em> </em><em>them</em><em> </em><em>as</em><em> </em><em>a</em><em> </em><em>contribution</em><em> </em><em>to</em><em> </em><em>the</em><em> </em><em>open</em><em> </em><em>source</em><em> </em><em>community.</em><em> </em><em>They</em><em> </em><em>have</em><em> </em><em>been</em><em> </em><em>developed</em><em> </em><em>by</em><em> </em><em>the</em><em> </em><em>ML</em><em> </em><em>team</em><em> </em><em>of</em><em> </em><em>MongoDB</em><em> </em><em>Research.</em><em> </em><em>The</em><em> </em><em>models</em><em> </em><em>are</em><em> </em><em>published</em><em> </em><em>under</em><em> </em><em>a</em><em> </em><em>permissive</em><em> </em><em>Apache</em><em> </em><em>2.0</em><em> </em><em>license</em><em> </em><em>and</em><em> </em><em>offered</em><em> </em><em>as</em><em> </em><em>is,</em><em> </em><em>without</em><em> </em><em>any</em><em> </em><em>explicit</em><em> </em><em>or</em><em> </em><em>implied</em><em> </em><em>support.</em><em> </em><em>At</em><em> </em><em>the</em><em> </em><em>time</em><em> </em><em>of</em><em> </em><em>writing,</em><em> </em><em>they</em><em> </em><em>are</em><em> </em><em>not</em><em> </em><em>used</em><em> </em><em>in</em><em> </em><em>any</em><em> </em><em>of</em><em> </em><em>MongoDB&#39;s</em><em> </em><em>commercial</em><em> </em><em>products</em><em> </em><em>or</em><em> </em><em>service</em><em> </em><em>offerings.</em></p><h2>The challenges</h2><p>Modern text embedding models have delivered huge gains in natural language processing tasks, from question‑answering to RAGs. But these gains come at a cost:</p><ul><li><p><strong>Model sizes are exploding.</strong> State‑of‑the‑art open‑weight embedding models can range from hundreds of millions to billions of parameters (e.g., 1B or 7B+). While these models can offer high accuracy, they typically need to run on GPU servers, making them impractical for many deployments. </p></li><li><p><strong>Inflexible deployments.</strong> In information retrieval (IR) systems, the same large model is typically used for both document indexing and query encoding—even though these steps have very different performance requirements. Document indexing happens infrequently and tolerates high latency, while query-time embedding must meet strict latency targets—often expressed as P99 or tail latency—where even the slowest queries must return results within a few hundred milliseconds. </p></li><li><p><strong>No easy swaps.</strong> Existing embedding models aren’t compatible with each other—even different sizes within the same family—so swapping models requires recomputing every document embedding from scratch.</p></li></ul><p>These constraints make it hard to scale high‑performance retrieval systems, especially when operating at a large scale or under tight hardware and latency requirements.</p><h2>How LEAF works</h2><p>LEAF is a <a href="https://en.wikipedia.org/wiki/Knowledge_distillation">knowledge distillation</a> technique that takes a larger &quot;teacher&quot; model and outputs a smaller version of it—a &quot;student&quot; model. </p><p>What’s innovative about LEAF is that the student models it produces are compatible<strong> </strong>with their larger teachers, meaning that the text embeddings produced by the two are interoperable. </p><p>This is achieved by a training scheme that has, as its sole goal, the objective of making the student model approximate the embedding space produced by the teacher model. Initial works [1] proposing distillation strategies attempted to maximize the number of internals of teacher and student models to be aligned. This included aligning attention matrices as well as hidden states of all the layers and all attention heads of the student. Later works [2, 3] realized that better results could be achieved by avoiding excessive alignment of all layers by, e.g., focusing on the last layer of the Transformer backbone only. We take this lesson further and propose to align only the outputs of the teacher and the student. Namely, we propose to use the following L2 loss on the approximation error between the student and teacher’s output embeddings:</p><p></p><p>Earlier this year, we published details about the model architecture, training data, and training regime in our <a href="https://arxiv.org/abs/2509.12539">technical report</a> [4].</p><p>Model compatibility unlocks new flexible asymmetric architectures in which, for example, documents can be embedded with larger and more expensive models, while queries can be encoded by local, fast LEAF models, as shown in Figure 1.</p><p></p><p>Further key advantages of LEAF:</p><ul><li><strong>No need for labeled data.</strong> With LEAF, obtaining training data is extremely simple. This is in contrast to traditional training techniques based on contrastive loss, which require so-called judgments and hard negatives. </li><li><strong>Modest training infrastructure requirements.</strong> While previous methods prefer or even require working with large batch sizes—meaning they need a cluster of GPUs to train—LEAF favors small batches. As a consequence, we were able to train our distillations on a single A100 GPU.</li><li><strong>Automatic inheritance of advanced features.</strong> LEAF models automatically inherit properties like MRL and robustness to output quantization from the teacher, without explicitly training for them.</li></ul><p>Below we demonstrate that LEAF can produce models retaining up to 97% of their teacher’s performance, while being 5×–15× smaller and 7×–24× faster. </p><h2>Two models, two state‑of‑the‑art results</h2><p>To demonstrate LEAF in action, we’re releasing two new compact, best-in-class text embedding models, both available on <a href="https://huggingface.co/MongoDB">Hugging Face</a> under the Apache 2.0 license.
<a href="https://huggingface.co/MongoDB/mdbr-leaf-ir">mdbr-leaf-ir</a> is specifically designed for Information Retrieval (IR) tasks, such as the retrieval stage of RAG pipelines. It currently ranks #1 on the <a href="https://huggingface.co/spaces/mteb/leaderboard?benchmark_name=BEIR">public MTEB leaderboards</a> of the BEIR and RTEB benchmarks for models with ≤100M parameters. It has been distilled from <a href="https://huggingface.co/Snowflake/snowflake-arctic-embed-m-v1.5">snowflake-arctic-embed-m-v1.5</a>.</p><p></p><p></p><p><a href="https://huggingface.co/MongoDB/mdbr-leaf-mt">mdbr-leaf-mt</a>, on the other hand, excels at general purpose tasks like classification, clustering, sentence similarity and summarization. It currently ranks #1<strong> </strong>on <a href="https://huggingface.co/spaces/mteb/leaderboard?benchmark_name=MTEB%28eng%2C+v2%29">the public leaderboard</a> for the MTEB v2 (Eng) benchmark<strong> </strong>for models with ≤30M parameters. It has been distilled from <a href="https://huggingface.co/mixedbread-ai/mxbai-embed-large-v1">mxbai-embed-large-v1</a>.</p><p></p><p></p><p>These models are an excellent choice in deployment scenarios where a GPU is not available or is not cost-effective. This includes CPU-only servers, as well as IoT and mobile devices. Since they run on your hardware, they do not require an internet connection.</p><p>Typical throughputs obtained on a 2vCPUs instance are 120 queries/sec and 20 docs/sec, respectively. The memory footprint of the full-precision versions is 87MB. <a href="https://huggingface.co/MongoDB/mdbr-leaf-ir#transformersjs">Several quantizations</a> are available to further increase throughput and reduce memory footprint.</p><p>Besides offering state-of-the-art retrieval performance for their size, both models are equipped with MRL and robustness to output quantization. They can be fine‑tuned on domain‑specific data to further boost performance.</p><p>They are well-suited to work with a vector DB (such as MongoDB Vector Search in Community Edition) to power your next AI-enabled application.</p><p></p><h2>References </h2><ul><li><p>[1] Xiaoqi Jiao, Yichun Yin, Lifeng Shang, Xin Jiang, Xiao Chen, Linlin Li, Fang 
Wang, and Qun Liu. TinyBERT: Distilling BERT for Natural Language Understanding. In Findings of the Association for Computational Linguistics: EMNLP, 2020. </p></li><li><p>[2] Wenhui Wang, Furu Wei, Li Dong, Hangbo Bao, Nan Yang, and Ming Zhou. MiniLM: Deep self-attention distillation for task-agnostic compression of pre-trained transformers. Advances in neural information processing systems, 2020. </p></li><li><p>[3] Victor Sanh, Lysandre Debut, Julien Chaumond, and Thomas Wolf. DistilBERT, a distilled version of BERT: smaller, faster, cheaper and lighter. <a href="https://arxiv.org/abs/1910.01108">https://arxiv.org/abs/1910.01108</a>, 2020. </p></li><li><p>[4] Vujanic, Robin, and Thomas Rueckstiess. &quot;LEAF: Knowledge Distillation of Text Embedding Models with Teacher-Aligned Representations.&quot;<a href="https://arxiv.org/abs/2509.12539"> arXiv preprint arXiv:2509.12539</a> (2025). </p></li><li><p>Hugging Face Models: <a href="https://huggingface.co/MongoDB/mdbr-leaf-ir">mdbr-leaf-ir</a> and <a href="https://huggingface.co/MongoDB/mdbr-leaf-mt">mdbr-leaf-mt</a></p></li></ul><p>*In throughput terms (documents or queries per second), measured on a EC2 i3.large instance. Details are in the technical report.</p>]]></description>
      <pubDate>Tue, 03 Nov 2026 19:54:38 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/engineering/leaf-distillation-state-of-the-art-text-embedding-models</link>
      <guid>https://www.mongodb.com/company/blog/engineering/leaf-distillation-state-of-the-art-text-embedding-models</guid>
    </item><item>
      <title>Financial Crime Mitigation with MongoDB / Series Overview</title>
      <description><![CDATA[<p>Where money moves, crime evolves. As banking becomes fully digital—with instant payments, open finance APIs, and mobile-first onboarding—it has opened new roads for cyberattacks, forcing financial institutions to respond in real-time. With just seconds to detect, prevent, and react to suspicious activity—without disrupting the customer experience—banks face an immense challenge that only modern, AI-powered solutions can meet.</p><p>Welcome to our new series on mitigating financial crime with MongoDB. In the Financial Crime Mitigation series (this is the first of five posts we have planned!), you will learn how to build modern, anti-fincrime platforms that keep pace with increasingly automated, AI-assisted adversaries.</p><p>Let’s begin by understanding what financial crime is and why it matters. </p><h2>A trillion-dollar problem</h2><p>Financial crime encompasses illicit activities that exploit the financial system, from sophisticated money laundering schemes to AI-powered synthetic identity fraud. The numbers are staggering. According to the Global Financial and Economic Crime Outlook, global financial institutions&#39; losses could reach over $2 trillion USD due to financial crime each year. Putting this in perspective, these losses may represent 3.5% of global GDP, with an expectation of having this figure nearly double to $6 trillion by 2030.*</p><p>But financial crime doesn’t just cause monetary losses. It also undermines customer trust, harms brand reputation, disrupts operations, and diminishes conversion rates. For all financial institutions, regulatory compliance demands a full-time dedicated team (led by a Chief Compliance Officer) for managing activities like investigating false positives, filing suspicious activity reports, and managing regulatory oversight, all of these subject to an optimized automation by using emerging technologies around AI.</p><p>This is why most leading financial organizations around the globe have launched financial crime prevention programs, working toward:</p><ol><li><p><strong>Enhanced security by having proper data governance and policies in place</strong> (particularly for digital banking services). With financial services now fully digitized, a strong digital security framework must be implemented to remain resilient from cyberattacks.</p></li><li><p><strong>Transparency &amp; Traceability</strong>. Adopting AI for critical decision-making processes implies incorporating explainability by design. Full disclosure is a requirement for dealing with intensifying regulatory pressure in favor of transparent, fair operations. </p></li><li><p><strong>Immediacy.</strong> Real-time banking services demand running anti-fraud controls in the moment, which in turn requires high-processing capabilities for correlating all the relevant data points. All of these are feasible only with AI-powered high-level automation—in conjunction with data services provided by platforms like MongoDB Atlas.</p></li><li><p><strong>Modernizing outdated legacy architecture</strong>. Traditional systems were designed based on a “single transaction” principle. Modern cyberattacks require a contextual analysis that requires combining transactional information with a massive inflow of unstructured data.</p></li></ol><p>This last aspect is the most critical one. Let’s dive into the details.</p><h2>The challenge: Legacy systems can&#39;t keep up</h2><p>Traditional fraud and anti-money laundering (AML) systems were built for a simpler era. They are fragmented, rigid, and reactive, proving inadequate against today&#39;s adaptive, network-based criminal enterprises. </p><p></p><p>When these legacy systems attempt to manage modern threats, several challenges arise: </p><ul><li><p><strong>Disparate data silos</strong>: Customer data lives scattered across separate systems: core banking platforms, card processors, KYC systems, and CRM tools. Since each one uses its own schema, it creates integration nightmares and produces blind spots that criminals exploit.</p></li><li><p><strong>Batch processing delays</strong>: End-of-day ETL processes move data into warehouses for analytics and rule tuning. By the time insights emerge, fraudulent transactions have already been cleared and settled.</p></li><li><p><strong>Siloed detection tools</strong>: Separate engines handle transaction fraud, AML monitoring, KYC/customer due diligence (CDD), and case management. The problem is that little context flows between them, leading to duplicate data, conflicting logic, and missed connections.</p></li><li><p><strong>Transaction-by-transaction myopia: </strong>Rules evaluate individual events in isolation, missing broader behavioral patterns and network relationships. Complex joins across multiple tables are slow, expensive, and error-prone.</p></li><li><p><strong>False positive fatigue</strong>: Legacy systems generate up to 90% or more false positives**, overwhelming compliance teams and causing real threats to slip through. Without holistic entity views, they miss sophisticated, multi-party schemes.</p></li><li><p><strong>Organizational Resistance to Change: </strong>Organizations often face resistance to change due to entrenched silos, with AML teams focused on compliance and fraud teams operating in real-time, creating cultural divides that technology alone cannot resolve.</p></li></ul><h2>The solution: A unified modern anti-financial crime platform</h2><p>To overcome all these challenges, organizations require a fundamentally different approach: modern anti-financial crime platforms. Successful platforms that consolidate operational processing, search, entity resolution, and network analysis on a single, flexible data foundation. </p><p></p><h2>Platform architecture: five integrated modules</h2><p>MongoDB Atlas enables this unified approach through several key capabilities: </p><ol><li><strong>Entity management and resolution</strong>
Organizations can power AI-driven entity resolution and duplicate detection using Atlas Search&#39;s $rankFusion to combine fuzzy text matching with semantic vector search. Perform network analysis directly in the database using the Aggregation Framework&#39;s $graphLookup to uncover hidden money laundering and fraud rings.</li><li><strong>Advanced transaction monitoring</strong>
Blend traditional rule-based screening with <a href="https://www.mongodb.com/products/platform/atlas-vector-search">Atlas Vector Search</a> for semantic pattern matching. Identify suspicious behaviors that resemble known fraud patterns even when they don&#39;t match explicit rules. Evaluate transactions against both static rules and learned behavioral baselines in unified pipelines.</li><li><strong>Behavioral risk scoring engine</strong> 
Calculate risk scores via high-performance APIs that pull features directly from MongoDB. Support multiple model versions—rules, thresholds, feature weights—and switch between them instantly by updating an &quot;active&quot; pointer. All scoring services reflect new models immediately without downtime.</li><li><strong>Risk model management</strong> 
Enable fraud teams to create, edit, and version risk models dynamically. Use Change Streams to propagate real-time updates when new model versions activate, allowing rapid adaptation to emerging threat patterns without system restarts.</li><li><strong>Case management and regulatory reporting</strong> 
Triage alerts with full entity and network context. Support investigative workflows that surface related entities, transactions, and historical patterns. Generate regulatory reports like suspicious activity reports (SARs) with complete audit trails and automated filing capabilities.</li></ol><h2>Why MongoDB for anti-financial crime platforms?</h2><h3>Customer 360 foundation </h3><p>With MongoDB&#39;s flexible document model, you can build a comprehensive, entity-centric view of customers, accounts, instruments, transactions, devices, and relationships. Store entities, events, and relationships in natural document structures—eliminating complex joins and data duplication across operations, search, vector analysis, and network investigations.</p><h3>Real-time intelligence </h3><p>Capture transactions and update them instantly as they occur using MongoDB’s Change Streams and Time Series Collections. Compute features, calculate aggregates, and assess risk with complete entity and network context at the moment of decision—enabling immediate action instead of retrospective analysis.</p><h3>Hybrid detection approaches </h3><p>Combine traditional rules with statistical models, graph pattern analysis, fuzzy search, and vector similarity in a single system. Run built-in analytics directly on your data to catch either known attack patterns or emerging threats without shuttling information between specialized tools.</p><h3>Security and governance </h3><p>Encrypt sensitive data at the field level while isolating workloads and maintaining a single source of truth. Track every change with comprehensive audit trails and version control to meet regulatory compliance requirements.</p><h3>Run MongoDB anywhere</h3><p>MongoDB offers flexible deployment options to suit your business needs. Choose MongoDB Atlas for a fully managed, multi-cloud environment, or deploy self-managed MongoDB Enterprise Advanced in private cloud or on-premises settings for a hybrid deployment architecture.</p><h2>Building for competitive advantage</h2><p>Having gained a better understanding of the “art of possible” to replace traditional systems with modern anti-fincrime platforms, the question then becomes: what is the most convenient approach for companies to address these issues: buying an off-the-shelf solution or building one in-house with MongoDB?</p><p><strong>Buying:</strong> commercial solutions promise quick deployment but often constrain flexibility and may not integrate well with existing systems. More importantly, fraud and AML patterns are unique to each business model, customer base, and geographic footprint—making generic solutions less effective over time. Licensed solutions can also become expensive through customization costs, integration fees, and ongoing maintenance.</p><p><strong>Building:</strong> custom platforms on MongoDB offers strategic advantages: rapid iteration of detection typologies, freedom from vendor constraints, and seamless integration of third-party signals like device fingerprinting and behavioral biometrics. Teams can leverage MongoDB&#39;s managed capabilities to focus on detection logic rather than infrastructure complexity. The build approach enables organizations to create platforms that evolve with their specific risk profiles and business needs, ultimately providing stronger protection and competitive differentiation in financial crime prevention.</p><h2>The real “paradigm shift” </h2><p>The paradigm shift isn’t just about faster tech; it’s about rethinking how we represent and act on data. Customers and their networks should be modeled as entities and events, not scattered across dozens of joined tables. Risk needs to be detected in real time, as business flows, not tomorrow in a batch report. A single, unified platform should power search, semantic similarity, graph reasoning, rules, and machine learning side by side, instead of relying on point solutions. And intelligence must be adaptive—models that ship, measure, and iterate in hours, not quarters, all without downtime.</p><p>Ready to modernize your approach to financial crime? Follow this series to see how a unified anti-fincrime platform with MongoDB can help you move beyond legacy approaches and build future-ready defenses against fraud and AML.</p><h2>Stay tuned</h2><p>In the upcoming blogs, we&#39;ll dive deep into each platform component:</p><ul><li><strong>Entity Resolution for KYC</strong>: Create a true single view of your customers with behavioral analysis </li><li><strong>Real-Time Fraud Detection</strong>: Catch suspicious transactions instantly using vector search and change streams </li><li><strong>AML Risk Scoring with Graph Analytics</strong>: Spot hidden money laundering networks and complex relationships</li><li><strong>Agentic AI for Due Diligence</strong>: Empower risk analysts with LLMs and AI copilots for smarter, faster investigations</li></ul><p><strong></strong></p><p><strong></strong></p><p><strong>References</strong></p><p>*<a href="https://secretariat-intl.com/wp-content/uploads/2025/04/Secretariat-Global-Financial-and-Economic-Crime-Outlook-2025.pdf">Global Financial and Economic Crime Outlook 2025</a> 
**<a href="https://www.mckinsey.com/capabilities/risk-and-resilience/our-insights/the-investigator-centered-approach-to-financial-crime-doing-what-matters?ref=lucinity.ghost.io#/">The investigator-centered approach to financial crime: Doing what matters</a></p><p></p>]]></description>
      <pubDate>Tue, 03 Nov 2026 19:53:52 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/building-financial-crime-mitigation-platform-with-mongodb-series-overview</link>
      <guid>https://www.mongodb.com/company/blog/innovation/building-financial-crime-mitigation-platform-with-mongodb-series-overview</guid>
    </item><item>
      <title>Enforce Data Sovereignty With MongoDB Atlas Resource Policies</title>
      <description><![CDATA[<p><em>Editor’s note: This post is the fourth in a five-part series exploring how MongoDB Atlas Resource Policies help you strengthen database security and enforce consistent guardrails across your organization. Read the first post on </em><a href="https://www.mongodb.com/company/blog/innovation/secure-mongodb-atlas-automated-ip-access-list-policies"><em>IP access list management</em></a><em>, the second on </em><a href="https://www.mongodb.com/company/blog/innovation/layer-mongodb-atlas-resource-policies-for-defense-in-depth"><em>defense in depth strategies</em></a><em>, and the third on </em><a href="https://www.mongodb.com/company/blog/innovation/stop-a-dangerous-database-security-mistake-wildcard-ips"><em>blocking the wildcard IP address</em></a><em>.</em></p><h2>Maintaining control in a multi-cloud world</h2><p>As organizations scale their database infrastructure, maintaining consistent security and compliance policies becomes increasingly complex. Development teams need agility, but security teams need control. One misconfigured cluster deployed in the wrong region or on an unapproved cloud hyperscaler can lead to:</p><ul><li><p><strong>Compliance violations</strong> with data residency requirements.</p></li><li><p><strong>Security gaps</strong> from shadow IT deployments.</p></li><li><p><strong>Cost overruns</strong> from unplanned multi-cloud sprawl.</p></li><li><p><strong>Audit failures</strong> when infrastructure does not match documented policies.</p></li></ul><h2>Introducing MongoDB Atlas Resource Policies</h2><p><a href="https://www.mongodb.com/docs/atlas/atlas-resource-policies/">MongoDB Atlas Resource Policies</a> are organization-level controls that enable you to define and enforce infrastructure governance rules using policy as code. These policies act as intelligent guardrails, automatically constraining configuration options available to developers while maintaining the flexibility teams need to build and deploy.</p><p>Today, we’re diving deep into two of the most powerful policies for multi-cloud governance: <strong>Restrict Cloud Hyperscaler </strong>and <strong>Restrict Cloud Hyperscaler Region</strong>.</p><h2>Policy #1: Restrict Cloud Hyperscaler</h2><h3>What it does</h3><p>The Restrict Cloud Hyperscaler policy gives you fine-grained control over which cloud platforms—AWS, Google Cloud, or Azure—can be used for <a href="https://www.mongodb.com/products/platform">MongoDB Atlas</a> cluster deployments within your organization.</p><h3>Why it matters</h3><p><strong>Compliance and data sovereignty:</strong> Many industries have strict requirements about where data can be processed. If your compliance framework mandates AWS-only infrastructure, this policy ensures no clusters are accidentally deployed on Google Cloud Platform or Azure.</p><p><strong>Cost optimization:</strong> Committed to an AWS Enterprise Discount Program? This policy prevents cost leakage to other hyperscalers and helps you maximize your cloud spend commitments.</p><p><strong>Operational consistency:</strong> Standardizing on one or two cloud hyperscalers simplifies your operational model, reduces training overhead, and streamlines your disaster recovery procedures.</p><p><strong>Security posture:</strong> Each cloud hyperscaler has unique security features and configurations. By restricting to approved hyperscalers, you ensure your security teams have deep expertise in the platforms you actually use.</p><h3>Real-world examples</h3><p>MongoDB Atlas Resource Policies are defined using the open-source <a href="https://www.cedarpolicy.com/en">Cedar policy language</a>. Here are some examples of resource policies creating guardrails around which cloud providers can be used for MongoDB Atlas cluster deployments. </p><p><strong>Example 1: Block a specific hyperscaler</strong></p><p>Prevent any clusters from being deployed on Google Cloud:</p><p></p><p></p><p></p><p><strong>Example 2: Allow only one hyperscaler</strong></p><p>Your organization has standardized on Google Cloud. Ensure all clusters must be deployed there:</p><p></p><p></p><p></p><p><strong>Example 3: Enforce Project-specific restrictions</strong></p><p>Lock down a sensitive MongoDB Atlas Project so that only AWS can be used for cluster deployment:</p><p></p><p></p><h2>Policy #2: Restrict Cloud Hyperscaler Region</h2><h3>What it does</h3><p>The Restrict Cloud Hyperscaler Region policy enables you to control the specific geographic regions where MongoDB Atlas clusters can be deployed, down to the individual region level (e.g., <em>aws:us-east-1</em><em>, </em><em>azure:westeurope</em>).</p><h3>Why it matters</h3><p><strong>Data residency compliance:</strong> GDPR, California Consumer Privacy Act (CCPA), and other regulations often mandate that data must remain within specific geographic boundaries. This policy streamlines compliance, making it automatic rather than manual.</p><p><strong>Latency optimization:</strong> Restrict deployments to regions closest to your users for optimal performance. No more clusters accidentally deployed on the wrong continent.</p><p><strong>Cost management:</strong> Some cloud regions are significantly more expensive than others. Control costs by preventing deployments to high-cost regions.</p><p><strong>Disaster recovery planning:</strong> Define approved regions for production workloads and separate regions for disaster recovery, ensuring proper geographic distribution for business continuity.</p><p><strong>Security compliance:</strong> Certain regions may not meet your security certification requirements. This policy ensures only approved, audited regions are used.</p><h3>Real-world examples</h3><p><strong>Example 1: Block a specific region</strong></p><p>Your compliance team has determined that <em>aws:us-east-1</em> has unacceptable data residency risks for your use case, so clusters must not be deployed there:</p><p></p><p></p><p></p><p><strong>Example 2: Block multiple regions</strong></p><p>Prevent deployments across three regions that don’t meet your requirements:</p><p></p><p></p><p></p><p><strong>Example 3: Allow approved regions</strong></p><p>Take a zero-trust approach—only permit deployments in preapproved regions:</p><p></p><p></p><p></p><h2>Exploring a real-world use case: Financial services compliance</h2><p>A global financial services company needed to ensure all customer data remained within GDPR-compliant regions while maintaining its commitment to AWS as its primary cloud hyperscaler. Its challenge required addressing multiple dimensions simultaneously: preventing deployments to unapproved hyperscalers, restricting geographic regions for data residency, and blocking insecure network configurations.</p><p>It implemented a layered approach that combined hyperscaler and region policies with network security controls:</p><p></p><p></p><p></p><p>This single policy restricts all Google Cloud Platform deployments while also blocking specific AWS regions that didn’t meet its data residency requirements. The company complemented this with an IP access list policy preventing wildcard access to address network security.</p><p>The result? <strong>Zero compliance violations</strong> were reported in their subsequent audit. Consequently, developers maintained full self-service capabilities within established guardrails, and security teams gained confidence in infrastructure governance. The policies transformed compliance from a documentation exercise into an automated enforcement mechanism, rendering violations technically impossible.</p><h2>Understanding the key benefits of using resource policies</h2><h3>1. Automated compliance</h3><p>Stop relying on documentation, training, and manual reviews. Resource policies are enforced automatically at the Organization level.</p><h3>2. Proactive, not reactive</h3><p>Resource policies prevent noncompliant configurations before they are created, rather than detecting problems after deployment.</p><h3>3. Developer velocity</h3><p>Teams can self-service their infrastructure needs within approved guardrails without waiting for security reviews.</p><h3>4. Audit trail</h3><p>MongoDB Atlas generates activity feed events when policies are created, updated, or deleted, providing complete auditability.</p><h3>5. Noncompliant resource visibility</h3><p>Use the API endpoint <em>/orgs/{ORG-ID}/nonCompliantResources</em> to identify any existing resources that do not meet your policy requirements.</p><h3>6. No service disruption</h3><p>Existing noncompliant clusters continue running. Policies only restrict modifications or the creation of new resources that would keep them out of compliance.</p><h2>Take the next step</h2><p>Infrastructure governance doesn’t have to mean slowing down development. With MongoDB Atlas Resource Policies, you can enforce security and compliance requirements automatically while empowering your teams to move fast.</p><p>You can implement resource policies through the <a href="https://www.mongodb.com/docs/atlas/atlas-ui/">MongoDB Atlas UI</a> with its visual policy editor, the <a href="https://www.mongodb.com/docs/atlas/api/atlas-admin-api-ref/">Atlas Administration API</a> for programmatic policy management, Terraform for infrastructure-as-code integration, or AWS CloudFormation for native AWS deployment. The policies are defined using Cedar, an open-source policy language designed for clarity and expressiveness. If you can read JSON, you can read Cedar policies.</p><h3>Try resource policies today</h3><ol><li><p><strong>Log into MongoDB Atlas</strong> with Organization Owner privileges.</p></li><li><p><strong>Navigate to Organization Settings</strong> &gt; Resource Policies.</p></li><li><p><strong>Create your first policy</strong> using one of the examples above.</p></li><li><p><strong>Monitor noncompliant resources</strong> and plan remediation.</p></li><li><p><strong>Iterate and refine</strong> based on your organization’s needs.</p></li></ol><p>Resource policies are included with all MongoDB Atlas deployments at no additional cost. There’s no reason not to start protecting your infrastructure today.</p><h2>Additional Resources</h2><ul><li><p><a href="https://www.mongodb.com/docs/atlas/atlas-resource-policies/">Full MongoDB Atlas Resource Policy documentation</a></p></li><li><p><a href="https://docs.cedarpolicy.com/">Cedar policy language guide</a></p></li><li><p><a href="https://www.mongodb.com/docs/atlas/api/atlas-admin-api/">MongoDB Atlas Administration API reference</a></p></li><li><p><a href="https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs">Terraform, MongoDB Atlas Provider</a></p></li></ul><p></p>]]></description>
      <pubDate>Tue, 03 Nov 2026 19:52:56 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/enforce-data-sovereignty-with-mongodb-atlas-resource-policies</link>
      <guid>https://www.mongodb.com/company/blog/innovation/enforce-data-sovereignty-with-mongodb-atlas-resource-policies</guid>
    </item><item>
      <title>Connect to a MongoDB Database Using Node.js</title>
      <description><![CDATA[<p></p><p>Use Node.js? Want to learn MongoDB? This is the blog series for you!</p><p>In this Quick Start series, I’ll walk you through the basics of how to get started using MongoDB with Node.js. In today’s post, we’ll work through connecting to a MongoDB database from a Node.js script, retrieving a list of databases, and printing the results to your console.</p><p></p><h2>Set up</h2><p>Before we begin, we need to ensure you’ve completed a few prerequisite steps.</p><h3>Install Node.js</h3><p>First, make sure you have a supported version of Node.js installed. The current version of MongoDB Node.js Driver requires Node 4.x or greater. For these examples, I&#39;ve used Node.js 14.15.4. See the <a href="https://www.mongodb.com/docs/drivers/node/current/compatibility/">MongoDB Compatabillity</a> docs for more information on which version of Node.js is required for each version of the Node.js driver.</p><h3>Install the MongoDB Node.js Driver</h3><p>The MongoDB Node.js Driver allows you to easily interact with MongoDB databases from within Node.js applications. You&#39;ll need the driver in order to connect to your database and execute the queries described in this Quick Start series.</p><p>If you don&#39;t have the MongoDB Node.js Driver installed, you can install it with the following command.</p><p></p><p>At the time of writing, this installed version 3.6.4 of the driver. Running npm list mongodb will display the currently installed driver version number. For more details on the driver and installation, see the <a href="https://docs.mongodb.com/drivers/node/current/">official documentation</a>.</p><h3>Create a free MongoDB Atlas cluster and load the sample data</h3><p>Next, you&#39;ll need a MongoDB database. The easiest way to get started with MongoDB is to use Atlas, MongoDB&#39;s fully-managed database-as-a-service.</p><p><a href="https://www.mongodb.com/products/platform/atlas-database">Head over to Atlas</a> and create a new cluster in the free tier. At a high level, a cluster is a set of nodes where copies of your database will be stored. Once your tier is created, <a href="https://docs.atlas.mongodb.com/sample-data/">load the sample data</a>. If you&#39;re not familiar with how to create a new cluster and load the sample data, check out <a href="https://developer.mongodb.com/quickstart/free-atlas-cluster/">this video tutorial</a> from MongoDB Developer Advocate <a href="https://www.linkedin.com/in/maximebeugnet">Maxime Beugnet</a>.</p><p></p><h3>Get your cluster’s connection info</h3><p>The final step is to prep your cluster for connection.</p><p>In <a href="https://www.mongodb.com/products/platform/atlas-database">Atlas</a>, navigate to your cluster and click <strong>CONNECT</strong>. The Cluster Connection Wizard will appear.</p><p>The Wizard will prompt you to add your current IP address to the IP Access List and create a MongoDB user if you haven&#39;t already done so. Be sure to note the username and password you use for the new MongoDB user as you&#39;ll need them in a later step.</p><p>Next, the Wizard will prompt you to choose a connection method. Select <strong>Connect Your Application</strong>. When the Wizard prompts you to select your driver version, select <strong>Node.js</strong> and <strong>3.6 or later</strong>. Copy the provided connection string.</p><p>For more details on how to access the Connection Wizard and complete the steps described above, see the <a href="https://docs.atlas.mongodb.com/connect-to-cluster/">official documentation</a>.</p><h2>Connect to your database from a Node.js application</h2><p>Now that everything is set up, it’s time to code!  Let’s write a Node.js script that connects to your database and lists the databases in your cluster.</p><h3>Import MongoClient</h3><p>The MongoDB module exports MongoClient, and that’s what we’ll use to connect to a MongoDB database.  We can use an instance of MongoClient to connect to a cluster, access the database in that cluster, and close the connection to that cluster.</p><p></p><h3>Create our main function</h3><p>Let’s create an asynchronous function named main() where we will connect to our MongoDB cluster, call functions that query our database, and disconnect from our cluster.</p><p></p><p>The first thing we need to do inside of  main()  is create a constant for our connection URI. The connection URI is the connection string you copied in Atlas in the previous section. When you paste the connection string, don&#39;t forget to update  &lt;username&gt;  and  &lt;password&gt;  to be the credentials for the user you created in the previous section. The connection string includes a  &lt;dbname&gt;  placeholder. For these examples, we&#39;ll be using the  sample_airbnb  database, so replace  &lt;dbname&gt;  with  sample_airbnb.</p><p><strong>Note</strong>: the username and password you provide in the connection string are NOT the same as your Atlas credentials.</p><p></p><p>Now that we have our URI, we can create an instance of MongoClient.</p><p></p><p><strong>Note</strong>: When you run this code, you may see DeprecationWarnings around the URL string  parserand the Server Discover and Monitoring engine. If you see these warnings, you can remove them by passing options to the MongoClient. For example, you could instantiate MongoClient by calling  new MongoClient(uri, { useNewUrlParser: true, useUnifiedTopology: true }). See the <a href="https://mongodb.github.io/node-mongodb-native/3.6/api/MongoClient.html">Node.js MongoDB Driver API documentation</a> for more information on these options.</p><p>Now we&#39;re ready to use MongoClient to connect to our cluster.  client.connect() will return a <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise">promise</a>. We will use the <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/await">await</a> keyword when we call  client.connect() to indicate that we should block further execution until that operation has completed.</p><p></p><p>Now we are ready to interact with our database. Let&#39;s build a function that prints the names of the databases in this cluster. It&#39;s often useful to contain this logic in well named functions in order to improve the readability of your codebase. Throughout this series, we&#39;ll create new functions similar to the function we&#39;re creating here as we learn how to write different types of queries. For now, let&#39;s call a function named listDatabases().</p><p></p><p>Let’s wrap our calls to functions that interact with the database in a try/catch statement so that we handle any unexpected errors.</p><p></p><p>We want to be sure we close the connection to our cluster, so we’ll end our try/catch with a finally statement.</p><p></p><p>Once we have our main() function written, we need to call it. Let’s send the errors to the console.</p><p></p><p>Putting it all together, our main() function and our call to it will look something like the following.</p><p></p><h3>List the databases in our cluster</h3><p>In the previous section, we referenced the listDatabases() function.  Let’s implement it!</p><p>This function will retrieve a list of databases in our cluster and print the results in the console.</p><p></p><h3>Save Your File</h3><p>You’ve been implementing a lot of code.  Save your changes, and name your file something like connection.js.  To see a copy of the complete file, visit the <a href="https://github.com/mongodb-developer/nodejs-quickstart/blob/master/connection.js">nodejs-quickstart</a> GitHub repo.</p><h3>Execute Your Node.js Script</h3><p>Now you’re ready to test your code!  Execute your script by running a command like the following in your terminal: node connection.js</p><p>You will see output like the following:</p><p></p><h2>What’s next?</h2><p>Today, you were able to connect to a MongoDB database from a Node.js script, retrieve a list of databases in your cluster, and view the results in your console. Nice!</p><p>Now that you&#39;re connected to your database, continue on to the <a href="https://developer.mongodb.com/quickstart/node-crud-tutorial/">next post in this series</a> where you&#39;ll learn to execute each of the CRUD (create, read, update, and delete) operations.</p><p>In the meantime, check out the following resources:</p><ul><li><p><a href="https://docs.mongodb.com/drivers/node/">Official MongoDB Documentation on the MongoDB Node.js Driver</a></p></li><li><p><a href="https://university.mongodb.com/courses/M220JS/about">MongoDB University Free Course: M220JS: MongoDB for Javascript Developers</a></p></li></ul><p>Questions? Comments? We&#39;d love to connect with you. Join the conversation on the <a href="https://developer.mongodb.com/community/forums/">MongoDB Community Forums</a>.</p><h3>All posts in the </h3><ul><li>How to connect to a MongoDB database using Node.js (this post)</li><li><a href="https://developer.mongodb.com/quickstart/node-crud-tutorial/">MongoDB and Node.js - CRUD Operations</a></li><li><a href="https://developer.mongodb.com/quickstart/node-aggregation-framework/">How to analyze your data using MongoDB&#39;s Aggregation Framework and Node.js</a></li><li><a href="https://developer.mongodb.com/quickstart/node-transactions/">How to implement transactions using Node.js</a></li><li><a href="https://developer.mongodb.com/quickstart/nodejs-change-streams-triggers/">How to react to database changes with change streams and triggers</a></li></ul><h2>Get Started with MongoDB Atlas</h2><h4>Run MongoDB with Node.js using MongoDB Atlas. Start free. No credit card required.</h4><a href="https://www.mongodb.com/cloud/atlas/register">Get Started</a>]]></description>
      <pubDate>Tue, 03 Nov 2026 19:51:39 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/technical/quick-start-nodejs-mongodb-how-to-get-connected-to-your-database</link>
      <guid>https://www.mongodb.com/company/blog/technical/quick-start-nodejs-mongodb-how-to-get-connected-to-your-database</guid>
    </item><item>
      <title>AI-Powered Customer Retention with MongoDB: Real-Time Behavioral Triggers for Retail IT Leaders</title>
      <description><![CDATA[<p>Every customer relationship is an investment, and like any investment, its value grows over time—when relationships are properly nurtured. Industry research has shown that retaining existing customers is far more cost-effective than acquiring new ones. For example, a 2025 article by Startup Guru Lab states that “businesses spend 5 to 7 times more to acquire new customers compared to keeping existing ones.” </p><p>New customers require significant marketing spend, extensive onboarding efforts, and a sustained period of trust-building before they can reach the level of loyalty and profitability of an existing customer. In contrast, customers who have already purchased from a brand have overcome those initial barriers. They know the products, the service standards, and the overall brand promise. What’s more, return customers tend to purchase more frequently, spend more per transaction, and are far more likely to recommend the brand to others.</p><p>Despite this well-documented return on investment, many retailers still focus the majority of their resources on acquisition rather than retention. A 2024 report by The CMO Survey notes how marketers spend “19.6% more on acquiring customers than retaining them.” Marketing campaigns often prioritize bringing in fresh traffic over protecting the relationships that already exist. The simple truth is that preventing a customer from leaving is almost always faster, cheaper, and more impactful than replacing them. When retailers proactively address signs of dissatisfaction, they not only keep revenue in-house but often strengthen the relationship through well-timed interventions.</p><h2>The challenge of retention in a hyper-competitive market</h2><p>Modern shoppers have an unprecedented amount of choice at their fingertips. With a few clicks, they can move from one site to another, compare prices, or abandon a cart if the experience feels too slow, too generic, or untrustworthy. Retention is not simply about having a loyalty program or sending follow-up emails after a cart has been abandoned. Customers expect retailers to anticipate their needs in the moment—not after the fact. </p><p>This challenge is compounded by the complexity of online shopping behavior. Customers hesitate for multiple reasons: indecision between similar products, uncertainty about delivery costs, skepticism about product quality, or simple distraction. Traditional analytics, which rely on batch data processing, fail to capture the immediacy of these moments. By the time an abandoned cart email is sent, the customer has likely already purchased the same product elsewhere.</p><p>Real-time behavioral understanding is now critical, seeing that IT decision makers in retail must evaluate technologies that can ingest, process, and act on behavioral data within milliseconds. This is not a trivial requirement. It demands a platform that unifies structured customer data with unstructured behavioral signals, processes vast volumes of event streams in real time, and executes interventions directly from the data layer without additional latency.</p><h2>MongoDB: A foundation for AI-powered retention</h2><p>MongoDB is uniquely positioned to support next-generation customer retention strategies by serving as the operational data layer for real-time behavioral triggers. Its flexible document model, real-time event handling, and integration with AI pipelines allow retailers to detect hesitation and respond instantly, keeping customers engaged before they abandon their journey.</p><p>Imagine a shopper browsing sneakers. With MongoDB, hesitation can be detected immediately through captured session data, time on page, navigation loops, and mouse movement patterns. MongoDB Triggers and change streams monitor these signals in real time and launch targeted actions the moment thresholds are exceeded.</p><p>For example, if the system identifies indecision, it can surface a recommendation widget highlighting products similar to those previously purchased by the same customer. If exit intent is detected, a social proof message can appear, noting that “25 people bought this item today” or that “only a few items remain in stock.” If delivery costs are a barrier, an instant free shipping offer can be triggered. In every case, MongoDB ensures that interventions are executed in milliseconds, before the shopper clicks away.</p><p>Crucially, MongoDB is not only about speed—it also ensures intelligent intervention. An embedded AI pipeline enriches raw behavioral events with contextual insights, distinguishing genuine hesitation from casual browsing and preventing system abuse. For instance, as shown in Figure 1, if a customer repeatedly triggers discounts by abandoning carts, MongoDB’s memory-driven session model can detect the pattern and adjust offers accordingly, ensuring retention efforts are sustainable and not exploited.</p><p></p><p><strong>Description: </strong>A shopper browses the site, generating events captured in the events collection (1) and processed in real time by the Atlas Stream Processor (2). The system detects patterns such as prolonged browsing, indecision, or exit intent, then updates the customer&#39;s collection and logs activity in customer_behaviour (3). This enriched data is sent to the AI Agent (4), which determines the next-best action and stores it in the strategies collection for delivery to the customer via the e-commerce/app interface (5).</p><p>The technology’s ability to unify data is central to its effectiveness. MongoDB stores structured data like transactions and purchase history alongside unstructured behavioral metadata like clickstream logs, session timers, and device fingerprints. This holistic view allows interventions to be precise, contextual, and aligned with the customer’s unique behavior. Atlas Search further enhances this by enabling lightning-fast retrieval of relevant product recommendations the instant they are needed.</p><p></p><p>MongoDB eliminates the need for fragmented architectures that combine separate databases, ETL jobs, and analytics engines. Instead, it provides a single, scalable solution that handles behavioral event capture, enrichment, storage, and real-time query execution. Its sharding and distributed architecture ensure the platform can support millions of concurrent sessions without latency, making it suitable for large-scale global retailers.</p><p>The benefits are clear. Abandonment rates are reduced because customers are intercepted before they leave. Conversion rates increase as hesitation is turned into a decision through contextual nudges. Personalization improves because actions are tied to live behavior, not static profiles updated once a week. And all of this is made transparent to operations teams through real-time dashboards powered by MongoDB’s aggregation framework, enabling leaders to monitor, measure effectiveness, and continuously optimize.</p><p>Real-world examples show the power of timely intervention. For example, <a href="https://useinsider.com/case-studies/carrefour/">Carrefour</a> has implemented real-time push notifications for cart abandonment that delivered a 350% uplift in conversion rates. This case underlines what is possible with proactive, behavior-based retention strategies. By leveraging MongoDB’s operational data layer, AI integration, and real-time triggers, ITDMs can implement these strategies at scale while ensuring flexibility and cost efficiency.</p><h2>How MongoDB sets retail teams up for success</h2><p>The promise of customer retention solutions is often balanced against technical feasibility, cost, and scalability. MongoDB addresses these concerns directly. Its document model offers flexibility to accommodate evolving data structures without requiring schema redesigns, reducing development friction and accelerating time to market. Its ability to unify operational and analytical workloads removes the overhead of complex data pipelines, lowering infrastructure costs and simplifying system maintenance.</p><p>MongoDB’s built-in capabilities—such as time-series collections, TTL indexes, and change streams—allow IT teams to model and execute timer-based events directly within the database layer. This reduces reliance on external schedulers or ETL frameworks, cutting down latency and simplifying architecture. MongoDB Atlas Search provides near real-time retrieval of contextual recommendations without needing an additional search engine. These features make MongoDB a comprehensive platform for real-time engagement.</p><p></p><p>Security, governance, and scalability are equally addressed. MongoDB’s distributed architecture supports high performance at scale, ensuring consistent low-latency responses even during peak shopping seasons. Fine-grained access controls, encryption, and auditing capabilities align with enterprise security standards. And with MongoDB Atlas, IT teams benefit from a fully managed cloud platform that automates scaling, patching, and monitoring, freeing resources to focus on delivering value to the business rather than maintaining infrastructure.</p><p>From a strategic perspective, MongoDB allows stakeholders to align technical capabilities with business outcomes. Instead of reacting to churn after it happens, IT leaders can equip their organizations with proactive, AI-driven retention workflows that directly impact revenue and customer loyalty.</p><h2>Winning the moments that matter</h2><p>Customer retention is no longer about broad loyalty programs or after-the-fact marketing campaigns. It is about winning the critical moments of hesitation before a customer leaves. The retailers who succeed are those who can detect indecision instantly, act on it with contextual relevance, and do so at scale across millions of sessions.</p><p>MongoDB provides the operational data layer required to make this possible. Its flexible document model, real-time triggers, AI enrichment, and Atlas Search integration enable interventions that fire in milliseconds, ensuring customers receive timely nudges that transform hesitation into conversion. For IT decision-makers, MongoDB offers not only the technical foundation to deliver these capabilities but also the assurance of scalability, security, and operational simplicity at enterprise scale.</p><p>Retention is the true driver of sustainable growth. By harnessing MongoDB to power AI-driven behavioral triggers, ITDMs can ensure their organizations are not just competing for attention but winning loyalty at the exact moments that matter most.</p><p></p><h2>References</h2><ul><li><a href="https://startupgurulab.com/customer-acquisition-vs-retention-costs">2025 article by Startup Guru Lab</a></li><li><p><a href="https://cmosurvey.org/wp-content/uploads/2024/11/The_CMO_Survey-Highlights_and_Insights_Report-Fall_2024.pdf">The CMO Survey</a> (2024 report)</p></li></ul>]]></description>
      <pubDate>Tue, 03 Nov 2026 19:48:13 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/ai-powered-customer-retention-with-mongodb-real-time-behavioral-triggers</link>
      <guid>https://www.mongodb.com/company/blog/innovation/ai-powered-customer-retention-with-mongodb-real-time-behavioral-triggers</guid>
    </item><item>
      <title>Simplifying Enterprise Security Management: MongoDB Atlas Logs in Microsoft Sentinel</title>
      <description><![CDATA[<p>Security teams face increasing pressure to maintain visibility and control across complex, hybrid environments. With data spread across multiple systems, detecting threats, correlating incidents, and enforcing governance can become fragmented and time-consuming—especially as organizations accelerate their cloud adoption and AI transformations.</p><p>Today, we’re happy to announce that MongoDB Atlas now integrates directly with Microsoft Sentinel, Microsoft’s cloud-native and AI-ready SIEM, SOAR, UEBA, and TI platform trusted by thousands of enterprises worldwide. This native integration allows teams to automatically ingest MongoDB Atlas logs into Microsoft Sentinel with just a few clicks—with no manual connectors or scripts required. </p><p>The MongoDB Atlas Data Connector, available via the Microsoft Marketplace or the Sentinel Content Hub, uses an Azure Function to pull logs from Atlas clusters through the Atlas Admin API and to stream them into Sentinel via the Log Ingestion API. Once in Microsoft Sentinel, the logs appear in your Log Analytics Workspace, ready for query, visualization, and automation using KQL, workbooks, and Logic Apps.</p><p>By combining MongoDB Atlas’s rich monitoring and alerting capabilities with Microsoft Sentinel’s AI-driven analytics, graph correlation, and automated response workflows, security teams gain unified visibility across their Atlas workloads and the rest of their cloud estate.</p><h2>Giving teams a single security view</h2><p>This integration gives enterprises a single, AI-ready security operations view across applications and data. By leveraging the integration, customers can:</p><ul><li><p><strong>Simplify incident detection and response</strong>, reducing mean time to resolution.</p></li><li><p><strong>Strengthen governance and compliance</strong> through centralized monitoring and automated reporting.</p></li><li><p><strong>Accelerate time-to-value</strong> by deploying directly from the Microsoft Marketplace with unified billing and familiar Azure management.</p></li></ul><p>Together, MongoDB Atlas and Microsoft Sentinel eliminate visibility gaps, streamline SecOps, and empower organizations to operate securely and confidently across their Azure environments.</p><p></p><h3>Setting up the integration</h3><p>The integration’s setup experience is designed for simplicity and speed:</p><ul><li><p><strong>Create a Log Analytics Workspace</strong> and connect it to your Microsoft Sentinel instance.</p></li><li><p><strong>Search for “MongoDB Atlas Data Connector”</strong> in the Microsoft Marketplace or Sentinel Content Hub, then install the solution.</p></li><li><p>In Microsoft Sentinel, navigate to <strong>Data Connectors → MongoDB Atlas Data Connector</strong>, and select <strong>Deploy to Azure</strong>.</p></li><li><p>Provide:</p></li><ul><li><p>Your <strong>Log Analytics workspace</strong> details.</p></li><li><p><strong>MongoDB Project ID</strong> and the list of <strong>clusters</strong> to monitor.</p></li><li><p><strong>Service Account credentials</strong> (or a Key Vault reference) for API authentication.</p></li></ul><li><p>Optionally also configure:</p></li><ul><li><p>Log categories filters (<strong>NETWORK</strong>, <strong>ACCESS</strong>, <strong>QUERY</strong>).</p></li><li><p>Exclusions for specific <strong>Category IDs</strong>.</p></li><li><p><strong>Polling frequency</strong> for the Azure Function based on log volume and activity.</p></li></ul></ul><p>Once deployed, the function app, DCE, DCR, storage account, and Key Vault are automatically created, and logs begin flowing into Microsoft Sentinel per your defined schedule.</p><h3>Technical deep dive</h3><p>The technical diagram below illustrates the following integration components:</p><ul><li><p>UI of Connector captures the Log analytics workspace, Atlas specifics, and schedule</p></li><li><p>Azure Function periodically retrieves MongoDB logs</p></li><li><p>JobState Table maintains the last run timestamp to ensure incremental log collection</p></li><li><p>DCE and DCR handle data transformation before ingestion into MDBALogTable_CL.</p></li><li><p>Azure Key Vault securely stores the MongoDB API credentials</p></li></ul><p>This architecture ensures security and scalability, while aligning with enterprise compliance requirements.</p><p></p><p>The MongoDB Atlas logs have the schema that includes timestamp, category, severity, category id, message, and additional attributes as detailed <a href="https://www.mongodb.com/docs/manual/reference/log-messages/">here</a>. Below is a screenshot of the logs as ingested into the MDBALogTable_CL table.</p><p>Once available in Microsoft Sentinel, these logs can be queried, filtered, or visualized in dashboards. Analysts can build custom workbooks, define alerts on specific severity levels or categories, and trigger automated playbooks for real-time remediation.</p><p></p><h2>Unifying data and security management</h2><p>Modern security operations demand centralized visibility, intelligent analytics, and automated response without compromising on flexibility or developer agility.</p><p>The MongoDB Atlas Data Connector for Microsoft Sentinel empowers organizations to unify their data and security management, ensuring MongoDB workloads benefit from the same advanced protection, analytics, and automation as the rest of their cloud ecosystem.</p><p>With this integration, customers can now:</p><ul><li><p>Simplify log ingestion and monitoring for Atlas workloads</p></li><li><p>Enhance incident detection and investigation</p></li><li><p>Apply consistent policies and automation across their entire enterprise environment</p></li></ul><p>By bringing MongoDB Atlas into the Microsoft Sentinel ecosystem, security teams can finally manage, monitor, and respond to database security events from a single, intelligent, AI-powered platform.</p><p></p><p></p>]]></description>
      <pubDate>Tue, 03 Nov 2026 19:46:59 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/simplifying-enterprise-security-management-mongodb-atlas-logs-microsoft-sentinel</link>
      <guid>https://www.mongodb.com/company/blog/innovation/simplifying-enterprise-security-management-mongodb-atlas-logs-microsoft-sentinel</guid>
    </item><item>
      <title>Unlocking AI Search: Introducing Automated Embedding in MongoDB Vector Search</title>
      <description><![CDATA[<p>We are excited to announce the public preview of Automated Embedding in MongoDB Vector Search (available in Public Preview in <a href="https://www.mongodb.com/try/download/community">MongoDB Community Edition</a>), a groundbreaking feature designed to make building sophisticated, AI-powered applications easier than ever. Since 2023, MongoDB has offered integrated vector search alongside our operational database, and last year we <a href="https://www.mongodb.com/company/blog/news/redefining-database-ai-why-mongodb-acquired-voyage-ai">announced the acquisition of Voyage AI</a>, bringing state-of-the-art embedding and reranking models to our customers. </p><p>Now, with Automated Embedding in MongoDB Vector Search and the integration of Voyage AI’s state-of-the-art models, we’re giving developers a feature which solves a major point of friction: one-click automatic embedding directly inside MongoDB, which eliminates the need to sync data and manage external models.</p><p></p><h2>Automated Embedding in MongoDB Vector Search</h2><p>At its core, Automated Embedding in Vector Search offers seamless, secure, and scalable AI-powered search natively in MongoDB. By automatically generating vector embeddings (numerical representations of your data to capture semantic meaning), we eliminate the significant complexity typically required when building semantic search, recommendation engines, RAG apps, and AI agents.</p><h2>The complexity we’re eliminating</h2><p>Before this release, building vector search into applications presented significant challenges:</p><ul><li><p><strong>Manual embedding generation: </strong>Choosing an embedding model from over 100 available options and figuring out how to integrate external API services (authentication, input payload, output parameters) is challenging. Developers had to generate embeddings using external providers as part of their application code before inserting data or querying vector search. </p></li><li><p><strong>Synchronization overhead:</strong> Every insert, update, or delete required keeping source data and vector embeddings in sync. Developers had to set up custom pipelines, monitor change streams, and write logic to trigger re-embedding and synchronize vectors every time source data changed. </p></li><li><p><strong>Additional API complexity:</strong> Each vector search query necessitated an extra API call to generate query embeddings. </p></li><li><p><strong>Managing large data ingestion:</strong> While simple embedding creation can be straightforward, embedding millions of documents becomes a production nightmare that developers need to monitor at scale. Teams must build complex MLOps pipelines with queuing systems, specialized workers, and retry logic to handle failures, integrate monitoring and alert systems, and ensure that primary database operations aren&#39;t blocked by slow or failing embedding endpoints.</p></li></ul><h2>The Solution: Streamlined AI-powered search</h2><p>Automating the embedding process reduces complexity and makes getting started with semantic search as simple as creating a vector search index.</p><p>For the first time, you can simply choose an embedding model while setting up a vector search index, and the entire embeddings generation process is automated—no longer needing to rely on different vendors for embedding models and vector databases, which adds complexity and integration risks.  Now, you can simply select the embedding model that best matches your needs, including best-in-class embedding models from Voyage AI. This simplified approach significantly reduces the effort required to get started with key AI use cases, while Voyage AI&#39;s industry-leading embedding models ensure high-accuracy retrieval.</p><p></p><p><strong>Offers architectural simplicity</strong></p><p>Our streamlined architecture eliminates the need to manage separate embedding generation workflows, especially when handling complex, high-volume ingestions. </p><p>Developers no longer need to maintain external embedding models, freeing up valuable engineering time that was previously spent on custom pipelines, complex error handling, and performance tuning. This simplification allows you to focus on improving application functionality rather than building embeddings from scratch or having to bring in external third parties. With MongoDB, you now get the benefits of OLTP database, vector search, and Voyage AI embedding models in one unified system, eliminating the need for multiple systems and messy data syncs. </p><p></p><p><strong>Eliminates embedding mismatches with automation</strong></p><p>The system automatically generates vector embeddings for text data during initial data sync when creating indexes, during document insertions and updates, and during query processing. Vector embeddings stay synchronized as underlying data changes, eliminating the risk of stale or mismatched embeddings.</p><p><strong>Powered by state-of-the-art Voyage AI embedding models</strong></p><p>Automated Embedding in MongoDB Vector Search features state-of-the-art embedding models from Voyage AI, including voyage-4-large, voyage-4, voyage-4-lite and voyage-code-3. These models deliver industry-leading performance on retrieval benchmarks (such as <a href="https://huggingface.co/spaces/mteb/leaderboard?benchmark_name=RTEB%28beta%29">RTEB</a>) with multilingual support.</p><p></p><p><strong>Optimized for performance and reliability</strong></p><p>Automated Embedding in MongoDB Vector Search eliminates the context window and rate-limiting headaches that plague direct API integrations. </p><p>Through asynchronous dynamic batch processing that optimizes for maximum tokens per request allowed for a model, the system achieves optimal throughput during index creation - automatically adjusting batch sizes based on document shape and size. With built-in automatic retries and error handling, your embedding operations run reliably without blocking primary database operations. This production-ready infrastructure means you can ingest millions of documents without building complex MLOps pipelines or monitoring systems.</p><p><strong>Future-proofs your AI applications </strong></p><p>With Automated Embedding in MongoDB Vector Search, you can create indexes across multiple models and compare them side-by-side, making it simple to find the optimal price-performance for your use case. Model lifecycle management becomes effortless with automatic re-embedding capabilities when upgrading to newer, better-performing models. </p><p>We know many users have delayed migrating from older embedding models precisely because of the complexity involved in re-embedding entire datasets across multiple services. Now transitioning to next-generation models requires no custom code or complex coordination across your data services, and you can compare the performance of different models on your own dataset.</p><p></p><h2>Simplification for everyone</h2><p>Automated Embedding in MongoDB simplifies vector search adoption, allowing Software Engineers, ML Engineers, and Data Scientists from large enterprises to startups to focus on building applications rather than managing embedding integrations. It provides a low-friction path to unlocking powerful AI-driven capabilities for a wide range of use cases, including:</p><ul><li><p><strong>Generative AI:</strong> Building RAG (retrieval augmented generation) systems.</p></li><li><p><strong>E-commerce: </strong>Delivering personalized product recommendations.</p></li><li><p><strong>Content management:</strong> Implementing robust semantic search capabilities.</p></li><li><p><strong>Customer service: </strong>Creating sophisticated question-answering functionalities.</p></li><li><p><strong>Data science: </strong>Professionals who need efficient ways to process large datasets and streamline the transition from prototyping with state-of-the-art models to production.</p></li><li><p><strong>Migration path:</strong> Providing an easy migration path for existing text search users looking to upgrade to vector and hybrid search capabilities for improved relevance.</p></li></ul><h2>Reducing development overhead and speeding results</h2><p>We invited a select number of customers across industries, including healthcare, financial services, transportation, and media, to test automated embedding and provide feedback during our private preview. These customers saw the massive benefits, including immediate performance enhancements and reduced overhead. Two preview customers had the following to say: </p><p><em>&quot;We deployed MongoDB’s automated embedding in vector search across our 40‑million‑document corpus, converting weeks of engineering into a low‑maintenance, production‑grade workflow that materially improved retrieval speed and relevance while reducing development overhead.”</em></p><p>—<em>Ohad Levinkron-Fisch</em>
<em>Vice President of R&amp;D and AI</em>
<em>MedINT Medical Intelligence</em></p><p><em>&quot;Being able to drop MongoDB’s automated embedding into an in-flight, production-scale system and see immediate performance and simplicity gains is huge - and we’re thrilled to deepen our partnership with MongoDB, given how much of our stack already runs on MongoDB.&quot; </em></p><p>—<em>Joe Marta </em>
<em>Senior Director, Applied AI</em>
<em>Coalfire</em></p><h2>How to get started with the Public Preview</h2><p>By automatically generating and synchronizing vector embeddings using Voyage AI models, Automated Embedding in MongoDB Vector Search eliminates traditional vector search complexities. This secure and scalable solution is native to MongoDB, accelerating the creation of powerful AI-enabled applications and significantly improving the developer experience. </p><p>Automated Embedding in MongoDB Vector Search in Community Edition is available now, with MongoDB Atlas and MongoDB Vector Search in Enterprise Edition access coming soon. Use your favorite MongoDB language drivers (Python, JavaScript, Java, C#, and GoLang), AI frameworks like LangChain and LangGraph, and the MongoDB MCP server. </p><p><a href="https://www.mongodb.com/docs/vector-search/crud-embeddings/create-embeddings-automatic/">Jump in with our quick start guide.</a></p><p></p>]]></description>
      <pubDate>Tue, 03 Nov 2026 17:17:18 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/product-release-announcements/unlocking-ai-search-introducing-automated-embedding-in-mongodb-vector-search</link>
      <guid>https://www.mongodb.com/company/blog/product-release-announcements/unlocking-ai-search-introducing-automated-embedding-in-mongodb-vector-search</guid>
    </item><item>
      <title>Bring Live MongoDB Atlas Data Into Microsoft 365 Copilot</title>
      <description><![CDATA[<p>The federated Copilot connector for MongoDB Atlas gives organizations a governed way to bring live operational data into the flow of work across Copilot experiences.</p><p>To operate efficiently, businesses require timely information about the systems that underpin their organizations. For example, they need to be able to answer questions like: Which incidents are open? Which orders are delayed? What fields and data types are present in the customer collection? The answers they need often live in operational applications built on <a href="https://www.mongodb.com/products/platform/atlas-database">MongoDB Atlas</a>, while the questions are asked in the productivity tools people use every day.</p><p>To help close that gap, MongoDB is excited to introduce a federated Copilot connector for MongoDB Atlas. Now generally available, the connector enables users to ask Microsoft 365 Copilot questions about live data in MongoDB Atlas, bringing operational context into the same experience where people collaborate, analyze information, and make decisions.</p><p>The connector surfaces MongoDB Atlas data across Microsoft Copilot experiences, including Copilot Chat, Researcher in Copilot, Copilot Cowork, Microsoft Word, Excel, and Teams, with additional experiences planned to follow.</p><h2>Bring operational data into the flow of work</h2><p>The connector brings MongoDB Atlas to Microsoft Copilot through MongoDB’s managed remote Model Context Protocol (MCP) server. When a user asks a relevant question, Copilot can query Atlas in real time—instead of relying on a static copy of the data.</p><p>This creates a more direct path from a business question to the information needed to answer it, and helps users—who may not have MongoDB expertise—access and analyze live operational data through an AI assistant. </p><p>Now, business users can use conversational prompts to:</p><ul><li><p>Retrieve live business data without writing database queries.</p></li><li><p>Find and filter customers, transactions, products, orders, content, or operational events.</p></li><li><p>Get quick counts and key performance indicators, such as the number of delayed orders or high-value customers.</p></li><li><p>Summarize and rank data to identify top categories, products, regions, trends, averages, and other business insights.</p></li></ul><p>For example, a user might ask Copilot to summarize the open incidents in an Atlas cluster supporting a payments application, identify delayed orders, or describe the fields and data types in the customer collection for a loyalty service. By industry, a supply chain team can investigate inventory, shipment, and warehouse exceptions. A financial services team can explore customer records, fraud alerts, and transaction investigations. And a retailer can ask questions about orders, loyalty, customer service, and personalization. </p><p>The connector can also help power business copilots and agents. Organizations can ground Copilot and other AI assistants in current MongoDB Atlas data for customer service, sales, operations, and decision support, bringing live operational context into the workflows where teams already work.</p><h2>Connect to live data without migrating or indexing it</h2><p>Organizations using MongoDB Atlas do not need to migrate their operational data, re-platform their applications, or rebuild their integrations to use the connector. </p><p>To do so, an administrator simply approves and enables the connector in the Microsoft 365 admin center. Users then sign in, and their existing Atlas permissions carry through to each query.</p><p>MongoDB Atlas remains the system of record. The connector queries Atlas directly rather than indexing a copy of Atlas data into Microsoft 365, so the information returned to users reflects the current state of the underlying application data.</p><p>This federated approach helps organizations connect their productivity layer to operational data while keeping that data in the environment where it is managed.</p><h2>Put governance into every interaction</h2><p>Making operational data more accessible requires controls that organizations can understand and manage. The connector is designed to support that approach through:</p><ul><li><p><strong>Permission-aware access:</strong> Each query runs as the signed-in user and honors the permissions already defined in MongoDB Atlas.</p></li><li><p><strong>Administrator control:</strong> Admins approve the connector and can manage deployment through the Microsoft 365 admin center.</p></li><li><p><strong>Read-only access: </strong>The connector is designed for read-only interaction with Atlas data.</p></li><li><p><strong>Auditability: </strong>Administrators can audit connector activity in Microsoft Purview.</p></li><li><p><strong>No separate search index:</strong> The connector queries Atlas on demand instead of indexing a copy of Atlas data in Microsoft 365.</p></li></ul><p>Together, these controls give organizations a practical way to make operational information available through Copilot without giving up the governance model around the source data.</p><h2>A foundation for more productive work</h2><p>AI-powered productivity depends on access to relevant business context. By connecting Microsoft Copilot and other AI assistants to live MongoDB Atlas data through a federated connection, MongoDB and Microsoft are helping organizations make operational information easier to use without adding a data-movement project or another application to maintain. Users can get answers, summaries, and insights from live data through natural language, while technical teams retain control over the underlying systems and permissions.</p><p>For organizations already running MongoDB Atlas on Azure and Microsoft 365 Copilot, the connector provides a way to build on existing investments. Teams can explore high-value operational questions, validate measurable business outcomes, and develop repeatable patterns for bringing current data into everyday decisions.</p><p>The result is a simpler path from question to context to action—grounded in the systems organizations already use and governed by the permissions they already have.</p>]]></description>
      <pubDate>Tue, 03 Nov 2026 14:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/product-release-announcements/bring-live-atlas-data-into-microsoft-365-copilot</link>
      <guid>https://www.mongodb.com/company/blog/product-release-announcements/bring-live-atlas-data-into-microsoft-365-copilot</guid>
    </item><item>
      <title>Introducing MongoDB Atlas Sharding Advisor: Know When and How to Scale Sharded Clusters</title>
      <description><![CDATA[<p>As applications grow, database teams need to make increasingly complex decisions about how to distribute data, manage workloads, and scale their infrastructure. <a href="https://www.mongodb.com/docs/manual/sharding/">Sharding</a> enables MongoDB to scale horizontally, but managing a sharded cluster can introduce its own challenges. Understanding cluster health, diagnosing uneven load, and choosing an appropriate shard key can require piecing together metrics across multiple views and relying on specialized expertise.</p><p><a href="https://dochub.mongodb.org/core/atlas-sharding-insights">MongoDB Atlas Sharding Advisor</a> solves this by bringing sharding insights, contextual recommendations, and shard key analysis directly into MongoDB Atlas, helping database teams understand cluster health, identify potential scaling actions, and make more informed decisions as their workloads grow.</p><p>Now available for dedicated Atlas deployments running MongoDB 8.0 or later, Sharding Advisor brings together three capabilities: Sharding Insights, Sharding Recommendations, and Shard Key Analyzer.</p><p><strong>Figure 1.</strong> See how MongoDB Atlas Sharding Advisor helps database teams investigate sharded cluster health, identify potential issues, and evaluate shard key candidates.</p><h2>Sharding Insights: Clear views of sharded cluster health</h2><p>Troubleshooting a sharded cluster often means investigating signals across individual shards, collections, and mongos routers. When that information is spread across multiple views, it can be difficult to determine where an issue originates or understand how different parts of the cluster interact.</p><p>Sharding Insights brings shard-level, collection-level, and mongos metrics together in a single view in Atlas, giving database teams a clearer picture of cluster health and helping them investigate potential performance and data distribution issues.</p><p>With Sharding Insights, teams can:</p><ul><li><p><strong>Investigate shard-level performance:</strong> Understand whether resource pressure or workload activity is concentrated on particular shards.</p></li><li><p><strong>Understand collection-level distribution</strong>: Examine how data and operations are distributed across collections, and identify potential sources of imbalance.</p></li><li><p><strong>Explore mongos behavior:</strong> Inspect routing and connection metrics at the entry point to the sharded cluster.</p></li></ul><p>Together, these signals help teams narrow down where to investigate when performance or distribution issues arise, without having to piece together the same information across multiple views. Sharding Insights uses MongoDB Atlas’s existing metrics infrastructure, so there are no additional agents to install or separate telemetry pipeline to configure.</p><p><strong>Figure 2.</strong> Sharding Insights brings shard, collection, and mongos metrics together in MongoDB Atlas to help teams investigate the health of sharded clusters. </p><h2>Sharding Recommendations: Identify issues and next steps</h2><p>Visibility is an important first step, but database teams also need to know which conditions warrant attention and which options to consider. A growing collection, uneven load across shards, or a shard approaching its capacity can introduce operational challenges as workloads evolve. Identifying these conditions and understanding their underlying causes can require manual investigation and specialized expertise.</p><p>Sharding Recommendations help teams identify conditions in their clusters that may need attention. For each recommendation, Atlas provides context about why it appeared and suggests potential next steps to help teams investigate and evaluate their options.</p><p>For example, recommendations can flag situations like:</p><ul><li><p>A collection growing beyond the capacity of a single shard</p></li><li><p>Uneven load across shards</p></li><li><p>Shards approaching capacity</p></li></ul><p>By explaining the conditions behind a recommendation, Sharding Advisor helps database teams move from identifying a potential issue to understanding what they should investigate next. Recommendations provide decision support, not automatic remediation. Teams remain in control of evaluating the suggested actions and determining the right approach for their workloads and operational requirements.</p><p><strong>Figure 3. </strong>Sharding Recommendations highlights conditions that may need attention, explains why they were flagged, and provides suggested next steps.</p><h2>Shard Key Analyzer: Make shard key decisions with workload data</h2><p>Shard key selection is one of the most consequential decisions in designing a sharded collection. A key that doesn’t align well with an application’s data and access patterns can contribute to uneven distribution, hot spots, or inefficient workload routing. Yet evaluating candidate shard keys can be difficult. Database teams need to consider key characteristics and understand how those characteristics relate to their workloads before deciding how to distribute data.</p><p>The Shard Key Analyzer brings shard key analysis into MongoDB Atlas, helping teams evaluate candidate keys and understand potential trade-offs before making sharding decisions.</p><p>Using MongoDB’s analyzeShardKey command, the analyzer evaluates characteristics such as:</p><ul><li><p><strong>Cardinality:</strong> How many distinct values a candidate key contains</p></li><li><p><strong>Frequency:</strong> How frequently particular key values occur</p></li><li><p><strong>Monotonicity:</strong> Whether key values tend to increase or decrease in sequence</p></li></ul><p>When query sampling is configured, the analyzer can also incorporate read and write distribution data to help teams understand how a candidate shard key may distribute workload across shards. It supports single-field, compound, and hashed shard-key analysis, giving teams the flexibility to evaluate different candidates.</p><p>By bringing this analysis into Atlas, Shard Key Analyzer helps database teams compare candidates using evidence rather than assumptions alone. The result is a more informed basis for evaluating how a shard key may align with an application’s workload and data distribution needs. Note that Shard Key Analyzer provides analysis to support decision-making; it does not automatically select or apply a shard key.</p><p><strong>Figure 4.</strong> Shard Key Analyzer evaluates candidate shard keys using key characteristics and, when configured, workload-related read and write distribution data.</p><h2>Sharding guidance, built into MongoDB Atlas</h2><p>Sharding Advisor brings visibility, recommendations, and shard key analysis together in the Atlas experience, helping database teams better understand their clusters and evaluate their options as workloads grow.</p><p>With Sharding Advisor, teams can:</p><ul><li><p>Understand cluster health by bringing shard, collection, and mongos metrics into a unified view.</p></li><li><p>Identify conditions that require attention, along with contextual recommendations and suggested next steps.</p></li><li><p>Evaluate shard key candidates using key characteristics and optional workload-related data.</p></li></ul><p>These capabilities help teams investigate potential issues, assess scaling options, and make more informed decisions about their sharded deployments.</p>]]></description>
      <pubDate>Mon, 02 Nov 2026 15:13:14 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/product-release-announcements/introducing-atlas-sharding-advisor-know-when-how-scale-sharded-clusters</link>
      <guid>https://www.mongodb.com/company/blog/product-release-announcements/introducing-atlas-sharding-advisor-know-when-how-scale-sharded-clusters</guid>
    </item><item>
      <title>Building an Agentic Warehouse Management System—Part 2: Java and Spring AI</title>
      <description><![CDATA[<p>If you arrived here without reading the first part, I recommend starting with <a href="https://www.mongodb.com/company/blog/technical/building-an-agentic-warehouse-management-system-part-1-where-ai-agents-add-value"><strong>Agentic WMS — Part 1: Where AI Agents Add Value</strong></a><strong>.</strong> There, we introduced the WMS scenario, explored the replenishment problem, and discussed where an AI agent can add value without replacing deterministic application logic.
In this second part, we will move from the design to the first steps of the implementation.</p><p>We will look at how the agent is built with <strong>Java and Spring AI</strong>, how its capabilities and boundaries are defined, how it is triggered by the WMS, and how the planner turns the agent’s goal into an execution plan.</p><p>In <strong>Part 3</strong>, we will continue from that plan and see how the agent executes tasks using controlled tools, gathers the context it needs, makes the replenishment decision, and takes action when necessary.</p><h2>Designing the agent </h2><p>From this point on, we will focus on the main parts of the agent implementation using Java and Spring AI. Rather than covering Spring AI from the ground up, we will concentrate on the components directly relevant to this part of our agent: prompts, capabilities, triggering, and planning. For a broader introduction to Spring AI, see this <a href="https://dev.to/mongodb/how-to-build-rag-applications-with-spring-ai-and-mongodb-5gaj">article</a> by my colleague <a href="https://timotheekelly.com/">Tim Kelly</a>.</p><p>In Part 1, we established an important boundary: the WMS defines what the agent is allowed to do, while the agent decides what to do within those boundaries. Now we can translate that design into code.</p><p>Before diving into the implementation, the following diagram summarizes the complete agent flow across Parts 2 and 3. In this part, we will focus on <strong>defining the agent, triggering its execution, and creating the plan.</strong></p><p><strong>Figure 1. </strong>Agent lifecycle: Define, trigger, and plan.</p><h2>Define the Agent</h2><p>The agent is triggered after an outbound operation is completed, with the goal of determining whether that operation created a need for replenishment.</p><p>The first step is to define how the agent should behave and what it is allowed to do.</p><p>In our implementation, we organize the agent around three main components: </p><ol><li><p><strong>Planner</strong></p></li><li><p><strong>Executor</strong></p></li><li><p><strong>Reporter</strong></p></li></ol><p>The planner receives the goal and determines the tasks required to achieve it:</p><p>The executor will receive one task at a time and perform it using the tools available for that task:</p><p>Finally, the reporter summarizes what happened during the execution:</p><p>These are simplified versions of the prompts used in the <a href="https://github.com/mongodb-developer/mongodb-jvm-showcase/blob/5051a4953b2d8f41528fb4bba024b78263f96095/java/use-cases/agentic-wms/src/main/java/com/devrel/wms/config/AgentConfig.java#L19">complete application</a>, but they show the responsibility of each component. Together, these components become part of our agent definition:</p><p>The definition also contains the <strong>capabilities</strong> available to the agent. In our replenishment workflow, we use five:</p><ul><li><p><strong>Analysis:</strong> Access invoices, inventory, and stock movements.</p></li><li><p><strong>Policy:</strong> Retrieve depositor policies.</p></li><li><p><strong>Decision:</strong> Determine whether replenishment is required.</p></li><li><p><strong>Replenishment:</strong> Create a replenishment request.</p></li><li><p><strong>Notification:</strong> Draft the related email.</p></li></ul><p>Each capability defines a type of operation and the tools that can be used while performing it:</p><p>This gives us a simple boundary around each task. An <em>ANALYSIS</em> task, for example, can access inventory and stock movement tools, but it cannot create a replenishment request. A <em>DECISION</em> task does not expose any tool and uses the results collected by the previous tasks.</p><p>Finally, we can connect these pieces when defining the replenishment agent:</p><p>At this point, we have defined <strong>what the agent can do and the boundaries around those operations</strong>. Before looking at how the plan is created, let&#39;s see how the agent execution starts.</p><h2>Trigger the agent</h2><p>The agent starts after an outbound operation has been <a href="https://github.com/mongodb-developer/mongodb-jvm-showcase/blob/ea5c87c042867a0ea0c71f9ca80c41b466bd2981/java/use-cases/agentic-wms/src/main/java/com/devrel/wms/service/OutboundInvoiceService.java#L128">successfully completed</a>. Once the transaction is committed, the application publishes the <em>OUTBOUND_INVOICE_COMPLETED</em> event:</p><p>A <a href="https://github.com/mongodb-developer/mongodb-jvm-showcase/blob/ea5c87c042867a0ea0c71f9ca80c41b466bd2981/java/use-cases/agentic-wms/src/main/java/com/devrel/wms/event/ReplenishmentAnalysisListener.java#L38">listener</a> receives that event and starts the agent using the outbound invoice number as the reference:</p><p>Using <em>AFTER_COMMIT</em> ensures that the agent starts only after the outbound operation has been persisted and the inventory already reflects the latest state. From there, the agent receives its goal and can begin planning how to accomplish it.</p><h2>Plan</h2><p>Once the agent is triggered, the first responsibility of the <a href="https://github.com/mongodb-developer/mongodb-jvm-showcase/blob/main/java/use-cases/agentic-wms/src/main/java/com/devrel/wms/agent/AgentRunner.java">AgentRunner</a> is to create an execution plan.</p><p>The application does not define this list of tasks in advance. Instead, the planner receives the <strong>goal</strong> together with the <strong>capabilities available to the agent</strong> and determines which tasks are required for its execution.</p><p>Each planned task contains two pieces of information: what needs to be done and which capability should be responsible for it:</p><p>Based on this information, the planner generates an ordered list of tasks:</p><p>Here, Spring AI maps the model response directly to our <em>PlannedTask</em> objects through structured output, giving the application a typed execution plan instead of requiring us to parse generated text manually.</p><p>Once the planner returns the tasks, we persist the initial state of the execution as an AgentRun in MongoDB.</p><p>At this point, the execution is marked as <em>RUNNING</em>, and every task generated by the planner starts with the <em>PENDING</em> status:</p><p>This gives us a persistent representation of the execution from the beginning, including the tasks that were planned. At this point, the document may look like this:</p><p>The plan is now ready, and the execution has been registered.</p><h2>Conclusion</h2><p>In this second part, we translated the agent design into the first pieces of the implementation. We defined its responsibilities and capabilities, connected it to the WMS workflow, and used the planner to turn the agent goal into a persistent execution plan.</p><p>At this point, the agent knows what needs to be done and which capability is responsible for each task. In Part 3, we will focus on how that plan is executed: using controlled tools, gathering operational and business context, making the replenishment decision, and acting when necessary.</p>]]></description>
      <pubDate>Thu, 29 Oct 2026 17:33:15 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/technical/building-an-agentic-warehouse-management-system-part-2-java-spring-ai</link>
      <guid>https://www.mongodb.com/company/blog/technical/building-an-agentic-warehouse-management-system-part-2-java-spring-ai</guid>
    </item><item>
      <title>Agentic Smart Payment Routing with MongoDB / Part I: The Multi-Modal Blueprint</title>
      <description><![CDATA[<p>Transaction routing is a delicate balancing act between authorization rates, execution cost, and latency. A declined transaction can mean a lost sale, making payment optimization one of the most direct levers for top-line revenue growth. Yet payment operations teams remain trapped in manual operational cycles: Pulling batch CSV reports, analyzing spreadsheets, and manually updating rule tables in legacy gateways. And that repetitive cycle can cost you dearly.</p><p>Global businesses lose 1.5% to 2.2% of annual revenue to poor payment performance and false declines, according to research by Checkout.com and Oxford Economics.  While those percentages may seem small, it actually adds up to more than $50 billion in lost revenue each year. And the impact isn’t seen in weeks, months, or a year later. In fact, the fallout is immediate: 45% of shoppers abandon purchases and shift to competitors after a single checkout decline.</p><p>To recover lost revenue, modern infrastructure must decouple routing intelligence from checkout execution. Running a background multi-agent control plane to analyze telemetry, simulate options, enforce cost guardrails, and update JSON rules in MongoDB enables continuous smart routing optimization with execution in milliseconds.</p><p>Welcome to our new series on agentic payment smart routing, where we architect a modern payment routing platform. This first installment introduces the core concepts for designing an AI-driven control plane across all payment modalities. In the following series, we will apply these foundational principles to specialized deep dives into card payment and cross-border bank transfer routing.</p><h2>Foundational principles of smart routing</h2><p>To build a resilient payment stack, you need to understand four universal principles that apply whether processing a credit card, a cross-border, or a crypto stablecoin payment. These four principles answer four questions:</p><ul><li><p><strong>Where?</strong> Routing applies only before the transaction enters the network or rail.</p></li><li><p><strong>Who?</strong> Networks, PSPs, and acquirers have distinct roles.</p></li><li><p><strong>What?</strong> Input signals map to an output target: a Merchant ID (MID), clearing rail, or blockchain network.</p></li><li><p><strong>When?</strong> Before payment entry (prerouting), at initiation (smart routing), and after a recoverable failure (cascading failover)</p></li></ul><p>Figure 1 summarizes these principles:</p><p><strong>Figure 1</strong>. Foundational principles of smart routing (universal across modalities).</p><h2>Why do scripted payment routing rules fall short?</h2><p>Payment routing selects which gateway, acquirer, or network rail processes a transaction from intent to settlement. Choosing the right architecture requires evaluating three distinct paradigms along the maturity spectrum: static, traditional dynamic, and AI agentic routing.</p><p>The business objective is to improve authorization rates without allowing processing costs, fraud exposure, or operational complexity to outpace revenue. A declined transaction can mean a lost sale, and poor payment performance erodes revenue through false declines. Yet many payment ops teams still rely on batch reports, spreadsheets, SQL queries, and manually maintained rule tables.</p><p><strong>Figure 2</strong>. The evolution of payment routing mechanics.</p><p>Robotic process automation and scripted workflows face three main limitations in payment routing:</p><ul><li><p><strong>Dimensionality explosion</strong>: Payment performance can shift at complex intersections, such as a specific clearing rail, jurisdiction, routing identifier (BIN, BIC, or chain ID), asset type, or transaction amount range. A script can only analyze combinations that engineers explicitly anticipated.</p></li><li><p><strong>Unstructured error interpretation</strong>: Processing endpoints, banks, and digital asset networks often return inconsistent responses and decline codes. Rigid scripts struggle to process vague signals (such as &quot;Do Not Honor&quot; or generic rejection codes).</p></li><li><p><strong>Multi-constraint trade-offs</strong>: Achieving higher authorization rates often comes at the cost of higher processing fees, network wire or gas costs, foreign exchange spreads, volume commitments, or liquidity constraints. Nested conditions quickly become complex to maintain, explain, and test.</p></li></ul><p>Agentic AI bridges this gap, not by replacing fast execution with slow LLM calls, but by handling background reasoning and continuous rule optimization while preserving a fast, predictable execution path.</p><h2>An agentic control plane and fast data plane help improve payment routing</h2><p>An agentic architecture separates background payment rule optimization from payment execution. Payment rule optimization is executed at an asynchronous multi-agent control plane, while payment execution runs on a high-speed execution data plane.</p><p>The asynchronous multi-agent control plane does not evaluate individual payment requests in real time. Invoking AI agents on the hot execution path would introduce unsustainable processing costs and unacceptable latency for high-volume scenarios. Instead, the control plane operates continuously in the background to monitor route degradation, simulate net-margin impacts, and present optimized routing rules on an operational dashboard for human payment manager approval. Meanwhile, the high-speed execution data plane handles live transactions at the point of interaction—whether at a POS terminal, an e-commerce checkout, a bank transfer portal, or a Web3 payment widget—by deterministically querying active, declarative rules and evaluating relevant context in milliseconds. </p><p><strong>Figure 3</strong>. High-level architecture of multi-agent control and high-speed execution data planes underpinned by MongoDB and Atlas Agent Engine.</p><p>The control plane can automate the five-step payment routing optimization loop typically executed manually by the human payment analyst. The asynchronous multi-agent control plane works continuously in the background. Specialized agents can divide the optimization loop into focused responsibilities:</p><p>While this is a simplified example applicable to card payment routing, these concepts can be easily adapted to bank transfers and crypto payments.</p><p>A telemetry agent detects that U.K. Mastercard debit transactions have a 78% authorization rate through Gateway Alpha versus a 91% rate through Gateway Beta. The simulation agent estimates moving 50,000 monthly transactions (average $80 value) could recover $520,000 in sales. Gateway Beta charges higher fees, but the 0.18% projected fee increase remains below the 0.5% policy cap. The supervisor agent can present the projection results as a scorecard for approval and then persist an active rule with Gateway Beta as the primary route and Gateway Alpha as the backup.</p><h2>How MongoDB supports agentic payment routing</h2><p>Agentic payment routing needs more than a place to store rules. It needs a data platform that unifies telemetry, transaction history, provider profiles, policies, agent state and memory, and active configurations to support investigation and execution.</p><p>MongoDB’s document model naturally fits payment data that evolves across providers and rails. An acquirer may return structured decline fields, a clearing house nested ISO 20022 XML error payloads, and a crypto RPC node unformatted event logs. A document model preserves these native payload differences without rigid schema migration or separate extraction pipelines. This flexibility enables AI agents to analyze complete payment context rather than relying only on predefined fields a rigid script anticipated.</p><p>MongoDB Atlas brings search and aggregation capabilities together. <a href="https://www.mongodb.com/docs/vector-search/">MongoDB Vector Search</a> helps find similar historical payment contexts, while metadata filters and aggregation pipelines narrow results by country, network, payment modality, currency or token asset, and policy constraints. Agents use these signals to detect hidden performance patterns and rank routes by success rate, similarity, and processing fees.</p><p>The database also stores active JSON rules that the execution engine reads. Agents write new rules, record their confidence and justification, set their status to pending approval, and activate them upon manager approval. Time-to-live (TTL) indexes handle rule expiration, while <a href="https://www.mongodb.com/docs/manual/changestreams/">MongoDB Change Streams</a> instantly notify the control-plane components of transaction data or rule updates without waiting for batch jobs.</p><p>Deployable anywhere, <a href="https://www.mongodb.com/products/platform/atlas-agent-engine">Atlas Agent Engine</a> is an enterprise platform for managing the full lifecycle of AI agents. It delivers native short- and long-term memory primitives within the database, eliminating custom state pipelines. Running in a sandboxed execution runtime with built-in observability, it enables auditing of agent recommendations. With native safety controls and support for open standards like MCP and A2A, it integrates into existing stacks to deliver secure, audit-ready payment routing.</p><p>Security and deployment requirements shape the architecture. <a href="https://www.mongodb.com/docs/manual/core/queryable-encryption/overview-enable-qe/#std-label-qe-overview-enable-qe">MongoDB Queryable Encryption</a> keeps sensitive fields encrypted while supporting specific query patterns, supporting PCI DSS and privacy obligations. <a href="https://www.mongodb.com/docs/manual/core/zone-sharding/">Zone-based sharding</a> keeps selected data in target regions, while multi-cloud deployments ensure high availability across cloud providers. These capabilities help build an architecture that meets regulatory, availability, and data residency needs.</p><p>Most importantly, MongoDB supports the separation between control and execution. The control plane can analyze telemetry, logs, vectors, and policies, while the data plane retrieves only the active rule and attributes required for a fast decision.</p><h2>What agentic payment routing enables</h2><p>Smart payment routing is evolving from static rules into a continuous, self-healing optimization system. Static routing remains useful for deterministic paths, and machine learning can add real-time scoring. But neither approach fully addresses the work of discovering new segments, interpreting changing unstructured decline or failure signals, simulating alternatives, and enforcing competing multi-variable constraints across cards, bank rails, and digital assets.</p><p>Agentic AI handles this background work. With a multi-agent control plane and MongoDB, PSPs, orchestration providers, banks, and enterprise merchants can continuously analyze payment performance, test routes, protect margins, and approve impactful changes. MongoDB manages the changing operational context, enables advanced search capabilities across similar payment scenarios, and serves active rules for low-latency execution.</p><p>The result is a practical path to smarter payments: Autonomous optimization where reasoning is useful, deterministic execution where speed is essential, and human oversight where governance requires it.</p><p><strong>References:</strong></p><ul><li><p><a href="https://www.checkout.com/guides-and-reports/the-hidden-billion-dollar-opportunity">Checkout.com: High Performance Payments Report – The Hidden Billion-Dollar Opportunity</a></p></li><li><p><a href="https://www.checkout.com/newsroom/checkout-com-research-finds-us-businesses-lag-behind-in-payment-performance-losing-2-1-of-global-revenues-annually">Checkout.com Newsroom: Research Finds Businesses Lag Behind in Payment Performance</a></p></li><li><p><a href="https://www.checkout.com/blog/high-performance-payments-the-hidden-billion-dollar-opportunity">Checkout.com Blog: High-Performance Payments: The Hidden Billion-Dollar Opportunity</a></p></li></ul>]]></description>
      <pubDate>Thu, 29 Oct 2026 16:38:20 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/agentic-smart-payment-routing-part-1-multi-modal-blueprint</link>
      <guid>https://www.mongodb.com/company/blog/innovation/agentic-smart-payment-routing-part-1-multi-modal-blueprint</guid>
    </item><item>
      <title>Scanning 7.25 Million Public Repositories on China&#39;s Largest Git Platform for Secrets</title>
      <description><![CDATA[<p><em>This guest post by independent security researcher Ben Zimmermann was developed in collaboration with the Kingfisher team at MongoDB. Ben specializes in large-scale credential exposure research across public source-hosting platforms.</em></p><p><strong>TL;DR:</strong> I scanned <strong>7,256,531 public repositories</strong> on Gitee (China&#39;s largest indigenous Git hosting platform), using both TruffleHog and <a href="https://github.com/mongodb/kingfisher">Kingfisher</a>, and found <strong>26,400 unique verified-live credentials</strong>. Findings included an active organization-admin credential for a major enterprise AI platform and thousands of live cloud provider access keys.</p><h2>What is Gitee?</h2><p>Gitee, launched in 2013 by OSChina, was selected by China&#39;s Ministry of Industry and Information Technology as the country&#39;s national open-source code hosting platform. Its public API is severely constrained relative to GitHub and GitLab: no paginated projects endpoint, and the on-site code-search feature appears to have been retired years ago. A<a href="https://chinggg.github.io/post/git-leaks/"> 2021 attempt</a> to study credential exposure on Gitee concluded that its APIs were too limited to scale the research.</p><p>Like any large Git platform, it&#39;s an attractive surface for credential exposure:</p><ul><li><p>It is Git-based, so secrets buried deep in commit history persist.</p></li><li><p>It hosts millions of public repositories with active commit volume.</p></li><li><p>It has no public equivalent of the platform-vendor secret-scanning partnerships that have become standard on GitHub.</p></li></ul><h2>Enumerating millions of Gitee repositories</h2><p>Gitee&#39;s public API is severely limited, so enumerating millions of repositories required combining many surfaces: the only official REST endpoint that returned useful data at scale, the platform&#39;s Explore feed, per-user repository and stargazer pages on the website itself, and Gitee&#39;s internal Elasticsearch widget that backs the on-site search UI.</p><h3>Bootstrapping a username corpus</h3><p>The single official REST endpoint that returned useful data at scale was GET /api/v5/search/users?q=&lt;query&gt;. I hit it with three-character prefix queries (aaa, aab, ..., zzz) and combined the results with usernames extracted from the public Explore feed (/explore/all?order=starred|popular|updated). I then expanded that set via each user&#39;s following list and the stargazers of popular repositories. This produced a seed corpus of <strong>1,704,759 usernames</strong>.</p><h3>Scraping per-user pages on the frontend</h3><p>With the username corpus in hand, two per-user pages yielded repositories: gitee.com/{user}/projects (a user&#39;s own repos) and gitee.com/{user}/stared_projects (repos the user has starred). Page 1 of /projects returns full HTML; subsequent pages are AJAX-paginated (X-Requested-With: XMLHttpRequest). The stargazer-list pages used during username bootstrap paginate the same way, additionally requiring a CSRF token extracted from the page-1 HTML.</p><h3>Querying the on-site search widget</h3><p>A large fraction of the platform sits outside the social graph. To reach it, I used the same internal Elasticsearch endpoint that backs Gitee&#39;s on-site search UI: so.gitee.com/v1/search/widget/wong1slagnlmzwvsu5ya. It takes a query ID, a q parameter, and pagination via from + size:</p><p>Each query returned at most 20 results per page, with a hard cap of <strong>200 results total</strong> (from + size &lt;= MAX_RESULTS) regardless of how many matches actually existed. For specific usernames, this was usually fine; for common usernames and trigram prefix queries against the widget, the cap silently truncated results.</p><h3>Escaping the 200-result cap with bucket splitting</h3><p>The widget&#39;s response includes Elasticsearch aggregations that bucket results by language (编程语言) and license (许可证). For the per-username scrape, when a query was capped, I split it by the language buckets the response already returned:</p><p>For trigram prefix queries against the widget (used to surface repos not associated with any user I&#39;d discovered), I extended this into a BFS over a query tree: capped nodes split first by language, then by license, then by deeper prefix until each branch fit within 200 results.</p><p>After deduplicating repo IDs across all sources, this produced a working set of <strong>7,256,531</strong> unique public Gitee repositories.</p><h2>Wiring up the scan pipeline</h2><p>The next challenge was cloning and scanning the 7.25 million repositories. To do this in a single Python script, I used<a href="https://modal.com"> Modal</a>, a serverless compute platform popular for AI workloads but well-suited to most parallel jobs. I ran TruffleHog and Kingfisher concurrently against every repository for increased coverage. Each surface verified credentials that the other missed, so running both caught more exposed credentials than either alone.</p><p><strong>Figure 1.</strong> Dual-scanner pipeline architecture.</p><h3>The Docker image</h3><p>The container image is a multi-stage build that pulls both scanner binaries from their upstream releases into a single Python base, plus git and OpenSSH for cloning:</p><h3>The per-repo scan function</h3><p>A single Modal function bare-clones each repo over SSH and runs both scanners concurrently as subprocesses against the same on-disk clone:</p><h3>Dispatching 7.25M repos in batches</h3><p>I split the corpus into 50 batches of ~150K repos and ran them sequentially at a steady 350 concurrent containers. Smaller batches were safer at this scale and easier to resume after interruptions; running larger batches was unstable and would hit clone-side blocks.</p><h3>Cost and scale</h3><p>Total wall time: roughly one month of continuous execution. Per-repo clone times were a major contributor: Gitee&#39;s servers sit in China, and cross-Pacific network distance plus SSH protocol overhead made each clone materially slower than an equivalent GitHub clone would be. The total cost was $3,097.64, fully absorbed by the $5,000 compute-credit sponsorship from Modal that supported this research. The same Modal + dual-scanner architecture works against most Git hosts with little more than a clone-URL substitution. I used a smaller-scale version of this approach in a<a href="https://benzimmermann.dev/blog/algolia-docsearch-admin-keys"> prior investigation of Algolia DocSearch admin keys</a>.</p><h2>The results</h2><p>Across the 7,256,531 public Gitee repositories scanned, the dual-scanner pipeline surfaced <strong>26,400 unique, verified-live credentials</strong> after deduplicating by token value.</p><p>Both scanners authenticate each candidate against its vendor&#39;s API at scan time (TruffleHog&#39;s --only-verified and Kingfisher&#39;s --only-valid modes), discarding anything that pattern-matches but fails to authenticate. The 26,400 figure is deduplicated by raw secret value, so duplicates across repositories or scanners count once.</p><p>Either scanner alone would have caught only about half of these credentials. The two tools&#39; detector coverage was largely complementary: TruffleHog dominated Alibaba Cloud key detection (9,428 vs. 993), while Kingfisher dominated DeepSeek (2,940 vs. 230), OpenAI (1,198 vs. 150), HuggingFace (154 vs. 1), and Chinese-AI services like Zhipu (1,489 vs. 0) that TruffleHog has no detector for.</p><h3>Secrets by type</h3><p>The single most common leaked credential type was Alibaba Cloud AccessKey pairs: roughly <strong>1 in every 766 Gitee repositories</strong> contained a verified-live Alibaba Cloud credential.</p><p><strong>Figure 2.</strong> Credentials by vendor. </p><p>A long tail of additional vendors (LangSmith, OpenWeather, Algolia, PostHog, OpenRouter, MySQL, Stripe, Slack, Twitter, and others) accounts for the rest.</p><h3>Secrets committed by date</h3><p>The vast majority of verified-live credentials were committed in the last two years. 2025 alone accounts for 12,242 unique credentials, nearly half the entire dataset.</p><p><strong>Figure 3.</strong> Unique credentials committed by year. </p><h3>Secrets by committer email domain</h3><p>Most credentials were committed from personal mail services (qq.com, 163.com, gmail.com), making per-company attribution impossible at scale. The corporate-domain numbers below are a floor; even so, the names span major Chinese and Western tech companies alike.</p><p><strong>Figure 5.</strong> Unique credentials by committer email domain. </p><p>Smaller corporate footprints also appear from Oracle, Apple, Meta, Anthropic, and others, plus Chinese commercial and academic domains.</p><h3>Comparing Gitee with GitLab and Bitbucket</h3><p>The closest prior data points come from<a href="https://trufflesecurity.com/blog/scanning-5-6-million-public-gitlab-repositories-for-secrets"> TruffleSecurity&#39;s scan of 5.6 million public GitLab repositories</a>, and a companion Bitbucket scan referenced in that post.</p><p>Gitee tops both Western platforms on raw count and per-repository density. One methodology note: the TruffleSecurity scans used TruffleHog alone, while this one used TruffleHog and Kingfisher together. TruffleHog&#39;s detector library skews toward Western vendors, and Gitee has heavy Chinese-vendor activity (Alibaba Cloud, DeepSeek, Zhipu, and others) that Kingfisher&#39;s coverage helps to surface; stripping our findings to TruffleHog-only puts Gitee at 1.76 per 1,000 repos.</p><h2>Disclosure</h2><p>I emailed the vendors with the highest exposure volume in this scan, providing each a coordinated report containing the full list of verified-live credentials associated with their service, along with source-repository metadata to help them attribute affected customers.</p><p>Per-developer notification (contacting the committer of each leaked credential individually) was not pursued at this scale. Vendor-side revocation is the more reliable path, since it doesn&#39;t require any action from the user who leaked the credential.</p><p>At the time of writing, revocation status for the disclosed credentials has not yet been confirmed.</p><h2>Summary</h2><ul><li><p><strong>Gitee is a meaningful credential-exposure surface.</strong> 26,400 verified-live credentials across 7.25M repositories. Per-repository density higher than comparable published scans of GitLab and Bitbucket.</p></li><li><p><strong>Major tech companies appear in the committer metadata, Chinese and Western alike.</strong> The breadth includes Huawei, ByteDance, Google, Microsoft, Oracle, and others, suggesting this is not a purely-Chinese-developer phenomenon.</p></li><li><p><strong>Disclosure paths are asymmetric.</strong> Western companies typically have bug bounty programs or accessible security channels. Most Chinese companies don&#39;t, leaving leaked credentials without a clear remediation path.</p></li><li><p><strong>The architecture is portable.</strong> The same Modal + dual-scanner pipeline works on most Git hosts with little more than a clone-URL substitution; the full scan cost roughly $3,000.</p></li></ul>]]></description>
      <pubDate>Wed, 28 Oct 2026 16:17:24 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/technical/scanning-7-point-25-million-public-repositories-chinas-largest-git-platform-for-secrets</link>
      <guid>https://www.mongodb.com/company/blog/technical/scanning-7-point-25-million-public-repositories-chinas-largest-git-platform-for-secrets</guid>
    </item><item>
      <title>DataGrip: a great database IDE to work with MongoDB Atlas</title>
      <description><![CDATA[<p></p><p><em>JetBrains released </em><a href="https://blog.jetbrains.com/datagrip/2020/06/16/introducing-mongodb-shell-in-datagrip/"><em>a new version of DataGrip</em></a><em> that includes support for MongoDB and ships with the MongoDB Shell out of the box.</em></p><p>A few months ago, JetBrains released the first version of DataGrip that supports MongoDB. DataGrip is a professional DataBase IDE and is a great tool for advanced data exploration and analytical queries for your data in MongoDB and Atlas.</p><p>If you use any of the other JetBrains commercial products for development (e.g. PhpStorm, PyCharm), you can install the Database Tools plugin and work with MongoDB right inside your IDE.</p><p>As <a href="https://youtu.be/sAwZAxAM8mw">we announced last week at MongoDB.live</a>, the MongoDB plugin in DataGrip and in the other JetBrains IDE now includes <strong>a database console built on top of</strong> <a href="https://www.mongodb.com/company/blog/product-release-announcement/introducing-the-new-shell">the MongoDB Shell</a>. This is the result of a close collaboration between engineering teams at MongoDB and JetBrains and we are excited to finally release it to all our users.</p><p>With this integration, when you connect to MongoDB and Atlas with DataGrip, you get a console/shell experience that is 100% consistent with what you get in the terminal or in the other MongoDB’s developer tools.</p><p></p><h2>DataGrip and Atlas</h2><p>When your data is stored in Atlas, navigating through it with DataGrip is extremely easy.</p><p></p><p>For example, to connect to my <a href="https://www.mongodb.com/cloud/atlas/register">free Atlas cluster</a>, I can just grab a connection string from the Atlas UI, use it to add a new data source in DataGrip and I am connected and ready to explore my data.</p><p></p><h2>Using Consoles</h2><p>If you need to run queries, aggregations, or other database commands, consoles are a great way to do that.</p><p>The engineering teams at JetBrains and at MongoDB worked together to <strong>bring the new</strong>, <a href="https://github.com/mongodb-js/mongosh">embeddable MongoDB Shell</a> <strong>to DataGrip</strong> and use it as the engine behind database consoles. This means the same commands that you can run in the MongoDB Shell are available in DataGrip and the other JetBrains IDEs and you can expect them to work exactly in the same way with the addition of the beautiful UI you are already used to on top.</p><p></p><h2>A great fit for Atlas Data Lake</h2><p>DataGrip works well MongoDB deployments, whether self-managed or in Atlas. You can also use it with <a href="https://www.mongodb.com/products/updates/product-support-deprecation">Atlas Data Lake</a>. If you have data is stored in Amazon S3 and you want to query and analyze it with MQL, you can <a href="https://docs.mongodb.com/datalake/tutorial/getting-started">create a Data Lake</a> and start working with it right away.</p><p></p><p>DataGrip’s search capabilities give you a quick way to find the data you are interested in, and its powerful export tool makes it easy to extract it in the format you need to use it with other tools like Excel, for example.</p><h2>Get started with MongoDB Atlas and DataGrip</h2><p>We are really happy with the result of our collaboration with the team at JetBrains and we are looking forward to working more together to bring all the future capabilities of the MongoDB Shell to DataGrip and the other JetBrains IDEs.</p><p>You can experience for yourself how DataGrip is a perfect companion for MongoDB Atlas:</p><ol><li>Get <a href="https://www.mongodb.com/cloud/atlas/register">a free MongoDB Atlas cluster</a>;</li><li>Deploy some <a href="https://docs.atlas.mongodb.com/sample-data/">sample datasets</a>;</li><li><a href="https://www.jetbrains.com/datagrip/">Download DataGrip</a> and start working with your data immediately.</li></ol>]]></description>
      <pubDate>Wed, 28 Oct 2026 01:07:06 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/technical/datagrip-great-database-ide-work-with-atlas</link>
      <guid>https://www.mongodb.com/company/blog/technical/datagrip-great-database-ide-work-with-atlas</guid>
    </item><item>
      <title>MongoDB.local London 2024: Better Applications, Faster</title>
      <description><![CDATA[<p></p><p>Since we kicked off MongoDB’s series of 2024 events in April, we’ve connected with thousands of customers, partners, and community members in cities around the world—from Mexico City to Mumbai. Yesterday marked the nineteenth stop of the 2024 MongoDB.local tour, and we had a blast welcoming folks across industries to MongoDB.local London, where we discussed the latest technology trends, celebrated customer innovations, and unveiled product updates that make it easier than ever for developers to build next-gen applications.</p><p>Over the past year, MongoDB’s more than 50,000 customers have been telling us that their needs are changing. They’re increasingly focused on three areas:</p><ol><li><p>Helping developers build faster and more efficiently</p></li><li><p>Empowering teams to create AI-powered applications</p></li><li><p>Moving from legacy systems to modern platforms</p></li></ol><p>Across these areas, there’s a common need for a solid foundation: each requires a resilient, scalable, secure, and highly performant database.</p><p>The updates we shared at MongoDB.local London reflect these priorities. MongoDB is committed to ensuring that our products are built to exceed our customers’ most stringent requirements, and that they provide the strongest possible foundation for building a wide range of applications, now and in the future.</p><p>Indeed, during yesterday’s event, Sahir Azam, MongoDB’s Chief Product Officer, discussed the foundational role data plays in his keynote address. He also shared the latest advancement from our partner ecosystem, <a href="https://www.mongodb.com/docs/atlas/ai-integrations/amazon-bedrock/">an AI solution powered by MongoDB, Amazon Web Services, and Anthropic</a> that makes it easier for customers to deploy gen AI customer care applications.</p><h2>MongoDB 8.0: The best version of MongoDB ever</h2><p>The biggest news at .local London was the <a href="https://www.mongodb.com/products/updates/version-release">general availability of MongoDB 8.0</a>, which provides significant performance improvements, reduced scaling costs, and adds additional scalability, resilience, and data security capabilities to the world’s most popular document database.</p><p>Architectural optimizations in MongoDB 8.0 have significantly reduced memory usage and query times, and MongoDB 8.0 has more efficient batch processing capabilities than previous versions. Specifically, MongoDB 8.0 features 36% better read throughput, 56% faster bulk writes, and 20% faster concurrent writes during data replication. In addition, MongoDB 8.0 can handle higher volumes of time series data and can perform complex aggregations more than 200% faster—with lower resource usage and costs. Last (but hardly least!), <a href="https://www.mongodb.com/docs/v7.0/core/queryable-encryption/">Queryable Encryption</a> now supports range queries, ensuring data security while enabling powerful analytics.</p><p>For more on MongoDB.local London’s product announcements—which are designed to accelerate application development, simplify AI innovation, and speed developer upskilling—please read on!</p><h2>Accelerating application development</h2><h3>Improved scaling and elasticity on MongoDB Atlas capabilities</h3><p>New enhancements to MongoDB Atlas’s control plane allow customers to scale clusters faster, respond to resource demands in real-time, and optimize performance—all while reducing operational costs.</p><p>First, our new granular resource provisioning and scaling features—including independent shard scaling and extended storage and IOPS on Azure—allow customers to optimize resources precisely where needed. Second, Atlas customers will experience faster cluster scaling with up to 50% quicker scaling times by scaling clusters in parallel by node type.</p><p>Finally, MongoDB Atlas users will enjoy more responsive auto-scaling, with a 5X improvement in responsiveness thanks to enhancements in our scaling algorithms and infrastructure. These enhancements are being rolled out to all Atlas customers, who should start seeing benefits immediately.</p><h3>MongoDB Copilot Participant for VS Code (Public Preview)</h3><p>Now in public preview, the new MongoDB Participant for GitHub Copilot integrates domain-specific AI capabilities directly with a chat-like experience in the <a href="https://www.mongodb.com/products/tools/vs-code">MongoDB Extension for VS Code</a>.</p><p>The participant is deeply integrated with the MongoDB extension, allowing for the generation of accurate MongoDB queries (and exporting them to application code), describing collection schemas, and answering questions with up-to-date access to MongoDB documentation without requiring the developer to leave their coding environment. These capabilities significantly reduce the need for context switching between domains, enabling developers to stay in their flow and focus on building innovative applications.</p><h3>Multicluster support for the MongoDB Enterprise Kubernetes Operator</h3><p>Ensure high availability, resilience, and scale for MongoDB deployments running in Kubernetes through added support for deploying MongoDB and Ops Manager across multiple Kubernetes clusters.</p><p>Users now have the ability to deploy ReplicaSets, Sharded Clusters (in public preview), and Ops Manager across local or geographically distributed Kubernetes clusters for greater deployment resilience, flexibility, and disaster recovery. This approach enables multi-site availability, resilience, and scalability within Kubernetes, capabilities that were previously only available outside of Kubernetes for MongoDB. To learn more, <a href="https://www.mongodb.com/docs/kubernetes-operator/v1.33/multi-cluster-deploy-replica-set/">check out the documentation</a>.</p><h3>MongoDB Atlas Search and Vector Search are now generally available via the Atlas CLI and Docker</h3><p>The local development experience for MongoDB Atlas is now generally available. Use the MongoDB Atlas CLI and Docker to build with MongoDB Atlas in your preferred local environment, and easily access features like Atlas Search and Atlas Vector Search throughout the entire software development lifecycle. The Atlas CLI provides a unified and familiar terminal-based interface that allows you to deploy and build with MongoDB Atlas in your preferred development environment, locally or in the cloud.</p><p>If you build with Docker, you can also now use Docker and Docker Compose to easily integrate Atlas in your local and continuous integration environments with the <a href="https://www.mongodb.com/products/tools/atlas-cli">Atlas CLI</a>. Avoid repetitive work by automating the lifecycle of your development and testing environments and focus on building application features with full-text search, AI and semantic search, and more.</p><h2>Simplifying AI innovation</h2><h3>Reduce costs and increase scale in Atlas Vector Search</h3><p>We announced vector quantization capabilities in <a href="https://www.mongodb.com/products/platform/atlas-vector-search">Atlas Vector Search</a>. By reducing memory (by up to 96%) and making vectors faster to retrieve, vector quantization allows customers to build a wide range of AI and search applications at higher scale and lower cost.</p><p>Generally available now, support for scalar quantized vector ingestion lets customers seamlessly import and work with quantized vectors from their embedding model providers of choice—directly in Atlas Vector Search. Coming soon, additional vector quantization features, including automatic quantization, will equip customers with a comprehensive toolset for building and optimizing large-scale AI and search applications in Atlas Vector Search.</p><h3>Additional integrations with popular AI frameworks</h3><p>Ship your next AI-powered project faster with MongoDB, no matter your framework or LLM of choice. AI technologies are advancing rapidly, making it important to build and scale performant applications quickly, and to use your preferred stack as your requirements and available technologies evolve.</p><p>MongoDB’s enhanced suite of integrations with LangChain, LlamaIndex, Microsoft Semantic Kernel, AutoGen, Haystack, Spring AI, the ChatGPT Retrieval Plugin, and more <a href="https://www.mongodb.com/docs/atlas/ai-integrations/">make it easier than ever to build the next generation of applications on MongoDB</a>.</p><h2>Advancing developer upskilling</h2><h3>New MongoDB Learning Badges</h3><p>Faster to achieve and more targeted than a certification, <a href="https://learn.mongodb.com/pages/learner-badges">MongoDB&#39;s free Learning Badges</a> show your commitment to continuous learning and to proving your knowledge about a specific topic. Follow the learning path, gain new skills, and get a digital badge to show off on LinkedIn.</p><p>Check out the two new gen AI learning badges!</p><ul><li><p><a href="https://learn.mongodb.com/learning-paths/building-genai-apps-learning-badge-path">Building gen AI Apps</a>: Learn to create innovative gen AI apps with Atlas Vector Search, including retrieval-augmented generation (RAG) apps.</p></li><li><p><a href="https://learn.mongodb.com/learning-paths/deploying-and-evaluating-genai-apps-learning-badge-path">Deploying and Evaluating gen AI Apps</a>: Take your apps from creation to full deployment, focusing on optimizing performance and evaluating results.</p></li></ul><h2>Learn more</h2><p>To learn more about MongoDB’s recent product announcements and updates, check out our <a href="https://www.mongodb.com/products/updates/">What’s New</a> product announcements page and all of our <a href="https://www.mongodb.com/company/blog">blog posts about product updates</a>. Happy building!</p>]]></description>
      <pubDate>Wed, 28 Oct 2026 01:04:18 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/product-release-announcements/mongodb-local-london-2024-better-applications-faster</link>
      <guid>https://www.mongodb.com/company/blog/product-release-announcements/mongodb-local-london-2024-better-applications-faster</guid>
    </item><item>
      <title>Getting Started With MongoDB and AWS CodeWhisperer</title>
      <description><![CDATA[<p></p><p>Amazon CodeWhisperer is trained on billions of lines of code and can generate code suggestions — ranging from snippets to full functions — in real-time, based on your comments and existing code. AI code assistants have revolutionized developers’ coding experience, but what sets Amazon CodeWhisperer apart is that MongoDB has collaborated with the AWS Data Science team, enhancing its capabilities!</p><p>At MongoDB, we are always looking to enhance the developer experience, and we&#39;ve fine-tuned the AWS CodeWhisperer Foundational Models to deliver top-notch code suggestions — trained on, and tailored for, MongoDB. This gives developers of all levels the best possible experience when using AWS CodeWhisperer for MongoDB functions.</p><p>This tutorial will help you get AWS CodeWhisperer up and running in VS Code, but CodeWhisperer also works with a number of other IDEs including AWS Cloud9, AWS Lambda console, JupyterLab, and Amazon SageMaker Studio. On the <a href="https://aws.amazon.com/codewhisperer/resources/#Getting_started">Amazon CodeWhisperer site</a>, you can find tutorials that demonstrate how to set up AWS CodeWhisperer on different IDEs, as well as other documentation.</p><p><em>Note:</em> Amazon CodeWhisperer allows users to start without an AWS account because, usually, creating an AWS account requires a credit card. Currently, CodeWhisperer is free for individual users. So it’s super easy to get up and running.</p><h2>Installing Amazon CodeWhisperer for VS Code</h2><p>CodeWhisperer doesn’t have its own VS Code extension. It is part of a larger extension for AWS services called AWS Toolkit. AWS Toolkit is available in the VS Code extensions store.</p><p>Step 1. Open VS Code and navigate to the extensions store (bottom icon on the left panel).</p><p>Step 2. Search for AWS CodeWhisperer, and it will show up as part of the AWS Toolkit.</p><p>Step 3. Once found, hit Install. Next, you’ll see the full AWS Toolkit Listing.</p><p>Step 4. Once installed, you’ll need to authorize Amazon CodeWhisperer via a Builder ID to connect to your AWS developer account (or set up a new account if you don’t already have one).</p><h2>Using AWS CodeWhisperer</h2><h3>Navigating code suggestions</h3><p>With Amazon CodeWhisperer installed and running, as you enter your prompt or code, CodeWhisperer will offer inline code suggestions. If you want to keep the suggestion, use TAB to accept it. AWS CodeWhisperer may provide multiple suggestions to choose from depending on your use case. To navigate between suggestions, use the left and right arrow keys to view them, and TAB to accept.</p><p>If you don’t like the suggestions you see, keep typing (or hit ESC). The suggestions will disappear, and Amazon CodeWhisperer will generate new ones at a later point based on the additional context.</p><p>Requesting suggestions manually</p><p>You can request suggestions at any time. Use Option-C on Mac or ALT-C on Windows. After you receive suggestions, use TAB to accept and the arrow keys to navigate.</p><p>Getting the best recommendations</p><p>For best results, follow these practices.</p><ul><li>Give Amazon CodeWhisperer something to work with. The more code your file contains, the more context CodeWhisperer has for generating recommendations.</li><li>Write descriptive comments in natural language — for example.</li></ul><p></p><p>Or</p><p></p><ul><li>Specify the libraries you prefer at the start of your file by using import statements.</li></ul><p></p><ul><li>Use descriptive names for variables and functions.</li><li>Break down complex tasks into simpler tasks.</li></ul><h2>Provide feedback</h2><p>As with all generative AI tools, they are forever learning and forever expanding their foundational knowledge base, and MongoDB is looking for feedback. If you are using Amazon CodeWhisperer in your MongoDB development, we’d love to hear from you.</p><p>We’ve created a special “codewhisperer” tag on our <a href="https://www.mongodb.com/community/forums/">Developer Forums</a>, and if you tag any post with this, it will be visible to our Amazon CodeWhisperer project team, and we will get right on it to help and provide feedback. If you want to see what others are doing with CodeWhisperer on our forums, the <a href="https://www.mongodb.com/community/forums/tag/codewhisperer">tag search link</a> will jump you straight into all the action.</p><p>We can’t wait to see your thoughts and impressions of MongoDB and Amazon CodeWhisperer together.</p>]]></description>
      <pubDate>Wed, 28 Oct 2026 00:58:19 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/technical/getting-started-with-mongodb-and-codewhisperer</link>
      <guid>https://www.mongodb.com/company/blog/technical/getting-started-with-mongodb-and-codewhisperer</guid>
    </item><item>
      <title>How MongoDB Fits into the EU Sovereign Cloud Ecosystem</title>
      <description><![CDATA[<p>The question of what the term “sovereign cloud” means in Europe has moved from policy debates to formal European Commission (EC) procurement frameworks and industrial investments. The <a href="https://commission.europa.eu/news-and-media/news/sovereign-cloud-framework-explained-2026-06-01_en">Cloud Sovereignty Framework (CSF)</a>, Sovereignty Effectiveness Assurance Levels (SEAL), and the developing <a href="https://www.enisa.europa.eu/publications/eucs-cloud-service-scheme">EU Cybersecurity Certification Scheme for Cloud Services (EUCS)</a> are separate initiatives that provide distinct reference points. Alongside strategic capital mobilization under the <a href="https://eur-lex.europa.eu/EN/legal-content/summary/strategic-technologies-for-europe-platform-step.html">Strategic Technologies for Europe Platform (STEP)</a>, they establish a clearer direction for critical cloud infrastructure. While specific to EU institutional tenders and funding programs rather than acting as universal mandates, this combined momentum offers IT leaders and enterprise architects across regulated sectors a concrete reference point for how sovereignty criteria shape long-term architectural thinking. These developments help illustrate that operating in a regulated market does not mean every workload must remain on-premises; instead, they demonstrate that sovereignty is a spectrum, helping organizations evaluate the specific level of data control their architecture truly requires. </p><p>As organizations evaluate these models, the critical question is not just which infrastructure provider can meet tech sovereignty expectations, but whether the rest of the technology stack upholds that sovereignty posture once workloads are deployed. This is where the database layer becomes a critical consideration, and where MongoDB provides key capabilities to define who has operational custody of data and how seamlessly workloads adapt to evolving governance requirements.</p><p>In April 2026, the European Commission awarded sovereign-cloud contracts under the <a href="https://commission.europa.eu/news-and-media/news/commission-launches-new-procurement-process-cloud-services-2024-02-07_en">Cloud III Dynamic Purchasing System</a> and used SEAL-2 and SEAL-3 as practical reference points in its <a href="https://commission.europa.eu/document/download/09579818-64a6-4dd5-9577-446ab6219113_en">CSF</a> for that procurement. This provides a concrete example of how sovereignty-related criteria can be evaluated in an EC-level procurement context. It also raises a practical architectural question: if sovereign-cloud requirements are being evaluated against the CSF as a benchmark, what does that mean for the rest of the technology stack, and especially for the database tier?</p><p>This overview examines the potential implications of the awarded landscape, the operational relevance of SEAL-2 and SEAL-3*, and how MongoDB deployment models can support different architectural approaches for organizations to evaluate against their own requirements.</p><h2>Why the new procurement benchmark matters</h2><p>The Commission selected several European provider groups for this initiative. These included:</p><ol><li><p><strong>Post Telecom</strong> (headquartered in Luxembourg), working alongside OVHcloud and CleverCloud (both based in France).</p></li><li><p><strong>STACKIT</strong>, the cloud division of Schwarz Group, based in Germany.</p></li><li><p><strong>Scaleway</strong>, the cloud arm of Iliad Group, based in France.</p></li><li><p><strong>Proximus</strong>, based in Belgium, partnered with S3NS (a joint venture of Thales and Google Cloud in France), Clarence (Luxembourg), and Mistral (France).</p></li></ol><p>As published in the <a href="https://ec.europa.eu/commission/presscorner/detail/en/ip_26_833">European Commission’s report under reference IP/26/833</a>, three of the four awarded groups achieved the reported assessment level of SEAL-3, while the Proximus consortium attained SEAL-2. The Proximus result of SEAL-2 is an assessed level within the CSF, not a failed outcome; the consortium’s remaining non-EU dependencies distinguished it from the groups assessed at SEAL-3. Together, these results show that the procurement considered a range of sovereignty postures rather than a simple pass-or-fail threshold, and may help inform future market expectations around sovereignty-driven infrastructure and digital resilience.</p><p>In environments governed by frameworks such as the General Data Protection Regulation (GDPR), the Digital Operational Resilience Act (DORA), and the Network and Information Systems Directive 2 (NIS2), where requirements vary by organization and industry, engineering teams face concrete design priorities: mitigating ICT third-party concentration risk, establishing tested exit strategies, or enforcing granular boundaries over data access and telemetry. The CSF evaluation offers technical leaders a reference point for examining these operational dependencies, informing technical due diligence across database tiers and multi-cloud strategies without prescribing a single deployment model or replacing organization-specific legal analysis.</p><h2>The challenge: infrastructure certification does not cover the full stack</h2><p>Using cloud infrastructure assessed in the European Commission’s procurement event addresses only part of the broader sovereignty discussion and does not automatically answer questions about every layer of the technology stack. The relevant considerations can include data residency, service operation, metadata flows, external control-plane dependencies, encryption, access controls, and workload portability if requirements or risk posture change.</p><p>The database tier is particularly important in a broader data-sovereignty assessment because it stores, processes, and governs access to the data itself. An infrastructure-focused assessment such as the CSF evaluation can provide useful information about the underlying cloud environment, but it does not by itself characterize the database service’s data paths, plaintext exposure, key management, backups, logs and metadata, support and control-plane dependencies, or workload portability. </p><p>Regulatory frameworks such as the US CLOUD Act (Clarifying Lawful Overseas Use of Data Act, enacted in 2018) have heightened enterprise sovereignty concerns over access to data held by providers subject to foreign jurisdiction under applicable legal processes, illustrating why physical data residency alone does not establish operational or jurisdictional control. One practical question is therefore not whether a platform carries a universal “sovereignty” label, but which controls and operating boundaries an organization must evaluate for its own environment. Variables such as control-plane dependencies, cross-region support access, cloud provider corporate jurisdiction, and cryptographic key custody must be individually assessed based on the organization&#39;s unique requirements. An organization may adopt cloud infrastructure aligned with SEAL-3 expectations and still find that database-layer telemetry, external support paths, or unencrypted metadata introduce unintended exposures. The infrastructure assessment and the database governance posture remain separate engineering challenges that require independent validation.</p><h2>MongoDB&#39;s three roles in the European sovereign cloud ecosystem</h2><p>MongoDB serves three distinct roles in the European sovereign cloud ecosystem when viewed through the lens of the European Commission’s CSF. MongoDB’s flexible document model and query API can remain consistent across deployment models, while the operating model, responsibilities, data flows, access controls, and contractual arrangements may differ.</p><p><strong>Figure 1. </strong>MongoDB deployment modes.</p><h3>Role one: DBaaS on SEAL-3 sovereign clouds</h3><p>In this model, a European cloud provider—such as STACKIT, OVHcloud, or Scaleway—operates a MongoDB database service under its own brand, infrastructure, and legal entity. MongoDB supplies the database engine, compatibility guarantees, and technical support framework, while responsibility for operating the service remains with the European provider.</p><p>Because the European provider operates the service, it is the entity with operational custody of customer data in this model. MongoDB is a software supplier and does not have operational custody of customer data on the European-operated service. All three provider groups that achieved SEAL 3 for the purposes of the April 2026 EC procurement event include a <a href="https://www.mongodb.com/company/partners/certified-by-mongodb-dbaas-program">MongoDB Certified DBaaS partner</a>. For organizations seeking sovereign cloud environments aligned with SEAL-3-style expectations, MongoDB is already available through those partnerships, without workarounds, unsupported deployments, or vendor substitution.</p><p>However, architecture teams must carefully evaluate the specific database edition offered by each sovereign cloud provider. Managed offerings in the European ecosystem typically fall into two categories: DBaaS based on <a href="https://www.mongodb.com/try/download/community-kubernetes-operator">MongoDB Community Server</a> and DBaaS powered by MongoDB Enterprise Server, which is the engine underlying <a href="https://www.mongodb.com/products/self-managed/enterprise-advanced">Enterprise Advanced</a>. While both editions share the same flexible document model and core query API, they differ significantly in built-in operational capabilities. Community Server provides core database functionality, but achieving enterprise-grade security and operational maturity requires teams to build and manage custom configurations for auditing, access controls, and maintenance. In contrast, DBaaS powered by Enterprise Server delivers turnkey features, including native enterprise auditing, advanced authentication integration, and enhanced operational tooling, representing the closest functional equivalent to MongoDB Atlas in a self-contained or sovereign environment. </p><p>Availability of these editions varies across the European market. Currently, European providers like <a href="https://stackit.com/en/products/database/stackit-mongodb-flex">STACKIT</a> and <a href="https://www.ovhcloud.com/es-es/public-cloud/mongodb/">OVHcloud</a>, alongside providers like <a href="https://cloud.ionos.es/managed/dbaas/mongodb">IONOS</a>, offer DBaaS backed by Enterprise Server, whereas <a href="https://www.scaleway.com/en/managed-mongodb/">Scaleway</a> provides managed Community Server with enterprise-grade offerings currently in development. Selecting the appropriate provider therefore depends on whether a given workload requires these out-of-the-box enterprise capabilities or can be supported through community-tier deployments. </p><h3>Role two: MongoDB Atlas with sovereignty controls</h3><p>MongoDB Atlas is a multi-cloud intelligent data platform with availability across Amazon Web Services (AWS), Microsoft Azure, and Google Cloud Platform (GCP). Atlas provides data placement controls; Resource Policies can restrict cluster creation to approved EU regions, and zone-based sharding can support regional data placement, subject to the workload’s shard key and application design.</p><p>For encryption, MongoDB Atlas supports Bring Your Own Key (BYOK) integration with cloud provider key management services, which can keep encryption keys outside MongoDB’s direct control. Atlas also supports Client-Side Field Level Encryption (CSFLE) and Queryable Encryption (QE), which encrypt sensitive fields on the client side before data reaches the database. MongoDB cannot access plaintext for those protected fields during supported query operations.</p><p>BYOK, CSFLE, and Queryable Encryption (QE) can materially reduce data-layer disclosure risks by preventing unauthorized or platform-level access to plaintext data. However, the effective protection boundary depends on the key-management model, query capabilities, and whether sensitive metadata remains exposed.</p><p>Certified DBaaS and Enterprise Advanced are alternative deployment models to evaluate for workloads where data sovereignty and encryption considerations are material. The appropriate choice depends on the organization’s technical, contractual, operational, and legal requirements.</p><h3>Role three: MongoDB Enterprise Advanced for maximum jurisdictional control</h3><p><a href="https://www.mongodb.com/products/self-managed/enterprise-advanced">MongoDB Enterprise Advanced (EA)</a> is a commercial subscription that grants organizations the right to run MongoDB on their own infrastructure: on-premises, in a private cloud, on a sovereign provider’s dedicated environment, or in an air-gapped facility. MongoDB does not operate the customer’s clusters and, in this model, does not have operational custody of customer data at rest.</p><p>The infrastructure operator remains responsible for the environment in which the clusters run. How access to customer data and any legal or regulatory request would be handled depends on the applicable law, contractual arrangements, and the specific operating model; the relevant custody and control analysis therefore focuses on the entity operating that infrastructure rather than treating MongoDB as the infrastructure operator.</p><p>Enterprise Advanced preserves the same document model and core query semantics as MongoDB Atlas, supporting strong application-level portability across deployment models. Organizations can typically move regulated workloads from Atlas to EA while preserving the application data layer and most core query logic, which can reduce redesign effort and support portability, exit planning, and concentration-risk evaluation. The relevance of these capabilities to any particular regulatory framework depends on the organization’s specific requirements and legal and operational analysis.</p><h2>Aligning the deployment model to your sovereignty requirements</h2><p>The three MongoDB deployment models offer different combinations of deployment location, operational control, data access, encryption, and portability, which organizations can evaluate against their own data or technology sovereignty-related requirements.</p><p>For organizations evaluating technical, contractual, operational, or procurement requirements associated with SEAL-3-style sovereign infrastructure, the Certified Database as a Service (DBaaS) path provides MongoDB capability through a European provider, previously assessed at SEAL-3 in the Commission’s April 2026 procurement. </p><p>For organizations evaluating a US-operated managed cloud service with technical controls, MongoDB Atlas with Bring Your Own Key (BYOK), Client-Side Field Level Encryption (CSFLE), and Queryable Encryption (QE) can provide data-layer protections relevant to that assessment. </p><p>For organizations evaluating greater direct jurisdictional control, air-gapped operation, or self-managed deployment on sovereign or private cloud infrastructure, Enterprise Advanced preserves the same core document model and query semantics as Atlas and supports application portability without requiring MongoDB to operate the customer’s clusters. Depending on the deployment environment, it can also support customer-managed infrastructure and avoid dependency on a public cloud service, with no MongoDB operational custody of customer data at rest.</p><p>A practical advantage is that these three models are not mutually exclusive. An enterprise may evaluate a mixed deployment approach, such as using Atlas for standard workloads in EU-approved regions, Certified DBaaS for higher-sensitivity workloads, and Enterprise Advanced for classified or air-gapped workloads, while application-layer portability and governance requirements may vary by tier. </p><h2>Final thoughts</h2><p>Europe’s sovereign cloud ecosystem now includes an example of a formal assessment used in the European Commission’s procurement, four Commission-selected reference providers, and other national frameworks applicable in specific member states. These developments may be relevant to how regulated organizations evaluate cloud infrastructure over the coming years.</p><p>MongoDB is present at the database tier through Certified DBaaS partnerships with providers that have been assessed at SEAL-3 in the Commission’s April 2026 procurement, available with technical controls on managed cloud through MongoDB Atlas, and deployable in customer-managed environments through Enterprise Advanced. Each deployment model presents different technical, contractual, and operational characteristics for organizations to evaluate against their own requirements. Each preserves the same core document model and query semantics, which may help reduce redesign effort when moving workloads across deployment models.</p><p>*Within the CSF, the SEAL levels range from SEAL-0 to SEAL-4 and describe varying degrees of EU jurisdiction and control over legal, operational, and supply-chain dependencies. At SEAL-2 (Data Sovereignty), EU law is enforceable, though some material non-EU dependencies persist. SEAL-3 (Digital Resilience), assesses whether relevant non-EU dependencies have been reduced to marginal levels under the CSF. SEAL-4 (Full Digital Sovereignty), represents the theoretical goal of complete EU control without critical dependencies on non-EU entities, a standard no provider has reached so far. These descriptions refer to the CSF framework and the assessment made in the Commission’s procurement context; they do not prescribe what any particular organization must do.</p><h3><em>Disclaimer </em></h3><p><em>This content is for informational purposes only and does not constitute legal advice. Regulatory requirements vary by jurisdiction and industry. Organizations should consult qualified legal counsel and their internal compliance teams to understand their specific obligations.</em></p>]]></description>
      <pubDate>Tue, 27 Oct 2026 14:00:01 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/how-mongodb-fits-into-eu-sovereign-cloud-ecosystem</link>
      <guid>https://www.mongodb.com/company/blog/innovation/how-mongodb-fits-into-eu-sovereign-cloud-ecosystem</guid>
    </item><item>
      <title>Give Deep Agents a Searchable Filesystem on MongoDB Atlas</title>
      <description><![CDATA[<p>Many of the agent demos published this year are some version of the same thing: connect your agent to a data source, let it get familiar with the data, and get a report back.</p><p>We’ll build a coordinator agent and three sub-agents that search a roughly 2,900-page federal rulemaking docket, write their findings to a shared workspace, and hand off to a fourth agent that reconciles the findings into a memo. You&#39;ll interrupt the pipeline mid-run, restart it, and confirm it resumes from the last completed stage instead of redoing finished work.</p><p><strong>Working through it cost us $2 to $5 in API calls and took about 45 minutes.</strong></p><p>Specifically, you will:</p><ul><li><p>Load a mixed-format document corpus into Amazon Simple Storage Service (S3) and index it in MongoDB Atlas.</p></li><li><p>Watch an agent navigate that corpus incrementally instead of loading it into a prompt.</p></li><li><p>Build a coordinator that delegates to three sub-agents sharing one workspace.</p></li><li><p>Interrupt a running pipeline and resume it from saved run state, without redoing completed work.</p></li></ul><p>This tutorial moves from architecture (what&#39;s searched vs. what&#39;s stored in bytes), to a single-agent search example, to a four-agent pipeline, to failure recovery, to production caveats.</p><p>The complete code and corpus are in the <a href="https://github.com/mongodb-developer/GenAI-Showcase/tree/main/partners/langchain/langchain-deepagents">companion repository</a> (GenAI-Showcase, partners/langchain/langchain-deepagents).</p><h2>What is a virtual filesystem?</h2><p>A virtual filesystem is a path-based interface that abstracts away where file bytes actually live. An agent sees a path such as <em>corpus/rules/88FR21752-final-rule.pdf</em>, but the underlying bytes might sit in object storage, a database, or a LangGraph store. The agent calls the same <em>ls</em>, <em>glob</em>, <em>grep</em>, read, write, and edit operations no matter what&#39;s underneath; the configured backend decides where each call actually goes.</p><p>That abstraction is what lets an agent work incrementally: list a directory, narrow by filename pattern, search for a concept, read one file, write a finding — without ever loading the whole corpus into its context window.</p><h2>Background</h2><h3>What are LangChain Deep Agents?</h3><p><a href="https://github.com/langchain-ai/deepagents">LangChain Deep Agents</a> is an agent harness built on LangChain and LangGraph for complex, multi-step work. It adds planning, sub-agents, and filesystem-oriented tools, so an agent can break a large task into smaller actions rather than solving everything within a single context window.</p><p>A Deep Agent works through a small set of filesystem operations: ls for directory structure, glob to find files by path pattern, grep to search content, read to retrieve a file, write and edit to create or modify artifacts. Those tools are exposed through a backend contract, so the agent never knows whether files live on local disk, in a LangGraph store, or in object storage. It calls the same interface, and the configured backend supplies the data.</p><h3>What the MongoDB VFS backend does</h3><p>The <em>langchain-mongodb-deepagents-vfs</em> package implements that contract. It lives in the LangChain monorepo at <a href="https://github.com/langchain-ai/langchain-mongodb/tree/main/libs/langchain-mongodb-deepagents-vfs">langchain-ai/langchain-mongodb/libs/langchain-mongodb-deepagents-vfs</a>, and is co-maintained by LangChain and MongoDB. It presents an object-store-backed corpus to the agent as a filesystem, and routes each operation to the system built for it:</p><p>That separates the source of truth from the search index. Object storage is built for durable, low-cost storage of file bytes; it is not built to maintain live indexes or rank hybrid queries. Atlas is an operational database with built-in Search, Vector Search, and hybrid ranking.</p><p>Keeping ranking in the database also removes a client-side reranking round trip: <em>$rankFusion</em> combines the full-text and vector result sets natively, in one query, on the database side.</p><p><strong>Figure 1.</strong> How the LangChain Deep Agents VFS backend routes file bytes through object storage and search operations through MongoDB Atlas.</p><p>An object watcher keeps the Atlas representation aligned with the bucket. For the full design rationale, see the <a href="https://www.mongodb.com/company/blog/technical/vfs-langchain-deep-agents-searchable-filesystem-agents">MongoDB VFS announcement post</a>, which explains how the backend separates storage and search.</p><h2>Prerequisites</h2><ol><li><strong></strong><a href="https://www.mongodb.com/cloud/atlas/register">A MongoDB Atlas cluster</a> running <strong>8.1 or later</strong>. <em>$rankFusion</em> requires it. An M0 cluster works for development; MongoDB Search and Vector Search require an M10 or higher cluster for production workloads.</li><li>Your IP address in the project&#39;s <a href="https://www.mongodb.com/docs/atlas/security/ip-access-list/">Network Access list</a>, and a database user with read and write access.</li><li>An AWS account with an S3 bucket, and an IAM policy granting <em>s3:GetObject</em>, <em>s3:PutObject</em>, <em>s3:DeleteObject</em>, and <em>s3:ListBucket</em> on both arn:aws:s3:::&lt;bucket&gt; and arn:aws:s3:::&lt;bucket&gt;/*. If you use Bedrock embeddings, also grant <em>bedrock:InvokeModel</em> for <em>amazon.titan-embed-text-v2:0</em>. If you switch to the SQS watcher, also grant <em>sqs:ReceiveMessage</em> and <em>sqs:DeleteMessage</em> on the queue.</li><li>An embedding provider. Amazon Bedrock is the default and uses the <em>boto3</em> credential chain. To use OpenAI instead, install the <em>[openai]</em> extra, set <em>EMBEDDING_PROVIDER</em>=openai, and set <em>OPENAI_API_KEY</em> from the <a href="https://platform.openai.com/api-keys">OpenAI API keys page</a>.</li><li>An API key for the model that drives the agents.</li><li>Python 3.11 or later.</li></ol><p>This tutorial is written against <em>langchain-mongodb-deepagents-vfs</em> 0.1.0, released 25 August 2026 and still the only release, and <em>langgraph-store-mongodb</em> 0.4.0 if you run the <em>StoreBackend</em> comparison in the hybrid search section.</p><h2>Set up the environment</h2><h3>1. Install the packages</h3><h3>2. Load the corpus</h3><p>The corpus is a United States Department of Energy rulemaking: <a href="https://www.regulations.gov/docket/EERE-2021-BT-STD-0035">docket EERE-2021-BT-STD-0035 on regulations.gov</a>, the first federal efficiency standards for room air cleaners. The <a href="https://www.federalregister.gov/documents/2023/04/11/2023-06499/energy-conservation-program-energy-conservation-standards-for-air-cleaners">final rule in the Federal Register</a> was published at 88 FR 21752 in April 2023.</p><p>The final rule and DOE&#39;s own analysis documents are works of the United States government. The comment letters were filed by third parties into a public federal docket and are redistributed here on that basis. The files are committed to the companion repository rather than fetched at runtime, so you need no regulations.gov API key to follow along.</p><p>It runs to roughly 2,900 pages across 45 files, in three directories. <em>corpus/rules/</em> holds five: the final rule as both PDF and XML, the simultaneous NOPR in both formats, and a confirmation-of-dates notice. <em>corpus/analysis/</em> holds fifteen: the technical support document, five analysis documents committed as <em>.htm</em> and <em>.pdf</em> pairs, and four macro-enabled spreadsheets (<em>lcc.xlsm</em>, <em>nia.xlsm</em>, <em>grim-joint.xlsm</em>, <em>grim-dfr.xlsm</em>). <em>corpus/comments/</em> holds twenty-five attachments from manufacturers, California utilities, efficiency advocates, and trade associations. By extension that is 32 PDFs, 5 HTML files, 4 <em>.xlsm</em> and 1 <em>.xlsx</em> spreadsheet, 2 XML files, and 1 Word document. Several of the comment letters are Word or PDF files whose body text reads, in full, &quot;please see attached.&quot;</p><p>A word on formats before you seed. The package documents parsers for <em>.txt</em>, <em>.md</em>, <em>.rst</em>, .<em>csv</em>, <em>.pdf</em>, <em>.docx</em>, <em>.xlsx</em>, <em>.xls</em>, <em>.pptx</em>, and <em>.ppt</em>. This corpus goes past that list: the five analysis documents are committed as .htm alongside their PDFs, the final rule and NOPR carry <em>.xml</em> versions, and the four analysis workbooks are macro-enabled <em>.xlsm</em> rather than <em>.xlsx</em>. In the run shown throughout this tutorial, hybrid <em>grep</em> returned ranked matches from the <em>.htm</em> files with real line numbers, so those reached the index. Whatever you point this at, treat the format list as the documented floor rather than the full set, and check <em>initial_sync_report</em><em>.failed</em> against your own file count before you trust a search that comes back empty.</p><p>Or use the seeder script, which writes through the backend so MongoDB metadata is created alongside the S3 objects:</p><p>If you use aws s3 sync instead, the backend&#39;s background watcher will index the files on its next polling interval.</p><h3>3. Set your connection string</h3><p>Copy the driver connection string from Atlas. It looks something like this:</p><p>Change the <em>appName</em> before you use it:</p><p>Atlas fills that parameter with your cluster name so its own connection metrics have a label. Replace it rather than adding a second one; the driver keeps the last value it parses. If your string also carries <em>retryWrites</em> or <em>w=majority</em>, leave those alone — they are connection options, not labels.</p><p>If your password contains <em>: / ? # [ ] @</em> or a <em>%</em> sign, those characters have to be percent-encoded, or the driver misreads the URI and reports an authentication failure that has nothing to do with your password being wrong.</p><h3>4. Create the backend and the agent</h3><p>Point the backend at a bucket and a cluster, hand it to the agent, and the agent has a filesystem:</p><p>s<em>3_prefix</em> is doing real work in that call. It defaults to &quot;mongodb_vfs/&quot; and restricts every operation, including read, write, edit, sync, and watch, to keys under that prefix. Setting it to &quot;<em>corpus/</em>&quot; scopes this backend to the docket and nothing else in the bucket. Passing an empty string opts into whole-bucket access, which you rarely want in a shared bucket.</p><p><em>debug=True</em> changes how failures reach you: methods raise <em>AdapterError</em> instead of returning error DTOs. That catches real bugs. It also turns an expected miss into an exception, so reading a manifest on a fresh run raises instead of returning None. Wrap those reads in try/except <em>AdapterError</em>.</p><p>There are no custom MongoDB tools in the reasoning loop, and no retrieval chain. The agent calls <em>grep</em> and read the way it would against a local directory, and the backend decides where each call goes.</p><h3>5. Verify the initial sync</h3><p>The constructor returns immediately, whereas index provisioning, the initial sync, and watcher startup run on a background thread. Your first <em>grep</em> blocks until it finishes, so it takes noticeably longer than every subsequent call. On this corpus it took us 5 to 8 seconds.</p><p><strong>Checkpoint — what you should see: </strong><em>init_errors</em> is empty and <em>initial_sync_report</em>.failed is 0 before you move on. If either assertion fails, do not continue to the discovery step; the corpus isn&#39;t fully searchable yet.</p><p>Do not skip this check. Three conditions degrade search without producing an error: pointing at a non-Atlas MongoDB drops <em>grep</em> to a regex query, losing the embedding API drops it to full-text only, and a partially failed sync leaves a collection that looks healthy while missing documents. <em>init_errors</em> and <em>initial_sync_report</em> catch all three.</p><p>The readiness gate has one subtlety. It releases between the sync stage and the watcher start, so a search that returns guarantees the index and sync stages finished, but a watcher-start failure is recorded a moment later and can be missed by a check made immediately after that first <em>grep</em><em>. </em><em>initial_sync_report</em> is also None outright when the sync raises rather than completing with failures, which is why the assertion tests report before report.failed.</p><h2>How the agent searches a mixed-format corpus</h2><p>Ask it something that requires finding a needle in the docket:</p><p>Every number in this tutorial comes from a single run against one cluster and one corpus. They show the shape of the thing. Your region, cluster tier, corpus, and model will move them. If you want your own figures, <em>src/vfs_demo/metrics.py</em> tracks tokens, wall clock, and cost per stage, and its <em>compare_runs</em>() prints a cold-versus-resumed table.</p><p>Four calls before it reads a single document, and each one narrows the next. The agent never holds the corpus — it holds a directory listing, a filtered path list, a ranked set of chunks with line numbers, and one PDF.</p><p><strong>Figure 2.</strong> Each step narrows before the next one pulls bytes, which is what keeps a 2,900-page corpus inside a context window.</p><p>The discovery step calls the backend directly, so no LLM tokens are consumed. Across the three runs above, each hybrid grep came back in under two seconds, and the ranking stayed stable.</p><h2>Hybrid search reaches vocabularies and formats ripgrep cannot</h2><p>That <em>grep</em> worked because the parties in this docket do not share vocabulary. State standards and ENERGY STAR measure smoke CADR per watt. DOE measures PM2.5 CADR per watt through an integrated efficiency factor. Both describe the same physical quantity — how much clean air you get per unit of power — and the rule spends pages establishing that they are not interchangeable.</p><p>Compare against ripgrep over the same files on the local disk:</p><p>Most of these file types are not text, so <em>grep</em> cannot open them at all. Even if you extract the text first, literal matching still misses every passage that says &quot;smoke CADR&quot; when you searched for &quot;IEF.&quot;</p><p>Here is how using <em>StoreBackend</em> over <em>MongoDBStore</em>, which implements the same protocol, works today:</p><p>The limitation here is in <em>StoreBackend</em> rather than in <em>MongoDBStore</em>, which can do vector search. <em>StoreBackend</em>&#39;s <em>grep</em> never calls it that way; it fetches every item in the namespace and matches literal substrings in Python. <em>StoreBackend</em> is what the package guarantees for use as an agent scratchpad for small, agent-authored files; it is not built for a large, pre-existing, document-heavy corpus. The VFS backend in this tutorial is built for the latter.</p><p>This is not a result of vector search beating keyword search. <em>$rankFusion</em> runs both at equal weight, and lexical retrieval is strong for agentic search. The hybrid index adds two things a ranker cannot: parsing, because a spreadsheet is not a text file, and coverage across parties who describe one measurement four different ways.</p><h2>How to coordinate sub-agents over a shared corpus</h2><p>The single agent answered one question. Working out whether DOE adopted the coalition&#39;s proposal takes three separate lines of inquiry, reconciled at the end.</p><p>In this rulemaking, the manufacturers and the environmental advocates filed together. AHAM, ACEEE, ASAP, CFA, and NRDC submitted a joint consensus proposal with specific efficiency levels in it. The question is whether DOE adopted them.</p><p>Give each sub-agent one question and one output path. The shape below is trimmed for readability; the real definitions add typed permissions, shown after the figure:</p><p>The read-only corpus is enforced rather than merely requested. Each reader carries permission rules, evaluated in declaration order with first match winning:</p><p>The trailing deny matters: Deep Agents allows a call when no rule matches, so without that last rule a reader could write anywhere. The writer is scoped tighter still: read and write on <em>/workspace/**</em>, no corpus access at all. That is what stops it grepping for findings instead of reading them by path.</p><p>The prompts above are trimmed for readability. The production versions in <em>src/vfs_demo/agents.py</em> are much more prescriptive, and that difference is what makes the pipeline find things. Each reader gets five starter <em>grep</em> queries with varied vocabulary and is told to run at least five before concluding something is absent. The prompt explains that <em>grep</em> here does hybrid semantic search rather than literal matching, and gives short two-to-six word phrases as the good case (&quot;IEF&quot;, &quot;CADR per watt&quot;, &quot;energy savings quads&quot;) against full questions as the bad case. output_mode=&quot;content&quot; is required so the agent sees matching text instead of filenames. <em>read_file</em> must always carry offset and limit, a window of thirty to fifty lines around the match, because a PDF or spreadsheet&#39;s extracted text can be large enough to error. And each reader is told in capitals to call <em>write_file</em> even when it found nothing, writing NOT FOUND along with what it searched for.</p><p>Keep the leading slash on that path. <em>CompositeBackend</em> routes are keyed on &quot;<em>/corpus/</em>&quot;, so a relative &quot;<em>corpus/</em>&quot; would miss the route and fall through to the workspace backend. On a bare <em>MongoFilesystemBackend</em> the leading slash is a known bug, and the reason it is safe here is the wrapper shown in the next section. Common problems covers what it looks like when this goes wrong.</p><p>The SHARED prompt tells readers to write NOT FOUND and say what they searched for, which is the right discipline. It does not catch a mistyped path, because an empty <em>grep</em> result looks identical whether the corpus was searched or the path selected nothing. Common problems has the detail.</p><h2>The corpus and the workspace need different guarantees</h2><p>The backend above is not the same object as the corpus. The readers write their findings somewhere, and that destination needs a different guarantee from the corpus.</p><p>Search on this backend is eventually consistent by design. A write reaches S3 immediately; the polling watcher then notices the object at 10-second intervals, re-chunks it, re-embeds it, and updates the index. That is exactly right for the docket, which nobody is editing. It is exactly wrong for a findings file. The writer needs that file two seconds after a reader produces it, which is run state rather than memory.</p><p>So the writer must read the findings by exact path, never <em>grep</em> for them. If it greps, the pipeline fails intermittently: the files are in S3, but the index has not caught up, so the writer finds nothing. When readers run slowly, the watcher wins the race, and everything works, which is worse than failing outright, because it passes testing and produces confident, empty reports later.</p><p>So split the two by prefix and give the agent one filesystem over both:</p><p><em>CompositeBackend</em> routes by path prefix, so the agents see one filesystem while two sets of guarantees run underneath. Discovery happens in <em>corpus/</em> with <em>grep</em>. Coordination happens in <em>workspace/&lt;run_id&gt;/</em> by exact path, and each reader writes only to its own file, so there are no collisions.</p><p>Two things about this pairing are not optional. <em>CompositeBackend</em> strips the route prefix before passing a path to the routed backend, so an agent reading <em>/corpus/analysis/tsd.pdf</em> reaches the corpus backend as /analysis/tsd<em>.pdf</em>. <em>MongoFilesystemBackend</em> stores paths including its <em>s3_prefix</em> and rejects anything that does not start with it, so reads fail with <em>E2009</em> and <em>grep</em> returns zero matches. You need a wrapper that re-adds the prefix on the way in and strips it from <em>grep</em> results on the way out.</p><p>The second is lifecycle. <em>CompositeBackend</em> is not a context manager, but the <em>MongoFilesystemBackend</em> instances underneath it are, starting and stopping their change-stream watchers in __enter__ and __exit__. The composite has to be yielded from inside a with block that enters both.</p><p>Here is the wrapper, from <em>src/vfs_demo/backend.py</em> in the companion repository. Both planes use it:</p><p>And the construction, which enters both backends before yielding the composite:</p><p><strong>Use it as a context manager: </strong>with <em>create_backend</em>() as backend. Both <em>MongoFilesystemBackend</em> instances start and stop their watchers in __enter__ and __exit__. <em>CompositeBackend</em> is not a context manager, so the composite gets yielded from inside the with block rather than constructed and returned.</p><p>One thing to set before you run this: <em>create_backend</em>() reads <em>AWS_REGION</em> and falls back to &quot;us-east-1&quot;. The package on its own would raise <em>NoRegionError</em> when no region resolves, and the hardcoded fallback removes that signal. If your bucket lives elsewhere, set <em>AWS_REGION</em> explicitly.</p><p><strong>Figure 4.</strong> The corpus is searched; the workspace never is. Both live in the same bucket and cluster, separated by prefix.</p><p>Run it:</p><p>That finding is in no single file. It needs the coalition proposal, the final rule, and the national impact spreadsheet, written by different parties in different formats.</p><h2>Recover an interrupted run</h2><p>The coordinator keeps a <em>manifest.json</em> at <em>workspace/&lt;run_id&gt;/manifest.json</em>. It is a run receipt, and the schema is deliberate about what a resumed run needs to know: <em>run_id</em>, the question, woke_up_by (what triggered this run), inherited_state (what was already in the workspace at startup), authority (corpus read-only, workspace read-write), a stages list, and evidence. This is run state: it exists so this run can resume, and future runs never read it.</p><p>Each stage carries name, status (pending, in_progress, complete, or failed), output path, tokens, usd, started_at, completed_at, and error. Resume works by reading the manifest and skipping any stage whose status is complete:</p><p><em>load_manifest</em><em>()</em> catches <em>AdapterError</em> and returns None, because with <em>debug=True</em> a read of a manifest that does not exist yet raises rather than returning an empty result. This is the expected-not-found case from the setup section. The first run of any new <em>run_id</em> takes that path.</p><p>The first command sends SIGKILL after two of four stages. The second restarts with the same run ID. The coordinator lists the workspace, reads the manifest, finds two completed findings, and starts at the third reader.</p><p><strong>Figure 5.</strong> The manifest records which stages completed, so the resumed run starts at stage three.</p><p>On the run shown here, the cold pipeline took about 90 seconds of wall clock and the resumed one about 55 seconds for its two remaining stages. What the resume skipped was two reader stages, roughly 45 seconds of agent time and the API calls that went with them.</p><p>The same principle runs one layer down. ETags make ingestion idempotent, so restarting the backend after a partial sync failure skips unchanged objects rather than re-downloading and re-embedding them.</p><h2>Common problems</h2><p>Most failures in this stack are quiet. The pattern to watch for is an agent that reports an empty corpus or writes a confident NOT FOUND, because almost every misconfiguration below surfaces that way rather than as an exception.</p><p><strong>grep, ls, and glob return nothing, and the agent says the corpus is empty</strong></p><p>Four different causes produce this same symptom, in roughly the order worth checking.</p><ul><li><p><strong>The initial sync has not finished or partially failed. </strong>Check <em>init_errors</em> and <em>initial_sync_report</em>.failed. A partially failed sync leaves a collection that looks healthy while missing documents.</p></li><li><p><strong>The wrapper is missing. </strong>If you are routing through <em>CompositeBackend</em> without a path-normalizing subclass, the routed backend receives a path stripped of its <em>s3_prefix</em> and rejects it. Reads fail with <em>E2009</em> and <em>grep</em> returns zero matches.</p></li><li><p><strong>A leading slash on a bare backend. </strong>Deep Agents&#39; file tools pass absolute paths. <em>SearchRouter</em> builds a ^ regex against <em>source_path</em> and stored keys are relative, so ^<em>/corpus/</em> matches nothing. Pull request #460 against langchain-ai/langchain-mongodb (INTPYTHON-1101) fixes this and is still open, so it is not in 0.1.0. The wrapper in this tutorial absorbs it with path.lstrip(&quot;/&quot;).</p></li><li><p><strong>The path selects no indexed files. </strong>A mistyped or non-existent path returns error None and matches [], exactly like a genuine no-match. See below.</p></li></ul><h3>An empty result that should have been an error (issue #462)</h3><p><em>grep</em>() returns the same thing whether it searched indexed files and found nothing, or the requested path selected no indexed files at all. Both give error None and matches []. In a multi-agent pipeline this compounds: a reader given a bad path writes NOT FOUND, and the writer reconciles that as a verified finding.</p><p>Until <em>GrepResult</em>.error carries a path-scope message, the cheap defense is to assert that <em>ls</em>(&quot;<em>/corpus/</em>&quot;) is non-empty before the readers run, and to treat any all-NOT-FOUND result as a configuration failure rather than a research finding.</p><h3>Search results are worse than expected but nothing errors</h3><p>Three conditions degrade <em>grep</em> silently. Pointing at a non-Atlas MongoDB drops it to a regex query. Losing the embedding API at query time drops it to full-text only, so natural-language phrasing stops working while literal terms still hit. And a partially failed sync leaves some documents unsearchable. <em>init_errors</em> and <em>initial_sync_report</em> catch all three. Assert on both at startup in anything long-running.</p><h3>A region error that has nothing to do with regions</h3><p><em>aws_region</em> governs S3, SQS, and Bedrock together, and they cannot be split. If the Bedrock embedding model is not enabled where your bucket lives, embedding fails and surfaces as a region error with nothing in it pointing at embeddings. Enable <em>amazon.titan-embed-text-v2:0</em> in the bucket&#39;s region, or switch providers.</p><p>The companion repository&#39;s <em>create_backend</em>() compounds this by defaulting <em>AWS_REGION</em> to &quot;us-east-1&quot;. The package alone would raise <em>NoRegionError</em> when nothing resolves; the fallback removes that signal. Set <em>AWS_REGION</em> explicitly.</p><h3>You installed the OpenAI extra and are still being charged for Bedrock</h3><p>The extra does not select the provider. <em>EMBEDDING_PROVIDER</em> does, and it defaults to Bedrock. Set <em>EMBEDDING_PROVIDER</em>=openai alongside the extra, or pass a LangChain Embeddings instance to <em>embedding_model</em> and bypass the lookup.</p><h3>A read raises instead of returning empty</h3><p>With <em>debug=True</em>, methods re-raise rather than returning error DTOs, so reading a file that does not exist yet raises <em>AdapterError</em>. This catches real bugs, but the manifest read on a fresh run is an expected miss. Catch the specific code rather than everything:</p><h3>The writer reports INCOMPLETE, but only sometimes</h3><p>This means the writer is greping for the findings rather than reading them by exact path. Search on this backend is eventually consistent: the write reaches S3 immediately, then the polling watcher notices it up to ten seconds later, re-chunks, re-embeds, and updates the index. When the readers run slowly, the watcher wins the race and the pipeline passes. When they run quickly it does not. Read findings by exact path and never grep the workspace plane.</p><h3>Your agent stopped planning after an upgrade</h3><p><em>deepagents</em> 0.7.0 removed <em>TodoListMiddleware</em> from the <em>create_deep_agent</em> defaults, so <em>write_todos</em>, the todos state channel, and the planning prompt are gone unless you pass <em>middleware=[TodoListMiddleware()]</em>. The same applies per sub-agent. Nothing errors; the agent just stops writing a plan. The same release emptied the default authored base prompt and deprecated <em>BASE_AGENT_PROMPT</em>, with removal scheduled for 0.9.0.</p><h3>A file in the bucket never becomes searchable</h3><p>Two causes account for most of these. The file exceeds the 64 MiB read cap, in which case it gets skipped rather than failing the run. The initial sync counts those in <em>SyncReport</em>.failed; the watchers only log them. Or the format sits outside the documented parser list, covered in the note on formats in the corpus step.</p><p>⬜ Error strings for the skip cases are not documented; add the observed log line here once someone has reproduced it.</p><h2>What to verify before production</h2><p><strong>Search freshness: </strong>neither this backend nor a LangGraph store gives you read-your-writes for search. Atlas Search and Vector Search are eventually consistent by design, and this package adds a watcher interval on top of that. Ten seconds with the polling watcher; closer to real time with the SQS watcher, which consumes S3 event notifications and needs those configured in AWS.</p><p><strong>Silent degradation: </strong>the three conditions from the setup check produce no error. Assert on <em>init_errors</em> and <em>initial_sync_report</em> at startup in anything long-running.</p><p><strong>Object size: </strong>reads cap at 64 MiB (<em>MAX_READ_BYTES</em> in langchain_mongodb_deepagents_vfs.backends.base). S3Backend.read() enforces it, so the cap covers read, edit, <em>download_files</em>, the initial sync, and the watchers, not just the public read API. write and upload_files refuse oversized content too. Skips never fail the run. The initial sync counts them in <em>SyncReport</em>.failed; the watchers only log them, leaving the log as your sole record. Chunking adds further bounds: OOXML archives get checked for entry count, uncompressed size, and expansion ratio before parsing, and PDF extraction caps page count and extracted characters.</p><p><strong>AWS coupling: </strong>the configuration table exposes no endpoint or endpoint_url parameter, so MinIO and LocalStack cannot be pointed at. You need a real S3 bucket.</p><p><strong>Access control: </strong>the package&#39;s responsibilities are the Deep Agents filesystem contract and the object-store-to-Atlas search path. Tenant isolation, retention, and audit belong to your application and your metadata model, not to the package. For a public docket, that is fine. For a corpus with customer data, that is the part you build.</p><h2>FAQ</h2><p><strong>What persists between runs, and what doesn&#39;t? </strong>Indexed content in Atlas and file bytes in S3 persist across runs and process restarts — that&#39;s the corpus. Files under <em>workspace/&lt;run_id&gt;/</em> are run state: <em>manifest.json</em> and findings are read back by that same <em>run_id</em> when you resume it. They are not a general memory store for other runs, and a checkpointer like this should not be described as agent memory.</p><p><strong>Why are S3 and Atlas separate systems instead of one? </strong>Object storage is optimized for durable, low-cost byte storage; it doesn&#39;t maintain live search indexes. Atlas runs Search, Vector Search, and hybrid ranking as first-class, indexed capabilities on the same data platform.</p><p><strong>Is search eventually consistent? </strong>Yes. Atlas Search and Vector Search index updates lag the S3 write by the watcher&#39;s polling interval (about 10 seconds), or closer to real time with the SQS watcher.</p><p><strong>Which package versions does this tutorial require? </strong><em>langchain-mongodb-deepagents-vfs</em> 0.1.0, Python 3.11 or later, and <em>langgraph-store-mongod</em>b 0.4.0 if you run the <em>StoreBackend</em> comparison. The <em>deepagents</em> pin is still open — see the note on the 0.7.0 middleware change in Prerequisites.</p><p><strong>Which credentials do I need? </strong>An Atlas connection string and database user, AWS credentials with the four S3 permissions listed in Prerequisites, and either the Bedrock <em>boto3</em> credential chain or an <em>OPENAI_API_KEY</em>, depending on the embedding provider you choose.</p><h2>Where to find the package and examples</h2><p>Swap in your own corpus by pointing <em>s3_prefix</em> at a different bucket path and re-running the seed script.</p><p>To build a corpus from a different federal docket, the repository includes <em>tools/fetch_docket.py</em>. It needs a free key from the <a href="https://open.gsa.gov/api/regulationsgov/">regulations.gov API</a> — read-only access, issued immediately, no approval step. Pass ?include=attachments on both the documents and comments endpoints, or you will get metadata without the spreadsheets and letters, which is most of what makes a docket worth searching.</p><p>The <a href="https://www.mongodb.com/company/blog/technical/vfs-langchain-deep-agents-searchable-filesystem-agents">MongoDB VFS announcement post</a> covers how the backend separates storage from search. For Deep Agents itself, see the <a href="https://docs.langchain.com/oss/python/deepagents/backends">LangChain Deep Agents backends documentation</a> and the <a href="https://www.mongodb.com/docs/atlas/ai-integrations/langchain/">MongoDB Atlas LangChain integration docs</a>. The package itself lives at <a href="https://github.com/langchain-ai/langchain-mongodb/tree/main/libs/langchain-mongodb-deepagents-vfs">langchain-ai/langchain-mongodb/libs/langchain-mongodb-deepagents-vfs</a> and takes contributions; see the repository-level <em>CONTRIBUTING.md</em>.</p>]]></description>
      <pubDate>Mon, 26 Oct 2026 14:45:24 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/technical/give-deep-agents-searchable-filesystem-on-atlas</link>
      <guid>https://www.mongodb.com/company/blog/technical/give-deep-agents-searchable-filesystem-on-atlas</guid>
    </item><item>
      <title>Building an Agentic Warehouse Management System—Part 1: Where AI Agents Add Value</title>
      <description><![CDATA[<p>I spent a large part of my career working in banking and logistics. In logistics, I spent more than eight years working across different stages of logistics systems, from development to implementation and production support.</p><p>That experience shaped the way I think about technology. Knowing a tool or framework is important, but what interests me most is understanding the business problem behind it and where technology can actually add value.</p><p>A few weeks ago, I returned as a speaker to a company where I had worked for many years. Being back there reminded me of several day-to-day logistical challenges and made me wonder how I would approach those problems today.</p><p>That is where the <strong>Agentic Warehouse Management System</strong> came from.</p><p>With this project, I am not trying to build a complete WMS. Instead, I want to use a logistics scenario I know well to explore how an AI agent can become part of a real business workflow and where it can add value.</p><p>In this first part, we will introduce the WMS scenario and identify where an AI agent can help. In <strong>Part 2</strong>, we will define and connect the agent using Java and Spring AI. Finally, in <strong>Part 3</strong>, we will execute the plan, gather context, make the replenishment decision, and act when necessary.</p><h2>The Warehouse Management System</h2><p>A Warehouse Management System, or simply WMS, is a software system used to manage and control the movement of products inside a warehouse. It typically handles processes such as receiving goods, tracking inventory, shipping products, replenishment, and many others. A warehouse may store products owned by the company operating it, but it may also store products for other companies. In this article, we will call these companies <strong>depositors</strong>:</p><p><strong>Figure 1.</strong> Warehouse Operations Overview.</p><p>A depositor owns the products stored in the warehouse, while the warehouse is responsible for receiving, storing, managing, and shipping them. A single warehouse may serve multiple depositors at the same time. For example, products from <em>Amazon</em>, <em>Nike</em>, or <em>Walmart</em> could be stored and managed in the same warehouse, while the inventory of each depositor remains separated. A real WMS can support many more processes, but for our application, we will focus on a smaller part of this flow: </p><p><strong>Figure 2.</strong> Inventory Flow and Replenishment Trigger.</p><p>An <strong>Inbound</strong> operation represents goods entering the warehouse and increases the available inventory for a depositor.  An <strong>Outbound</strong> operation represents goods leaving the warehouse and reduces that inventory. </p><p>We will also include a simple <strong>Replenishment Request</strong> process. When additional units are needed, the warehouse can create a request indicating which products should be replenished and in what quantities. The depositor can then arrange a new inbound shipment to the warehouse. Once a replenishment request is created, a <strong>Depositor Email Draft</strong> is also prepared for notification.</p><h2>Modeling the WMS flow</h2><p>In the flow above, a traditional implementation would involve a few basic entities such as Inbound, Outbound, Inventory, and Replenishment Request, along with products and depositors. An <strong>Inbound</strong> operation represents products owned by a depositor entering the warehouse. For example: </p><p>Once completed, those quantities are added to the <strong>Inventory</strong>:</p><p>An <strong>Outbound</strong> operation does the opposite. Products leave the warehouse, and their quantities are reduced from the inventory:</p><p>After this operation, the inventory for product <em>BR01</em> belonging to the depositor Amazon would contain only <em>20</em> units. At this point, a <strong>Replenishment Request</strong> may be needed. In practical terms, the warehouse is essentially saying:</p><p><em>“Amazon, your product BR01 is down to only 20 units. Could you arrange a new inbound shipment before we run out of stock?”</em></p><p>In our WMS, this request can be represented by a document like the following:</p><h2>Deciding when to replenish</h2><p>Creating a Replenishment Request is straightforward. The more interesting question is deciding when one should be created. Consider the following stock movements for product <strong>BR01</strong>:</p><p>On August 18, Amazon sent 1,500 units of the product to the warehouse. Over the following days, the warehouse processed outbound operations of 300 units per day. </p><p><strong>Figure 3.</strong> Inbound and Outbound Movements List.</p><p>After each outbound operation, the available inventory becomes: </p><p><strong>1,500 → 1,200 → 900 → 600 → 300 → 0 </strong></p><p>If this consumption pattern continues, the warehouse will completely run out of BR01 on the <strong>fifth</strong> outbound operation.</p><p>A common way to automate this process is to define a minimum stock threshold. For example, whenever fewer than 500 units are available, a replenishment request could be created:</p><p>This is a perfectly reasonable rule. Once the inventory reaches 300 units, the WMS detects that the stock is below the threshold (500) and requests more products.</p><p>However, consider that the depositor takes, on average, <strong>7 days</strong> to deliver new products to the warehouse. If we wait until the stock falls below 500 units, the request may come too late, and the warehouse may run out of BR01 before the new shipment arrives.</p><p>We can account for this by adding the remaining days of stock to the decision:</p><p>Now the WMS can react to  low stock while also anticipating replenishment when the remaining inventory is not enough to cover the depositor&#39;s delivery lead time.</p><p>These are deterministic rules, and they work well when the decision can be clearly expressed through known conditions and calculations. As the business evolves, however, new rules and exceptions may continue to appear.</p><p>At some point, the challenge is no longer just adding another condition.</p><h2>When the decision becomes contextual</h2><p>The problem becomes more interesting when deciding what to do requires more than evaluating a predefined condition. Let&#39;s go back to the same example.</p><p>Amazon sent 1,500 units of BR01, and the warehouse has been shipping 300 units per day. After three days, only 600 units remain.</p><p>Using the rule we created earlier, the calculation is straightforward:</p><ul><li><p>Current inventory: 600 units</p></li><li><p>Recent consumption: 300 units per day</p></li><li><p>Remaining stock: 2 days</p></li><li><p>Amazon lead time: 7 days</p></li></ul><p>Since two days of stock are not enough to cover a seven-day lead time, our code will create a replenishment request.</p><p>But consider two different situations:</p><ol><li><p><strong>Scenario A:</strong> The recent consumption of 300 units per day is part of the normal demand range for BR01. There is no indication that it will slow down. In this case, creating a replenishment request makes sense.</p></li><li><p><strong>Scenario B:</strong> The same 300-unit outbound operations came from a short promotion that has already ended. Previous movements show that BR01 typically consumes only around 50 units per day. In this case, immediately requesting the same replenishment may not be necessary.</p></li></ol><p>Our deterministic rule sees the same values in both situations: 600 units in stock, 300 units of recent daily consumption, and a seven-day lead time, so it produces the same result.</p><p>But the situations <strong>are not the same.</strong></p><p>To make a better decision, the system needs more context. It may need to inspect previous stock movements, understand whether the recent consumption represents the normal behavior of the product, retrieve relevant depositor policies, and then decide whether action is actually necessary.</p><p>This is where an AI agent starts to add value.</p><p>The agent does not replace deterministic operations such as inventory calculations, validations, persistence, or the creation of a replenishment request. Those operations remain regular application logic.</p><p>Instead, the agent can use controlled tools to look beyond the values used by the fixed rule. It can inspect previous stock movements, check pending replenishments, retrieve depositor policies, and gather additional information that helps explain the current situation.</p><p>The question is no longer only: <em>Is the inventory below 500 units, or is the remaining stock not enough to cover the depositor&#39;s lead time?</em></p><p>It becomes: <em>What does this situation actually mean, and do we need to act now?</em></p><p>That is the role of the agent in our WMS: gather the relevant information, understand the current situation, decide whether replenishment is necessary, and determine what should happen next,  while keeping well-defined business operations in deterministic code.</p><h2>Where does the agent fit?</h2><p>In our application, the agent enters the flow after an outbound operation is successfully completed. At that point, the inventory has already been updated, and the agent receives a goal:</p><p><em>Determine whether this outbound operation created a need for replenishment.</em></p><p>Before looking at the flow, it is useful to clarify what we mean by an AI agent.</p><p>In simple terms, an AI agent receives a <strong>goal</strong>, follows a set of <strong>instructions</strong>, interacts with the application through <strong>tools</strong>, observes the information it retrieves, and decides what to do next.</p><p>In our WMS, these elements have clear responsibilities:</p><ol><li><p><strong>Goal:</strong> defines what the agent needs to accomplish. In this case, determine whether the completed outbound operation created a need for replenishment.</p></li><li><p><strong>Instructions:</strong> define how the agent should behave, what it should consider, and the boundaries it must respect.</p></li><li><p><strong>Tools:</strong> provide controlled access to the WMS. The agent can use them to inspect inventory and stock movements, retrieve depositor policies, check pending replenishments, or perform actions such as creating a replenishment request.</p></li></ol><p>The important point is that the agent does not replace the existing WMS services or take control of the entire application. Inbound processing, outbound processing, inventory updates, validations, and persistence continue to be handled by regular Java code.</p><p>Instead, the agent acts as an <strong>orchestrator</strong>, deciding which available tools to use based on the goal and the context it gathers.</p><p>The following diagram shows where the agent becomes part of the WMS flow:</p><p><strong>Figure 4.</strong> AI agent architecture for automated replenishment.</p><p>The diagram may look like a sequence of steps, but this is not a traditional hard-coded workflow where the application defines every decision in advance.</p><p>The application defines the agent&#39;s <strong>configuration, instructions, boundaries, and available tools</strong>. Within those boundaries, the agent determines what information it needs, uses the results it collects as context, decides whether action is necessary, and determines what should happen next.</p><p>For one outbound operation, the agent may conclude that replenishment is required and create a request. For another, after analyzing the available context, it may decide that no action is necessary.</p><p>This is an important distinction: the WMS controls what the agent is allowed to do, while the agent is responsible for deciding what to do within those boundaries.</p><p>Once the outbound invoice is completed, the <em>OUTBOUND_INVOICE_COMPLETED</em> event triggers the agent. From there, the workflow can be summarized in four steps:</p><ol><li><p><strong>Plan:</strong> Based on the goal, instructions, and available capabilities, the agent determines what information and actions may be required.</p></li><li><p><strong>Analyze:</strong> The agent uses read-only tools to inspect information such as inventory, stock movements, pending replenishments, and depositor policies.</p></li><li><p><strong>Decide:</strong> Using the information collected, the agent determines whether replenishment is actually necessary.</p></li><li><p><strong>Act:</strong> If action is required, the agent can use controlled tools to create the replenishment request and prepare the depositor notification. If no action is required, the workflow ends without changing anything.</p></li></ol><h2>Conclusion</h2><p>In this first part, we focused on where an AI agent can add value inside a Warehouse Management System and, just as importantly, where it should not replace deterministic application logic.</p><p>In Part 2, we will translate this design into Java and Spring AI by defining the agent, connecting it to the WMS workflow, and creating its execution plan.</p><p>Then, in Part 3, we will see how the agent executes those tasks using controlled tools, gathers the necessary context, makes the replenishment decision, and acts when required.</p><p>The complete source code is available <a href="https://github.com/mongodb-developer/mongodb-jvm-showcase/tree/main/java/use-cases/agentic-wms">here</a>.</p>]]></description>
      <pubDate>Thu, 22 Oct 2026 14:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/technical/building-an-agentic-warehouse-management-system-part-1-where-ai-agents-add-value</link>
      <guid>https://www.mongodb.com/company/blog/technical/building-an-agentic-warehouse-management-system-part-1-where-ai-agents-add-value</guid>
    </item><item>
      <title>Build AI-Powered Applications with MongoDB Atlas in Grok Build</title>
      <description><![CDATA[<p>The rise of AI agents has fundamentally changed how software is built, with agentic platforms like Grok Build redefining the unit of software work. Instead of asking an AI assistant for a function, a developer or architect gives an autonomous agent a goal, constraints, a codebase, and a definition of done. The agent researches, proposes a plan, edits files, runs tests, and iterates. The goal is not human approval of every keystroke; it is human ownership at consequential decision points, with agents handling mechanical work and humans supplying judgment.</p><p>This tutorial shows how to combine that workflow with MongoDB Atlas as the operational database, memory layer, and retrieval engine for a small knowledge assistant.</p><p>The workflow is portable: usePlan Mode and Agent mode, or planning/build loop in Grok Build. Keep the application artifacts rules, specs, tests, seed data, and deployment files in Git so either builder (i.e., the human developer or the AI agent) can work from the same source of truth.</p><h2>Why choose Grok Build for agentic development?</h2><p>A modern coding agent can inspect a repository, find related files, propose multi-file changes, run terminal commands, and use external tools through Model Context Protocol (MCP). That makes the developer less of a line-by-line typist and more of an architect, reviewer, and test designer.</p><p>Grok Build is compelling because it combines an IDE-native workflow with persistent project context. Its project rules live in <em>.grok/rules</em>, where teams can version-control conventions, commands, and architectural constraints. Its Plan Mode researches the codebase, asks clarifying questions, creates a reviewable implementation plan, and waits for approval before building. That separation is valuable for AI applications, where an apparently small feature can touch schemas, indexes, prompts, APIs, security, and deployment.</p><p>The practical reason to choose Grok Build is control. You can inspect diffs as the agent works, constrain the files it should touch, require tests before implementation, and connect MCP servers without leaving the editor. The agent supplies speed; Git, rules, plans, tests, and human approval supply the guardrails. </p><p>See <a href="https://cursor.com/docs/agent/plan-mode">Grok Build (Cursor) Plan Mode</a> and <a href="https://cursor.com/docs/rules">Grok Build (Cursor) Rules</a> for the current workflow and configuration model.</p><h2>How MongoDB Atlas powers today’s agentic AI applications</h2><p>An agent needs more than an LLM. It needs durable conversation state, user and tenant boundaries, tool results, business records, documents, and fast retrieval. MongoDB Atlas brings those workloads together in a document model, so an application can keep operational data and AI context close to one another instead of synchronizing multiple specialized stores.</p><p>MongoDB Atlas Vector Search lets developers retrieve semantically related content from MongoDB collections. It can support retrieval-augmented generation (RAG), long-term memory, recommendations, and tool context, while ordinary MongoDB queries still handle exact filters and transactional reads. This combination matters: an agent can find “refund policy for annual plans” semantically, then apply an exact tenant or product filter before the LLM sees the result.</p><p>MongoDB Atlas is also designed for the realities of production: managed clusters, database access controls, indexes, backups, observability, and deployment across major clouds. </p><p>A particularly useful simplification is Automated Embedding. Atlas can generate and maintain embeddings for a configured text field using a Voyage AI model, including at index time and query time. That reduces custom embedding workers and synchronization code. Choose voyage-4 for a balanced general-purpose default, voyage-4-lite for cost-sensitive, high-volume workloads, or a code-focused Voyage model for technical content when available in your Atlas configuration.</p><p>Read <a href="https://www.mongodb.com/docs/vector-search/crud-embeddings/automated-embedding/">MongoDB Automated Embedding</a> and <a href="https://www.mongodb.com/docs/atlas/ai-integrations/">MongoDB AI Integrations</a> before selecting the exact model and index options exposed in your region and Atlas project.</p><h2>The joint value proposition: MongoDB Atlas and Grok Build</h2><p>Grok Build helps developers turn intent into a tested code change, MongoDB Atlas turns that code into a data-aware AI application with one place for documents, memory, metadata, and vector retrieval.</p><p><strong>Figure 1.</strong> MongoDB Atlas connects SpaceXSI’s agentic coding workflow in use.</p><p>Together, they shorten the path from prompt to production: Grok Build can inspect the repository and call Atlas tools through MCP, while Atlas supplies managed data services, Vector Search, Automated Embedding, and access controls. The developer stays in a tight plan-build-test loop instead of stitching together a separate database, vector store, embedding pipeline, and infrastructure script.</p><h2>The MongoDB Atlas Managed MCP Server and agent skills with Grok Build</h2><p>The MongoDB Atlas Managed MCP Server functions as the critical integration layer, empowering Grok Build agents to move beyond speculative code generation and directly interact with your Atlas deployments.</p><p>This server equips coding agents with over 40 specialized tools categorized into three primary domains:</p><p>By default, the Atlas Managed MCP Server runs read-only; destructive or billable operations like <em>insert/update/delete</em> require an explicit opt-in. A self-managed (local) MCP Server is different — it allows writes by default, so set <em>--readOnly</em> (or MDB_MCP_READ_ONLY=true) if you want the same safety net. See MongoDB MCP Server Configuration Options for the full defaults.</p><p>The official <a href="https://www.mongodb.com/docs/cursor/">MongoDB Grok Build Plugin</a> bundles the MongoDB MCP Server and pre-built MongoDB agent skills. Install it from Grok Build’s Marketplace by opening the command palette or Settings, searching for “MongoDB,” and following the prompts. You can also install it from the Agent input with:</p><p>After installation, pick the right connection for your setup. Choose the MongoDB Atlas managed connection when the plugin offers it and authorize your Atlas organization and project — Atlas handles authentication for you. For a self-managed server, point Grok Build&#39;s MCP settings at your own instance and connection string (SCRAM-SHA-256 by default, with OIDC, LDAP, Kerberos, and X.509 also supported). Follow <a href="https://www.mongodb.com/docs/mcp-server/get-started/?client=cursor&amp;deployment-type=self">MongoDB MCP Server Get Started</a> and MongoDB MCP Server Configuration Options for client- and auth-specific setup.</p><p>Authenticate your Atlas account by following the instructions below:</p><p>Every tool remains active initially; however, you can adjust these settings or refresh the environment to suit specific requirements.</p><p>Use a development project, least-privilege roles, and environment-managed secrets. A connection string supports database access; Atlas-specific cluster management requires appropriately scoped service-account credentials. The developer still approves billable, destructive, or production changes.</p><h3>Provision a new MongoDB Atlas cluster from Grok Build</h3><p>Start with discovery rather than guessing project IDs:</p><p>Then ask for a bounded development resource:</p><p>The agent executes the instructions, prompting for confirmation and clarifying required permissions before any cluster provisioning begins.</p><p>Upon confirming the configuration, this tutorial utilizes a dedicated M10 cluster as the primary deployment resource.</p><p>Tool names and tiers depend on the plugin and MongoDB Atlas permissions. Let the agent discover them rather than hard-coding MCP method names. See <a href="https://www.mongodb.com/docs/mcp-server/tools/">MongoDB MCP Server Tools</a>.</p><p>Load seed data through the plugin. </p><p>Use a small, synthetic fixture for development. Save this as <em>seed/knowledge.json</em>:</p><p>Prompt Grok Build to create the database and load it:</p><p>In MongoDB Atlas you can now see the collection created with define data schema and documents.</p><h3>Query and interact with MongoDB Atlas using natural language</h3><p>Once connected, Grok Build can translate intent into safe database exploration. Examples include:</p><p><strong>Find tenant distribution:</strong></p><p>You can prompt the agent with query natural language requests such as:</p><p>Which results in:</p><p><strong>Configure or inspect Vector Search index:</strong></p><p>To inspect or create the vector search index using Automated Embedding, run:</p><p>Run a vector search test:</p><p>This keeps Grok Build close to live Atlas context while preserving human approval for mutations and infrastructure.</p><p>The detailed steps to create your first agentic application with MongoDB Atlas and SpaceXAI models using Grok Build are available <a href="https://github.com/ashwin-gangadhar-mdb/atlas-agent-demo">here</a>.</p><h2>Why build with Grok Build and MongoDB Atlas?</h2><p>MongoDB Atlas and Grok Build complement each other at the exact point where AI projects become real software. Grok Build accelerates exploration, implementation, and testing. Atlas supplies the durable application state, semantic retrieval, and managed operational foundation.</p><p>The result is not “AI-generated code” as an end in itself. It is a repeatable delivery loop: specify the architecture, provision a controlled data layer, seed realistic fixtures, evaluate behavior, build in small slices, and deploy with evidence. That is a practical way to move from an idea in a prompt to an AI application you can operate.</p>]]></description>
      <pubDate>Wed, 21 Oct 2026 16:56:34 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/technical/build-ai-powered-applications-with-atlas-in-grok-build</link>
      <guid>https://www.mongodb.com/company/blog/technical/build-ai-powered-applications-with-atlas-in-grok-build</guid>
    </item><item>
      <title>Introducing AptMQL-Bench: A Text-to-MQL Benchmark</title>
      <description><![CDATA[<p>Large language models increasingly sit between people and their data, whether answering questions in a chat interface or acting as agents that query databases directly. Either way, the model must reliably translate a request into the query language the database speaks. </p><p>For SQL, progress on this task has been driven by large benchmarks such as BIRD1 and Spider2. MQL, the query language of MongoDB, has received less attention despite the fact that MongoDB is one of the world’s most popular and widely used databases.</p><p>In this blog post, we introduce <strong>AptMQL-Bench</strong> (Access-Patterns-Based Text-to-MQL), a <strong>Text-to-MQL benchmark</strong> obtained by converting existing Text-to-SQL datasets. We also present the agent-driven conversion pipeline that produced it.</p><p>We&#39;re releasing:</p><ul><li><p><a href="https://huggingface.co/datasets/MongoDB/AptMQL-Bench">AptMQL-Bench</a>: the benchmark dataset. It consists of <strong>21 new MongoDB databases</strong> along with <strong>3,186 natural-language requests</strong>, migrated from BIRD1, spanning domains such as commerce, science, sports, and finance.</p></li><li><p><a href="https://arxiv.org/abs/2610.02770">A technical report</a> describing our proposed conversion pipeline for access-pattern schema design, data-preserving migration, and SQL-to-MQL translation.</p></li><li><p><a href="https://huggingface.co/datasets/MongoDB/AptMQL-Bench/tree/main/prompts">Conversion pipeline prompts</a></p></li><li><p><a href="https://huggingface.co/datasets/MongoDB/AptMQL-Bench/blob/main/eval_script.py">Evaluation script</a>, including our proposed <em>soft execution accuracy</em> (<em>Soft-EX</em>).</p></li></ul><h2>The challenges</h2><p>Existing Text-to-MQL approaches take one of two routes. The <a href="https://huggingface.co/datasets/mongodb-eai/natural-language-to-mongosh">NL-to-mongosh</a> dataset3 starts from native MongoDB data, pairing 766 synthetically generated requests with the eight MongoDB Atlas sample databases. Other works convert existing Text-to-SQL datasets mechanically: DocSpider4 maps each relational table to its own collection one-to-one, while TEND-v25 and its multilingual extension MultiTEND6 embed tables along foreign keys (FK).</p><p>However, doing these conversions well is not trivial. Mechanical denormalizations along foreign keys, in particular, can be fragile. In our experiments, three out of 24 databases failed to migrate due to infinite recursion on self-referential keys, while another three produced individual documents so large that they didn&#39;t fit in MongoDB&#39;s 16 MB document limit. Additionally, on eight other databases, rows whose foreign keys resolved to no surviving parent were silently dropped, reaching 25.9% row loss in the worst case.</p><p>Finally, as we show below, these conversions also lead to schemas with poor scalability characteristics.</p><h2>Our proposed conversion pipeline</h2><p>As Figure 1 shows, we treat schema design as a first-class step and then revise that design while migrating the data. The pipeline is driven by coding agents (e.g., Claude Code) with human review at designated quality gates, and runs in three stages.</p><p><strong>Figure 1.</strong><em> </em>The conversion pipeline: document schema design, migration and validation, and SQL-to-MQL translation, each driven by a coding agent with human review at the quality gates.</p><p><strong>1. Access-pattern schema design.</strong> Given the source SQLite database and its column descriptions, an agent first infers a real-world application the database would serve and the access patterns it would generate. The agent then designs a high-level <em>conceptual schema</em> (which collections exist and how they relate), and a low-level <em>logical schema,</em> specifying each collection’s fields, data types, and mappings from the source database. Both follow a design guidebook we curated from three MongoDB University courses. A reviewer then confirms each modeling choice and verifies that every source table remains retrievable from the design.</p><p>This approach ensures that the resulting schemas adhere to <a href="https://learn.mongodb.com/learn/course/relational-to-document-model/relational-to-document-model/model-for-workloads">MongoDB&#39;s golden rule for schema design</a>: <strong>data that is accessed together should be stored together</strong>.</p><p><strong>2. Migration and validation.</strong> To catch errors or omissions in the schema design and migration code, the agent runs three automated checks after each migration: (1) queries over each MongoDB collection retrieve the same data as corresponding queries over the original SQL tables, (2) references between collections point to existing documents, and (3) nothing on the SQLite side was left behind. Anything that fails is surfaced to a human reviewer, who then works with the agent to fix the design or the migration code. We repeat this until every check passes.</p><p><strong>3. SQL-to-MQL translation, then optimization.</strong> Each reference SQL query from the source benchmark is translated into MQL by an agent, which revises the translation until automated checks confirm that both queries return identical results. Translations that pass are correct but often still relational in shape. For instance, they&#39;ll contain redundant <em>$lookup</em> stages that fetch already-embedded documents. A second pass rewrites them to use embedded fields and precomputed aggregates directly; 1,444 MQL queries (45.32%) were optimized this way, and a reviewer confirmed each one is equivalent to the original translation. BIRD&#39;s external knowledge evidence is rewritten in the same spirit, so its field references point to MongoDB paths rather than SQL columns, and each rewritten evidence is checked by a reviewer against the ground-truth MQL.</p><h2>The importance of schema design</h2><p>We compare the characteristics of schemas produced by our access-pattern design approach against the two mechanical strategies on the same source data.</p><p><strong>Table 1.</strong><em> </em>DB migration results. 24 databases: the 21 BIRD databases in AptMQL-Bench plus 3 Spider databases used in the scaling experiments.</p><p>One-to-one is lossless by construction: every row becomes its own document, but the result merely mirrors the relational schema, at a cost we measure below. Foreign key embedding <strong>fails outright on six out of 24 DBs</strong>, while in 8 other cases the migration is lossy.</p><p>On execution time, we find that the performance of the three designs diverges as the size of the underlying DBs is increased. To measure this, we took three DBs from Spider (<em>bike_1</em><em>,</em> <em>car_1,</em> and <em>pets_1</em>) and 11 DBs from BIRD. We then expanded each DB by appending synthetic rows (see <a href="https://arxiv.org/abs/2610.02770">our paper</a> for more details on this procedure), obtaining different versions of these DBs with sizes up to ~200 MB.</p><p><strong>Figure 2.</strong><em> </em>Execution time of the ground-truth MQLs as database size grows (log-log, averaged across databases), for each conversion strategy. </p><p>Figure 2 shows the resulting execution times. At 200 MB, access-pattern MQLs run about 11× faster than foreign key embedding and roughly two orders of magnitude faster than a one-to-one migration on the Spider datasets. On BIRD, the speedup over one-to-one grows from around 40× on the original databases to 77× once they reach the largest sizes investigated.</p><p>These results demonstrate the advantages of the workload-driven schema design advocated in this work.</p><h2>Benchmarking LLMs</h2><p>We evaluated eight models in total (five open-weight, three proprietary), each with and without BIRD&#39;s external knowledge evidence.</p><p><strong>Table 2.</strong> Soft execution accuracy (Soft-EX) on AptMQL-Bench. Full results, including execution success rate and Strict-EX, are in the paper.</p><p>The results show that the benchmark is challenging for every model. The strongest model, Claude Opus 4.5, reaches only 57.38% Soft-EX without external knowledge and 70.34% with it. External knowledge helps every model, adding 12–19 points.</p><p>Some of the latest models (Gemma 4 and the Claude family of models) produce executable MQL about 98–99% of the time, confirming that invalid MQL is more and more rare and that the remaining difficulty is semantic rather than syntactic.</p><h3>Why we score with Soft-EX</h3><p>In metrics borrowed from Text-to-SQL, strict execution accuracy (Strict-EX) requires the returned result to equal the gold result field-for-field, so a prediction that hands back the whole document instead of a single projected field is marked wrong, even though it contains the right answer, and even though returning the document is the idiomatic thing to do in MongoDB.</p><p>We therefore propose <strong>soft execution accuracy (Soft-EX)</strong>: a prediction is correct if it returns the same rows as the gold result, with matching values for every ground-truth field. Extra fields are allowed, but extra or missing rows and incorrect values are not.</p><p><strong>Table 3. </strong>The following examples illustrate the difference between Strict-EX and Soft-EX.</p><p>With external knowledge, Opus 4.5 scores 50.44% under Strict-EX but 70.34% under Soft-EX. To confirm that this gap is due only to extra fields, we manually reviewed all 634 queries where the two metrics disagree, which covers every prediction that Soft-EX accepts but Strict-EX rejects. </p><p>In every case, the prediction returned the same rows as the gold result, with matching values for every gold field, and differed only by including extra fields. Strict-EX therefore marks these predictions wrong even though they contain the complete gold answer.</p><h2>Next steps</h2><p><strong>Try it and learn more!</strong></p><ul><li><p>Benchmark and databases: <a href="https://huggingface.co/datasets/MongoDB/AptMQL-Bench">Hugging Face dataset</a></p></li><li><p>Conversion pipeline prompts and evaluation scripts are <a href="https://huggingface.co/datasets/MongoDB/AptMQL-Bench/tree/main/prompts">here</a></p></li><li><p><a href="https://arxiv.org/abs/2610.02770">Technical report</a></p></li></ul><h2>References</h2><ul><li><p>1 Jinyang Li et al. 2023. Can LLM Already Serve as A Database Interface? A BIg Bench for Large-Scale Database Grounded Text-to-SQLs. <em>Advances in Neural Information Processing Systems</em>, 36:42330–42357.</p></li><li><p>2 Tao Yu et al. 2018. Spider: A Large-Scale Human-Labeled Dataset for Complex and Cross-Domain Semantic Parsing and Text-to-SQL Task. In <em>Proceedings of the 2018 Conference on Empirical Methods in Natural Language Processing</em>, pages 3911–3921, Brussels, Belgium. Association for Computational Linguistics.</p></li><li><p>3 MongoDB Education AI. 2025. Natural Language to MongoDB Shell (mongosh) Benchmark. Hugging Face dataset. <a href="https://huggingface.co/datasets/mongodb-eai/natural-language-to-mongosh">https://huggingface.co/datasets/mongodb-eai/natural-language-to-mongosh</a></p></li><li><p>4 Arif Görkem Özer, Recep Firat Cekinel, Ismail Hakki Toroslu, and Pinar Karagoz. 2025. DocSpider: A Dataset of Cross-Domain Natural Language Querying for MongoDB. <em>Natural Language Processing</em>, 31(6):1367–1398.</p></li><li><p>5 Jinwei Lu, Yuanfeng Song, Zhiqian Qin, Haodi Zhang, Chen Zhang, and Raymond Chi-Wing Wong. 2025. Bridging the Gap: Enabling Natural Language Queries for NoSQL Databases through Text-to-NoSQL Translation. Preprint, arXiv:2502.11201.</p></li><li><p>6 Zhiqian Qin, Yuanfeng Song, Jinwei Lu, Yuanwei Song, Shuaimin Li, and Chen Jason Zhang. 2025. MultiTEND: A Multilingual Benchmark for Natural Language to NoSQL Query Translation. In <em>Findings of the Association for Computational Linguistics: ACL 2025</em>, pages 24632–24657, Vienna, Austria. Association for Computational Linguistics.</p></li></ul>]]></description>
      <pubDate>Wed, 21 Oct 2026 12:49:21 GMT</pubDate>
      <link>https://www.mongodb.com/company/research/introducing-aptmql-bench-text-to-mql-benchmark</link>
      <guid>https://www.mongodb.com/company/research/introducing-aptmql-bench-text-to-mql-benchmark</guid>
    </item><item>
      <title>Modernize Your Insurance Data Models With MongoDB Relational Migrator</title>
      <description><![CDATA[<p>In the 70s and 80s, there were few commercial off-the-shelf solutions available for many core insurance functions, so insurers had to build their own applications. Such applications are often host-based, meaning that they are mainframe technologies. These legacy platforms include software languages such as COBOL and CICS. Many insurers are still struggling to replace these legacy technologies due to a confluence of variables such as a lack of developers with programming skills in these older technologies and complicated insurance products. This results in high maintenance costs and difficulty in making changes. In brief, legacy systems are a barrier to progress in the insurance industry.</p><p>Whether you’re looking to maintain and improve existing applications or push new products and features to market, the data trapped inside those systems is a drag on innovation.</p><p>This is particularly true when we think about the data models that sit at the core of application systems (e.g., underwriting), defining entities and relationships between them.</p><p>In this tutorial, we will demonstrate:</p><ul><li><p>Why the document model simplifies the data model of a standard insurance system.</p></li><li><p>How MongoDB&#39;s Relational Migrator effortlessly transforms an unwieldy 21-table schema into a lean five-collection MongoDB model.</p></li></ul><p>This will ultimately prove that with MongoDB, insurers will launch new products faster, swiftly adapt to regulatory changes, and enhance customer experiences.</p><p>To do this, we will focus on the Object Management Group’s <a href="https://www.omg.org/spec/PC/1.0/PDF">Party Role model</a> and how the model can be ported from a relational structure to MongoDB’s document model.</p><p><strong>Figure 1.</strong> OMG Property and Casualty Data Model, representing the major entities and their relationships.</p><p>In particular, we will describe the refactoring of Party in the context of Policy and Claim &amp; Litigation. For each of them, a short description, a simplified <a href="https://hackolade.com/">Hackolade</a> model (Entity Relationship Diagrams - ERD), and the document refactoring using Relational Migrator are provided.</p><p><a href="https://www.mongodb.com/products/tools/relational-migrator">Relational Migrator</a> is a tool that allows you to:</p><ul><li>Design an effective MongoDB schema, derived from an existing relational schema.</li><li><p>Migrate data from Oracle, SQL Server, MySQL, PostgreSQL, or Sybase ASE to MongoDB, while transforming to the target schema.</p></li><li><p>Generate code artifacts to reduce the time required to update application code.</p></li></ul><p>At the end of this tutorial, you will have learned how to use Relational Migrator to refactor the Party Role relational data model and migrate the data into MongoDB collections.</p><h2>Connect to Postgres and set up Relational Migrator</h2><h3>Prerequisites</h3><ul><li><p><strong>MongoDB Relational Migrator</strong> (version 1.4.3 or higher): <a href="https://www.mongodb.com/docs/relational-migrator/">MongoDB Relational Migrator</a> is a powerful tool to help you migrate relational workloads to MongoDB. <a href="https://www.mongodb.com/try/download/relational-migrator">Download and install the latest version</a>.</p></li><li><p><strong>PostgreSQL </strong>(version 15 or higher): PostgreSQL is a relational database management system. It will serve as the source database for our migration task. <a href="https://www.postgresql.org/download/">Download the last version of PostgreSQL</a>.</p></li><li><p><strong>MongoDB </strong>(version 7.0 or higher): You will need access to a MongoDB instance with write permissions to create the new database where we are going to migrate the data. You can install the latest version of the <a href="https://www.mongodb.com/try/download/community">MongoDB Community Server</a> or simply <a href="https://www.mongodb.com/docs/atlas/tutorial/deploy-free-tier-cluster/">deploy a free MongoDB Atlas cluster</a> in less than three minutes!</p></li></ul><p>In this tutorial, we will use PostgreSQL as the RDBMS to hold the original tabular schema that will be migrated to MongoDB. To follow it, you will need access to a PostgreSQL database server instance with permission to create a new database and user. The instance may be in the cloud, on-prem, or on your local machine. You just need to know the URL, port, username, and password for the PostgreSQL instance you choose.</p><p>We will also use two <a href="https://www.postgresql.org/docs/15/reference-client.html">PostgreSQL Client Applications</a>: <a href="https://www.postgresql.org/docs/15/app-psql.html">psql</a> and <a href="https://www.postgresql.org/docs/15/app-pgrestore.html">pg_restore</a>. These terminal-based applications will allow us to interact with our PostgreSQL database server instance. The first application, <em>psql</em>, enables you to type in queries interactively, issue them to PostgreSQL, and see the query results. It will be useful to create the database and run queries to verify that the schema has been successfully replicated. On the other hand, we will use <em>pg_restore</em> to restore the PostgreSQL database from the archive file available in <a href="https://github.com/mongodb-industry-solutions/insurance-relational-refactoring">the GitHub repository</a>. This archive file contains all the tables, relationships, and sample data from the Party Role model in a tabular format. It will serve as the starting point in our data migration journey.</p><p>The standard ready-to-use packages will already include both the server and these client tools. We recommend using version 15 or higher. You can download it from the official <a href="https://www.postgresql.org/download/">PostgreSQL Downloads</a> site or, if you are a macOS user, just run the command below in your terminal.</p><p><em><strong>Note:</strong></em> Verify that Postgres database tools have been successfully installed by running `psql --version` and `pg_restore --version`. If you see an error message, make sure the containing directory of the tools is added to your `PATH`.</p><h3>Replicate the Party Role model in PostgreSQL</h3><p>First, we need to connect to the PostgreSQL database.</p><p>If it’s a newly installed local instance with the default parameters, you can use `127.0.0.1` as your host, `5432` as the port, `postgres` as the database, and type `whoami` in your terminal to get your default username if no other has been specified during the installation of the PostgreSQL database server.</p><p>Once you are connected, we need to create a database to load the data.</p><p>Then, we will create the user that will have access to the new database, so we don’t need to use the root user in the relational migrator. Please remember to change the password in the command below.</p><p>Finally, we will populate the database with the Party Role model, a standard widely used in the insurance industry to define how people, organizations, and groups are involved in agreements, policies, claims, insurable objects, and other major entities. This will not only replicate the table structure, relationships, and ownership, but it will also load some sample data.</p><ol><li><p>First, <a href="https://github.com/mongodb-industry-solutions/insurance-relational-refactoring/blob/main/mongodb_insurance_model.tar">download the .tar file</a> that contains the backup of the database.</p></li><li><p>Navigate to the folder where the file is downloaded using your terminal.</p></li><li><p>Run the command below in your terminal to load the data. Please remember to change the host, port, and user before executing the command.</p></li></ol><p>After a few seconds, our new database will be ready to use. Verify the successful restore by running the command below:</p><p>You should see a list of 21 tables similar to the one in the figure below.</p><p><strong>Figure 2.</strong> List of tables in the Party Role model.</p><p>If all looks good, you are ready to connect your data to MongoDB Relational Migrator.</p><h3>Connect to Relational Migrator</h3><p>Open the Relational Migrator app and click on the “New Project” button. We will start a new project from scratch by connecting to the database we just created. Click on “Connect database,” select “PostgreSQL” as the database type, and fill in the connection details. Test the connection before proceeding, and if the connection test is successful, click “Connect.” If a “no encryption” error is thrown, click on SSL → enable SSL.</p><p><strong>Figure 3.</strong> Database connection in Relational Migrator.</p><p>In the next screen, select all 21 tables from the OMG schema and click “Next.” On this new screen, you will need to define your initial schema. We will start with a MongoDB schema that matches your relational schema. Leave the other options as default. Next, give the project a name and click “Done.” </p><p>This will generate a schema that matches the original one. That is, we will have one collection per table in the original schema. This is a good starting point, but as we have seen, one of the advantages of the document model is that it is able to reduce this initial complexity. To do so, we will take an object-modeling approach. We will focus on four top-level objects that will serve as the starting point to define the entire schema: Party, Policy, Claim, and Litigation.</p><p>By default, you will see a horizontal split view of the Relational (upper part) and MongoDB (lower part) model. You can change the view model from the bottom-left corner “View” menu. Please note that all the following steps in the tutorial will be done in the MongoDB view (MDB). Feel free to change the view mode to “MDB” for a more spacious working view.</p><h2>Party domain</h2><p>The Party Subject Area (Figure 4) shows that all persons, organizations, and groups can be represented as “parties,” and parties can then be related to other major objects with specified roles. The Party design also provides a common approach to describing communication identifiers, relationships between parties, and legal identifiers.</p><p><strong>Figure 4.</strong> Party Subject Area.</p><p>To illustrate the process in a simpler and clearer way, we reduced the number of objects and built a new ERD in Relational Migrator (Figure 5). Such models are most often implemented in run-time transactional systems. Their impact and dependencies can be found across multiple systems and domains. Additionally, they can result in very large physical database objects, and centralized storage and access patterns can be bottlenecks.</p><p><strong>Figure 5.</strong> Party Model tables.</p><p>The key Party entities are:</p><ul><li><p><strong>Party</strong> — represents people, organizations, and groups</p></li><li><p><strong>Party Role </strong>— defines the role a party plays within a context:</p></li><ul><li><p>Policy</p></li><li><p>Claim</p></li><li><p>Agreement</p></li><li><p>Litigation</p></li><li><p>Insurable Object</p></li></ul><li><p><strong>Communication Identity </strong>— generic representation of things like:</p></li><ul><li><p>Address</p></li><li><p>Phone</p></li><li><p>Email</p></li></ul></ul><p>Party represents people, organizations, and groups. In the original schema, this is represented through one-to-one relationships. Party holds the common attributes for all parties, while each of the other three tables stores the particularities of each party class. These differences result in distinct fields for each class, which forces tabular schemas to create new tables. The inherent flexibility of the document model allows embedding this information in a single document. To do this, follow the steps below: </p><ul><li><p>Select the &quot;party&quot; collection in the MDB view of Relational Migrator. At the moment, this collection has the same fields as the original matched table.</p></li><li><p>On the right-hand side, you will see the mappings menu (Figure 6). Click on the “Add” button, select “Embedded documents,” and choose &quot;person&quot; in the “Source table” dropdown menu. Click “Save and close” and repeat this process for the &quot;organization&quot; and &quot;grouping&quot; tables.</p></li><li><p>After this, you can remove the &quot;person,&quot; &quot;organization,&quot; and &quot;grouping&quot; collections.</p></li><li><p>Right-click on them, select “Remove Entity,” and confirm “Remove from the MongoDB model.” You have already simplified your original model by three tables, and we’re just getting started.</p></li></ul><p><strong>Figure 6.</strong> Party mapping menu.</p><p>Looking at Figure 5, we can see that there is another entity that could be easily embedded in the party collection: location addresses. In this case, this table has a many-to-many relationship facilitated by the &quot;party_location_address&quot; table. As a party can have many location addresses, instead of an embedded document, we will use an embedded array. You can do it in the following way:</p><ul><li><p>Select the collection &quot;party&quot; again, click the “Add” button, select “Embedded array,” and choose &quot;party_location_address&quot; in the “Source table” dropdown. Under the “All fields” checkbox, uncheck the `partyIdentifier` field. We are not going to need it. Addresses will be contained in the “party” document anyway. Leave the other fields as default and click the “Save and close” button.</p></li><li><p>We have now established the relationship, but we want to have the address details too. From the “party” mapping menu, click the “Add” button again. Then, select “Embedded documents,” choose “location_address,” and in the “Root path” section, check the box that says “Merge fields into the parent.” This will ensure that we don’t have more nested fields than necessary. Click “Save and close.”</p></li><li><p>You can now delete the “party_location_address” collection, but don’t delete “location_address” as it still has an existing relationship with “insurable_object.”</p></li></ul><p>You are done. The “party” entity is ready to go. We have not only reduced six tables to just one, but the “person,” “organization,” and “grouping” embedded documents will only show up if that party is indeed a person, organization, or grouping. One collection can contain documents with different schemas for each of these classes.</p><p><strong>Figure 7.</strong> Document representation of the Party entity.</p><p>At the beginning of the section, we also spoke about the “party role” entity. It represents the role a party plays in a specific context such as policy, claim, or litigation. In the original schema, this many-to-many relationship is facilitated via intermediate tables like “policy_party_role,” “claim_party_role,” and “litigation_party_role” respectively. These intermediate tables will be embedded in other collections, but the “party_role” table can be left out as a reference collection on its own. In this way, we avoid having to update one by one all policy, claim, and litigation documents if one of the attributes of “party role” changes.</p><p><strong>Figure 8.</strong> Document representation of the PartyRole entity.</p><p>Let’s see next how we can model the “policy” entity.</p><h2>Policy domain</h2><p>The key entities of Policy are:</p><ul><li><p><strong>Insurable Object</strong> — an object insured by a policy agreement</p></li><li><p><strong>Insurable Object Party Role</strong> — associative entity which links:</p></li><ul><li><p>Party</p></li><li><p>The role the Party plays</p></li><li><p>Insurable Objects</p></li></ul><li><p><strong>Agreement Party role</strong> — associative entity which links:</p></li><ul><li><p>Party</p></li><li><p>The role the Party plays</p></li><li><p>Agreement (which is related to a product and policy)</p></li></ul></ul><p><strong>Figure 9.</strong> Party in the context of Policy tables.</p><p>From a top-level perspective, we can observe that the “policy” entity is composed of policy coverage parts and the agreements of each of the parties involved with their respective roles. A policy can have several parts to cover and several parties&#39; agreements involved. Therefore, similarly to what happened with party location addresses, they will be matched to array embeddings.</p><p>Let’s start with the party agreements. A policy may have many parties involved, and each party may be part of many policies. This results in a many-to-many relationship facilitated by the “policy_party_role” table. This table also covers the relationships between roles and agreements, as each party will play a role and will have an agreement in a specific policy.</p><ul><li><p>From the MDB view, select the “policy” collection. Click on the “Add” button, select “embedded array,” and choose “policy_party_role” in the source table dropdown. Uncheck the `policyIdentifier` field, leave the other fields as default, and click “Save and close.”</p></li><li><p>We will leave the party as a referenced object to the “party” collection we created earlier, so we don’t need to take any further action on this. The relationship remains in the new model through the `partyIdentifier` field acting as a foreign key. However, we need to include the agreements. From the “policy” mapping menu, click “Add,” select “Embedded document,” pick “agreement” as the source table, leave the other options as default, and click “Save and close.” </p></li><li><p>At this point, we can remove the collections “policy_party_role” and “agreement.” Remember that we have defined “party_role” as a separate reference collection, so just having `partyRoleCode` as an identifier in the destination table will be enough.</p></li></ul><p>Next, we will include the policy coverage parts.</p><ul><li><p>From the “policy” mapping menu, click “Add,” select “Embedded array,” pick “policy_coverage_part” as the source table, uncheck the `policyIdentifier` field, leave the other options as default, and click “Save and close.”</p></li><li><p>Each coverage part has details included in the “policy_coverage_detail”. We will add this as an embedded array inside of each coverage part. In the “policy” mapping menu, click “Add,” select “Embedded array,” pick “policy_coverage_detail,” and make sure that the prefix selected in the “Root path” section is `policyCoverageParts`. Remove `policyIdentifier` and `coveragePartCode` fields and click “Save and close.”</p></li><li><p>Coverage details include “limits,” “deductibles,” and “insurableObjects.” Let’s add them in! Click “Add” in the “policy” mapping menu, “Embedded Array,” pick “policy_limit,” remove the `policyCoverageDetailIdentifier`, and click “Save and close.” Repeat the process for “policy_deductible.” For “insurable_object,” repeat the process but select “Embedded document” instead of “Embedded array.”</p></li><li><p>As you can see in Figure 9, insurable objects have additional relationships to specify the address and roles played by the different parties. To add them, we just need to embed them in the same fashion we have done so far. Click “Add” in the “policy” mapping menu, select “Embedded array,” and pick “insurable_object_party_role.” This is the table used to facilitate the many-to-many relationship between insurable objects and party roles. Uncheck `insurableObjectIdentifier` and click “Save and close.” Party will be referenced by the `partyIdentifier` field. For the sake of simplicity, we won’t embed address details here, but remember in a production environment, you would need to add it in a similar way as we did before in the “party” collection.</p></li><li><p>After this, we can safely remove the collections “policy_coverage_part,” “policy_coverage_detail,” “policy_deductible,” and “policy_limit.”</p></li></ul><p>By now, we should have a collection similar to the one below and five fewer tables than in our original model.</p><p><strong>Figure 10.</strong> Document representation of the Policy entity.</p><h2>Claim &amp; litigation domain</h2><p><strong>Figure 11.</strong> Party in context of Claim &amp; Litigation Hackolade model.</p><p>The key entities of Claim and Litigation are:</p><ul><li><p><strong>Claim</strong> — claim for coverage or compensation</p></li><li><p><strong>Litigation </strong>—<strong> </strong>claim<strong> </strong>litigation </p></li><li><p><strong>Claim Party Role</strong> — associative entity which links:</p></li><ul><li><p>Party</p></li><li><p>The role the Party plays</p></li><li><p>Insurable Objects</p></li></ul><li><p><strong>Litigation Party Role</strong> - associative entity which links:</p></li><ul><li><p>Claim</p></li><li><p>The role the Party plays</p></li><li><p>Insurable Objects</p></li></ul><li><p><strong>Insurable Object Party Role</strong> - associative entity which links:</p></li><ul><li><p>Party</p></li><li><p>The role the Party plays</p></li><li><p>Insurable Objects</p></li></ul></ul><p>In this domain, we have already identified the two main entities: claim and litigation. We will use them as top-level documents to refactor the relationships shown in Figure 10 in a more intuitive way. Let’s see how you can model claims first.</p><p></p><ul><li><p>We’ll begin embedding the parties involved in a claim with their respective roles. Select “claim” collection, click “Add” in the mapping menu, select “Embedded array,” and pick “claim_party_role” as the source table. You can uncheck `claimIdentifier` from the field list. Lastly, click the “Save and close” button.</p></li><li><p>Next, we will integrate the insurable object that is part of the claim. Repeat the previous step, but choose “Embedded documents” as the table migration option and “insurable_object” as the source table. Again, we will not embed the “location_address” entity to keep it simple.</p></li><li><p>Within insurableObject, we will include the policy coverage details establishing the link between claims and policies. Add a new mapping, select “Embedded array,” choose “policy_coverage_detail” as the source table, and uncheck the field insurableObjectIdentifier. Leave the other options as default.</p></li><li><p>Lastly, we will recreate the many-to-many relationship between litigation and claim. As we will have a separate litigation entity, we just need to reference that entity from the claims document, which means that just having an array of litigation identifiers will be enough. Repeat the previous step by selecting “Embedded array,” “litigation_party_role,” and unchecking all fields except `litigationIdentifier` in the field list.</p></li></ul><p><strong>Figure 12.</strong> Document representation of the Claim entity.</p><p>The claim model is ready to go. We can now remove the collection “claimPartyRole.” </p><p>Let’s continue with the litigation entity. Litigations may have several parties involved, each playing a specific role and with a particular associated claim. This relationship is facilitated through the “litigation_party_role” collection. We will represent it using an embedded array. Additionally, we will include some fields in the claim domain apart from its identifier. This is necessary so we can have a snapshot of the claim details at the time the litigation was made, so even if the claim details change, we won’t lose the original claim data associated with the litigation. To do so, follow the steps below:</p><ul><li><p>From the “litigation” mapping menu, click on the “Add” button, select “Embedded array,” and pick “litigation_party_role” as the source table. Remove `litigationIdentifier` from the field list and click “Save and Close.” </p></li><li><p>In a similar way, add claim details by adding “claim” as an “Embedded document.” </p></li><li><p>Repeat the process again, but choose “insurable_object” as the source table for the embedded document. Make sure the root path prefix is set to `litigationPartyRoles.claim`.</p></li><li><p>Finally, add “insurable_object_party_role” as an “Embedded array.” The root path prefix should be `litigationPartyRoles.claim.insurableObject`.</p></li></ul><p><strong>Figure 13.</strong> Document representation of the Litigation entity.</p><p>And that’s it. We have modeled the entire relationship schema in just five collections: “party,” “partyRole,” “policy,” “claim,” and “litigation.” You can remove the rest of the collections and compare the original tabular schema composed of 21 tables to the resulting five collections.</p><h2>Migrate your data to MongoDB</h2><p>Now that our model is complete, we just need to migrate the data to our MongoDB instance. First, verify that you have “dbAdmin” permissions in the destination OMG database. You can check and update permissions from the Atlas left-side security menu in the “Database Access” section.</p><p><strong>Figure 14.</strong> New Migration Job, Connect Source DB menu.</p><p>Once this is done, navigate to the “Data Migration” tab in the top navigation bar and click “Create sync job.” You will be prompted to add the source and destination database details. In our case, these are PostgreSQL and MongoDB, respectively. Fill in the details and click “Connect” in both steps until you get to the “Migration Options” step. In this menu, we will leave all options as default. This will migrate our data in snapshot mode, which means it will load all our data at once. Feel free to check our documentation for more <a href="https://www.mongodb.com/docs/relational-migrator/jobs/sync-jobs/">sync job</a> alternatives.</p><p><strong>Figure 15.</strong> New migration job, migration options menu.</p><p>Finally, click the “Start” button and wait until the migration is complete. This can take a couple of minutes. Once ready, you will see the “Completed” tag in the snapshot state card. You can now connect to your database in MongoDB Atlas or Compass and check how all your data is now loaded in MongoDB, ready to leverage all the advantages of the document model.</p><p><strong>Figure 16.</strong> Successful migration job message.</p><h2>Additional resources</h2><p>Congratulations, you’ve just completed your data migration! We&#39;ve not just simplified the data model of a standard insurance system; we&#39;ve significantly modernized how information flows in the industry.</p><p>On the technical side, MongoDB&#39;s Relational Migrator truly is a game-changer, effortlessly transforming an unwieldy 21-table schema into a lean five-collection MongoDB model. This translates to quicker, more efficient data operations, making it a dream for developers and administrators alike.</p><p>On the business side, imagine the agility gained—faster time-to-market for new insurance products, swift adaptation to regulatory changes, and enhanced customer experiences.</p><p>The bottom line? MongoDB&#39;s document model and Relational Migrator aren&#39;t just tools; they&#39;re the catalysts for a future-ready, nimble insurance landscape.</p>]]></description>
      <pubDate>Wed, 21 Oct 2026 11:27:10 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/modernize-your-insurance-data-models-mongodb-relational-migrator</link>
      <guid>https://www.mongodb.com/company/blog/innovation/modernize-your-insurance-data-models-mongodb-relational-migrator</guid>
    </item><item>
      <title>Building AI with MongoDB and Patronus AI</title>
      <description><![CDATA[<p>It is hardly headline news that large language models can be unreliable. For some use cases, this can be inconvenient. For others — especially in regulated industries — the consequences are way more severe. Enter <a href="https://www.patronus.ai/">Patronus AI</a>.</p><p>Patronus AI is a research lab developing training data and simulated environments for frontier AI. Its work spans reinforcement learning environments and digital world models for agents operating in software. The integration below reflects the company&#39;s earlier work in LLM evaluation.</p><p></p><p>Rebecca Qian, Patronus co-founder and CTO, explains, “Our platform enables engineers to score and benchmark LLM performance on real-world scenarios, generate adversarial test cases, monitor hallucinations, and detect PII and other unexpected and unsafe behavior. Customers use Patronus AI to detect LLM mistakes at scale and deploy AI products safely and confidently.”</p><p>In recently published and widely cited research based on the <a href="https://arxiv.org/abs/2311.11944">FinanceBench question answering (QA) evaluation suite</a>, Patronus made a startling discovery. Researchers found that a range of widely used state-of-the-art LLMs frequently hallucinated, incorrectly answering or refusing to answer up to <strong>81%</strong> of financial analysts’ questions! This error rate occurred <strong>despite</strong> the models’ context windows being augmented with context retrieved from an external vector store.</p><p>While <a href="https://www.mongodb.com/resources/basics/artificial-intelligence/retrieval-augmented-generation">retrieval augmented generation (RAG)</a> is a common way of feeding models with up-to-date, domain-specific context, a key question faced by app owners is how to test the reliability of model outputs in a scalable way. This is where Patronus comes in. The company has partnered with the leading technologies in the gen AI ecosystem — from model providers and frameworks to vector store and RAG solutions — to provide managed evaluation services, test suites, and adversarial data sets.</p><p>“As we assessed the landscape to prioritize which partners to work with, we saw massive demand from our customers for <a href="https://www.mongodb.com/products/platform">MongoDB Atlas</a>,&quot; said Qian. “Through our Patronus RAG evaluation API, we help customers verify that their RAG systems built on top of MongoDB Atlas consistently deliver top-tier, dependable information.&quot;</p><p>In its new <a href="https://www.patronus.ai/blog/the-10-minute-guide-to-reliable-rag-systems-using-patronus-ai-mongodb-atlas-and-llamaindex">10-minute guide</a>, Patronus takes developers through a workflow showcasing how to evaluate a MongoDB Atlas-based retrieval system. The guide focuses on evaluating hallucination and answers relevance against an SEC 10-K filing, simulating a financial analyst querying the document for analysis and insights. The workflow is built using:</p><ul><li><p>The LlamaIndex data framework to ingest and chunk the source pdf document</p></li><li><p><a href="https://www.mongodb.com/products/platform/atlas-vector-search">Atlas Vector Search</a> to store, index, and query the chunk’s metadata and embeddings</p></li><li><p>Patronus to score the model responses</p></li></ul><p>The workflow is shown in the figure below.</p><p>Equipped with the results of an analysis, there are a number of steps developers can take to improve the performance of a RAG system. These include exploring different indexes, modifying document chunking sizes, re-engineering prompts, and for the most domain-specific apps, fine-tuning the embedding model itself. Review the <a href="https://www.patronus.ai/blog/the-10-minute-guide-to-reliable-rag-systems-using-patronus-ai-mongodb-atlas-and-llamaindex">10-minute guide</a> for a more detailed explanation of each of these steps.</p><p>As Qian goes on to say, “Regardless of which approach you take to debug and fix hallucinations, it’s always important to continuously test your RAG system to make sure performance improvements are maintained over time. Of course, you can use the Patronus API iteratively to confirm.” To learn more about LLM evaluation, visit <a href="https://www.patronus.ai/company">Patronus</a>. </p><p></p>]]></description>
      <pubDate>Tue, 20 Oct 2026 18:00:13 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/how-patronus-automates-llm-evaluation-boost-confidence-genai</link>
      <guid>https://www.mongodb.com/company/blog/how-patronus-automates-llm-evaluation-boost-confidence-genai</guid>
    </item><item>
      <title>Introducing MongoDB Agents: Open Source Agent Templates for Atlas Agent Engine</title>
      <description><![CDATA[<p>Teams increasingly want agents that handle routine database work: checking cluster alerts, reviewing slow queries, and answering questions about a schema. But building agents takes much more than a prompt. It requires credential handling, access scoping, tool orchestration, approval flows, a chat integration, evaluation, observability, and ongoing testing and maintenance. That plumbing is easy to underestimate, and it&#39;s where much of the effort goes. </p><p>Today we&#39;re launching MongoDB Agents: a collection of open source agent templates that handle that setup for you. Each template combines the <a href="https://www.mongodb.com/products/tools/mcp-server">MongoDB MCP Server</a> and MongoDB Agent Skills with the plumbing you&#39;d otherwise build yourself: scoped MongoDB Atlas credentials, approval flows for writes, and a ready-to-run deployment configuration. You bring your own model API key, choose what the agent can access, and deploy it to <a href="https://www.mongodb.com/products/platform/atlas-agent-engine">Atlas Agent Engine</a>.</p><h2>What&#39;s included</h2><p><strong>MongoDB Agents launches with two templates: MongoDB Atlas Explorer for conversational questions and everyday workflows, and MongoDB Atlas Query Insights for slow-query reports on demand or on a schedule.</strong></p><p><strong>Atlas Explorer</strong> is a conversational agent for questions and everyday workflows across your MongoDB Atlas environment. It connects to Atlas through the <a href="https://www.mongodb.com/docs/mcp-server/tools/">MongoDB MCP server</a>, and when it needs specialist guidance—such as query optimization or schema design—it loads the matching <a href="https://www.mongodb.com/docs/agent-skills/">MongoDB Agent Skills</a>. </p><p>Teams can use the Atlas Explorer agent to:</p><ul><li><p>Ask an ad hoc question, such as “How many failed payments did we have today, by error code?” The agent will share an answer from the collections it can access.</p></li><li><p>See which clusters exist in a project, inspect their configurations, and find active alerts.</p></li><li><p>Settle practical questions like “Does this collection have an index on customerId?” or &quot;What fields does it contain?&quot;</p></li><li><p>Ask why a query is slow and which index would help.</p></li></ul><p><strong>Atlas Query Insights</strong> is a read-only agent that produces a slow-query report for one Atlas cluster. It uses the MongoDB MCP Server to pull recent slow query logs and suggested indexes from Performance Advisor.</p><p>This agent groups the logs into query shapes, ranks them by documents examined, working time, and execution count, and reports on the top recommendations. Each shape gets a plain-language overview and recommendations for areas worth investigating. </p><h2>How MongoDB Agents work</h2><p>Going from a template to a running agent takes three steps:</p><ol><li><p><strong>Start from a template.</strong> Fork or clone the agent from the <a href="https://github.com/mongodb/agents">GitHub repository</a>.</p></li><li><p><strong>Set its boundaries. </strong>Create an Atlas MCP configuration for one MongoDB Atlas project with the Atlas CLI. The roles you give that configuration decide what the agent can see and do, and the example grants read-only access. Then choose your model provider in the agent&#39;s configuration.</p></li><li><p><strong>Test and deploy.</strong> Try the agent in the Agent Engine Playground, store your credentials as platform secrets, and deploy with the `agentengine` CLI.</p></li></ol><p><strong>Figure 1. </strong>How a MongoDB Agent runs on Atlas Agent Engine.</p><p>As shown in the figure above, Atlas Agent Engine is the managed runtime. It stores Atlas credentials and model API keys as platform secrets, blocks outbound traffic to any host you haven&#39;t allowed, checkpoints each session so an agent can pause for approval and resume where it left off, and records traces of each run&#39;s model and tool calls. </p><h2>Built-in guardrails </h2><p>Agents that can see production data need clear limits. The templates ship with these guardrails in place:</p><ul><li><p><strong>Its own MongoDB Atlas identity.</strong> Each agent connects to Atlas through the <a href="https://www.mongodb.com/docs/mcp-server/overview/#mongodb-atlas-managed-mcp-server">Atlas MCP Server</a>. Configure each agent with its own programmatic identity for one Atlas project, and you choose its roles. The example configurations grant read-only access.</p></li><li><p><strong>Two opt-ins for writes: </strong>Atlas Explorer hides its write tools unless you turn on write operations, and Atlas rejects writes unless the credential is write-capable. Atlas Query Insights has no write tools. </p></li><li><p><strong>Approval for every write tool</strong>. When writes are enabled for Atlas Explorer, any tool that changes data or Atlas resources, such as creating an index or pausing a cluster, requires human approval. </p></li><li><p><strong>Restricted egress and no shell</strong>. Atlas Agent Engine blocks outbound traffic to any host not allowed in the agent&#39;s agent.yaml, and neither agent can run shell commands.</p></li></ul><h2>Use it where your team already works</h2><p>You can use the agents in the Agent Engine Playground or call them with the `agentengine` CLI. The repository also includes an optional Slack bot for Atlas Explorer. </p><p>The Slack bot offers users an example to learn from and adapt. You can host and operate it yourself, along with a MongoDB database for its thread state. The Slack bot is built on the popular open source <a href="https://chat-sdk.dev/">Chat SDK</a>, so you can adapt it to other supported platforms like Microsoft Teams and Discord.</p><p>The Slack bot is designed so that anyone on its allowlist can ask questions in a channel or DM, approve or reject writes they requested, and post read-only reports on a schedule with Slack Workflow Builder.</p><p><strong>Figure 2. </strong>Reviewing an Atlas Query Insights slow-query report in Slack and asking follow-up questions.</p><p><strong>Examples of what you can do with Slack:</strong></p><ul><li><p>Ask a question on demand: &quot;Which of my clusters have alerts?&quot;</p></li><li><p>Get a recommendation, then approve the change: &quot;Users often browse movies by genre and want the most recently released titles first. What index would you recommend?&quot; If writes are enabled, the agent can propose creating the index and wait for your approval in Slack before running it.</p></li><li><p>Schedule a read-only report with Slack Workflow Builder, such as &quot;Which production clusters have open alerts?&quot; every weekday at 9 am, or &quot;How many orders from the last 24 hours have no shipping address?&quot; every night.</p></li></ul><p><strong>A note on access in Slack</strong>: The Slack bot connects to Atlas with one shared identity, not each user&#39;s own Atlas permissions. Give it only the roles every allowlisted user should have. Only the person who requested a write can approve it.</p><h2>Before you deploy</h2><p>For now, MongoDB Agents can connect only to MongoDB Atlas (so not Enterprise Advanced, on-premises deployments, or Atlas for Government). Atlas Agent Engine is in Public Preview, so review the <a href="https://www.mongodb.com/docs/agentengine/reference/limitations/">Agent Engine limitations</a> before deploying. Each deployment shares one Atlas identity, which supports about 50 new conversations per hour across all of its users. See the <a href="https://www.mongodb.com/docs/agent-templates/">MongoDB Agents docs</a> for details.</p><p>Like any AI agent connected to your data, MongoDB Agents can be influenced by the content they read, including documents in your collections and messages in Slack. The built-in guardrails limit what an agent can do, but you decide what each agent can access. We recommend starting with a narrow, read-only scope and expanding it as you gain confidence. The MongoDB Atlas Explorer and Atlas Query Insights templates are built for Atlas Agent Engine, and open source and available under the Apache License, Version 2.0.</p>]]></description>
      <pubDate>Tue, 20 Oct 2026 16:00:25 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/product-release-announcements/introducing-mongodb-agents-open-source-agent-templates-atlas-agent-engine</link>
      <guid>https://www.mongodb.com/company/blog/product-release-announcements/introducing-mongodb-agents-open-source-agent-templates-atlas-agent-engine</guid>
    </item><item>
      <title>The Intelligent Data Platform for the AI Era</title>
      <description><![CDATA[<p>Some of you may have noticed a different, and perhaps familiar, name at the top of this post.</p><p>Following this week’s leadership change, the board asked me to step in as interim CEO. I led MongoDB for more than 11 years and have served on the board ever since, so I&#39;ve stayed close to our people, our customers, and the business. I’m happy to be back, and excited to share where MongoDB is headed next.</p><p>AI is undergoing an important transition. Models are getting better at reasoning, but the bigger change is what we’re asking them to do. AI is moving from generating answers to taking action. Software no longer just helps people do their work. Increasingly, agents do parts of the work themselves. They resolve customer issues, write and deploy software, execute business processes, and operate continuously with progressively less human intervention.</p><p>That shift has profound implications for the infrastructure underneath applications. An agent doesn’t simply take a prompt and return an answer. It observes what is happening, retrieves context, reasons about what to do, takes action, sees the result, and often starts the cycle again. As agents become more capable, these loops become longer, more autonomous, and more consequential.</p><p>Model quality matters enormously. But so does the quality, freshness, and accessibility of the data the model operates on. That is where MongoDB plays an important role.</p><p>Today, we’re announcing the largest expansion of our platform yet:</p><ul><li><a href="https://www.mongodb.com/company/newsroom/press-releases/mongodb-launches-mongodb-9-0-the-best-version-ever-built-and-atlas-infinite-for-ai-scale-demand"><strong>MongoDB 9.0</strong></a><strong> </strong>is<strong> </strong>the fastest, most performant version of MongoDB we’ve ever built, designed for applications and agents that act on live data.</li><li><a href="https://www.mongodb.com/company/newsroom/press-releases/mongodb-launches-mongodb-9-0-the-best-version-ever-built-and-atlas-infinite-for-ai-scale-demand"><strong>Atlas Infinite </strong></a>is a new deployment option built for highly elastic workloads, allowing storage and compute to scale independently as demand changes.</li><li><a href="https://www.mongodb.com/company/newsroom/press-releases/mongodb-launches-atlas-agent-engine-to-put-ai-agents-in-production-without-a-new-stack"><strong>Atlas Agent Engine</strong></a><strong> </strong>provides the memory, runtime, and governance needed to operate agents in production, on the same data foundation customers already trust and open to any model, framework, or cloud.</li></ul><p>Before I share more about what we’re doing, it’s worth explaining the problem we’re trying to solve.</p><h2>Why this moment demands more from the data layer</h2><p>Almost every data company now describes itself as a platform for AI. The more interesting question is what happens to the data architecture when AI stops just answering questions and starts taking actions. </p><p>Consider a customer-service agent deciding whether to issue a refund, a commerce agent promising delivery of an item, or a financial agent taking action on an account. The agent needs to know what is true right now. A model can reason perfectly over the information it has and still make the wrong decision if that information is stale. Yesterday’s inventory, an old account balance, or an outdated order status can turn a technically sound inference into a bad action.</p><p>That makes freshness much more important. For many agentic applications, periodically copying operational data into another system isn’t enough. Agents need access to the business&#39;s live state, and increasingly they need to act on that same state.</p><p>But having current data doesn’t solve the entire problem. An enterprise may have enormous amounts of potentially relevant information. The agent has to identify the small subset that matters for the decision it is making. Better retrieval improves the context presented to the model, reduces irrelevant tokens, and lowers the likelihood that the model has to infer what it doesn’t know.</p><p>This is why we believe operational data and retrieval are converging. MongoDB is already the operational system of record for some of the world’s largest enterprises and fastest-growing AI companies. With native search and vector search, together with <a href="https://www.voyageai.com/">Voyage AI’s</a> retrieval and embedding technology, developers can retrieve relevant context from the same live operational data their applications already use. You don&#39;t need to choose between operational data and AI context. Increasingly, they are the same thing. </p><p>Agents also create a very different workload. Traditional applications tend to have relatively understandable traffic patterns. Agentic systems can behave very differently. One user request may trigger a sequence of planning, retrieval, tool calls, database reads and writes, and additional reasoning. One agent may generate hundreds of operations. Thousands of agents may begin working concurrently.</p><p>As a result, the relationship between users and infrastructure consumption becomes far less predictable. Demand can be quiet one minute and enormous the next. Provision for the average and you risk falling over during a surge. Provision for the peak and you pay for infrastructure that sits idle much of the time.</p><p>We think the database architecture has to change with the workload. Compute should expand quickly when agents need it and contract when they don’t. Storage shouldn’t have to scale simply because compute does. And developers shouldn’t have to redesign their applications every time their workload crosses another threshold. That is the idea behind Atlas Infinite.</p><p>There is another architectural shift underway that I think is under appreciated. Useful agents are stateful.</p><p>They need to remember what has happened, retrieve what matters, understand who or what is taking an action, maintain context across interactions, and operate within explicit permissions and policies.</p><p>Today, developers often assemble that infrastructure themselves. They combine an operational database with a vector database, memory system, orchestration framework, model provider, and governance layer. Each additional system creates another integration point, another security boundary, and often another copy of the data.</p><p>That may be manageable for a prototype. It becomes much harder when agents take consequential actions inside a production enterprise.</p><p>We believe the state, memory, retrieval, and governance layer for agents should sit as close as possible to the operational data those agents act on. That is what Atlas Agent Engine is designed to provide.</p><p>Today&#39;s announcements build on MongoDB’s foundation.</p><h2>What we’re announcing today</h2><h3>MongoDB 9.0 </h3><p>Agents operating on live data put enormous demands on the database underneath them.</p><p>MongoDB 9.0 is the fastest, most performant version of MongoDB we’ve ever built. Compared with MongoDB 8.0, it delivers up to 2x higher throughput on large instances, 35% faster reads, and 30% faster updates, significantly improving price-performance at scale.</p><p>We’ve also continued to raise the bar on security, observability, and developer productivity. Queryable Encryption now protects more types of data in more situations, while expanded private networking in Atlas makes it easier for organizations in highly regulated industries to run their most sensitive workloads on MongoDB.</p><p>The goal is straightforward. As applications become more autonomous and operate at greater scale, the operational database underneath them has to become faster, more secure, and more efficient.</p><h3>Atlas Infinite</h3><p>Agentic workloads can be extraordinarily bursty and Atlas Infinite is designed around that reality.</p><p>It represents the biggest architectural change we’ve made to Atlas, allowing storage and compute to scale independently so customers can scale each according to what their workload actually requires.</p><p>The result is an architecture designed to grow from prototype to petabyte scale without forcing developers to predict tomorrow’s infrastructure requirements today. Time to scale is more than 96% faster, and each shard can hold 10x more storage.</p><p>Just as importantly, customers don’t have to rewrite their applications to use it.</p><p>Atlas Infinite is a new cluster type inside the Atlas platform developers already know. Customers can choose it alongside Atlas Core depending on the characteristics of their workload.</p><p>Public preview begins on AWS, with full multi-cloud availability planned for general availability (GA) .</p><h3>Atlas Agent Engine</h3><p>The hardest part of building an agent is no longer the demo, it’s operating the agent reliably in production.</p><p>Atlas Agent Engine brings the stateful infrastructure agents need onto the same data platform where their operational data already lives.</p><p>Built-in memory and retrieval give agents access to relevant, real-time context while reducing unnecessary token consumption. A unified control plane provides identity and governance over agent actions. And because Agent Engine is open to any model, framework, or cloud, developers can choose the AI stack that best fits their application rather than being locked into a single provider.</p><p>This particularly matters for enterprises.</p><p>More than 70,000 customers and over 75% of the Fortune 100 already trust MongoDB with their operational data. Atlas Agent Engine gives them a way to build and operate agents on that same foundation rather than creating an entirely separate data architecture for AI.</p><h2>The road ahead</h2><p>We are still early in this transition. Models will get better. Context windows will get larger. Inference will get cheaper. Agents will become more capable and autonomous. But none of these advances eliminate the need for high-quality operational data. They make it more important.</p><p>As software moves from systems that record what people do, to systems that help people decide what to do, to systems that increasingly take action themselves, the data layer becomes part of the control plane for the business.</p><p>That is the opportunity we are building MongoDB for.</p><p>The name at the top of this post may be familiar, but MongoDB is much more than its leader. It’s the product and engineering teams who continue to deliver meaningful innovation, the go-to-market teams who obsess over customer outcomes, and the customers who trust MongoDB with their most sophisticated and strategic applications.</p><p>I’m grateful to all of them for what went into today. See you tomorrow at .local NYC.</p>]]></description>
      <pubDate>Tue, 20 Oct 2026 13:24:15 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/product-release-announcements/intelligent-data-platform-for-ai-era</link>
      <guid>https://www.mongodb.com/company/blog/product-release-announcements/intelligent-data-platform-for-ai-era</guid>
    </item><item>
      <title>Composable Banking, Canonical Payments: A Foundation for Agentic Operations</title>
      <description><![CDATA[<p>Financial institutions face a critical challenge: legacy payment architectures are fragmented, rigid, and deeply siloed, making it difficult to adapt to new payment rails or build trustworthy systems for AI operations. To overcome these limitations, banks need an operational data foundation that decouples payment logic from tightly coupled legacy systems. MongoDB provides the unified document data layer required to implement composable capabilities and canonical payment models, enabling financial institutions to seamlessly evolve their payment operations while giving AI agents the trusted, real-time context necessary for reliable decision-making.</p><h2>Why these changes matter now</h2><p>Every new payment rail, standard, regulatory requirement, or customer expectation can introduce another data model, integration, and processing path. Agentic AI adds another dimension. Banks are exploring systems that reason over payment information, investigate exceptions, and assist operations teams. But adding AI to a fragmented payment environment does not make the architecture less fragmented — it just gives the fragmentation a faster, more confident way to fail.</p><p>We&#39;ve written before about the <a href="https://www.mongodb.com/company/blog/innovation/unlocking-agentic-power-to-modernize-cross-border-payment-systems">canonical payment model as a way to preserve context across ISO 20022</a>, legacy formats, cross-border rails, and about the agentic patterns — resolution agents, human-in-the-loop repair — that can act on that context once it exists. This blog is about the layer underneath both of those: the business-capability architecture that determines whether a canonical model and its agents stay coherent as the bank keeps changing, or risk becoming one more thing to untangle in five years.</p><p>That&#39;s where composability, and specifically the Banking Industry Architecture Network (BIAN) standard, comes in.  And it’s not just a concept for future use. It&#39;s being built out now directly in our current reference implementation.</p><h2>The challenge: Fragmentation across the payment lifecycle</h2><p>A payment may look like a simple journey to the customer, who may not even think about what goes through once they hit send. But behind the scenes, that payment can span many systems. After a customer initiates a payment, the bank puts it through a series of steps in which it:</p><ul><li><p>Authenticates the request and checks entitlements and limits</p></li><li><p>Validates and enriches the instruction</p></li><li><p>Determines how it should be executed</p></li><li><p>Sends it to the appropriate payment rail</p></li><li><p>Records the financial impact</p></li><li><p>Reconciles the transaction against clearing and settlement information</p></li></ul><p>Conceptually, it appears as one lifecycle. Technically, each stage may involve different systems, data structures, and processing models.</p><p>Wires, internal transfers, ACH, and cards can each introduce different schemas and integrations. When rich payment information is forced through rigid schemas or repeated transformations, context gets lost. If the information an agent needs is scattered across applications, assembling trusted context becomes another integration problem before it&#39;s ever an AI problem.</p><p>The challenge then isn&#39;t just connecting more systems. It&#39;s building an architecture where payment capabilities can evolve without continually increasing complexity.</p><h2>The architectural response: composable capabilities, a canonical model</h2><p>Composable architecture organizes around reusable business capabilities rather than individual payment products or applications. BIAN provides a framework for defining those capabilities independently from the systems that implement them, such as initiation, orchestration, execution, and reconciliation.</p><p>Each capability has a defined responsibility while participating in the same payment journey, moving across capabilities without becoming one tightly coupled application.</p><p>BIAN defines the business architecture rather than prescribing a physical database schema. This is a common vocabulary and set of capability boundaries that leaves institutions free to determine how those capabilities are implemented and evolved. </p><p>These capabilities become more powerful when they share a consistent representation of the payment moving between them. That&#39;s the canonical model&#39;s job. It gives every payment a common business vocabulary and identity throughout the lifecycle, covering the debtor, creditor, amount, currency, account information, status, and processing metadata. Each rail then extends that core with its own attributes, since a wire needs information an internal transfer doesn&#39;t, and ACH and cards add more. The canonical model isn&#39;t just a translation mechanism. It&#39;s the operational representation of the payment as it progresses through the lifecycle, changes state, and accumulates context. It shows which validations ran, what was enriched, which execution path was chosen, what came back from the rail, and how any exception was resolved.</p><h2>BIAN alignment in practice: One payment and one capability</h2><p>It&#39;s easier to see how this holds together with an actual payment moving through a single capability boundary than to describe it in the abstract.</p><p>Let&#39;s consider orchestration. The term is used to describe the <a href="https://bian.org/servicelandscape-14-0-0/views/view_53431.html">BIAN Payments Hub</a> stage responsible for submitting a validated, approved payment to the appropriate <a href="https://bian.org/servicelandscape-14-0-0/object_16.html?object=47741">payment rail</a> within its applicable timing constraints. This capability reads the canonical payment document, tracks elapsed time against the internal cutoff for that rail and value date, and either submits the payment or raises an exception. It doesn&#39;t own how the payment was validated upstream or how it&#39;s later reconciled. That separation is what lets the bank change cutoff policy for one payment type without touching anything else.</p><p>Here&#39;s what that looks like for one payment: A USD international wire completes authentication, validation, screening, and approval at 6:22 p.m. ET—seven minutes past Leafy Bank&#39;s 6:15 p.m. ET internal cutoff. Under a traditional setup, it would simply roll to next-business-day processing. Instead, the capability writes a cutoff-exception event into the payment&#39;s accumulating context: which stage it was in, how long it had been there, and that the external Fedwire pacs.008 cutoff of 6:45 p.m. ET remains open even though the internal cutoff was missed. The payment&#39;s canonical status moves to an exception state, without another capability needing the timing details.</p><p>That accumulated context gives the agent a specific basis for action, not a generic exception signal. A cutoff risk and exception management agent can read the canonical document and its history, confirm that approvals and screening are complete, weigh the remaining external window against what submission still requires, and recommend expedited same-day processing rather than an automatic deferral—with human review (HITL) mandatory where policy requires it. The agent never has to reconstruct what happened by querying five different systems; the capability boundary already made that context legible.</p><p>Another benefit can show up later, when the bank adds a new rail. ACH or cards can be introduced by extending the canonical representation, and composing all the capabilities (including execution) into the new lifecycle, rather than standing up a parallel validation stack. The capability’s responsibility has not changed, only its rule set has. This is composability doing its actual job... Change becomes localized to the capability and the schema extension, not systemic.</p><h2>MongoDB: The data foundation underneath both</h2><p>This is where MongoDB goes beyond an operational data layer. The document model can concurrently hold a lot, from canonical fields to processing metadata, without forcing every payment into a rigid structure, and the model can evolve as standards and payment types do.</p><p>A few platform capabilities are particularly relevant here:</p><ul><li><p><strong>Flexible data model</strong>:<em> </em>Structured, semi-structured, and contextual information coexist in a <a href="https://www.mongodb.com/docs/manual/data-modeling/">document model</a> that evolves with new payment types and new capabilities, without migrations forcing a redesign.</p></li><li><p><strong>Search and semantic retrieval</strong>: MongoDB Search supports lexical and fuzzy retrieval; <a href="https://www.mongodb.com/docs/vector-search/">MongoDB Vector Search</a> enables semantic matching. With this, an agent can find similar historical exceptions, not just exact ones.</p></li><li><p><strong>Real-time, event-driven processing</strong>: <a href="http://mongodb.com/docs/manual/changestreams/">Change streams</a> allow workflows and agents to react to a payment&#39;s state change—like the validation-failure event above—the moment it happens, rather than on a batch cycle.</p></li><li><p><strong>Consistency and auditability</strong>:<em> </em><a href="https://www.mongodb.com/docs/manual/core/transactions">Multi-document transactional support</a> keeps operational and audit updates atomic, so an agent&#39;s proposed and approved changes are as reliable as any other posting.</p></li></ul><p><strong>Figure 1</strong>. Canonical payments model with MongoDB.</p><p>MongoDB isn&#39;t just where the payment sits. It&#39;s also the layer where the capability boundaries, the canonical representation, and the agent&#39;s context all meet—governed by the same access controls, encryption, and audit trail throughout.</p><h2>How canonical payment context supports agentic operations</h2><p>Banks have started exploring agentic AI for reasoning over payment information, investigating exceptions, and assisting operations teams, as noted above. Recall the cutoff exception from &quot;orchestration.&quot; Once that event lands in the payment&#39;s context, a cutoff risk and exception management agent can read the canonical document and its history. At this stage, it can identify whether the delay reflects normal variance or a specific blocker such as a pending approval. It will then propose an action grounded in what actually happened and how much time remains—without creating a generic exception ticket. Human review stays in the loop where policy requires it, and once approved, the payment resumes through the lifecycle deterministically.</p><p>None of that works if the agent is reasoning over data it isn&#39;t authorized to see, or that isn&#39;t verifiably up to date; that’s a governance question we&#39;re treating in depth elsewhere. At the data layer, MongoDB Atlas <a href="https://www.mongodb.com/docs/manual/security/">encrypts and access-controls</a> the underlying data. Every agent action is logged alongside the payment&#39;s own audit trail, allowing agent-assisted steps to be traceable the same way any other posting is.</p><p><strong>Figure 2</strong>. Agentic payment operations.</p><h2>How composable capabilities isolate future payment changes</h2><p>The practical value of this approach is that change stays local. A wire and an internal transfer can share initiation, validation, and a canonical identity from day one, diverging only where the rail requires it. ACH and cards extend the model later without creating another silo. A cutoff risk and exception management agent scoped to wires today can be handed approved tools for reconciliation or broader exception analysis tomorrow, capability by capability, rather than through a platform rewrite.</p><p>The future of payments won&#39;t be defined by one rail, standard, or AI model. BIAN separates banking responsibilities into composable capabilities. The canonical model gives those capabilities a shared representation of payment intent and lifecycle. MongoDB provides the flexible, secure operational and agentic data foundation underneath both.</p><p>A modern payments architecture shouldn&#39;t only be designed to process today&#39;s payments. It should be designed for the future that is right around the corner.</p>]]></description>
      <pubDate>Mon, 19 Oct 2026 16:24:15 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/composable-banking-canonical-payments-foundation-agentic-operations</link>
      <guid>https://www.mongodb.com/company/blog/innovation/composable-banking-canonical-payments-foundation-agentic-operations</guid>
    </item><item>
      <title>How to Encrypt LangGraph Checkpoints With MongoDB CSFLE</title>
      <description><![CDATA[<p>Would you trust an AI agent if a database administrator could read every message in its session? For a customer-facing chatbot, that reality already feels unsettling. Even if you trust your internal operators, plaintext checkpoints remain equally readable to anyone who gains database access during a breach.</p><p>Deploying agents into production requires more than equipping them with the right tools and context: it also requires securing the state they persist as they operate, to safeguard end-user data and satisfy security and regulatory requirements.</p><p>This post demonstrates how <a href="https://www.mongodb.com/docs/manual/core/csfle/">MongoDB Client-Side Field Level Encryption</a> (CSFLE) can be leveraged to encrypt LangGraph checkpoints before they are written to the database. The application can decrypt the state when it needs to resume a run, while anyone with no access to the encryption keys will only see ciphertext instead of the sensitive payload.</p><h2>What you’ll build</h2><p>By the end of this post, you will have a coding example of how to extend LangGraph’s <em>CipherProtocol</em> to encrypt checkpoint state with MongoDB CSFLE and store the encrypted payload through <em>MongoDBSaver</em>.</p><p>The example uses explicit CSFLE with AWS Key Management Service (AWS KMS). You can adapt the KMS provider configuration for Azure Key Vault, Google Cloud KMS, or KMIP by following the provider-specific PyMongo configuration.</p><h2>What you need before you start</h2><p>This example assumes that you have:</p><ul><li><p>A MongoDB deployment and a connection string.</p></li><li><p>A key vault namespace for CSFLE data encryption keys.</p></li><li><p>A data encryption key (DEK) with the alternate name langgraph_csfle_key.</p></li><li><p>KMS credentials available through your runtime environment.</p></li></ul><p>For DEK creation, key-vault configuration, credentials, and key rotation, view the <a href="https://pymongo.readthedocs.io/en/stable/api/pymongo/encryption.html">PyMongo encryption API</a> and <a href="https://www.mongodb.com/docs/manual/core/csfle/fundamentals/manage-keys/">CSFLE encryption key management</a>.</p><h2>Why encrypt the LangGraph checkpoint state?</h2><p>In the LangGraph framework, checkpointers persist a snapshot of graph state at each step. That persisted state lets an agent resume a run after a failure and supports human-in-the-loop workflows. Those snapshots can include user messages, tool results, and anything else the agent accumulated on the thread. <em>MongoDBSaver</em> persists that state in collections such as <em>checkpoints</em>, which is how you get resumable sessions when you <a href="https://www.mongodb.com/docs/atlas/ai-integrations/langgraph/build-agents/">build an AI agent with LangGraph and MongoDB</a>. MongoDB has also documented why checkpointers matter for production agent applications in <a href="https://www.mongodb.com/company/blog/innovation/checkpointers-native-parent-child-retrievers-with-langchain-mongodb">Checkpointers and native parent-child retrievers with LangChain and MongoDB</a>.</p><p>If those documents contain confidential customer details, employee records, or medical context, the checkpoint collection is a high-value target. Role-based access control, encryption at rest, and TLS still matter, but they do not stop a privileged database user (legitimate or not) from reading the documents if they are stored in plaintext.</p><h2>What does MongoDB CSFLE protect?</h2><p>MongoDB <a href="https://www.mongodb.com/docs/manual/core/csfle/">Client-Side Field Level Encryption</a> (CSFLE) encrypts data in the application before it leaves the client, so the values of encrypted fields are never visible to the database engine. This gives you a set of practical benefits:</p><ul><li><p>A database user without access to the encryption keys will not be able to read the encrypted fields.</p></li><li><p>The MongoDB driver integrates with AWS KMS, Azure Key Vault, Google Cloud KMS, or a KMIP-compliant key store, so developers do not have to build and harden a custom KMS client.</p></li><li><p>Envelope encryption separates a customer master key (CMK) in your KMS from data encryption keys (DEKs) stored in a key vault collection, with APIs for rotation and rewrapping.</p></li></ul><p>MongoDB drivers support two types of CSFLE: automatic encryption, where a JSON schema tells the driver which fields to encrypt and decrypt, and explicit encryption, where the client application calls encrypt and decrypt primitives directly for the fields that need to be encrypted. We will use explicit CSFLE in this example.</p><h2>Why Base64 encoding doesn’t protect checkpoint state</h2><p>Out of the box, LangGraph serializes checkpoints and <em>MongoDBSaver</em> stores the bytes as BSON Binary. In a database client such as MongoDB Compass, the payload looks like <em>Binary.createFromBase64(...)</em>. Base64 is a machine-friendly encoding, but it is not encryption: anyone who can read the document can decode it without a key. The goal of this example is to replace that reversible representation with ciphertext produced by CSFLE.</p><p><strong>Figure 1.</strong> A LangGraph checkpoint stored by MongoDBSaver without CSFLE.</p><h2>How to use CSFLE with LangGraph’s EncryptedSerializer</h2><p>LangGraph’s <em>EncryptedSerializer</em> already provides an extension point for a custom cipher. Its built-in AES factory requires an encryption key as an input. That approach can work for a simple demonstration, but a production design also needs envelope encryption, key-vault storage, KMS integration, and key rotation.</p><p>As the <a href="https://docs.langchain.com/oss/python/langgraph/checkpointers#encryption">LangGraph checkpointer documentation</a> notes, it is possible to change the default AES cipher of an <em>EncryptedSerializer</em> by writing a custom implementation of <em>CipherProtocol</em>: the proposed implementation leverages MongoDB CSFLE to implement checkpoint encryption and decryption.</p><h3>Configure the MongoDB encryption handler</h3><p>The handler owns the MongoDB client and the explicit CSFLE client. It reads connection and credential values from environment variables and uses the DEK’s alternate name to encrypt the serialized payload.</p><p>When initializing the <em>ClientEncryption</em> object, it is possible to choose between different encryption algorithms. In particular:</p><ul><li><p>Deterministic encryption is appropriate when an application needs equality queries on an encrypted field, but it can reveal frequency patterns;</p></li><li><p>Randomized encryption produces different ciphertext for the same plaintext and provides stronger confidentiality.</p></li></ul><p>This example encrypts the serialized checkpoint payload as an opaque value and does not query inside it, for this reason it uses randomized encryption. </p><h3>Implement CipherProtocol</h3><p>The <em>CipherProtocol</em> adapter is intentionally small. LangGraph passes serialized bytes to <em>encrypt</em> and passes the stored cipher name and ciphertext back to <em>decrypt</em>.</p><h3>Construct and invoke the encrypted checkpointer</h3><p>The next block creates the serializer and passes it to MongoDBSaver. The model is shown only to make the example complete; use the model integration appropriate for your agent.</p><h2>What remains queryable after encryption?</h2><p>Inspecting the LangGraph checkpoint collection in MongoDB Compass confirms that the checkpoint payload, including user messages and agent responses, is successfully encrypted.</p><p>Depending on your LangGraph and MongoDBSaver versions, routing and serializer metadata (such as thread IDs, checkpoint IDs, and namespaces) may remain visible. Because the runtime relies on these fields to locate and resume checkpoints, you must ensure your application does not include Personally Identifiable Information (PII), especially within the <em>thread_id</em>.</p><p>Keep in mind that LangGraph always persists checkpoint data as a binary blob, regardless of encryption. By design, this means the payload cannot be used as a query filter. If your use case requires encrypted application data to remain queryable (supporting equality, range, prefix, suffix, or substring queries), you can leverage MongoDB Queryable Encryption instead. See the <a href="https://www.mongodb.com/docs/manual/core/queryable-encryption/">MongoDB Queryable Encryption documentation</a> for details.</p><p><strong>Figure 2.</strong> The checkpoint collection after CSFLE is integrated with LangGraph’s EncryptedSerializer.</p><h2>Key takeaways</h2><p>LangGraph checkpoint state can contain sensitive messages and tool results, so storing the payload in cleartext (base64 in the default implementation) may not be aligned with the security or compliance requirements of many enterprise use cases.</p><p>By connecting <em>EncryptedSerializer</em> to a custom <em>CipherProtocol</em> implementation, the LangChain framework can leverage MongoDB CSFLE to encrypt the checkpoint payload before <em>MongoDBSaver</em> persists it. MongoDB continues to provide durable checkpoint storage and routing metadata, while KMS-backed encryption protects the serialized content from database readers who lack decryption access.</p>]]></description>
      <pubDate>Thu, 15 Oct 2026 14:00:01 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/technical/how-to-encrypt-langgraph-checkpoints-csfle</link>
      <guid>https://www.mongodb.com/company/blog/technical/how-to-encrypt-langgraph-checkpoints-csfle</guid>
    </item><item>
      <title>Enriching Product Catalogs For Agentic Commerce Discovery with MongoDB</title>
      <description><![CDATA[<p>Retail discovery is moving from clicks and filters to a conversation an AI agent conducts on a customer’s behalf. A customer may ask an AI answer engine like ChatGPT or Gemini for a carry-on bag that fits a 16-inch laptop and has strong sustainability credentials. They may instruct an AI agent to watch for price drops in high-end bean-to-cup coffee machines. The products selected by AI agents in those scenarios will not be based on the most persuasive product description on a retailer’s website or even on a slew of customer reviews. Instead, AI recommendations will favor products that can be systematically retrieved, understood through rich context, and compared across surfaces for consistency.</p><p>The urgency is already emerging. McKinsey estimates that AI agents could orchestrate $3 trillion to $5 trillion globally by 2030, while Bain estimates 30% to 45% of U.S. consumers already use AI answer engines to research products. Research on generative engine optimization (GEO) has demonstrated visibility gains of up to 40% when content is made more legible to AI systems. For retailers, this creates a new discoverability challenge where product data must be: </p><ol><li><p>Rich enough for AI systems to reason over </p></li><li><p>Consistent across every surface the retailer publishes product data to </p></li><li><p>Fast enough to serve inbound agentic commerce traffic.</p></li></ol><p>The need to be recommended ahead of competitors’ offerings makes AI discovery a product-data challenge, one that MongoDB is positioned to help retailers solve. Retailers need a single, context-rich catalog that can project its products to three distinct surfaces: </p><ul><li><p>Outbound product feeds used by AI answer engines </p></li><li><p>Agentic commerce endpoints that support inbound requests for live catalog data sent by autonomous AI agents </p></li><li><p>Structured data on product detail pages (PDPs). </p></li></ul><p>MongoDB’s <a href="https://www.mongodb.com/solutions/use-cases/artificial-intelligence">AI-ready data platform</a> provides the foundation. It offers a flexible document model for enriched agentic context, real-time synchronization to keep operational data current, and integrated keyword, vector, and hybrid retrieval to help AI agents find the right products.</p><p>The retailers that gain a sustainable competitive advantage in the agentic commerce era will build machine-readable, enriched product catalogs as a foundation, making it easier for AI agents to evaluate and recommend. Focusing on three priorities can help retailers achieve that goal.</p><h2>1. Enrich the catalog with the context agents need to reason</h2><p>Traditional product catalogs often prioritize the fields needed to render a product detail page: title, image, price, and availability. Those remain essential, but they are no longer sufficient. An AI agent also needs the facts and relationships that answer an intent-shaped question. That means it needs to know what the product is suitable for, what it works with, how it compares with alternatives, and which policies or reviews support the recommendation.</p><p>A practical enrichment model has three tiers:</p><ol><li><p>Tier one establishes identity and transactability with fields such as GTIN, SKU, brand, price, currency, condition, availability, and canonical URLs.</p></li><li><p>Tier two makes products filterable using structured attributes such as dimensions, materials, capacity, compatibility, ingredients, certifications, and care instructions. </p></li><li><p>Tier three adds agentic context: use cases, frequently asked questions, compatible accessories, substitutes, fit guidance, sustainability attributes, returns and shipping policies, ratings, review summaries, and semantic embeddings.</p></li></ol><p>MongoDB’s <a href="https://www.mongodb.com/docs/manual/data-modeling/">document model</a> can help answer those questions. A product is naturally a richly nested object, not a collection of unrelated rows that must be reassembled on every request. Retailers can represent core attributes, variants, offers, policies, relationships, and agentic context together in the same JSON-like format that is the lingua franca of agentic commerce. Frequently used, feed-critical fields can be strongly typed and indexed, while long-tail category attributes can be modeled flexibly without creating a new schema for every product type.</p><p>The business outcome created by tier three data is an improved likelihood of being matched to a shopper’s intent and included in AI-generated shortlists. Highlighting facts also reduces ambiguity when an AI answer engine compresses a catalog into a comparison table or a product card.</p><h2>2. Make every discovery surface a projection of one live catalog</h2><p>AI agents can discover products through two paths. On the indexed path, third-party AI platforms ingest structured data from PDPs and product feeds, then reason over their own product index. On the programmatic path, an AI agent calls a retailer’s API or model context protocol (MCP) server for live catalog, offer, inventory, or policy data.</p><p><strong>Figure 1.</strong> The enriched product catalog is discovered via two paths: the indexed path and the programmatic path.</p><p>Retailers should support both paths, but without having to create separate, independently maintained catalogs for each. The recommended pattern is to establish an enriched product catalog in an <a href="https://www.mongodb.com/resources/solutions/use-cases/implementing-an-operational-data-layer">operational data layer (ODL)</a> and project it consistently to three machine-readable surfaces: product feeds for AI platforms; REST APIs and/or MCP for direct agent access; and schema.org JSON-LD on PDPs.</p><p>MongoDB helps make that single-source-of-truth approach practical. <a href="https://www.mongodb.com/resources/products/capabilities/change-streams">Change streams</a> and <a href="https://www.mongodb.com/resources/basics/what-is-stream-processing">stream processing</a> can propagate updates from systems such as PIM, ERP, pricing, inventory, and reviews into a canonical product representation. <a href="https://www.mongodb.com/resources/products/capabilities/aggregation-pipeline">Aggregation pipelines</a> can then reshape that representation for the exact contract required by an outbound product feed, an API response, or a schema.org Product payload on a PDP.</p><p>That consistency matters because AI agents cross-check signals. If a price, availability state, or product identifier disagrees between a product feed and a PDP, confidence falls. A product catalog that is rich in one channel, but stale in another will be less discoverable than a simpler catalog that is accurate everywhere. With MongoDB, the same operational data can drive each projection, while change events keep downstream surfaces aligned as product and inventory conditions change.</p><h2>3. Design for semantic retrieval and inbound agentic traffic</h2><p>Once products are visible, AI agents need to retrieve the right candidates quickly. Their queries are likely to be continuous, automated, and shaped around intent rather than exact keywords. “A carry-on that fits a 16-inch laptop” or “A high-end bean-to-cup coffee maker” requires a combination of literal filtering and semantic matching.</p><p>MongoDB brings keyword, vector, and hybrid search together with the operational product document. <a href="https://www.mongodb.com/products/platform/atlas-search">MongoDB Search</a> can retrieve on explicit fields, while <a href="https://www.mongodb.com/products/platform/atlas-vector-search">MongoDB Vector Search</a> can match the meaning of a query against product context and embeddings. <a href="https://www.mongodb.com/docs/vector-search/crud-embeddings/automated-embedding/">Automated embedding</a> helps keep those embeddings synchronized as relevant product data changes, reducing the risk that the semantic representation describes an older version of the product.</p><p><strong>Figure 2.</strong> Three surfaces have consistent product representations, with tier-three agent context and vector embeddings in the enriched catalog driving semantic discovery.</p><p>The same foundation also supports the performance requirements of inbound agentic traffic. Autonomous agents will expect low latency, high availability, and current data when they request a catalog response. A retailer should not expose fragmented systems of record directly to that traffic or depend on a long chain of synchronous joins to assemble a product at request time. An ODL architecture creates a governed intermediary that is optimized for the consumers that need fast, reliable access.</p><p><a href="https://www.mongodb.com/resources/basics/role-based-access-control#role-based-access-control-in-mongodb">MongoDB’s role-based access control (RBAC)</a> and the native <a href="https://www.mongodb.com/products/tools/mcp-server">MongoDB MCP server</a> provide a path to governed, programmatic access for inbound agentic traffic. This enables retailers to safely expose selected discovery features directly, ensuring AI agents retrieve accurate, up-to-date catalog data without compromising system performance or exposing backend operational systems.</p><p>The goal is to create a durable product data foundation that can adapt as platforms, protocols, and consumer behavior evolve in the agentic commerce era. A flexible document model, real-time synchronization, integrated retrieval, and scalable access are useful whether discovery happens through an outbound product feed today, an MCP interaction tomorrow, or a new agentic commerce standard that emerges in the future.</p><h2>Enrich your product catalog for agentic discovery</h2><p>Agentic commerce is changing the product catalog from a publishing asset into an operational system. Retailers must enrich product data with the context AI agents’ value, keep that context reconciled across product feeds, PDPs, and APIs, and serve it with the speed and reliability that agentic traffic demands. The alternative is becoming invisible to the agentic commerce systems that are increasingly filtering, comparing, and deciding which products get presented to consumers.</p><p>MongoDB is built for modern AI use cases, such as agentic commerce. Its flexible document model keeps enriched product representations similar to the way AI agents consume them in a changing landscape. <a href="https://www.mongodb.com/resources/products/capabilities/change-streams">Change streams</a>, <a href="https://www.mongodb.com/resources/basics/what-is-stream-processing">stream processing</a>, and <a href="https://www.mongodb.com/resources/products/capabilities/aggregation-pipeline">aggregation pipelines</a> keep projections to AI surfaces current and consistent. <a href="https://www.mongodb.com/products/platform/atlas-search">MongoDB Search</a> and <a href="https://www.mongodb.com/products/platform/atlas-vector-search">Vector Search</a> support an AI agent’s literal and intent-based product discovery goals, while governed access supports production at enterprise scale.</p><p>Retailers that make their catalogs machine-readable, context-rich, and consistent across AI-mediated surfaces will be better set up to thrive in the agentic commerce era, regardless of which AI answer engines, autonomous agents, or agentic commerce protocols mediate the shopping journey. The strategic path to agentic commerce discoverability is being paved today. By updating product catalog capabilities to meet the needs of AI-mediated surfaces, retailers can gain a lasting advantage in the rapidly advancing agentic commerce landscape.</p>]]></description>
      <pubDate>Tue, 13 Oct 2026 19:34:26 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/enriching-product-catalogs-for-agentic-commerce-discovery</link>
      <guid>https://www.mongodb.com/company/blog/innovation/enriching-product-catalogs-for-agentic-commerce-discovery</guid>
    </item><item>
      <title>MongoDB Extension for Hibernate ORM is Now GA</title>
      <description><![CDATA[<p>The MongoDB Extension for Hibernate ORM is now generally available, giving Java teams a production-ready way to use familiar Hibernate APIs with MongoDB’s document model. It is a first-party, open-source library that enables Java applications to use MongoDB as the backing database via the Hibernate ORM. The extension allows Java developers to enjoy the same experience with MongoDB, reducing the friction for those who want to switch. </p><p>Java developers can continue using @Entity annotations, Hibernate Query Language (HQL), Criteria Queries, and Session APIs while building new applications or migrating existing Hibernate workloads from relational databases to MongoDB.</p><p>The GA release adds support for JOINs (INNER and LEFT OUTER), optimistic locking, Spring Boot auto-configuration, and clearer exception messaging and logging. </p><p>The extension requires an upgrade to Hibernate ORM 7.4 LTS to run.</p><p>Read on to learn more about these features and how they can help Java developers.</p><h2>What are the key features in the GA version of the MongoDB Extension for Hibernate ORM?</h2><p>Now, Java developers using Hibernate have the best of both worlds: they can use familiar Hibernate paradigms for entity operations, queries, and more, while enjoying the flexibility to evolve their schema over time that comes with building on MongoDB. </p><p>The extension now supports key features: </p><ul><li><p><strong>JOIN support (INNER and LEFT OUTER): </strong>Query across related MongoDB collections using standard HQL/JPQL `JOIN` syntax, with no manual lookups required.</p></li><li><p><strong>Optimistic locking: </strong>Version-based concurrency control (`@Version`) prevents conflicting updates to the same entity.</p></li><li><p><strong>Spring Boot auto-configuration: </strong>Dialect and connection provider are auto-detected from your MongoDB JDBC URL, so manual overrides aren’t needed.</p></li><li><p><strong>Improved exception messaging and logging: </strong>Clearer error messages and structured logging make issues easy to diagnose, right out of the box.</p></li><li><p><strong>Native embedded documents for faster reads: </strong>Nest objects and collections inside a single document for higher read performance and a more intuitive data hierarchy.</p></li><li><p><strong>Familiar JPA annotations: </strong>Use the same annotations and patterns you already know, bridging the document model with standard JPA semantics.</p></li><li><p><strong>Query using Hibernate&#39;s query languages and MongoDB&#39;s Query API: </strong>Write queries in HQL/JPQL, including JOINs, comparison operators, and nested paths, or drop into <em>MongoDB&#39;s native Query API</em> for advanced operations like vector search, geospatial queries, and MongoDB Search.</p></li></ul><h2>Why build your Java applications with MongoDB and Hibernate?</h2><p>As an ORM framework for Java, Hibernate was created to map object-oriented Java code to relational databases while accommodating their constraints. For example, a Java object with a nested list of properties can&#39;t be stored as-is in a relational table; it has to be broken apart into separate, normalized tables linked by foreign keys, and reassembled through joins every time it&#39;s read back. This allowed Java developers to focus more on writing code and less on the tedious, often error-prone process of translating their Java objects into relational persistence.</p><p>However, while Java developers building with Hibernate can get a more intuitive experience when working with relational databases, using Hibernate cannot eliminate the core constraints of relational data models, including the difficulty of evolving schemas and handling different data types. As modern applications evolve, they demand support for changing data structures, a capability that can be difficult to implement in relational databases.</p><p>When developers need to modify the schema (like adding a new column to a table or introducing a new relationship), they must perform a schema migration. This requires careful consideration of data dependencies (like foreign keys), default values for existing rows (or NULL values), and the performance impact of altering large tables.</p><p>MongoDB provides developers with the flexibility they need through its document model, while still allowing them to maintain schema control where needed. For example, Java developers can design suitable data models for their applications and easily add new fields or make other changes to their data schema thanks to the document model. Developers no longer need to predefine a row-and-column structure. They can then enforce the schema using MongoDB&#39;s <a href="https://www.mongodb.com/docs/manual/core/schema-validation/">built-in schema validation</a>.</p><p>Moreover, MongoDB also makes it easier to store and manage various types of data—from simple text and numbers to complex embedded documents and arrays—all within a single database. </p><h2>Under the hood: How the Extension talks to MongoDB</h2><p>To explain how this extension works, let’s look at a code example:</p><p>With the new MongoDB Extension, Hibernate can map your entities to MongoDB collections and automatically transform common operations, such as persist, find, and HQL queries, into MongoDB commands. For instance, consider a straightforward HQL query like:</p><p>The MongoDB dialect translates the query into an equivalent MongoDB aggregation pipeline, such as: </p><p>This translation occurs transparently; developers continue to use Hibernate’s familiar API while the framework generates the corresponding <a href="https://www.mongodb.com/docs/manual/reference/mql/">MongoDB Query API</a> commands under the hood.</p><h2>Get started with the MongoDB Extension for Hibernate</h2><p>The integration is straightforward—simply add the extension to your project&#39;s build setup and configure Hibernate to use it. Follow this getting-started <a href="https://www.mongodb.com/docs/languages/java/mongodb-hibernate/current/get-started">guide</a> for a step-by-step walkthrough.</p><p>For more technical information about this extension, please refer to our <a href="https://www.mongodb.com/docs/languages/java/mongodb-hibernate/">documentation</a>.</p><h2>Providing feedback</h2><p>While the extension covers the most common Hibernate patterns for building and migrating production applications, we haven&#39;t aimed for full HQL coverage; some SQL constructs simply don&#39;t map to MongoDB&#39;s document model, and that&#39;s by design. For everything else, we&#39;d love to hear what&#39;s missing for your use case. You can suggest new features or vote on existing ideas at the <a href="https://feedback.mongodb.com/?category=7548141831345841376">MongoDB Feedback Portal</a>, or reach out directly to your MongoDB account team</p>]]></description>
      <pubDate>Tue, 13 Oct 2026 14:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/product-release-announcements/extension-for-hibernate-orm-now-ga</link>
      <guid>https://www.mongodb.com/company/blog/product-release-announcements/extension-for-hibernate-orm-now-ga</guid>
    </item><item>
      <title>Building the Agentic Ecosystem: Partner Updates from MongoDB.local NYC</title>
      <description><![CDATA[<p>Building AI applications has never been easier. Making them reliable in production remains the real challenge.</p><p>That’s because agents need more than intelligence - they need the right context, access to real-time data, and the controls to act with confidence.</p><p>The next generation of agentic software will be built across an ecosystem—the systems businesses run on, the applications people use, and the tools developers already build with. That is why we’re actively building this next generation with partners from day one, rather than bolting an ecosystem on afterward.</p><p>Today at MongoDB.local NYC, we launched the next chapter of our intelligent data platform, with partners front and center.</p><h2>Building the agentic ecosystem with Atlas Agent Engine</h2><p>Atlas Agent Engine, <a href="https://www.mongodb.com/company/newsroom/press-releases/mongodb-launches-atlas-agent-engine-to-put-ai-agents-in-production-without-a-new-stack">announced</a> this week in Public Preview, gives enterprises a single foundation for building, deploying, and governing AI agents. We’re building it with the partners who are already helping enterprises navigate their most important technology shifts.</p><p>Six of the leading global systems integrators are launching with us: <a href="https://www.accenture.com/en">Accenture</a>, <a href="https://www.capgemini.com/us-en/">Capgemini</a>, <a href="https://www.cognizant.com/us/en">Cognizant</a>, <a href="https://www.infosys.com/">Infosys</a>, <a href="https://www.tcs.com/">Tata Consultancy Services (TCS)</a>, and <a href="https://www.techmahindra.com/">Tech Mahindra</a>. They are building Atlas Agent Engine into the AI offerings they already take to market, backed by the industry depth, delivery muscle, and client relationships they have spent decades earning. </p><p>That delivery foundation is complemented by a broader ecosystem of technology partners. Atlas Agent Engine is neutral across models and frameworks, so enterprises can use the technologies they already trust and adapt as the market evolves. Customers can choose their preferred authentication and security tools to keep agents safe, while technology partners like <a href="http://arize.com/">Arize AI</a> help make those agents production-ready with trace monitoring.</p><p>That combination matters because getting agents into production is rarely a technology problem alone. It takes people who know an industry well enough to know which decisions an agent should be trusted with, and who are already in the room when enterprises make them.</p><p>It also changes where MongoDB shows up. Our partners are building agentic practices, training delivery teams, developing reference architectures, and shaping enterprise offerings across key markets worldwide. When those teams build on Atlas Agent Engine, that capability travels with them, extending MongoDB’s reach to more customers and industries than we could reach alone.</p><p>MongoDB provides the intelligent data and agent platform. Partners bring the expertise, workflows, and reach that help put the platform to work with all the tools that enterprises know and love. Together, we are building a production path for enterprise agents alongside some of the strongest ecosystem partners out there.</p><h2>Modernizing enterprise applications with Cognition’s Devin</h2><p>Agents cannot act on data that is trapped behind legacy infrastructure. Before most enterprises can put an agent to work, they have to modernize the code tying that infrastructure together.</p><p>We’re taking on that challenge in partnership with <a href="https://cognition.com/">Cognition</a>. This week, we <a href="https://www.mongodb.com/company/newsroom/press-releases/cognition-and-mongodb-partner-to-modernize-enterprise-infrastructure-in-months-not-years">announced</a> Devin for MongoDB Modernizations, a new offering leveraging Cognition’s AI software engineer to help customers modernize their systems and realize value from MongoDB faster and easier.</p><p>Now, Devin connects to MongoDB&#39;s Application Modernization Platform (AMP), giving it direct access to AMP&#39;s migration tooling. Those tools move and validate data into MongoDB Atlas, giving joint customers a faster, more automated path from legacy code to production on Atlas.</p><p>Modernization has two parts: rewriting business logic and data-access layers, and moving the underlying data. Devin handles the code, planning, and rewriting the business logic and data access layers case by case, while AMP’s deterministic tooling handles the data itself, moving and validating each record into MongoDB. Devin orchestrates the full process end-to-end, so customers get one coordinated migration instead of a patchwork of scripts and manual handoffs. In early joint testing, work that had taken five to six hours finished in a little over one.</p><p>What stays with the human engineers are the decisions that shape the outcome: how to model the data on the other side, and when to cut over. Teams get to production on Atlas in months rather than years, with their engineers freed up for what comes next.</p><h2>Meeting developers where they build</h2><p>AI is changing not only what developers build, but how they build it. Increasingly, an application starts as a prompt. We want MongoDB to be there from that first prompt all the way through production, which is why we’re excited to announce three new partnerships that extend that reach.</p><p><a href="https://app.emergent.sh/landing/"><strong>Emergent</strong></a> helps builders turn a natural-language idea into a working AI application, now with Atlas as their default database. Through this partnership, builders on Emergent will be able to connect their Atlas account and ship with MongoDB through Emergent from the first prompt, rather than stumbling into the database decision after the fact.</p><p><a href="http://monk.io"><strong>Monk.io</strong></a> is a universal software operator, available as a plugin inside popular coding agents with MongoDB Atlas now as the target data layer. Customers can leverage coding agents such as Claude Code, Codex, and SpaceXAI to write the code, while Monk deploys and operates the application—including the Atlas data layer—in customers’ accounts, taking care of provisioning and networking to backups and recovery. Monk maintains a live map of the application and its infrastructure, executes changes deterministically, keeps credentials hidden from agents, enforces organizational permissions for every action, and requires human approval outside the agent’s chat for costly or destructive changes—giving joint customers more ways to run applications safely.</p><p><a href="https://retool.com/"><strong>Retool</strong></a> gives teams a secure, governed way to use AI to build internal tools on the data their business already runs on. MongoDB has been a first-class Retool integration for years, and now Retool Cloud customers can connect directly to Atlas and provision scoped access without manually managing credentials. Together, we’re making it easier to ship apps on real business data without trading away the security and control enterprises need.</p><p>Emergent, Monk.io, and Retool join a much broader ecosystem extending MongoDB across the models, frameworks, tools, and services that make AI applications useful in the real world.</p><h2>A vision for the ecosystem</h2><p>None of this is a collection of one-off integrations. It is a deliberate recognition that the agentic era<em><strong> is</strong></em> the ecosystem era.</p><p>The enterprises that get agents into production over the next few years will not do it alone, and neither will we. They will succeed alongside partners who already understand their industry, their systems, and their data—on a foundation that does not force them to bet everything on a single model, cloud, or framework.</p><p>To every partner and sponsor with us at MongoDB.local NYC today: <strong>thank you</strong>. You are the reason this is an ecosystem story and not just a product story. We are only getting started.</p>]]></description>
      <pubDate>Tue, 13 Oct 2026 12:22:06 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/events/building-agentic-ecosystem-partner-updates-from-mongodb-local-nyc</link>
      <guid>https://www.mongodb.com/company/blog/events/building-agentic-ecosystem-partner-updates-from-mongodb-local-nyc</guid>
    </item><item>
      <title>Building a Culture of Growth: MongoDB&#39;s Massive Opportunity in APAC</title>
      <description><![CDATA[<p>MongoDB’s go-to-market organization in APAC has grown rapidly, nearly tripling in size over the past three years. In this article, learn more about MongoDB’s opportunity in APAC and how we build a culture of growth and accountability.</p><h2>MongoDB&#39;s opportunity in Asia-Pacific</h2><p>Five of the world’s top 13 economies by GDP are located in APAC: China, Japan, Australia, India, and South Korea. The ASEAN countries alone represent more than 650 million people.</p><p>This regional scale, combined with the size of the worldwide database market, creates a significant opportunity. IDC estimates that the database market will grow to $137 billion in 2027, while MongoDB has reached $1 billion in annual recurring revenue. This provides a sense of the opportunity available to MongoDB globally and across APAC.</p><p>Almost every company is becoming a technology company—and, as a result, every company is becoming a data company. MongoDB is well positioned to support that transformation as an intelligent data platform.</p><p>MongoDB has already captured thousands of customers around the world, but the shift to cloud computing and modern application development is still in its early stages. Unlike many software categories, the database is mission-critical for organizations. As digital transformation continues, MongoDB has an opportunity to help customers use software and data to innovate, create, and disrupt industries.</p><p>One example is <a href="https://www.mongodb.com/solutions/customer-case-studies/cathay-pacific">Cathay Pacific</a>, Hong Kong’s home airline carrier. Its digital team used MongoDB to build Flight Folder, an application that consolidates dozens of information sources into one place and supports a paperless flight deck. Since its launch, Cathay Pacific has completed more than 340,000 flights with full digital integration in the flight deck.</p><h2>Building a team across regions and cultures</h2><p>Our APAC team is unique because of the different markets and cultures within the region. We go to market differently in India than we do in Australia, and differently in Singapore than we do in South Korea. Each market is different, but each presents a significant opportunity.</p><p>In APAC, we have established business leaders who run regionalized teams in India, ASEAN, and ANZ, with all functions reporting to them. These teams operate as their own businesses and implement local best practices into their strategies.</p><p>That does not mean they operate in silos. At the leadership level, there is significant collaboration and sharing of experiences to identify what is working and what is not across each region. We also have a global sales organization that provides extensive training and best practices to help local teams support customers and grow the business.</p><h2>Culture</h2><p>The most important thing is culture.</p><p>We have a high standard for everything we do and how we interact with one another. We do not entertain politics. While new skills can be taught and people can be coached to succeed in new roles, alignment with our culture is essential. That is why culture is the most important aspect of the hiring process.</p><p>When the culture is right, everything else starts to fall into place. At MongoDB, our culture is shaped by <a href="https://www.mongodb.com/company?utm_campaign=simon_apac_blog&amp;utm_source=mongodb_blog&amp;utm_medium=life_at_mongodb">six core values</a>. One of the values that is particularly important to our APAC team is “Embrace the Power of Differences.”</p><p>APAC includes a wide range of cultural identities and nuances. These differences can influence values, beliefs, and go-to-market strategies. It is important that everyone on the team respects the cultures of the regions where we operate.</p><p>Across APAC and our global teams, leadership has taken people on a journey to understand and embrace cultural differences. The role of our leaders is to develop our teams from the bottom all the way up. That includes MongoDB’s <a href="https://www.mongodb.com/company/blog/culture/bdr-to-cro-empowering-our-salespeople-career-path">BDR to CRO career development initiative</a>, which is designed to help develop the next generation of leaders.</p><p>For APAC, development means coaching every team member on the cultural nuances needed to lead people and go to market across the region, regardless of where they are from.</p><p>It is also important that every team member contributes to a culture of psychological safety. Working at a high-growth technology company requires taking risks and making mistakes. We hold one another accountable and maintain high standards, but never at the expense of creating an environment where people are afraid to fail.</p><p>When someone experiences a setback, we encourage them to share it so that we can learn collectively. Through mutual support, we build a stronger team that is capable of delivering exceptional results.</p><h2>The future of MongoDB in Asia-Pacific</h2><p>For any organization to be successful, the entire ecosystem needs to act as one. At MongoDB, our country ecosystems are aligned around a shared set of goals rather than operating in different directions.</p><p>Teams are willing to support one another and do what is needed to build a great business. In APAC, we are one team.</p><p>That means sales, marketing, customer success, solutions consulting, and professional services working together to focus on three things: making customers successful, building technical champions, and driving new workloads.</p><p>As we continue to grow MongoDB’s team and footprint in the region, these three priorities will drive our success.</p><p>There is a huge opportunity for MongoDB in APAC. While hiring has slowed or stopped at many organizations, MongoDB continues to invest in the region. Our APAC go-to-market team has nearly tripled in size over the past three years, and we have open roles across functions and regions.</p><p></p>]]></description>
      <pubDate>Mon, 12 Oct 2026 16:16:17 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/culture/building-culture-growth-svp-mongodb-massive-opportunity-apac</link>
      <guid>https://www.mongodb.com/company/blog/culture/building-culture-growth-svp-mongodb-massive-opportunity-apac</guid>
    </item><item>
      <title>MongoDB 9.0&#39;s Observability Capabilities: Less Hunting, More Resolving</title>
      <description><![CDATA[<p>Modern applications generate telemetry across every layer of the stack, but understanding what changed and why often remains difficult. Database signals frequently live in separate workflows, forcing teams to switch between dashboards, correlate disconnected data, and piece together performance issues without the full operational context.</p><p>With <a href="https://www.mongodb.com/company/blog/product-release-announcements/mongodb-9-0-this-is-what-a-database-should-be">MongoDB 9.0</a>, we’re making it easier to understand database behavior and accelerate troubleshooting. Now we’re introducing three observability enhancements that help teams move from detection to diagnosis faster:</p><ul><li><p><strong>OpenTelemetry enhancements</strong> that bring Atlas metrics, logs, and events into the observability tools engineering teams already use.</p></li><li><p>A redesigned <strong>Metrics UI</strong> that provides a clearer, cluster-level view of health and performance.</p></li><li><p><strong>Query Shape Insights</strong> for write operations, extending query-level diagnostics beyond reads.</p></li></ul><p>Together, these <a href="https://www.mongodb.com/products/capabilities/observability">observability capabilities</a> help teams spend less time hunting for answers and more time resolving issues, optimizing performance, and maintaining reliable applications.</p><h2>Bring MongoDB Atlas telemetry into the observability stack</h2><p>When critical database context lives in separate systems, troubleshooting can require switching tools and manually piecing together what’s changed; MongoDB Atlas helps close that gap by bringing database telemetry into the observability workflows teams already use. Now, Atlas Events Integration provides teams with a new source of operational context.</p><p><a href="https://www.mongodb.com/docs/atlas/export-logs-external-sinks/">Atlas Events Integration</a> enables customers to export Atlas Activity Feed events—including cluster modifications, user management changes, network access updates, and project or organization configuration changes—to <a href="https://www.mongodb.com/docs/atlas/tutorial/otel-integration/?otel-integration-type=custom">OpenTelemetry-compatible</a> destinations and other supported integrations. By making these events available alongside existing observability data, teams can better understand not only that something changed, but what changed.</p><p>Combined with MongoDB Atlas metrics and log integrations, teams can correlate performance issues with the operational activity that may have contributed to them. For example, a latency spike can be viewed alongside recent configuration changes, access updates, or scaling events, helping teams move more quickly from symptom to root cause.</p><p>Together, metrics, logs, and events provide a more complete picture of database operations. The result is a more connected observability experience that helps teams troubleshoot faster, reduce operational complexity, and gain the context needed to resolve issues with confidence.</p><h2>A simpler way to understand cluster health</h2><p>External integrations help teams bring Atlas into a broader observability strategy. The <a href="https://www.mongodb.com/docs/atlas/metrics-ui-rollout/">new Metrics UI</a> makes it easier to understand cluster health directly in Atlas.</p><p>The redesigned experience replaces a fragmented metrics workflow with a single unified view of cluster metrics. Metrics are presented in a clearer, cluster-level experience, with node selectors that help users focus on the systems relevant to an investigation.</p><p>This matters when time is limited. Platform engineers, SREs, and DBAs should not have to navigate across multiple pages to build a picture of cluster behavior. Application developers and engineering leads should be able to map an application symptom to the relevant Atlas signal without needing to become observability specialists. A more consistent workflow helps both groups spend less time searching and more time diagnosing.</p><p><strong>Figure 1.</strong> The redesigned Atlas Metrics UI provides a unified view of cluster performance and health, with streamlined navigation, cluster-level metrics, and node selection controls.</p><p>The new experience is also designed to provide a stronger foundation for future coverage of metrics and more reliable service. Existing links to the legacy experience continue to work through redirects, and surrounding workflows, including third-party integrations, Atlas Admin API metrics endpoints, alert delivery, billing, and Performance Advisor or Query Insights, are not changed by the UI refresh.</p><h2>Query Shape Insights now covers writes</h2><p>Application performance is shaped by both reads and writes. While read visibility is critical, inefficient write operations can also drive latency, consume excess resources, and increase infrastructure costs. With Atlas clusters running MongoDB 9.0 and later, <a href="https://www.mongodb.com/docs/atlas/query-shape-insights/#view-metrics-in-charts-and-tables">Query Shape Insights</a> now supports insert, update, and delete operations, giving teams a more complete understanding of how query patterns affect workload performance.</p><p>With write support, teams can:</p><ul><li><p>Identify inefficient update and delete operations, including unindexed filters and large updates.</p></li><li><p>Analyze the impact of writes using metrics such as <em>Docs Matched</em>, <em>Docs Modified</em>, <em>Docs Upserted</em>, <em>Docs Inserted</em>, and <em>Docs Deleted</em>.</p></li><li><p>Examine write-related index activity, including <em>Keys Inserted</em> and <em>Keys Deleted</em>.</p></li><li><p>Use CPU Time and other performance metrics to understand resource utilization and reduce unnecessary infrastructure costs.</p></li><li><p>Filter and investigate query behavior across replica sets and sharded clusters.</p></li></ul><p>On MongoDB 9.0 and later, Query Shape Insights uses a lightweight 1% random sample of read and write operations. This provides visibility into production workloads with low overhead. Note that displayed totals reflect only the sampled operations — roughly 1% of the actual workload—not the full volume. Query shapes that run infrequently may not appear.</p><p>Query Shape Insights groups operations by shape — capturing the structure of the query without its specific values—so thousands of individual queries collapse into a handful of shapes. Teams can identify recurring workload patterns, connect performance issues to the queries driving them, and validate the impact of indexing or application changes.</p><p>Available for dedicated Atlas clusters running MongoDB 8.0 and later, Query Shape Insights provides a more complete view of workload behavior and, with MongoDB 9.0, a faster path to optimizing both reads and writes.</p><h2>Observability that fits the way teams operate</h2><p>As applications grow more distributed and operational environments become more complex, teams need observability tools that provide both visibility and context.</p><p>MongoDB 9.0 helps organizations integrate database telemetry into existing observability workflows, simplify performance investigations within MongoDB Atlas, and better understand the query patterns that affect application performance.</p><p>Whether you’re routing Atlas metrics, logs, and events into your broader observability platform, investigating cluster health directly in Atlas, or optimizing read and write workloads with Query Shape Insights, the goal is the same: helping teams move faster from detecting an issue to understanding its cause and taking action. Observability isn’t just about collecting signals—it’s about turning those signals into operational insight.</p>]]></description>
      <pubDate>Mon, 12 Oct 2026 14:46:51 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/product-release-announcements/9-0-observability-capabilities-less-hunting-more-resolving</link>
      <guid>https://www.mongodb.com/company/blog/product-release-announcements/9-0-observability-capabilities-less-hunting-more-resolving</guid>
    </item><item>
      <title>The Ground Beneath the Database</title>
      <description><![CDATA[<p><em>From attached disks to a shared, elastic foundation—the story of disaggregating MongoDB and turning a database you manage into one you consume.</em></p><h2>Summary</h2><p><em>On September 29th, </em><a href="https://www.mongodb.com/company/newsroom/press-releases/mongodb-launches-mongodb-9-0-the-best-version-ever-built-and-atlas-infinite-for-ai-scale-demand"><em>MongoDB announced the public preview of Atlas Infinite</em></a><em>, the largest architectural innovation in MongoDB Atlas ever, built on disaggregated storage: compute and storage run on separate machines. Holding no data of their own, compute nodes become ephemeral and stateless. Durability, replication, and page serving move into a shared storage layer built from three services: a Log Service that reaches consensus on every write, a Page Service that keeps materialized pages warm in every zone, and an Object Index Service managing object storage underneath as the durability floor. From an application’s perspective, the wire protocol, the drivers, and the semantics do not change. </em></p><p><em>With independently scaled storage decoupled from compute, storage scalability becomes virtually unlimited. Read replicas come up without the need to copy a disk. Vertical scaling can swap compute atop the same storage. Snapshots, clones, and restores become forks of a log: constant time, zero copy, at any database size.</em></p><p><em>The shared layer does all of this without the ability to read your data. Pages are encrypted on your compute node before a byte is handed down, with keys that can stay yours. This post covers the architecture. The next two posts will cover how a storage fleet operates on data it cannot understand, and what it takes inside the database engine to live without an attached disk.</em></p><h2>Prologue</h2><p>In October 2024, six weeks into my tenure at MongoDB, I found myself in a meeting with fellow server and support engineers, drawing straws. The data growth in a large MongoDB Atlas cluster had been accelerating. Now, that is great news: this is the problem you strive to have! However, our back-of-the-envelope estimate for storage expansion came to several days. The desired answer would have been several minutes. The question on the table was who would go and tell this to the customer.</p><p>I’ve thought about that meeting a lot. The database was behaving as designed. Like every traditional database, standard MongoDB Atlas is architected with <em>coupled storage</em>: each database node has its storage tightly bound to its compute. </p><p>It was this coupling that was in the way, because <em>storage has gravity</em>. </p><p>Data doesn’t want to move. The bigger it gets, the harder it pulls down. Anyone who has managed a large database knows the symptoms: scaling a cluster, resharding, rebalancing, restoring from backup, and adding a read replica. They are slow. They are slow because they all reduce to the same storage-shaped primitive: copy a very large amount of data from one place to another. Nothing about better software makes a terabyte weigh less. </p><p>And because compute and storage are coupled, regardless of whether you need more storage or more compute, you get more of both.</p><p>So we ask the obvious question: if the problem at hand is tight coupling, then would decoupling be the answer? </p><p>Turns out the answer is yes. And that answer is Atlas Infinite, a new deployment option within MongoDB Atlas, launched in public preview at <a href="https://www.mongodb.com/company/newsroom/press-releases/mongodb-launches-mongodb-9-0-the-best-version-ever-built-and-atlas-infinite-for-ai-scale-demand">on September 29th at MongoDB’s Investor Day</a>. This post examines it in detail: what we set out to make possible; the architecture Atlas runs today and the disaggregated one we launched; the life of a write and of a read through the new machinery; what an append-only history buys you; what happens when things break; and the one line we would not cross to get any of that.</p><p>Decoupling is how a database stops being infrastructure you manage and starts being a capability you consume. But that&#39;s the marketing promise—here&#39;s the machinery that makes it real.</p><h2>A peek under the hood</h2><p>How do you move storage out from under a highly optimized, lock-free, parallel storage engine with non-deterministic, speculative eviction? Carefully.</p><p>Commercial databases built on decoupled compute and storage have existed for at least a decade. So it is reasonable to ask, &quot;Why did it take MongoDB this long, and what’s new here?&quot; The honest answer is that the properties that make our storage engine fast are exactly the ones that make it hard to pull apart—and that we refused to change it in ways that would give up the performance or the security our customers already had.</p><p>Besides, our customers have always had horizontal scale-out. When a workload outgrew a machine, sharding was the natural succession: one that several disaggregated architectures in the market lacked until recently. That freedom bought us the room to get this right rather than ship it first.</p><h2>The challenge</h2><p><a href="https://www.mongodb.com/docs/manual/core/wiredtiger/#wiredtiger-storage-engine">WiredTiger™</a> is one of the most sophisticated storage engines in production. It earns its speed by <em>deferring and batching</em> work. It is built around <strong>checkpoint-based consistency</strong>: rather than logging each page modification, <em>blow by blow</em>, it lets writes accumulate in memory. A page can absorb many mutations and get written to disk just once, at a checkpoint. This amortizes the cost of turning writes into a readable state, and it is increasingly where the field is heading, with modern engines converging on copy-on-write, multi-version, checkpointed designs precisely because of their efficiency. Something WiredTiger has been doing for years.</p><p>The decade-old mainstream disaggregation designs work by shipping a <em>physical redo log </em>that is obligated to record <em>every</em> change to a page, so the shared storage tier can reconstruct an arbitrary page version. Adopt that directly, and you’d have traded WiredTiger’s core efficiency for the newfound elasticity.</p><p>Furthermore, conventional disaggregation relies on the shared storage layer to read, compose, and rewrite your data in the clear. That is something we rejected. In Atlas Infinite, if your data is unencrypted cleartext, it is not shared. And if it is shared, it sure ain’t clear. We don’t hold cleartext in a shared service. Period.</p><p>The final wrinkle: because WiredTiger is lock-free, parallel, and evicts pages speculatively, two nodes holding identical logical data will not hold identical bytes on disk. Layout depends on timing, eviction order, and allocation state, so there is no canonical page image to ship and no single layout for copies to converge to. &quot;Replicate the pages&quot; has no well-defined target.</p><p>This is where being MongoDB helped. We are the one company with its hands on the whole stack: the storage engine, the database server, and the cloud that runs it. We didn&#39;t have to bolt disaggregation on from the outside and work around the engine—we could reach into the engine. This is what allowed us to solve something sharper than the textbook problem: keep WiredTiger&#39;s deferred, batched writes intact, keep the storage layer completely blind to customer data, and still deliver read replicas that lag the primary by milliseconds, not by checkpoint intervals. None of the existing recipes delivers all three at once. </p><p>The rest of this series is about what we had to invent to get there. We’ll take a glimpse at MongoDB Atlas Core’s architecture, followed by an in-depth look at the Atlas Infinite design, service decomposition, write and read paths, as well as how they inform our security, durability, availability, and performance: SDAP—the yardsticks by which we measure everything we do. Subsequent posts will expand further into the security and durability aspects in particular. </p><p>Let&#39;s start with a brief look at Atlas Core.</p><h2>MongoDB Atlas Core: The attached-storage architecture</h2><p>A MongoDB cluster is a replica set: three nodes, each a complete, self-sufficient machine. Each node holds a full copy of the data on its own attached disk. Each stays in step with the others by replicating the <em>oplog: </em>our logical operation log, from a primary to its secondaries. If the primary fails, a secondary is elected to replace it. Every node is doing every job: durability, availability, and serving queries, all bound together in the same box. It is shared-nothing. Its simplicity affords a near absolute security and isolation model: it simply relies on virtual private cloud (VPC) and virtual machine (VM) guaranteed isolation. One tenant’s actions cannot bleed into another.</p><p>But because compute and storage live on one machine, anything you want to do to the data, you have to do to the machine. Scaling reads means cloning an entire node before it can answer a query. High availability means paying for full physical copies that mostly stand and wait. Growing a node means rebuilding it and warming a cold cache. The design is simple, robust, and cleanly isolated tenant-from-tenant, and it makes every storage-shaped operation an act of moving the whole machine.</p><p><strong>Figure 1. </strong>MongoDB Atlas Core: Three<strong> </strong>nodes across zones A/B/C, each a <em>mongod</em> bound to its own full-copy disk, joined by oplog replication.</p><h2>Atlas Infinite: The disaggregated architecture</h2><p>We took a design so simple—three nodes in a replica set—and replaced it with at least fourteen! Database nodes, log nodes, page materializers, and page serving nodes. That sounds like the wrong direction, until you notice who runs them: not you. The cluster goes from three machines doing every job to fourteen sharing the work – extra hands, not extra burden. Managing data is hard. But done right, managing a million times more data is not a million times harder. Disaggregation splits the architecture into two halves.</p><p>The <strong>compute layer</strong> runs the database duties: parsing queries, running transactions, and handling aggregations. The change is that it becomes ephemeral and without storage: it becomes <em>weightless</em>. It offloads its other duties (oplog replication, consensus, page copying, and backups) to the storage layer. In place of Atlas Core’s three full replicas, Atlas Infinite runs a <em>primary</em> database node, <em>a standby node</em> for high availability, and optionally, additional read replicas for read scaling. Just as with Atlas Core, the compute layer runs isolated in its own VPC.</p><p>The <strong>storage layer </strong>is made up of multi-tenant <em>storage layer services, </em>responsible for managing storage for that “million times more data.” The machinery here is sophisticated, as we&#39;ll see. But none of it is yours to run. From the customer&#39;s side of the glass, storage is simply managed by MongoDB. </p><p>This layer consists of three main services: the Log Service, the Page Service, and the Object Index Service, each able to scale, fail, and recover independently. The entire storage layer was purpose-built from the ground up in Rust. </p><p><strong>The Log Service</strong> is the shortest path to durability. Every write becomes an append to a replicated log. The service does exactly one thing: reach consensus on the log. And a service that does exactly one thing can do it with verifiable correctness, higher performance, and a tighter tail latency than one juggling durability alongside the full duties of a database.</p><p><strong>The Page Service </strong>is a pool of page servers holding the materialized pages in each zone, serving page reads. A new compute node reads from a cache that is already warm instead of cloning a disk of its own. Every log’s pages are distributed across many page servers in each zone, so a read spike is absorbed across many instead of hammering one. This is the moment the fleet can finally bring more than one node&#39;s worth of muscle to bear on a single customer&#39;s workload.</p><p>A <strong>Page Materializer </strong>reads entries being written to the log and distributes them to the <em>page server group</em> responsible for that log. In parallel, it does one more thing: it continuously spools the log onto object storage.</p><p><strong>Object Index Service and Object Storage</strong>—S3, Google Cloud Storage, Microsoft Azure Blob—sits underneath as the durability floor: designed to provide eleven nines, continuously maintained, the bottom of the world. Object storage is organized and managed by an Object Index Service, and access is mediated by an Object Read Proxy, which can answer the same shape of read queries as a page server—except from object storage. This is what allows us to deliver continuous data protection, time travel, and fast backups and restores.</p><p>Through all this, the front door does not move. Same wire protocol, same drivers, same read and write semantics. The application cannot tell the difference. Everything that changed is underneath it.</p><p><strong>Figure 2.</strong> Atlas Infinite: Ephemeral compute on top, over three shared services—Log Service (consensus/durability), Page Service (shared warm cache), Object Storage (durability floor)—spanning zones A/B/C.</p><h3>Control plane and heat management</h3><p>I won&#39;t get into the details in this blog, but suffice it to say that the storage layer services are all provisioned, monitored, and heat-managed by control plane services that ensure automated fault tolerance and recovery as well as load spreading and tail-at-scale operations.</p><h3>Scale anything independently</h3><p>A quick reality check: if compute and storage are really separate, three operations that were expensive in the coupled world should become cheap without special-casing. Let&#39;s have a look.</p><p><strong>Adding a read replica is zero-copy.</strong> In MongoDB Atlas Core, a secondary needs to clone a full copy of the disk before it can answer a single query, which is where the wait comes from. In Atlas Infinite, the data was never on the node to begin with. A new compute node starts up, tails the committed oplog from the Log Service to catch up to the present, and reads its pages from the shared Page Service, whose cache is already warm. Its cost is bounded by the length of the oplog tail rather than the size of the database, so it is serving reads in seconds regardless of how large that database is.</p><p><strong>Vertical scaling swaps the compute without touching storage.</strong> In Atlas Core, resizing a node means standing up a bigger machine and then waiting out a cold cache, because both the cache and the data live on the machine you are replacing. In Atlas Infinite, they don’t. A larger compute node launches, takes over as primary, and the old one steps aside. Nothing moves, and nothing has to re-warm, and the swap closes in under a minute.</p><p><strong>Storage performance scales on its own axis.</strong> With attached storage in Atlas Core, IOPS are a property of the attached disk. In Atlas Infinite, IOPS scale with the storage pool rather than with any one disk. If a workload is storage-bound, you request more throughput or more IOPS, and the storage layer grants it, with no need to touch compute at all.</p><p>The common thread, and the real test of the design, is that each of these touches only the layer that has to change, and its cost scales with the size of that change rather than the size of the database. </p><h3>A deeper dive into the write path</h3><p>Let us take a closer look at the life of a single write. With consensus and replication delegated to the Log Service, and the separation of durability from readability, there is a lot happening on the write path.</p><p>A write arrives at the primary. The first thing that happens, as always, is that the primary appends an entry to the <strong>oplog</strong> describing what changed. That record goes to the Log Service, which replicates it across the three zones, and the write is acknowledged the instant a majority of the log replicas hold it durably.</p><p>As the storage engine settles its pages in the ordinary course of checkpointing, it emits a second, physical log we call the <strong>phylog</strong>. Where the oplog says <em>what changed</em> in logical terms, the phylog carries the physical manifestation of the change: page images, and far more often, page <strong>deltas</strong>. </p><p>The standby and read replicas are clients of the Log Service and tail the log. At the same time the page materializer—one in each zone—tails the log as well, and distributes the phylog records across the page servers.</p><p>The page servers receive the phylog records, organize images and deltas by page, and store them on fast, directly attached drives.</p><p>In parallel, the page materializer uploads both the oplog and the phylog to object storage.</p><p>Notice the shape of everything downstream of the primary: logs—append-structured, versioned, immutable. Hold on to that; it is about to pay off. </p><p><strong>Figure 3.</strong> Life of a write: critical path solid (client→primary→log→ack); async phylog + materialization dashed.</p><h3>The read path and solving standby lag: Layered tables</h3><p>The read path on the primary is ... uninteresting, in that it is substantially the same as before. On the standby and read replicas, it gets interesting.</p><p>Checkpoint-based consistency in WiredTiger means that durable page state only moves forward at checkpoint boundaries. That&#39;s bad news for a standby or read replica that reads only materialized pages: it would trail the primary by as much as a full checkpoint interval: multiple <em>seconds</em>. That is a deal-breaker for a read replica serving reads. We wanted replica lag measured in milliseconds.</p><p>We accomplish this by layering two tables. Underneath sits the <strong>stable table</strong>: the checkpoint-consistent, shared, materialized data, the same page state the primary authors as it checkpoints. On top of it sits an <strong>ingest table </strong>(more a <em>table cloth</em>, really), into which the standby applies the oplog as it arrives. The ingest table holds the recent tail of changes—the writes that have landed since the last checkpoint the standby <em>adopted</em>. As newer checkpoints arrive and the stable table catches up, the standby garbage-collects the now-redundant entries from its ingest table, keeping the tail bounded.</p><p>A read composes both. The stable table supplies everything settled as of the last checkpoint. The ingest table supplies the fresh changes on top. Together, they give the standby a current, consistent view without waiting for the primary to publish its next checkpoint. That is what turns standby lag from a checkpoint-interval problem into an oplog-replication-lag one, measured in milliseconds.</p><h3>Branching logs and ancestry</h3><p>At the end of the write path I asked you to hold on to one property: everything downstream of the primary is a log, append-structured and versioned, immutable. Here is where that pays off.</p><p>When history is an append-only log, the storage-shaped operations a database dreads most no longer require moving data at all. A snapshot, a clone, a branch, a rewind, a restore: in the coupled world, every one of these is a copy. Over a versioned log, they are metadata. You are naming a point in history that already exists. Constant time, zero copy, independent of how large the database is.</p><p>Start with restoring a backup. A restore creates a new log derived from an existing one, branching off at the chosen point in time and proceeding independently from there. The original keeps going untouched; the restored copy is its own independent timeline from that instant forward. Do this a few times, and the logs form a lineage. We call it <strong>log ancestry</strong>: an ancestry tree rooted at the original log, each restore a new branch hanging off the point it was taken from.</p><p>Restore is not special. It is just one use of a more general primitive: take any log, mark a point, and fork. A snapshot is a marker on the timeline, nothing copied, just a named instant you can return to. A clone, or a writable snapshot, is a fork in that timeline: a branch that shares all history up to the fork point and then diverges. </p><p>Atlas Infinite sets the foundation for a production database you can branch like a Git repository: to test a migration against real data and throw the branch away. A rewind to any moment inside a retention window. A full-fidelity copy in every engineer’s harness, costing almost nothing to create because it copies almost nothing.</p><h2>When things break</h2><p>Drama, they say, needs three things: a villain, a victim, and a hero. A failing database has the first two in abundance. The villain is failure itself, in all its usual garbs: a node that dies mid-write, a network that partitions, a disk that goes bad, an availability zone that drops off the map. The victims are the machines snared. With Atlas Infinite, there is no hero in operations. We designed the system so the situation never rises to the level of needing one. Nothing rescues the database, because nothing put it in peril.</p><p>If a database primary fails, the standby is hot and ready to take over. If the network partitions, the Log Service mediates consensus, and the storage layer control plane may even be able to heal the raft group. If a log server fails, a new one gets commissioned, while writes never stop. If a page server fails, there are others with staged copies of the data. If a disk fails, there are other copies. If an entire availability zone goes dark, the cluster keeps serving: the log commits on a majority spread across three zones, each zone has its own page servers, and object storage that sits beneath it all, is zone failure-proof as well. The durability and availability guarantees stem from data that is held in three independent forms at once: the replicated log, the materialized pages, and the object store. And since the storage layer is multitenant, most recovery parallelizes many-to-many: many machines pitch in to take over the work of the departed machine, and to help a new node get up to speed.</p><p>That non-event is the visible tip of a great deal of deliberately unglamorous work that happens behind the scenes. The fleet is carved into cells, spread across availability zones, so trouble in one cell is contained and cannot cascade into the next. The converse also holds: a cell is designed to insulate itself from most trouble happening outside it. We call it Anti-Vegas: <em>what happens outside a cell, stays outside a cell</em>. </p><p>A resource scheduler watches the heatmap continuously, a tenant or a shard drawing more than its share, a node running over the utilization threshold, resource pressures of any kind, and moves load before anyone becomes a noisy neighbor, or feels one. Storage volumes are checked for integrity and repaired, with nothing visible from above.</p><p>None of this is drama. <strong>Boring is the highest compliment you can pay infrastructure.</strong> It means the system runs predictably and safely through spikes and failures and the ordinary daily chaos of a very large fleet, and asks our customers to think about none of it.</p><h2>The line we wouldn&#39;t cross</h2><p>Every disaggregated database has to answer one question about its shared storage layer: can that <em>shared</em> layer read your data? For most of them, the answer is yes: a natural consequence of what conventional disaggregation demands of storage: to <em>materialize </em>pages from a redo log.</p><p>The database ships a log of changes, and the storage fleet reconstructs pages by interpreting that log: find the page, apply the change, produce the bytes. This composition has a consequence that no amount of engineering can wish away. To interpret data, you must be able to read it. A storage tier that reconstructs your pages is, by definition, a storage tier that can see your pages. </p><p>The defenses built around that fact tend to be <em>operational. </em>Mandatory access controls, sacrificial nodes, scoped credentials, periodic audits. In other words, part of the security promise is “trust us.”</p><p>In contrast, we wanted to say: trust our algorithm, not us. In Atlas Infinite, the shared storage layer is not semantically aware—on purpose. Your data is encrypted on the compute node, at the database level, before a single byte is handed down. It is decrypted in exactly one place: the single-tenant compute node running inside your own isolated network, using keys that can be yours to hold, rotate, and revoke. The storage layer services cannot read your documents. They cannot see your collection names, your indexes, or where one tenant&#39;s data ends and the next begins. An operator with root on the entire storage fleet would hold nothing but opaque bytes. </p><p>That is a different kind of boundary. We augmented the full network isolation of Atlas Core, with cryptographic segmentation. This is the reason we could take a system that had always been isolated by machine and network boundaries and put it on shared storage without compromising its trustworthiness.</p><p>Making an entire storage fleet operate, heal, compact, and garbage-collect data it cannot understand is genuinely hard, and it is where a lot of the real invention in this project lives. How we did it, and the tenant-isolation guardrails around it, is the subject of the next post in this series.</p><h2>Epilogue</h2><p>I studied databases at the University of Wisconsin–Madison, back when the field was still arguing about B-trees and data layouts. Then I wandered off for twenty-five years: high-performance computing, networks, security, and a long stretch building load balancers, whose entire job is to stand in front of machines that fail and make them, together, into something that doesn&#39;t.</p><p>I look at Atlas Infinite through that lens. We stood a service in front of the database&#39;s storage and made it something that is designed not to fail, not to run out, and not to require trust. And the old question of how data should sit on your disk got a new answer: it shouldn&#39;t sit on your disk at all.</p><p>Storage had gravity. Less so now.</p><p>Atlas Infinite is in public preview. This post is the first of three. Next, my colleagues will show how a storage fleet operates, heals, and compacts data it cannot understand. After that, we open up <em>mongod</em> itself: what it took to make a database engine born in the era of attached disks feel at home in a world without them.</p><p>If you&#39;ve read this far, you&#39;re who we built it for. Come kick the tires. Tell us how you experience it.</p>]]></description>
      <pubDate>Thu, 08 Oct 2026 16:46:27 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/engineering/ground-beneath-database</link>
      <guid>https://www.mongodb.com/company/blog/engineering/ground-beneath-database</guid>
    </item><item>
      <title>Intelligent Workload Management: Keeping Your Clusters Available When It Matters</title>
      <description><![CDATA[<p>Modern applications need to stay available even when traffic spikes suddenly or queries consume disproportionate resources. <a href="https://www.mongodb.com/products/platform/atlas-database">MongoDB Atlas</a> is designed for high availability, but availability in practice is about more than surviving host failures or a replica set election. It’s also about how a cluster behaves when demand exceeds what it can safely process.</p><p>Last week, we announced<a href="http://dochub.mongodb.org/core/intelligent-workload-management"> Intelligent Workload Management</a> (IWM) as GA in MongoDB 9.0. IWM is a managed availability capability that keeps Atlas clusters responsive and predictable even under overload. IWM queues transient spikes, keeps both short-running operations moving and long-running operations stable, and protects cluster health without requiring any application changes. </p><p>Overload events often unfold faster than infrastructure can scale. Even with <a href="https://www.mongodb.com/products/capabilities/auto-scaling">auto-scaling</a> enabled, provisioning additional capacity takes time. In the gap between a traffic spike and new capacity coming online, a cluster can become unstable if every request is treated the same way and clients retry aggressively. IWM is built to close that gap by preserving cluster health, optimizing performance, and turning what would be an unpredictable outage into a controlled, observable event.</p><p>For sustained overload, customers can optionally enable Load Shedding to reject excess operations. IWM helps manage pressure while a spike passes or capacity is added; it does not add capacity or replace auto-scaling and capacity planning.</p><p><strong>Figure 1.</strong> Intelligent Workload Management adapts to keep clusters responsive and predictable.</p><h2>Managing workload pressure while capacity catches up</h2><p>Traffic spikes and resource-intensive operations can increase demand faster than infrastructure can scale. Even when auto-scaling is enabled, provisioning additional capacity takes time. Aggressive client retries can add pressure while a cluster is already busy.</p><p>IWM helps manage workload pressure during that period. It works with or without auto-scaling: when auto-scaling is enabled, IWM helps keep the cluster stable as capacity comes online; without it, IWM manages work at the cluster’s provisioned capacity. For sustained or growing demand, adding capacity may still be necessary.</p><h2>How IWM responds to workload pressure</h2><p>When a cluster is healthy, IWM is effectively invisible. When demand exceeds what the cluster can safely process, IWM manages pressure in stages:</p><ul><li><strong>It limits incoming work and queues surplus requests:</strong> By default, IWM queues surplus requests rather than proactively rejecting them. This can help absorb transient spikes, though queued requests may take longer to complete while resources are constrained. Queueing changes when work is handled, not the amount of work the application ultimately asks the cluster to do.</li><li><strong>It helps keep short-running operations moving:</strong> A short-running operation, such as a typical read or write, and a long-running operation, such as a large reporting query, do not place the same demands on a cluster. When resources are constrained, IWM keeps short-running operations moving while managing long-running operations more conservatively.</li><li><strong>It helps manage resource pressure:</strong> Memory fragmentation, cache imbalance, and storage exhaustion can all destabilize a healthy cluster. IWM adjusts cluster memory and cache management when it detects unhealthy patterns and can pause new writes while still permitting reads when storage usage reaches critical levels.</li></ul><p>These protections help preserve cluster health during overload. They do not make capacity unlimited or replace good indexing, capacity planning, or auto-scaling.</p><h2>Default protections and optional Load Shedding</h2><p>IWM’s default protections are enabled at no additional cost on eligible dedicated Atlas clusters running MongoDB 9.0. They require no application changes or driver upgrades. By default, IWM manages overload without actively rejecting excess work.</p><p>Load Shedding is a separate, optional control for sustained overload. If enabled, it can reject excess operations, and those rejections are visible to your application as overload errors. Load Shedding is available at no additional charge for eligible M30+ dedicated replica-set Atlas clusters running MongoDB 9.0.</p><p>The default IWM protections work with any MongoDB driver. If you enable Load Shedding, use a supported <a href="https://www.mongodb.com/docs/atlas/overload-errors/?interface=driver&amp;language=python#backpressure-aware-client-libraries-versions">backpressure-aware driver</a> so your application can interpret overload signals and apply bounded retries with backoff. Check the supported driver matrix before enabling Load Shedding.</p><p><strong>Figure 2.</strong> The difference between the default (queuing) and the Load Shedding setting.</p><h2>Understand IWM interventions with Observability</h2><p>In Atlas, review the Operation Rate Limiting and Connection Rate Limiting metrics for queued, rejected operations or connections. When Load Shedding is enabled, rejected operations appear under Operation Rate Limiting. Configure or review the IWM alert condition to track relevant IWM activity, and check the Activity Feed for IWM-related events. Together, these Atlas surfaces help you assess whether pressure is continuing and whether to review workload patterns or add capacity.<a href="https://www.mongodb.com/docs/atlas/intelligent-workload-management/?interface=atlas-ui#monitor-iwm"> Learn more about IWM observability in Atlas</a>.</p><p>For teams evaluating optional Load Shedding, Atlas also provides a test to validate driver compatibility, application handling of overload errors, and operational visibility before relying on the control in production. When tested on active test or development clusters, Atlas randomly rejects a small percentage of operations regardless of load. Teams can follow rejected operations in the metrics chart and review the results after the test ends. Because applications may encounter overload errors during testing, teams should use these tests only to verify client behavior. Teams shouldn’t run tests on a production cluster.<a href="https://www.mongodb.com/docs/atlas/tutorial/test-resilience/test-load-shedding/"> Learn how to test Load Shedding</a>.</p><p>For details on IWM behavior and how to respond to overload, see the<a href="https://www.mongodb.com/docs/atlas/intelligent-workload-management/"> IWM documentation</a>.</p><h2>Getting started</h2><ol><li><p>Confirm that your cluster is an eligible dedicated Atlas cluster running MongoDB 9.0.</p></li><li><p>Decide whether auto-scaling should add capacity during sustained overload. IWM helps manage pressure while additional capacity comes online; it does not replace auto-scaling or capacity planning.</p></li><li><p>If you enable Load Shedding, check the supported driver matrix and confirm that your application uses bounded retries with backoff.</p></li><li><p>Review Atlas observability dashboards to understand when IWM intervenes and which workloads are affected.</p></li></ol>]]></description>
      <pubDate>Thu, 08 Oct 2026 15:40:35 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/product-release-announcements/intelligent-workload-management-keeping-your-clusters-available-when-it-matters</link>
      <guid>https://www.mongodb.com/company/blog/product-release-announcements/intelligent-workload-management-keeping-your-clusters-available-when-it-matters</guid>
    </item><item>
      <title>Code Mode Without the Interpreter: Agents That Write Aggregation Pipelines</title>
      <description><![CDATA[<p>Standfirst Code mode gives an AI agent a code interpreter and lets it write real programs—one round trip instead of five, filtering where the data lives instead of in the context window. It also means running arbitrary code that a model wrote, which is a hard sell in a regulated product. This is an account of doing the same thing without the interpreter: the agent authors a <a href="https://www.mongodb.com/docs/manual/core/aggregation-pipeline/">MongoDB aggregation pipeline</a>, a handler executes it server-side, and only the reshaped result crosses back. Two production systems, the query work that made them viable, and where the approach falls down. </p><h2>The problem with fixed tools</h2><p>Our document agent answers questions about the contracts a customer has uploaded. Which of these autorenews? What notice period does each one need? Where does a particular indemnity actually sit? </p><p><strong>Figure 1.</strong> Fixed tools workflow with multiple sequential round trips and context accumulation.</p><p>The first version used ordinary MCP tools. One tool per operation, each returning one shape of result. That works right up until a question doesn&#39;t map onto a tool. &quot;Which contracts auto-renew, and what notice do they need&quot; becomes a sequence: list the documents, fetch the first one&#39;s sections, scan them, fetch the next one&#39;s, scan those, and on. Five findOne calls in a row, where anyone who knows the database would have written one query. Two things go wrong, and the second is worse. </p><p>The obvious one is round-trips. Every call is a full turn. The model waits, the result arrives, and it decides what to ask next. The subtle one is what those results do to the context window. To find three paragraphs, you pull back the sections of every document you looked at—hundreds of kilobytes, most of it irrelevant, now sitting in the window permanently, with the model reasoning over all of it for the rest of the conversation. It compounds with every call. Nothing failed. Each tool returned exactly what it promised. That is the problem. You can paper over both of those by writing more specific tools, but then you are in the business of anticipating every question anyone will ever ask, and the ones you didn&#39;t anticipate fall back to the primitive calls. </p><p>There is a third problem, and it is the one that has no fix at this layer. A legal answer is often not in a document. It is in the relationship between several. A folder might hold sixty files: a master agreement, two addenda, a side letter, a handful of schedules, and superseded drafts nobody deleted. The notice period in the master agreement is real until an addendum changes it. An indemnity may be capped by a schedule whose title says nothing about indemnities. A clause that looks decisive on its own is routinely narrowed, extended, or voided by another document in the same folder. So you cannot know which documents matter until you have looked across all of them. No index helps, because you are not retrieving a row—you are reconciling a set. With fixed tools, the only available strategy is to pull all sixty documents&#39; sections into the context window and let the model compare them there. That is not an inefficiency to optimize away. It is the only move the toolset permits, and it is the move that fills the window. </p><h2>Agent code mode, and what it costs </h2><p>The pattern the industry has converged on is to let the model write code. TypeScript or Python, executed in a code interpreter, with the result of the run coming back rather than the raw data. It is a genuinely good answer to both problems. Filtering happens inside the program rather than inside the context window, and N round-trips collapse into one. The cost is that you are now executing arbitrary code that a model wrote. That means a sandbox, a filesystem policy, egress rules, resource limits, and a threat model covering all of it. Plenty of teams ship this and ship it well. In a product where the thing being processed is somebody&#39;s confidential contract, there is a lot of new surface to take on. </p><p><strong>Figure 2.</strong> Agent code mode pattern using a code interpreter for arbitrary code execution.</p><h2>Code mode with databases </h2><p>So the agent writes a program—just not code. It authors a MongoDB aggregation pipeline. A handler on our side validates it, prepends a tenancy filter, executes it against that workspace&#39;s documents, and returns the result. The five sequential lookups become one pipeline: scope to the workspace, $unwind the sections, $match the section type, $project only the fields needed, $group back by document. One round trip. What comes back is a few hundred bytes shaped for the next reasoning step, rather than the corpus it was computed from. </p><p><strong>Figure 3.</strong> Code mode with databases pattern using a validated aggregation pipeline instead of an interpreter.</p><p>The sixty-document case is the same shape, which is the point. One pipeline touches every file in the folder, pulls out only the sections that bear on the question, and returns them side by side with their source document attached—so the model receives the comparison rather than the material to assemble a comparison from. The cross-document work happens where the documents are. No interpreter. No sandbox process. No filesystem API. The program is JSON, and the runtime is the aggregation engine. That is the trade. You keep composition, filtering at the source, and transformation before the tokens are spent. You give up arbitrary execution. And you can afford to give it up, because the language is small enough to allow-list exhaustively. </p><h2>Why this works with MongoDB in particular </h2><p>This works for two reasons, and they are worth separating because only one of them is about the database. </p><p>The model already knows the language. Aggregation pipeline syntax is very well represented in the material these models were trained on. We are not teaching an agent a bespoke query DSL we invented and then hoping it generalizes. We are asking it to write something it has seen a great deal of. The failure modes are the ones any MongoDB developer would recognize, which also means they are the ones we know how to catch. </p><p>The document model and the security model happen to agree. Contracts are documents with nested sections, so $unwind and $project reach inside them directly. The same question against a relational schema needs joins—and cross-collection stages are exactly what we block, because a join is how a query escapes its tenancy scope. In a normalized schema, the thing we most need to forbid is the thing the query would most need to do. Here it isn&#39;t. That second point took us a while to notice, and it is the reason the allow-list can be as short as it is. </p><p>And the agent uses the framework well. This is the part I did not expect. It works in two passes: a first pipeline to see what is actually in the matter, then a second, targeted one written against what it found. The targeted pipeline is frequently large—fifty or sixty operators composed together—and it holds up. We instruct it to be token-efficient, and what that produces is the interesting bit. It reaches for $limit to paginate rather than pulling everything back. And it uses $addFields to compute the thing we actually asked for instead of returning the material to compute it from: concatenating fields into the string the answer needs, or assembling a boolean expression that comes back as true or false. That last habit is the whole argument in miniature. Asking whether any document in a folder contains an uncapped indemnity can return a boolean computed in the database, rather than the indemnity clauses of sixty documents for the model to read and compare. The comparison still happens. It just does not happen in the context window. </p><h2>Nine stages </h2><p>The permitted vocabulary is $match , $unwind , $project , $group , $sort , $limit , $skip , $count and $addFields. Every top-level key of every stage is checked, and a rejection returns a structured error naming the offending operator and listing the legal set. What that buys is concrete. $out and $merge are rejected, so the tool is read-only by construction rather than by convention. $lookup , $graphLookup, and $unionWith are rejected, so a query cannot reach another collection. Server introspection stages are rejected. Here is the part that surprised us. Restricting the language is not only a security control. It is a prompt engineering control. A nine-stage vocabulary is small enough to fit, with worked examples and anti-patterns, into a document that the model reads before every session. A forty-stage vocabulary is not. The property that makes the surface auditable is the same property that makes it learnable. </p><h2>The filter the model cannot reach </h2><p>Every pipeline gets a tenancy filter prepended before it runs. The workspace identifier is not a tool parameter—it is captured when the server is constructed for that conversation, so there is nothing for the model to supply, see or spoof. Because cross-collection stages are blocked, a query cannot get out from under it either. That filter also excludes documents that failed processing, since a failed document has no extracted text to reason over. It lives in one named constant, with a comment explaining why a different consumer elsewhere deliberately retains those same documents, so the interface can list them. Two consumers, two correct answers, one shared constant, so nobody re-inlines the wrong one. This is the strongest argument I have for executing server-side rather than running an interpreter. The invariant is enforced in one place, in reviewed TypeScript—not re-derived by a model in every program it writes. </p><h2>Teaching it the language </h2><p>We tried out of the box first. Models do write MongoDB. They do not write it well. The queries worked and were inefficient, and they were written against the MongoDB of a few years ago—newer operators simply were not in the picture. So we wrote the reference ourselves. A skill the agent must load before it writes a single stage: tool contracts, document types, the structure of a contract&#39;s sections, ready-to-adapt patterns, explicit antipatterns, and operator tables. It runs to 851 lines, and it is not optional. It is also not allowed to write against a remembered schema. Summary first, then details for the documents that matter, then a query using field paths taken from that response. The instruction is blunt: do not guess field names. Some of what is in that skill is scar tissue, and those are the best lines in it. One says: do not pass the global flag to $regexFindAll , it finds all matches already, and the flag will cause an error. That is a production failure distilled into a sentence, now read before every session. The skill is where post-mortems go to become prevention. </p><h2>What it bought us: Document intelligence </h2><p>On our evaluation suite, accuracy improved by roughly 20%. More useful than the percentage: cases that had never passed started passing. A number moving is easy to argue with; a test that was red going green is not. That figure needs a reference point, because on its own, a percentage means very little. In our experience, a well-judged prompt change or a better-written skill moves legal quality by five or six points. That is a good day&#39;s work. Twenty points, from changing how the agent gets its data rather than how it reasons about it, is not a return we normally see for that amount of effort. </p><h2>From red to passing evals</h2><p>To evaluate this capability specifically, we constructed a benchmark built around a challenging legal scenario: a fictitious matter encompassing over fifty files. It is the kind of massive corpus that taxes both a legal professional and an agentic legal solution. Working alongside our legal domain experts at Genie AI, we established nine strict validation parameters: identifying the exact contracting entity, determining notice windows accurately, avoiding cross-document clause misattributions, and six parallel constraints.</p><p>Scoring was strictly categorical: met, partially met, not met.</p><p><strong>The baseline: </strong>Without MongoDB Search and code-mode aggregation authorship, the agent satisfied just two of the nine requirements.</p><p><strong>With MongoDB Search in code-mode:</strong> The raw pipeline immediately doubled performance to four out of nine. Once we equipped the subagent with structured legal skill guidance tailored for contract analysis and better instruction on how to use MongoDB, success jumped to seven out of nine parameters.</p><p>Moving from a baseline calculation to over a 70% resolution rate was more than an incremental improvement; it reshaped how our architecture handles complex retrieval.</p><p>The comparison that told us most was not against another product. It was against the same model, with none of this around it. Hand a strong general model a contract and ask it to review, and it does a reasonable job. Give it structure, it can query, a language it already knows how to write, and a schema it does not have to guess at, and it does a substantially better one. The entire difference is in what surrounds the model. Finding the right clause used to be a conversation. It is now one pipeline of about sixty lines, written once and executed once. I should say plainly that we did not expect this. It started as a side project. It has been running in production for five months. </p><h2>We didn&#39;t stop there </h2><p>Investigating a production issue in an agentic system is hard in a specific way. The failure usually isn&#39;t an error. Nothing spikes. The system returns a fluent, complete answer, and the answer is wrong. We were running two observability platforms to cope — one for the AI behavior, one for the engineering — and neither answered the question we actually had, which was usually why it decided that, and whether the same thing was happening to anyone else. Dashboards answer questions you decided to ask when you built them. Those are not the questions worth asking about an agent. </p><p>So once the document work had been in production for a few months, we reused the strategy. Same pattern: the agent writes its own aggregations against the operational data and runs them, intersecting things we had never thought to connect in advance. It is agent-first, so there is no dashboard to design, build, review, and then maintain as the questions change — asking a new question is cheaper than adding a panel. And a full investigation now takes a couple of minutes rather than ten or twelve. That last part matters more than it sounds. At ten minutes, you investigate when something is clearly broken. At two, you investigate because you are curious. Those are different jobs, and the second one finds things. It only became viable after some query work, and the one that mattered most is worth stating plainly. A usage lookup was examining 34,053 documents to return a single workspace&#39;s rows. A partial index brought that down to 392 documents examined, and the query from 2.2 seconds to about 20 milliseconds. </p><p>That is the honest caveat on this whole pattern. A model-authored query can be perfectly correct and quietly expensive, and nothing in the result tells you. Past that, the problem of understanding our own data mostly dissolves. The agent runs large queries to explore bugs and patterns, and we stopped building things to look at data with. </p><h2>What it does not do </h2><p>Regex is not a semantic search. The retrieval quality floor is whether the agent thought of the right synonym, and security is embedded at multiple layers during the search. The prompt compensates by mandating synonym sweeps and a coverage check on queries claiming to be exhaustive, but the floor is still the floor. And $limit is a silent truncator. A query meant to find everything, which hits the limit, returns a subset that looks exactly like an answer. Both are real. In a legal review, an empty result is not an empty answer! Furthermore, our security framework treats every corpus as inherently untrusted; leveraging MongoDB Search enables us to enforce read-only execution and constrain query reach through $match filters that the model never sees.</p><h2>The shape of the argument </h2><p>The interesting decisions in agent systems are about what the model is allowed to do, not what it is asked to do. A bounded language, enforced outside the model, turned out to be better than a larger one plus a stern prompt — for safety, and unexpectedly for accuracy. You may not need the interpreter. If your data already lives somewhere with a composable query language the model has seen before, you may already have everything code mode was going to give you.</p>]]></description>
      <pubDate>Thu, 08 Oct 2026 14:00:01 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/technical/code-mode-without-interpreter-agents-that-write-aggregation-pipelines</link>
      <guid>https://www.mongodb.com/company/blog/technical/code-mode-without-interpreter-agents-that-write-aggregation-pipelines</guid>
    </item><item>
      <title>Data Modeling and Schema Design for MongoDB Search Part 2: Use Cases and Patterns</title>
      <description><![CDATA[<p>This is Part 2, continuing from “<a href="https://www.mongodb.com/company/blog/technical/data-modeling-schema-design-for-search-part-1-practical-considerations">Part 1: Practical Considerations</a>.” In Part 1, the foundational concerns were laid out. Here in Part 2, common use cases and patterns to address them with best practices are covered.</p><h2>Schema design process for search</h2><p>The search use cases that MongoDB Search is asked to support need to be evaluated within the identified physical constraints to produce a suitable schema design. MongoDB Search indexes content based directly on each field’s name and data type and returns the matching documents (or embedded documents) and facets from search requests. Modeling documents to use case needs is straightforward; what you index is what you get - you index “movies” and <em>$search</em> returns movies, or you index products, and <em>$search</em> returns products. The documents in the collection are what is returned and thus conceptually represent the types and granularity of “things” the user is being provided in response to a query.</p><p>Let’s use a movie search engine example: Movies themselves make sense to be a first-class search result item. What about cast members? Are they simply attributes and a means to find a movie? Or are they first-class entities that warrant being an independent item in search results? First-class search result items should be modeled as documents in a collection. How about <em>genre</em>? Would the users of a movie search system want to get to Documentaries as an entity unto itself, by typing only “doc” and it being the first suggestion?</p><h3>Build with the end experience in mind</h3><p>The search experience delivered by your application is a crucial part of the usefulness and satisfaction provided to your users; a lack of a quality search feature will deter users. Delightful search experiences provide facilities such as <a href="https://www.mongodb.com/docs/atlas/architecture/current/solutions-library/retail-as-you-type-suggestions/">as-you-type suggestions</a>, faceted navigation, and keyword highlighting, all while factoring in our explicit and implicit preferences by filtering out or boosting items. The quality of your application&#39;s search experience consists of much more than just a list of documents for a search query. It could be incorporating search into subtle areas such as “more like this” sections of existing pages, providing context-sensitive filtering and navigation of organized content, and other UX enhancements. The takeaway is this: Model and build to these experiences. </p><p>Some questions to ask yourself as you begin the modeling process:</p><ul><li><p>What types of queries do you expect?</p></li><li><p>How is your content best organized for navigation and searchability?</p></li><li><p>When search results are presented, how can the app best help users narrow or expand their search? </p></li></ul><h2>Useful search design patterns</h2><p>Don’t look at patterns to find a problem to solve, but rather find the patterns that best fit the challenges you’re facing. Several of the tried and true MongoDB design patterns work well for search use cases (and one in particular does not!!). </p><p></p><h3>Attribute Pattern and search</h3><p>The <a href="https://www.mongodb.com/blog/post/building-with-patterns-the-attribute-pattern">Attribute Pattern</a> is a commonly used document database technique to represent key/value pairs in a structure that does not introduce a potentially unlimited number of field names (or keys) by representing a key/value pair as a JSON  <em>{ k: “key”, v: “value”}</em> structure. Keys are values to a k field in a sub-document. Because MongoDB Search uses field names for mapping, k is the field name for all attributes, and thus a specific attribute key cannot be mapped, and even more insidious is that v values could potentially be of different types of data, even if all values for a particular key are of the same type, because of the blending of all values together in a single index. The <em>embeddedDocuments</em> field type can help with conservative use of the Attribute Pattern for some capabilities, but that comes with other considerations (see the nested documents section above). The best course of action for attributes that need to be searched? Model or transform them as straightforward <em>field_name: value</em> fields on the documents, where they can be handled in a type-sensitive manner. All values of a given field are indexed together and separate from other fields. </p><h2>Entity pattern for search</h2><p>The Entity Pattern models all key domain entities in a way that supports the “find anything anywhere” and “relevant as you type suggestions” use cases. Entities are represented as first-class documents in a specialized collection and a MongoDB Search index configuration tuned for matching domain entities in many ways and allowing for customized ranking factors. All of your domain entities can be indexed and findable in a myriad of ways using this pattern. Of course, scale matters, so this perhaps isn’t a practical pattern for billions of things, though many hundreds of millions are generally a pretty tractable scale. How many unique entities do you have in your system? A quick ballpark estimate for a realistic product catalog system, representing products, customers, and orders, could have, say, 10k products across 10 categories, serving around 1M customers who each could have a billing and shipping address within any of the 50 United States. Across around 200k cities, that would be 10k products + 1M customers + 2M addresses + 50 states + 200k cities = ~3.2M entities, which is no big deal scale-wise.</p><p>If your situation consists of only a single collection, with only one or perhaps more entity types, and they are modeled as first-class documents already, this pattern is effectively what you’ve already got — all domain entities represented as first-class documents in a single collection. A collection of all domain entities blended together and typed exemplifies the <a href="https://www.mongodb.com/developer/languages/swift/swift-single-collection-pattern/">Single-Collection Pattern</a>.</p><p>It&#39;s often the case that your main collection represents one type of entity as documents, and other domain entities as metadata fields or nested documents. For example, let’s take the infamous sample movie data: As a user types, movie titles certainly should be suggested. But what about cast member names? Can I find movies starring Keanu Reeves by typing only &quot;kea&quot;? What about documentaries by only typing &quot;doc&quot;? Both <em>cast</em> (actor name) and <em>genre</em> fields (<em>fields</em>, not documents) are, for a movie search application, truly first-class domain entity objects, and in a findability sense, deserve to be first-class documents in a collection backed by MongoDB Search.</p><p>It’s a simple model with the following basic schema:</p><p></p><p>It’s important that entity documents have stable, unique identifiers, as the entities will be regularly refreshed from their source of truth collection. Assigning a type to each entity allows for filtering, grouping, boosting, or faceting by type.</p><p>Additionally, modeling entities directly as individual documents allows each to carry optional metadata fields to assist in ranking, displaying, filtering, or grouping them. In the movie example, cast member entity documents could carry a computed number of movies the actor has been in, and the average rating of all those movies. These types of computed values, aggregated during the entities collection sync process, exhibit the Computed Pattern.      </p><p>At the heart of this solution, the straightforward document model feeds the <em>name</em> field through a sophisticated index configuration, which analyzes it in numerous ways, enabling incredible query and ranking power.</p><p>The Entity Pattern for Search, which debuted in <a href="https://www.mongodb.com/solutions/solutions-library/as-you-type-suggest-solution">Relevant As-You-Type Suggestions Search Solution</a> (see the data modeling approach section), is specialized for the as-you-type/autocomplete/typeahead use case.</p><h3>Entity collection uses</h3><ul><li><p>As-you-type suggest</p></li><li><p>Type-specific lookups (dropdown of Categories, States, Names)</p></li><li><p>General index of All (your) Things</p></li></ul><p>This collection can be used to initiate lookups and limit the results to only a few (or even just one) result, making looking up the canonical, more detailed data straightforward and performant.</p><p>Basic search operations on an entity collection make these use cases straightforward and performant:</p><ul><li><p>Filtering by type</p></li><ul><li><p>Dropdown entry for cities (“type” equals “city”)</p></li><li><p>Saved searches: Log users’ “saved searches” as entity type “saved_search” with an additional “username” field on each of those types of documents. As a user types, their saved searches can be displayed. No additional collection would be needed — this could be the source of truth collection for “saved searches.” For this type of entity, it would also be wise to add a timestamp, so they could be sorted by recency. </p></li></ul><li><p>Faceting by type</p></li><ul><li><p>As a user types, entities are returned, and additionally, the types of entities found and their count within the matched result set can be returned. These counts are useful for users to see the bigger context of the types of things being matched and facilities filtered navigation by type from there.</p></li><li><p>With no filter criteria, a $seachMeta faceting by type will quickly give the full set of entity types available. These global counts can be useful, again, for navigation of your “domain entity space” and also for diagnostic purposes to ensure the number of entities of each type matches the counts from the source of truth data.</p></li></ul><li><p>Boosting by type</p></li><ul><li><p>Perhaps certain entity types make sense to boost over other entity types in the results. As a user types in a movie database search, genre entity types and movie entity types could be boosted over cast member name types, so more commonly searched-for entities surface ahead in a list of suggestions. </p></li><li><p>Similarly, a user&#39;s saved search entities could be prioritized over product or category types of entities to increase the value to your customers&#39; experience.</p></li></ul><li><p>Boosting by entity weights</p></li><ul><li><p>In a movie database search, boost cast members by a factor related to the ratings of the movies they’ve been in. The average rating of all movies for an actor is not the best weight to use, as that prioritizes an actor who’s only been in one highly rated movie ahead of actors who have been in lots of movies, most of which have rated well. But there are ways to give seasoned actors a boost by using the sum of all their movie ratings rather than an average. The more good movies they’ve been in, the bigger their boost. Boost factors based on the entity data itself provide a flexible way to add “smart” weightings to results based on your business goals.</p></li></ul></ul><h3>Populating an entity collection from existing data</h3><p>You’ve already got data, and it’s well modeled for other use cases nested within sub-structures of related documents. However, the structure of that data doesn’t lend itself to being first-class findable. Leave the data where it fits the other use cases best, keeping the source of truth right where it already is. The unique entities nested within documents in other collections can generally be extracted and grouped uniquely, computing any useful values along the way. Maintaining a synchronization of data into the entities collection does require consideration and a process to implement.</p><p>A great example of an export/merge process comes from the movie collection data, where genre is an attribute of a movie, yet deserves to be a first-class domain entity. From the movies collection, we unwind the genres field from its nested per-movie value, then group genres into unique values, counting the number of movies for each genre along the way. Then, we format the unique genres into the entities collection schema (_id, type, name, etc.) where the _id is unique per genre and made to fit uniquely within the _id space of a blended collection of various entity types. And finally, these genre entity documents are merged into the catch-all entities collection. The $merge stage will overwrite documents with the same _id, making it important to uniquely and stably identify entities so they can easily be updated.</p><p>The following code snippet can be <a href="https://github.com/mongodb-developer/atlas-search-as-you-type-suggest/blob/main/examples/movies/setup.js#L57-L76">seen in full context</a> on GitHub.</p><p></p><p>Each entity type could have its own synchronization process and type-specific additional fields. </p><h3>Entity index configuration</h3><p>The entities collection’s index configuration specifies the mappings on the type and name fields, otherwise leaving it dynamically mapped to accommodate additional custom fields as needed.</p><p>View a <a href="https://github.com/mongodb-developer/atlas-search-as-you-type-suggest/blob/main/examples/movies/entities_index_config.json">full example configuration</a> for the as-you-type use case.</p><p>A few specific pieces of this configuration are worth highlighting. The entity <em>type</em> field is indexed in two different ways: as a <em>token</em> for filtering or boosting by exact value, and for faceting-by-type needs.</p><p>The heart of entity findability stems from the indexing strategies applied to the <em>name</em> field. MongoDB Search provides a powerful “multi” indexing technique for string fields, where that one string value is indexed numerous ways to facilitate any number of ways to match it. Strings are analyzed, a process creating a series of indexable units called terms. Terms represent words, character fragments, phonetics, or other lexical extraction tricks. In the example configuration mentioned above, the name field is indexed with just the left edge (“starts with”), as English text (“search”, “searches”, “searching”, “searched” all indexed the same), lowercase (case-insensitive matching), phonetic (“sounds like”), shingled (pairs of words concatenated and indexed together, good for relevancy boosting of words commonly used together), and using the default language-agnostic word-break delimited extraction analysis.</p><p>These various ways of analyzing the <em>name</em> field give the <em>text</em> and <em>phrase</em> operators potent ways of matching and ranking. Here’s an example as-you-type suggest query scenario, matching liberally on very little query text (“matr”) yet boosting best matches to the top:</p><p>From <a href="https://search-playground.mongodb.com/tools/code-playground/snapshots/66473b744e0a3f240a5de9e1">this MongoDB Search Playground</a>, we weigh each analyzed variant of the name field differently, and then multiply the result by any specified weight on the matched entity:</p><p>Searching across multiple indexed fields, performantly, in combinations with one another, is a superpower of MongoDB Search — and it’s the key to nuanced and controllable result relevancy.</p><h3>Type-specific metadata</h3><p>To avoid field name collisions on any custom entity type-specific fields, the fields can be nested into type-specific sub-documents, like this book sub-structure:</p><p>The MongoDB Search index configuration of the entities collection could then add specific document-type mappings for overrides to the default dynamic mappings in place, perhaps making the number of pages of book entities facetable:</p><h2>Summary: Key points for Data Modeling and Schema Design for Search </h2><ul><li><p><strong>Model for the End Experience</strong>: Design your schema and search capabilities by starting with the desired UI/UX and identifying the exact objects or entities your users need searched and returned.</p></li><li><p><strong>First-Class Documents</strong>: Represent searchable items and domain entities as first-class documents within their own collections rather than relying heavily on deeply nested structures or ambiguous attributes. This is a general best practice, though embeddedDocuments and returnScope are very powerful when the use case fits them.</p></li><li><p><strong>Consistent Field Types</strong>: Ensure that fields with the same name maintain consistent data types across all collection documents to prevent query and faceting issues.</p></li><li><p><strong>Optimize Indexing</strong>: Adhere to the principle that &quot;data that is searched together, is indexed together,&quot; using tailored typeSets, views, and mappings to manage index size and work within physical constraints.</p></li></ul><p></p>]]></description>
      <pubDate>Thu, 08 Oct 2026 12:41:05 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/technical/data-modeling-schema-design-for-search-part-2-use-cases-patterns</link>
      <guid>https://www.mongodb.com/company/blog/technical/data-modeling-schema-design-for-search-part-2-use-cases-patterns</guid>
    </item><item>
      <title>Data Modeling and Schema Design for MongoDB Search Part 1: Practical Considerations</title>
      <description><![CDATA[<p><a href="https://www.mongodb.com/docs/manual/data-modeling/">Data modeling in MongoDB</a> is the art and science of organizing data in a database to represent entities, attributes, and relationships, thereby optimally supporting business objectives.</p><p>There are three types of data models: conceptual, logical, and physical. Conceptually, for search, we have content, and it needs to be findable and rankable. Logically, content is generally segregated by types of data (e.g., books and library patron users are different types of entities in the system), each type having its own set of attributes and relationships.</p><p>The most primal level of data modeling is where the pedal meets the metal, almost literally — at the physical level. The physical model consists of a schema design, laying out how data is structured into databases, collections, shards, fields, field types, and indexes.</p><p>The structural and type flexibility of MongoDB’s document model leaves the exercise of schema design up to the developer to create the best layout for the workloads given physical, hardware, and software constraints. <a href="https://www.mongodb.com/blog/post/building-with-patterns-a-summary">Design patterns</a> have emerged by distilling and abstracting successful techniques for dealing with various common needs. And, as with any software, there are system constraints within which search operates.</p><p>This document serves as a blueprint for designing schemas for these common usage patterns, which leverage the power of the underlying search system and work within the boundaries imposed by the hardware and software environments.</p><p>There are 2 parts to this content. Here in Part 1, the practical considerations and foundational concepts and building blocks are detailed. In Part 2, common search use cases are presented with patterns that have emerged to tackle them including the current best practices.</p><h2>Use case workloads</h2><p><strong>&gt; Age-old data modeling adage: “The optimal grouping of objects into documents is determined by the workload.”</strong></p><p>Our first stop in schema design for search is understanding the workloads that our application will demand of MongoDB Search. Here are the common use cases, given a search request:</p><ul><li><p>Standard paged search results: return the top (10 or so) matching documents, in sorted or relevancy-ranked order, with or without facets.</p></li><li><p>Process all matching documents: docs may go through successive pipeline stages that need the entire set of results to continue, such as <em>$group</em> and <em>$sort</em>.</p></li><li><p>Return only facet counts, without any of the matching documents.</p></li><li><p>Relevant as-you-type suggestions.</p></li><li><p>Replace <em>$match</em> with <em>$search</em> to index and query on many more fields than can be indexed with database B-tree indexes.</p></li><li><p>“Find anything anywhere” - best practices; compared to <em>$match</em> and <em>$elemMatch</em>.</p></li><li><p>Leverage lexical and other types of vector pre-filtering.</p></li></ul><h2>Physical constraints</h2><p><strong>&gt; Wise modeling master: “We model to face and answer to constraints.”</strong></p><p>The architecture of MongoDB Search frames what’s possible. Given the way MongoDB Search is built, here’s a list of the main physical parameters that factor into schema design decisions:</p><ul><li><p>The <em>$search</em> stage queries a single MongoDB Search index.</p></li><li><p>A MongoDB Search index is tied to a single Atlas collection.</p></li><li><p>A mapping defines which fields are to be indexed in what manner, mapped by field name and data type.</p></li><li><p>Search criteria is used to score and return matching collection documents (or individual embedded documents!)</p></li></ul><p>It’s worth calling out that these particular architectural decisions are subject to change as MongoDB Search progresses. There are already several works in progress behind the scenes of the product that alter and relax, some of these architectural decisions, opening the door to some interesting ways of doing things that aren’t possible currently. These patterns will change as the system’s physical capabilities improve. As they say, we’re working on it… always!  And in the <a href="https://www.mongodb.com/products/self-managed/community-edition">OPEN</a>!</p><p>The preceding list of architecturally controlled physical operating parameters fits within the aggregation pipeline framework as a <em>$search</em> stage, which makes calls to a search service built on top of the powerful search engine, <a href="https://lucene.apache.org">Lucene</a>. Let’s look at both ends of the architecture, taking into consideration the typical workloads demanded of <em>$search</em> and the constraints it works within. First, let’s see how <em>$search</em> fits into the aggregation pipeline. Then, we’ll look at how the underlying index structure operates at the lowest level of MongoDB Search.</p><h3>Top down—how $search fits into an aggregation pipeline</h3><p>The <em>$search</em> stage must be, because of pragmatic choices made during implementation, the first stage in the aggregation pipeline (<a href="https://www.mongodb.com/docs/atlas/atlas-search/tutorial/search-with-unionwith/">or a $unionWith stage</a>). There’s no input set of documents at this stage. The output of this stage consists of an ordered list of documents and some additional search metadata. The output of the $search stage can be further aggregated using any of the available stages that take a list of documents as input, such as <em>$limit</em><em>, </em><em>$skip</em><em>, </em><em>$project</em><em>, </em><em>$addField</em><em>, </em><em>$facet</em><em>, </em><em>$match</em><em>, </em><em>$group</em><em>, </em><a href="https://www.mongodb.com/docs/atlas/atlas-search/tutorial/lookup-with-search/"><em>$lookup</em></a>, and others, though post-search aggregating stages can have a drastic effect on performance, as explained here later. </p><p>&gt; What about <em>$searchMeta</em>? This stage performs a search, but rather than return the matching documents, it returns search result metadata, such as the total count of matching documents and facets if they were requested. This stage is handy if all you need is this metadata, whereas $search returns all of this same metadata (as <a href="https://www.mongodb.com/docs/atlas/atlas-search/facet/#std-label-fts-facet-aggregation-variable">$$SEARCH_META</a>) along with the matching documents. </p><p>When <em>$search</em> executes from the <em>mongod</em> (mongo “database”) node running the aggregation pipeline stages, it makes a remote call to a Java-based <em>mongot</em><em> </em>(mongo “text”) process. The <em>mongot</em> process interfaces with the Lucene APIs for indexing, searching, ranking, highlighting, and faceting.</p><p>Important things to note as it relates to schema design: Matching collection documents are returned, in relevancy-ranked order. While a search may result in matching thousands, millions, or even billions of documents, the underlying search engine is designed to match, rank, and return the results quickly, providing the best matches first. The <em>mongot</em> service provides results in batches to the calling aggregation pipeline and will get invoked until the calling pipeline has exhausted the cursor and processed all of the matches or short-circuited from a stage like  <em>$limit</em>.</p><p><em><strong>Warning:</strong></em> Running aggregation pipelines in the Atlas UI or Compass will apply an implicit <em>$limit</em> to show only the first several resultant documents. Searches are quick. The same aggregation pipeline, if naively run from a driver-using code environment, may pull the entire cursors&#39; worth of documents into an array data structure. Retrieving all search results into an array can be quite time- and memory-consuming. It’s usually the desired pattern to <em>$limit</em> search results and paginate through them as needed. If all goes well, the best are at the top, so users won’t need to see many. :)</p><p>These working conditions of the <em>$search</em> stage inform some design decisions: that it must be the first stage in the pipeline, that it returns documents in relevancy order, that it crosses process boundaries returning batches of matches, and, unless otherwise specifically limited, all matching search results will, eventually, be returned. That last point is an important one — the number of results fed through the pipeline after <em>$search</em> has a direct and increasingly dramatic impact on the performance. For the best result, design for limited results, leaning on relevancy tuning to get the best first. Pagination through search results is efficient and quick when using the <a href="https://www.mongodb.com/docs/atlas/atlas-search/paginate-results/#search-after-a-specific-point-of-reference">searchAfter</a> token mechanism.</p><p>When deployed in Atlas, the scalability of the search process can be controlled by adding and increasing the use of <a href="https://www.mongodb.com/docs/atlas/cluster-config/multi-cloud-distribution/#std-label-configure-search-nodes">Search Nodes</a>. You can set specific nodes in your cluster to run only the MongoDB Search <em>mongot</em><em> </em>process. When <em>mongot</em> is run separately, availability improves, and workloads are balanced. To learn more, see the <a href="https://www.mongodb.com/docs/atlas/atlas-search/atlas-search-overview/#std-label-what-is-search-node">Search Nodes Architecture</a> documentation.</p><h3>Bottom up: Lucene and mongot</h3><p>At the core of MongoDB Search lives Lucene, a mature, powerful, open source search engine library. Lucene’s solid abstractions shine through the calling layers, as well as its limitations. </p><p>“Index objects” are the individual units of data (Lucene also calls them “documents”, though they are referred to as “index objects” to avoid more terminology confusion since they aren’t necessarily one-to-one) added to the Lucene index, consisting of one index object per database collection document, plus one for each mapped embedded document. Embedded documents are covered separately below. How sub-documents nested within main collection documents are handled, depending on scale, could impact the physical model sharding design. This means using embedded documents will result in a higher number of indexed Lucene objects and needs to be considered for sizing. Lucene has a two-billion limit on index objects. Going beyond 2B docs requires partitioning or sharding.</p><h4>Indexing</h4><p>After an index configuration is created/updated, all documents in the collection are (re)indexed. All fields of each document are available for indexing, and mapped (or ignored) according to the index configuration. The physical storage space taken by the index structure depends entirely on the index configuration. A simple configuration adjustment can have a dramatic impact on index size (and thus speed to build, etc).</p><h4>Searching</h4><p>The <em>mongot</em> process powers the <em>$search</em> stage, handling successive requests to pull search results in batches. These remote calls for batches of results shape what’s performantly possible. Lucene is optimized to serve and page through the most relevant or top-sorted documents quickly, satisfying the most common search use case of where it is expected users will find what they are looking for in those top results. Queries often match vastly more documents than would be presented to a user at one time, and only the top ones may be of interest. </p><p>The successive batches of results requested by the <em>$search</em> stage allow for the actual documents returned to be cut off at a desired limit. Regardless of how many matching results are actually brought back into the aggregation pipeline, the exact <a href="https://www.mongodb.com/docs/atlas/atlas-search/counting/">count of matching documents</a> can be provided, or a lower bound estimate for better performance, so the user can be presented with the magnitude of results available.</p><h3>Summarizing the physical constraints</h3><p>The key performance tips and system limitations are detailed on the <a href="https://www.mongodb.com/docs/atlas/atlas-search/performance/index-performance/">MongoDB Search Index Performance</a> page. Here are the main physical constraint highlights as they pertain to designing a schema for search use cases:</p><ul><li><p>The database and search server are separate processes and potentially/ideally on separate nodes for more scalability.</p></li><li><p>Batching a large search result set across processes and the network can be a major bottleneck.</p></li><li><p>2.1 billion index objects per MongoDB Search index; index objects consist of one for each document, and one for each explicitly mapped embedded document.</p></li></ul><h2>Schema considerations</h2><p>MongoDB Search maps document fields to indexes on Lucene index objects by field name and the data type. This direct connection to field name and type dictates what’s searchable and in what way, and is a crucial consideration in designing a schema for a search workload. </p><p>Consistent document structure matters. Field content is indexed based on the field name, data type, and structure of each collection document. It’s important to standardize document structure in MongoDB Search-backed collections:</p><ul><li><p><em>_id</em><em>:</em> If the collection is merged/aggregated specifically for search from data structured differently in other collections, stable identifiers matter for updates.</p></li><li><p>Do not mix field types. For a given field name, its type should remain the same in all documents that have that field. Example: A <em>price</em> field is a floating point number <em>price:37.99</em> in one document. It should not be a string <em>price: “4.95”</em> in another document. </p></li><li><p>If you plan to search or facet on any aspect of nested documents, a consistent layout is crucial. Index mappings are based on field name and structural placement (aka “path”).</p></li><li><p>Field name is <em>the</em> key. MongoDB Search architecture works best with a simple <em>field_name</em>=value structure, as index mapping configuration is first driven by the name of a field, and the internal Lucene index data structures are founded upon that field name. </p></li></ul><p>Further, if field types are inconsistent, each will be indexed based on the field mapping setting for that particular type. Queries and faceting are also type-specific. In the above <em>price</em> example, a numeric range query would only be able to match the numeric price value, and string faceting would only show the string <em>price</em> value. </p><h3>Partial indexing and transforming documents</h3><p>What you have might not be exactly what you want to index, so there’s a handy way to use <a href="https://www.mongodb.com/docs/search/about/view-support/">Views with MongoDB Search</a>, providing a flexible mechanism to omit or morph a document during indexing. Here are some use cases where a View shines:</p><ul><li><p>Computed (Search) Pattern: querying for array size</p></li><li><p>Partial indexing: Skipping docs from indexing</p></li><li><p>Unsearchable fields: Removing a sensitive field</p></li><li><p>Flattening Attribute Pattern</p></li><li><p>Vector dimension reduction</p></li><li><p>Textualize documents</p></li></ul><p>A search index compatible View is a constrained pipeline that can include documents using a <em>$match</em> or, stated another way, you can exclude documents that should not be indexed/searchable, and can morph the resultant document using <em>$addFields</em> and <em>$set</em> stages.</p><p>Let’s go through the steps to create and index a view, using the Computed Pattern use case.</p><p>You’ve got documents that have a reasonable size-constrained array present on documents, something like this (to be generic):</p><p>And you need to query by the number of items in the values array. A core search mantra is to “index it like you want to find it”, so it would be ideal if we had a searchable num_values field. Sure, we can create and maintain this in our application at every document create and update touch-point. </p><p>Using the MongoDB shell, here’s how to create a View on a collection. Here, the collection of documents is called <em>docs</em>, and the view is simply called <em>view</em>:</p><p>The results from the view during the indexing job are then mapped through the index configuration, allowing you to index fields and values that are created or augmented in the view.</p><p>Without using the view, or in some way maintaining the number of values and indexing it, searching for a document with a particular number of values is a full collection or index scan at the B-Tree level and not even possible at the Search level.</p><h4>Partial indexing</h4><p>This View only indexes non-archived documents:</p><h4>Unsearchable fields</h4><p>This View removes a field from the indexing so that it will not be searchable, even if mapping was fully dynamic.</p><h4>Flattening Attribute Pattern</h4><p>Here’s a document that uses the Attribute Pattern for arbitrary keys/values. Those keys and values are not really suitable for indexing and searching with MongoDB Search.</p><p>The following View converts the Attribute Pattern into easily indexed uniquely named fields with values.</p><p>With that indexing transformation, attributes are queried by their transformed field name:</p><h4>Vector dimension reduction</h4><p>With <a href="https://www.mongodb.com/docs/voyageai/tutorials/dimensions-and-quantization/">Matroyshka vectors</a>, dimensions can be truncated without adversely affecting distance computations by much. Take this 8-dimensional vector:</p><p>With the following transformation View, two additional fields are created, truncating the original 8-dimensional vector into 2 dimensions and also 4 dimensions.  The associated index configuration would map and index these vector fields appropriately for querying.</p><h4>Textualizing documents</h4><p>Given a basic movie document, a full plain text concatenation and formatting of all relevant, searchable text can be very useful for vectorizing (or using as a single full-text searchable blob).</p><p>The following View builds a <em>descriptive_text</em> field, concatenating all of the structured fields into a single textual blurb suitable for autoembedding, full-text search on a single field, and possibly for display purposes as a summary:</p><p>The view specification may not be pretty, but it’s easy to develop and work through the nuances of these sophisticated expressions in tools like Atlas UI or Compass, where you can see the results or errors and refine before making a View and indexing from it.</p><p>View transformations are a solid tool for tuning a search index to suit your needs. Use it when it fits!</p><h3>Field mappings</h3><p>Whether and how a field is to be indexed or not depends on the index configuration mapping.</p><p>The logic of whether a field is to be indexed follows this flow:</p><ul><li><p>An explicit field name mapping takes precedence.</p></li><li><p>If dynamic field mapping is enabled, and the field is not explicitly mapped, it will be mapped using the rules for that field&#39;s data type. Dynamic indexing rules are either an explicit <em>typeSet</em> specifying which types to index or an implicit “typeSet” that indexes all the basic field types, including strings as analyzed, indexed fields.</p></li></ul><p>Dynamic field mapping can be enabled at a document&#39;s top level and applies to all nested sub-documents, or can be individually controlled at any particular nested document level. </p><h4>The power of typeSet</h4><p>The default MongoDB Search index configuration specifies a fully dynamic mapping:</p><p>Which is an implicit “typeSet” with these mappings:</p><p>While this default flattens and index-mostly-everything mapping is convenient to be able to immediately query powerfully across all common data types in the fields on the documents in a collection, rarely is it the best configuration for your querying needs. </p><p>It is strongly recommended to define a <em>typeSet</em> in your index configuration for controlling settings on strings. The default for string fields turns on all the settings bells and whistles, such as storing the field value for highlighting and computing/indexing term offsets for highlighting… for every string field mapped! That not only adds up, but it also multiplies up too!  Huge savings can be made by turning down some of the default settings with a typeSet like this;</p><p>If you’ve been using dynamic: true for string fields, give that “lean_strings” configuration a try and compare index size. If you’re using highlighting, you’ll need to explicitly map that field to have <em>store: true</em> (a requirement for highlighting, but not a commonly used feature and certainly not on every string field of a document).</p><p>To treat a MongoDB Search index like a bunch of independent “B-tree”(-like) indexes so your queries can be served by fast indexes across any arbitrary number of fields and data types, simply ensure you’re indexing strings as <em>token</em> and include all other data types needed:</p><p>Note that <em>storedSource</em> is turned on to provide “index covered query” behavior, returning values directly from the search service, bypassing database lookup for each result document.</p><p>Sometimes you want to facet, sort, and <em>equals</em><em>/</em><em>in</em> query on a string value, but you also need full-text word-level search on it, too. This configuration illustrates how to index every string field as both a <em>token</em> type and an analyzed <em>string</em> type:</p><p>If you’re dynamically indexing string fields, a typeSet to at least set <em>store: false</em> and <em>indexOptions: “positions”</em> is greatly recommended - your index size will thank you!  There is likely only a single field or two that need to be highlightable. </p><p>Attributes on nested documents can be handled with a sub-document level mapping to encapsulate a section or all MongoDB Search-able fields for a document.</p><p>Field mapping details are officially documented in the <a href="https://www.mongodb.com/docs/atlas/atlas-search/define-field-mappings/">Define Field Mappings</a> doc.</p><p>These are the field types supported by MongoDB Search alongside the search operators available for those types:</p><p>The * annotated types are only available on explicit field mappings and do not apply dynamically. Both <em>document</em><em> </em>and <em>embeddedDocument</em> mappings apply to arrays of nested documents; the <em>document</em> mapping applies to dynamic mappings, whereas <em>embeddedDocument</em> only applies explicitly.</p><h2>Basic data types</h2><p>Indexing behavior is configurable within the options for the data type of that particular field instance. Numeric field types can be indexed for numeric <em>equals</em>, <em>in</em>, and <em>range</em> findability and range bucket faceting (counts per numeric range over a result set), and likewise for date field types.</p><p>Boolean values are indexed for <em>equals</em> and <em>in</em><em> </em>findability.</p><h3>Strings</h3><p>String fields are special, as they are analyzed and broken down into terms that are indexed into an inverted index data structure designed for word/token-level matching. Query ability with fast, relevance-ranked results on a pile of full-text documents stems from wisely tokenizing and further analyzing and organizing string text into an inverted index. </p><h3>Arrays</h3><p>The data type of the values within an array is used to determine how the field is mapped and indexed.  Arrays themselves aren’t their own field type. Nested documents by default are mapped as <em>document</em> type fields, and any fields within them are flattened and indexed as if they were fields on the main document with dotted name syntax, bringing all values of fields at the same relative path into an array of flattened values. There are good examples in the <a href="https://www.mongodb.com/docs/atlas/atlas-search/field-types/array-type/#std-label-fts-array-ref">How to Index the Elements of an Array</a> documentation. </p><h3>Nested documents</h3><p>The MongoDB mantra “data that is accessed together is stored together” builds upon the strengths of the document database, driving effective designs by nesting related and commonly accessed data into single values or arrays of attributes and sub-documents. MongoDB Search best practices adjust the mantra to “data that is searched together is indexed together.” By the nature of its architecture, a MongoDB Search index indexes all the mapped fields of a document together in a single structure so that any number of the indexed fields can be used (and intersected) in a single query for matching and ranking. There’s one index object per collection document, at least. Nested document structures present an interesting search challenge — are these structures to be intricately and independently matchable, or perhaps more straightforwardly considered a flat set of attributes used to match and return only the main document?</p><p>The results of a <em>$search</em> are typically only the matching top-level documents, not individual nested documents on their own. Top-level documents returned include the full document, including the nested structure; nested documents are, again, not typically returned independently or separately from their top-level parents. However, nested documents can be mapped as first-class index objects and matched, ranked, returned, and faceted independently of their ancestors and top-level containing structures.</p><p>There are two ways to handle indexing and searching content within nested documents: <em>document</em> and <em>embeddedDocuments</em>.  </p><ul><li><p>Flattened/<em>document</em> type: This is the default with dynamic mapping. It flattens sub-document structures into values on the root document. Queries match these flattened arrays and lose the nuance of the intra-embeddedDocument matching.</p></li><li><p><em>embeddedDocuments</em>: You must configure this — it doesn’t come by default. It indexes each specified embeddedDocument as a separate Lucene <a href="https://www.mongodb.com/docs/atlas/atlas-search/performance/index-performance/#embedded-documents">“index object”</a> tied to the parent index object. It allows for embeddedDocument-specific queries, similar to the <a href="https://www.mongodb.com/docs/manual/reference/operator/query/elemMatch/">$elemMatch</a> stage.</p></li></ul><p>Nested document structures can be several layers deep, and each level can be mapped in MongoDB Search as either <em>document</em> or <em>embeddedDocuments</em>—making it possible to index and intricately query multiple nested levels deep. Just because you can map things in this way, however, it doesn’t mean you should. Simpler and flatter is generally better, but some use cases will benefit greatly from indexing nested documents independently.</p><p>Let’s illustrate the pros and cons of the various ways to index nested structure with an example, Parents collection with a single “Mom” document, which has two kids. Kid1 is 5 years old. Kid2 is 11 years old. It looks like this in JSON:</p><h3>Flattened index objects</h3><p>Use <em>document</em> type mapping on paths containing nested documents (implicit <em>document</em>) to flatten the fields into a single index object in Lucene.  A <em>dynamic: true</em> mapping implicitly uses document mapping for nested sub-document structures.</p><p>This flat structure allows us to query for Parents with a child 5 years old and also have a child named “Kid2”, matching this “Mom” document. However, we cannot query for Parents who have a 5-year-old child who is named “Kid2”.  The original document, as far as the Lucene “index object” sees it, effectively looks like this, where the names and ages are not tied together:</p><p>Index object representation of <em>document</em> mapping of nested structure.</p><h3>Embedded index objects</h3><p>This same example document, with <em>children</em> mapped as an <em>embeddedDocuments</em> type, creates three index objects, one for each mapped embedded document and one for the main document. </p><p>This representation of what the example “Mom” document looks like as <em>embeddedDocuments</em> illustrates the difference from a <em>document</em><em> </em>mapping:</p><p>In the index structure, these documents are co-located as a physical contiguous block. Any update to the document, in any piece of its structure, reindexes that document, which in turn reindexes the entire block of mapped embedded documents.</p><p>Operationally, an update to an index object in Lucene is atomically a delete and re-add. Reindexing a document with mapped embedded documents causes that entire block of index objects to be deleted and then re-added. Constantly updating documents with mapped <em>embeddedDocuments</em> thrashes the Lucene indexed objects structure; the more embedded documents, the heavier it is to add, update, or delete a collection document.</p><p>Searches that query embedded documents are able to query each independent embedded “index object” document separately, along with all indexed ancestor values, and factor in the associated score into the returned documents&#39; computed relevancy ranking score.  Embedded documents can be individually returned and faceted using <em>returnScope</em> within <em>$search</em>; documents returned using <em>returnScope</em> are returned directly from the search engine with no database lookup, a great benefit when the use case fits. See <a href="https://www.mongodb.com/docs/search/query/return-scope/">Query, Filter, and Retrieve Arrays of Objects</a> for more details on this powerful feature.</p><p>To embed or not? It depends. Mapped embedded documents come at a cost and should only be used if the nuanced matching is needed and the explosion in the number of index objects is manageable. And even if that type of matching is needed, another deciding factor is the scale — a single Lucene index can contain a maximum of 2B documents. If you’re pushing up to that scale, partitioning and sharding are the next steps to consider. A collection of 200M database documents, each with 10 embedded documents, explodes to 2.2B (!) “index objects” ((10+1) * 200M), blowing up beyond what may be feasible or affordable.</p><p>Does the use case require matching across exact sub-document structure? Perhaps those sub-documents deserve to be first-class main documents in a search-based collection rather than contorting a nested structure to achieve something that fits best with an unwound, flatter structure. When considering embedded document mapping for search use cases, also consider turning the document structure inside-out so that the entities to be returned from a search request are first-class documents.</p><h2>On to the next section</h2><p>The practical considerations from physical and system constraints to field mappings and transformation views have been addressed above. These important details provide the basis for configuring a MongoDB Search index. Building on this foundation, <a href="https://www.mongodb.com/company/blog/technical/data-modeling-schema-design-for-search-part-2-use-cases-patterns">Part 2</a> will cover common use cases and the patterns that have emerged to address them.</p>]]></description>
      <pubDate>Thu, 08 Oct 2026 12:38:59 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/technical/data-modeling-schema-design-for-search-part-1-practical-considerations</link>
      <guid>https://www.mongodb.com/company/blog/technical/data-modeling-schema-design-for-search-part-1-practical-considerations</guid>
    </item><item>
      <title>Data-Driven, Interoperable Core Banking: A BIAN and MongoDB Perspective</title>
      <description><![CDATA[<p>Core banking is the operational heart of a bank: the system of record for accounts, payments, and ledger entries that every other capability depends on. Yet core banking modernization remains one of the industry’s hardest priorities because the problem is not just legacy infrastructure. Every new product, channel, regulatory requirement, or acquisition adds more complexity to the systems that run the bank.</p><p>Across products, channels, business units, and systems, the same banking concept is often defined in slightly different ways. A payment, an account, a balance, or a financial event may look similar across systems, but not identical. Over time, those small differences create duplicated logic, fragile integrations, and rising operational complexity, even in architectures designed to be more modern and distributed.</p><p>What banks need is not simply a faster way to replace old systems, but a foundation for building and evolving core capabilities consistently. The Banking Industry Architecture Network (BIAN)2 provides that shared semantic foundation by defining common banking domains, boundaries, and service interactions. MongoDB provides the data platform to implement those domains in a way that matches real banking structures, supports continuous change, and enables real-time, API-driven modernization.</p><p>In this blog, we explore how BIAN and MongoDB give banks a practical path to composable core banking: one that reduces semantic fragmentation, preserves financial integrity, and lets teams modernize domain by domain rather than through repeated enterprise-wide redesign.</p><h2><strong>What modern banking demands</strong></h2><p>As McKinsey(1) observed in its Global Banking Annual Review:<em> &quot;Banks must aspire to scalability at incremental cost, moving away from traditional, linear delivery models.... Speed here is not just about execution — it is about learning faster than competitors and the constant reinvention of core banking systems toward leaner, more modular models.&quot;</em></p><p>That observation reflects a broader shift across the industry. Modernization now requires a foundation that supports speed, learning, and continuous adaptation without adding complexity. This is why banks are moving toward more composable core banking models, where capabilities are clearly defined, services evolve independently, and frameworks such as The Banking Industry Architecture Network (BIAN) help preserve consistency, interoperability, and financial integrity without repeated enterprise-wide redesign.</p><h2><strong>The architectural framework BIAN defines</strong></h2><p>First, BIAN provides a shared business language. Rather than prescribing implementation, it establishes a shared vocabulary across domains, teams, and systems. Think of BIAN as a common grammar for banking. It does not determine what an organization says. It ensures that everyone understands it in the same way. For modernization programs, this is more than an architectural concern. A shared semantic model reduces integration effort, simplifies governance, accelerates project delivery, and creates a foundation that can scale across products, channels, and business lines without multiplying complexity.</p><p>Second, BIAN defines domain boundaries and business capabilities. It helps banks decompose core banking into clearer service domains, each with a more explicit scope and ownership model. This matters because composable architectures only work when those boundaries are understood.</p><p>Third, BIAN supports interoperability. It defines standardized service interactions so that applications, channels, and partners can work with banking capabilities in a more predictable way. In practice, this means less custom translation between systems and a better foundation for reusable APIs.</p><p>Taken together, BIAN is not just a vocabulary. It is a business and service model for designing modern banking architectures.</p><p>One concern sometimes surfaces: Does adopting BIAN mean developers need to learn an entirely new vocabulary? No. BIAN’s naming convention lives at the API and contract layer. Inside the application, developers work with the same familiar field names they always have. Adopting an industry standard doesn&#39;t stall developer velocity. Teams can build and iterate using familiar domain models internally, while BIAN canonical names govern the boundaries. This minimizes code refactoring, lowers training overhead, and allows institutions to adopt a standard framework incrementally without disrupting daily delivery pipelines.  </p><p>The diagram below shows how this works in practice: BIAN&#39;s shared semantic contract sits above four banking domains, each independently implemented as services, all grounded in a common data layer.</p><p><strong>Figure 1.</strong> BIAN provides the shared semantic contract, while MongoDB provides the implementation platform underneath it.</p><h2><strong>Why MongoDB is the right data platform</strong></h2><p>BIAN defines the semantics, business structure, and interaction model, but that model only creates value if it can be implemented consistently in technology. MongoDB provides that implementation layer, with the flexibility, integrity, and scale required for a modern banking platform.</p><p>A <a href="https://www.mongodb.com/docs/manual/data-modeling/">document model</a> built for banking complexity. New products introduce new attributes. Regulatory changes introduce new requirements. Customer expectations create new interactions and channels. Traditional relational approaches often struggle with this rate of change — schema modifications, data transformations, integration mappings, and migration projects become recurring activities that consume resources and slow innovation. Using a flexible document model, banks can represent business domains in ways that closely mirror real-world structures. Related information can be stored together, making business objects easier to understand, manage, and evolve. New capabilities can be introduced incrementally without requiring disruptive redesigns across dependent systems.</p><p>JSON is the connective tissue that makes this possible.<strong> </strong>As a universally understood, human-readable format, JSON acts as the glue across the entire architecture: from the database document to the API payload. BIAN&#39;s service APIs are JSON-based by design, a meaningful distinction in an industry where XML, plain text, and proprietary formats have historically fragmented integration layers and created costly mapping overhead.  When JSON is both the storage format and the interchange format, the same business object flows from MongoDB through microservices and into partner integrations with minimal translation or transformation. The traditional ORM (Object-Relational Mapping) impedance mismatch disappears. JSON-to-JSON transformation is an order of magnitude faster and simpler than mapping relational tables to fluid API payloads. Partners integrate more quickly, new channels launch with less effort, and teams develop independently without creating conflicting interpretations of core business entities. This reduces duplication and lowers the operational cost of complex architectures, allowing organizations to establish a single, authoritative model from database to API and gain coherence and agility that is difficult to achieve in any other way. </p><h2><strong>What this enables technically</strong></h2><ul><li><strong>Transactional integrity for financial workloads.</strong> Every banking architecture must answer a fundamental question: how do we safely account for money in a modern distributed system? The answer lies in an immutable source of truth: the General Ledger. Every financial event generates balanced journal entries that are recorded permanently. Corrections occur through reversals rather than edits, preserving a complete audit trail and ensuring accountability.  MongoDB guarantees financial integrity through two complementary mechanisms: single-document atomicity, which handles the most common case - updating a ledger account and its balance state in one operation, and multi-document ACID transactions, which cover complex, cross-domain workflows spanning multiple collections. The result is atomic consistency across payment records, ledger entries, and journal postings, without sacrificing the performance that high-throughput banking demands.</li><li><strong>Event-driven operations.</strong> Combined with event-driven capabilities such as Change Streams, organizations can build architectures in which financial events are propagated to downstream services using durable, ordered change notifications. Payment status events, balance updates, and compliance triggers flow reliably across the platform while transactional integrity remains protected. This enables composable architectures where services evolve independently without compromising the accuracy of financial records.</li><li><strong>Incremental modernization at enterprise scale.</strong> <a href="https://www.mongodb.com/products/platform">MongoDB Atlas</a> provides the global scale, resilience, security, and operational simplicity that enterprise banking requires. Banks can modernize incrementally — domain by domain, service by service — rather than through large-scale, disruptive transformation programs. The result is an organizational advantage as much as a technical one: when teams can evolve services independently while maintaining a shared business language, innovation accelerates, new products launch faster, and regulatory requirements are addressed more efficiently.</li></ul><h2><strong>A composable banking architecture on MongoDB</strong></h2><p>This architecture brings the pieces together across four layers: a core banking layer with accounting registry and general ledger, a unified data layer grounded in BIAN’s document-based industry model, an AI or agentic data layer connecting a broader ecosystem of banking applications, and an API semantic layer delivering BIAN domain-driven services. </p><p>With a unified, context-rich data layer in MongoDB — including <a href="https://www.mongodb.com/products/platform/atlas-vector-search">Atlas Vector Search</a> — AI agents can parse standardized BIAN domain data to automate compliance, detect fraud in real time, and deliver personalized insights. No complex ETL. No data assembly. The intelligence layer builds directly on the semantic and data foundation already in place.</p><p><strong>Figure 2.</strong>  An intelligent, agentic ecosystem.</p><h2><strong>An operating model for continuous transformation</strong></h2><p>A modern core banking platform is defined by how quickly it can absorb change. A semantic foundation built on BIAN and MongoDB gives banks three things legacy architectures cannot: a shared business language that eliminates integration friction, a document model that evolves without schema migrations, and transactional integrity that scales without compromise. That is the foundation for what the industry - and BIAN itself - calls coreless banking: not a single system of record, but a composable ecosystem of domain services, each owning its data, all speaking the same language.</p><p>The result is more than a modern banking platform. It is an operating model for continuous transformation.</p><ol><li>From McKinsey&#39;s Global Banking Annual Review 2026: Precision with speed: <a href="https://www.mckinsey.com/industries/financial-services/our-insights/global-banking-annual-review">https://www.mckinsey.com/industries/financial-services/our-insights/global-banking-annual-review</a> </li><li>BIAN website: <a href="https://bian.org/">https://bian.org/</a> </li></ol>]]></description>
      <pubDate>Tue, 06 Oct 2026 16:26:54 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/data-driven-interoperable-core-banking-bian-perspective</link>
      <guid>https://www.mongodb.com/company/blog/innovation/data-driven-interoperable-core-banking-bian-perspective</guid>
    </item><item>
      <title>MongoDB Queryable Encryption: Prefix, Suffix, and Substring Queries Are Now GA</title>
      <description><![CDATA[<p>Last week, <a href="https://www.mongodb.com/company/blog/product-release-announcements/everything-announced-mongodb-local-nyc-2026">we announced</a> the general availability of prefix, suffix, and substring query support in MongoDB Queryable Encryption. These capabilities extend Queryable Encryption beyond equality and range queries, and they’re now fully supported for production workloads. </p><p><a href="https://www.mongodb.com/docs/manual/core/queryable-encryption/">MongoDB Queryable Encryption</a> is a groundbreaking, industry-first in-use encryption technology, developed by the <a href="https://www.mongodb.com/company/research/cryptography-research-group">MongoDB Cryptography Research Group</a>. It enables customers to encrypt sensitive application data, store it in encrypted form in MongoDB, and run expressive queries on that encrypted data without decrypting it. The database never sees the data in plaintext.</p><p>Organizations can now run flexible text searches, matching partial names, words, or identifiers, on encrypted data in production—keeping the underlying information protected by design, under clearly defined security guarantees. That means stronger data protection, simpler compliance, and no need for workarounds like external search indexes. All with minimal code changes and no new infrastructure.</p><p>With support for prefix, suffix, and substring queries generally available in Queryable Encryption, MongoDB enables organizations to protect sensitive data throughout its lifecycle: at rest, in transit, and in use. As a result, teams can build secure, privacy-preserving applications without compromising functionality. Queryable Encryption is available at no additional cost in <a href="https://www.mongodb.com/atlas">MongoDB Atlas</a>, <a href="https://www.mongodb.com/products/self-managed/enterprise-advanced">MongoDB Enterprise Advanced</a>, and <a href="https://www.mongodb.com/products/self-managed/community-edition">MongoDB Community Edition</a>.</p><h2>The challenge: Data is only protected until you need to use it</h2><p>Most organizations store sensitive data: personally identifiable information (PII) like names and Social Security numbers, or protected health information (PHI) like medical records. Keeping that data secure while it sits in storage or moves across a network is well understood. Encryption at rest and in transit is standard practice today.</p><p>Querying that data is a different story. Traditional encryption makes data unreadable, which means a database can&#39;t search it without decrypting it first. Consider a healthcare provider that needs to find all patients with a diagnosis containing the word &quot;edema&quot;; without decrypting the records, the database can&#39;t search for that term.</p><p>To work around this, many organizations leave sensitive fields unencrypted or build external search indexes to enable the queries their applications need. Both approaches add operational overhead. Both also increase the risk of unauthorized access, right at the moment sensitive data is most exposed.</p><p>This gets harder under regulatory pressure. Standards like the <a href="http://hhs.gov/hipaa/index.html">Health Insurance Portability and Accountability Act</a> (HIPAA), the <a href="https://www.pcisecuritystandards.org/standards/pci-dss/">Payment Card Industry Data Security Standard</a> (PCI-DSS), and <a href="https://gdpr.eu/what-is-gdpr/">General Data Protection Regulation</a> (GDPR) increasingly expect organizations to demonstrate that sensitive data stays protected at every stage, not just at rest and in transit. Providing protection while data is actively in use is the piece most encryption approaches can&#39;t address.</p><p>To fully protect sensitive data and meet compliance requirements, organizations need a way to search encrypted data without decrypting it, and without sacrificing performance or adding new infrastructure.</p><h2>Zero-exposure data protection</h2><p>MongoDB Queryable Encryption is built to close this gap. It keeps sensitive data encrypted while it&#39;s actively being searched, the one stage that other encryption methods can&#39;t reach.</p><p>With Queryable Encryption, sensitive fields are never stored, transmitted, processed, or returned in plaintext, even on the database server itself. Queries are run on encrypted data. There&#39;s no decryption, and no window where the data is exposed.</p><p>This is possible because Queryable Encryption is built on a structured encryption scheme that keeps data encrypted during query processing on the server at all times. The scheme is fully open source and independently verifiable, not a black-box vendor claim. It&#39;s an industry-first approach: no other database technology offers this level of in-use encryption today, and it doesn&#39;t depend on specialized hardware like secure enclaves.</p><p>Organizations already trust Queryable Encryption to protect some of their most sensitive data. <a href="https://www.thestack.technology/how-frances-internal-security-forces-migrated-to-mongodb-in-just-three-months/">France&#39;s internal security forces (ANFSI)</a> rely on it to secure sensitive records, backed by government-grade security review.</p><p>For teams handling PII, PHI, or other regulated data, this means one less place where sensitive information can be exposed, even from insiders with direct database access.</p><h2>More expressive search, built in</h2><p>Until now, Queryable Encryption has supported equality and range queries in general availability. That covered exact matches and bounded numeric lookups, but applications often need something more flexible: partial-name lookups, autocomplete, or partial-word filtering. With prefix, suffix, and substring queries now generally available, that gap is closed.</p><p>Here&#39;s what&#39;s now possible directly on encrypted fields:</p><ul><li><p><strong>Prefix queries</strong> return documents where a field value starts with a specific sequence of characters. For example, finding all customers whose last names begin with &quot;Mac.&quot;</p></li><li><p><strong>Suffix queries</strong> return documents where a field value ends with a specific sequence. For example, matching the last four digits of an encrypted Social Security number.</p></li><li><p><strong>Substring queries</strong> return documents where a specific sequence appears anywhere in the field. Substring search covers short, structured fields up to 50 characters, searching 2- to 6-character terms. For example, searching for &quot;eng&quot; within an encrypted job title field, matching both &quot;Engineer&quot; and &quot;Engineering Manager.&quot;</p></li><li><p><strong>Range queries</strong> (existing) return documents where a field value falls within a specified lower and upper bound, like an encrypted salary range.</p></li><li><p><strong>Equality queries</strong> (existing) return documents where a field value matches exactly, like a specific encrypted email address.</p></li></ul><p>These query types run through MongoDB&#39;s native query engine and drivers, the same ones used for every other query type. There are no external search indexes to stand up, no middleware to maintain, and minimal changes to application code. Teams get expressive, partial-match search on encrypted data using the same architecture they already run.</p><h2>Compliance you can prove, not just claim</h2><p>Meeting requirements like HIPAA, PCI-DSS, and GDPR means demonstrating that sensitive data is protected, not just asserting it. That&#39;s difficult when encryption claims can&#39;t be independently verified, and even harder when the claim doesn&#39;t cover data while it&#39;s actively in use.</p><p>Queryable Encryption gives compliance and risk teams a defensible answer. Its structured encryption scheme is fully open source, so the cryptography behind it can be independently reviewed rather than taken on faith. And because it protects data through query processing, not just at rest and in transit, it addresses a stage most compliance programs can&#39;t otherwise account for.</p><p>With prefix, suffix, and substring queries now generally available, that same evidence extends to more use cases: partial name and email search, partial word filtering in free-text fields, and partial ID matching. The result is fewer audit gaps and fewer fragmented tools to reconcile, whether workloads run on-premises, in a hybrid environment, or across multiple clouds.</p><h2>What teams can now build</h2><p>With prefix, suffix, and substring queries generally available in Queryable Encryption, here are some examples of what organizations can now achieve:</p><ul><li><p><strong>PII search for compliance and usability:</strong> Regulations like GDPR and HIPAA mandate strict privacy of personal information. With prefix queries, teams can retrieve users by last name or email prefix while keeping the underlying data encrypted. That makes compliance easier without sacrificing search functionality.</p></li><li><p><strong>Partial word filtering on structured fields:</strong> Structured fields like diagnoses often require partial matching. With substring query support, teams can search an encrypted health condition field for a term like &quot;diabet,&quot; matching both &quot;diabetes&quot; and &quot;diabetic.”</p></li><li><p><strong>Secure ID validation:</strong> Identity workflows often rely on partial identifiers, like the last four digits of a Social Security Number, a National Insurance Number, or an Aadhaar Number. Suffix queries enable these lookups on encrypted fields without revealing full values, reducing the risk of data leaks in regulated environments.</p></li><li><p><strong>Case management for public agencies:</strong> Case numbers and reference IDs in public sector applications often follow structured formats. Prefix queries let agencies retrieve records using region- or office-based prefixes, like &quot;NYC-&quot; or &quot;EUR-,&quot; without exposing sensitive case metadata.</p></li></ul><h2>Get started with Queryable Encryption</h2><p>Prefix, suffix, and substring queries give teams a new level of flexibility in searching sensitive data without requiring them to choose between security and functionality. Whether the goal is meeting compliance requirements, reducing infrastructure complexity, or simply building better applications, these capabilities are ready for production today.</p><p>Prefix, suffix, and substring queries give teams a new level of flexibility in searching sensitive data. These new query types help protect sensitive data against unauthorized access and meet compliance requirements while reducing infrastructure and operational complexity. </p>]]></description>
      <pubDate>Tue, 06 Oct 2026 14:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/product-release-announcements/queryable-encryption-prefix-suffix-substring-queries-are-now-ga</link>
      <guid>https://www.mongodb.com/company/blog/product-release-announcements/queryable-encryption-prefix-suffix-substring-queries-are-now-ga</guid>
    </item><item>
      <title>Tag, You&#39;re It: Using MongoDB Labels to Drive DataDog Business Logic</title>
      <description><![CDATA[<p>MongoDB Atlas and DataDog work better together to enable you to take advantage of the automation, elasticity, and scalability of modern infrastructure and act on real-time information to make well-informed decisions.</p><p>With the latest release of MongoDB’s DataDog integration, we’ve added the ability to send custom defined labels in Atlas, CM, and OM to tags on the DataDog metrics object. Applying tags to DataDog&#39;s metrics allows users to organize and categorize their metrics in various ways.</p><p>Here&#39;s how the new DataDog metrics tagging works:</p><ul><li><p><strong>Define key-value labels in MongoDB at the cluster level that get automatically sent to DataDog as metrics tags.</strong> You  can define tags based on the attributes you want to track and then assign those tags to the relevant metrics. For example, a tag named &quot;region&quot; could be assigned to metrics representing servers in different geographic regions.</p></li><li><p><strong>Filter and group metrics in DataDog by tags.</strong> You can then use these tags to filter, group, and aggregate metrics in various ways. For example, you can group metrics by tags such as &quot;application,&quot; &quot;environment,&quot; or &quot;owner&quot; to gain insights into how different parts of your infrastructure are performing. You can also filter metrics by tags to view just the metrics you&#39;re interested in.</p></li><li><p><strong>Use tags to set alerts and dashboards.</strong> You can create alerts and dashboards in DataDog based on tags. This allows you to monitor specific aspects of your infrastructure, such as servers in a particular region or metrics related to a specific application.</p></li></ul><p>DataDog&#39;s metric tagging feature is highly flexible and customizable, allowing you to adapt it to your specific organizational needs. Effectively using metrics tagging will grant you a better understanding of your application’s performance and help organizations make data-driven decisions.</p><p>Read on to see an example of how MongoDB’s DataDog tagging integration can help organize your metrics and how you can use it to drive your business’ monitoring requirements.</p><h2>Setting cluster labels in Atlas</h2><p>In the example below, I’ll use MongoDB’s Data API to access and configure my MongoDB Atlas data. In this case, I’ll use MongoDB’s Data API to set new labels on my MongoDB Atlas clusters. To explore the new MongoDB Data API, you can use the <a href="https://www.postman.com/mongodb-devrel/workspace/mongodb-public/documentation/17898583-25682080-e247-4d25-8e5c-1798461c7db4">public Postman workspace</a> provided by the MongoDB developer relations team.</p><p>You can use the cluster configuration API endpoint to add labels to a cluster in MongoDB.</p><p>You can then use the get all clusters endpoint to verify that your labels were applied correctly.</p><p>Once you’ve labeled your MongoDB clusters, set up your DataDog integration as you would normally. For more information on configuring MongoDB’s DataDog integration, refer to the documentation <a href="https://www.mongodb.com/docs/atlas/tutorial/datadog-integration/">here</a>.</p><h2>Using DataDogs metrics tagging to drive business logic</h2><p>After setting up your DataDog integration, you’ll automatically start seeing the labels you previously defined in MongoDB show up as tags on your DataDog metrics. You can now use these tags to filter, organize, and define logic based on the needs of your business.</p><p>As an example, you can filter results in the DataDog Metrics Explorer. If I only want to see metrics for clusters associated with the “leafy” application, I can use tags to filter the metrics I get back.</p><p>You can also use tags to define custom logic for your DataDog monitors. In this example, I’m configuring monitors to trigger different priority alerts based on the metrics tags. When query targeting exceeds the threshold for production clusters, I’ll get a P2 alert. However, the same alert for non-production environments wouldn’t have the same priority. In this example, I can use the “usage” metrics tag to define different alerting priorities.</p><p>And finally, Datadog metrics tagging can help you organize and filter data in dashboards. Metrics tagging enables you to easily group related data together and create more focused and specific dashboards. For example, you can use the app_name tag here to filter on just the leafy application. This will help you quickly identify and troubleshoot issues. Using tags effectively can grant deeper insights into your data and help your organization make more informed decisions to improve the performance and availability of your applications and infrastructure.</p><p>This new enhancement to MongoDB’s DataDog integration provides significantly more flexibility in how you use DataDog and helps you get the most out of your investment. The DataDog integration is available on MongoDB Atlas on M10 cluster tiers and higher.</p><p></p>]]></description>
      <pubDate>Mon, 05 Oct 2026 14:49:38 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/product-release-announcements/tag-youre-it-using-mongodb-labels-drive-datadog-business-logic</link>
      <guid>https://www.mongodb.com/company/blog/product-release-announcements/tag-youre-it-using-mongodb-labels-drive-datadog-business-logic</guid>
    </item><item>
      <title>MongoDB 9.0: This Is What a Database Should Be</title>
      <description><![CDATA[<p>For years, organizations have been told to accept a series of tradeoffs when it comes to their technology stacks:</p><ul><li><p>If you want more performance, add more infrastructure.</p></li><li><p>If you want stronger security, prepare for application constraints.</p></li><li><p>If you want observability, you’ll have to connect more tools and translate more signals.</p></li><li><p>If you want resilience, hire operators.</p></li><li><p>If you want AI, rethink your entire architecture.</p></li></ul><p>We disagree with these and with the assumption that as applications grow more sophisticated, database operations are doomed to become impossibly complex. The database does not have to be a bottleneck. It can and should provide the performance, control, and flexibility to move faster.</p><p>Every application, transaction, customer interaction, AI model, and agent—the database should be the engine powering these, not what’s holding them back. <strong>That&#39;s the idea behind </strong><a href="https://www.mongodb.com/products/updates/version-release"><strong>MongoDB 9.0</strong></a><strong>, the most advanced release in MongoDB&#39;s history.</strong></p><h2>The world is changing. Databases need to keep pace.</h2><p>Modern applications must serve millions of users while simultaneously supporting growing fleets of AI agents. AI systems need access to fresh operational data, and agents execute actions continuously, introducing new levels of concurrency and unpredictability. Development teams are expected to move faster, while security and compliance requirements continue to rise. Yet many organizations are still stitching together separate systems for operational data, analytics, information retrieval, observability, security, and AI.</p><p>Every additional system creates complexity and an additional surface of risk. Every integration creates friction. Every bottleneck slows innovation. Organizations need a data foundation that supports applications, builders, and AI systems without requiring a new architecture for each emerging requirement in a fast-moving market.</p><p><a href="https://www.mongodb.com/docs/manual/">MongoDB 9.0</a> is built for that reality. It advances MongoDB’s core engine across performance, scale, security, resilience, observability, and developer productivity. It is not a collection of disconnected features. It is a single, coherent experience for building and operating modern applications across MongoDB’s entire offerings. Let’s explore the key pillars that make MongoDB 9.0 the foundation for organizations pushing innovation forward instead of working around the constraints of the past.</p><h2>More room to build</h2><p>Performance matters when it translates into faster user experiences and business growth.</p><p>MongoDB 9.0 raises the ceiling for demanding enterprise and AI-powered applications. Compared to 8.0, transactional workloads achieve up to 20% higher throughput, enabling applications to process more business-critical operations more efficiently. Core operations are faster across the board, with find-one queries up to 35% faster and update-one queries up to 30% faster, helping applications respond more quickly to users and downstream systems. For large deployments, MongoDB 9.0 delivers nearly 2x higher throughput, enabling teams to support more users, transactions, and AI-driven activity before adding infrastructure or re-architecting applications.</p><p>For MongoDB Atlas customers, <a href="https://dochub.mongodb.org/core/atlas-gen2-clusters">Gen2 compute</a> is now available for M30+ dedicated clusters on Amazon Web Services (AWS) and Google Cloud Platform (GCP). Gen2 delivers improved price-performance along with more flexible storage and IOPS controls, helping organizations optimize resources for their specific workload requirements.</p><p>The outcome is simple: faster application performance, greater operational efficiency, and more room to grow within the infrastructure you already run. MongoDB 9.0 helps organizations scale further before performance becomes a constraint.</p><p>Our goal remains the same across the board: superior performance at optimal cost.</p><h2>Security without compromise </h2><p>As organizations collect more sensitive data, security requirements continue to grow. Too often, stronger protection comes at the expense of application functionality. MongoDB 9.0 challenges that tradeoff.</p><p>MongoDB’s industry-first <a href="https://www.mongodb.com/docs/manual/core/queryable-encryption/">Queryable Encryption</a> now supports prefix, suffix, and substring queries, allowing applications to perform partial-match searches while data remains encrypted throughout its lifecycle. Real applications don’t search only for exact matches; they search names, identifiers, domains, and other fields the way users actually interact with them. With MongoDB 9.0, organizations can build rich search experiences over sensitive data without sacrificing security.</p><p>MongoDB Atlas also expands secure connectivity and encryption capabilities. New support for Google Private Service Connect (PSC) <a href="https://www.mongodb.com/docs/atlas/security-private-endpoint/?cloud-provider=gcp">port mapping</a> simplifies private networking by allowing multiple database nodes to be accessed through a single endpoint. AWS PrivateLink <a href="https://www.mongodb.com/docs/atlas/security-private-endpoint/?cloud-provider=aws#manage-accepted-endpoint-regions">cross-region connectivity</a> enables private communication between applications and Atlas clusters across AWS Regions without exposing traffic to the public internet. Azure Key Vault (AKV) encryption at rest now supports <a href="https://www.mongodb.com/docs/atlas/security/azure-kms-secretless/">secretless authentication</a> using an Atlas-managed Service Principal, eliminating the need to store long-lived credentials in Atlas. Atlas also adds <a href="https://www.mongodb.com/docs/atlas/reference/faq/security/#which-certificate-authority-signs-mongodb-atlas-tls-certificates">support</a> for Google Trust Services (GTS) as a certificate authority, providing additional resilience for TLS certificate management.</p><p>Together, these capabilities make it easier to secure sensitive data, simplify network architectures, and strengthen encryption workflows. The result is enterprise-grade security that supports modern application requirements rather than limiting them.</p><h2>When pressure arrives, the database should know what matters</h2><p>Production environments rarely fail because everything goes according to plan. They fail when traffic spikes, connections surge, resources contend, or workload patterns change faster than teams can respond. MongoDB 9.0 helps make those moments uneventful.</p><p><a href="https://www.mongodb.com/docs/atlas/intelligent-workload-management/">Intelligent Workload Management (IWM)</a> is a managed availability capability that keeps Atlas clusters responsive and predictable even under overload. When a cluster is overloaded, IWM queues transient traffic spikes, keeps short-running operations moving and long-running operations stable, and throttles excess requests only as a last resort to maintain cluster stability. It buys crucial time for auto-scaling to add capacity or for an operator to act. This means that, even under overload, your application stays online and your customers never notice the difference. </p><p>MongoDB 9.0 also strengthens the controls that help teams prepare for and recover from the unexpected. For self-managed MongoDB, Enterprise Advanced now writes <a href="https://www.mongodb.com/docs/ops-manager/current/tutorial/restore-direct-from-s3/">S3 backups</a> over a direct data path that bypasses the Ops Manager control plane entirely for faster performance. It also produces fully immutable, portable point-in-time restore (PITR) chains in S3. Safe-sequence maintenance controls help validate infrastructure updates in non-production environments before they reach production.</p><p><a href="https://www.mongodb.com/docs/atlas/backup/cloud-backup/restore-from-db-coll/?interface=atlas-api&amp;restore-type=snapshot#std-label-restore-from-db-coll">Database and collection-level restores</a> for Atlas, enhanced snapshot management, and customizable <a href="https://www.mongodb.com/docs/atlas/tutorial/cluster-maintenance-window/">maintenance waves</a> give teams greater control over data recovery and maintenance operations. Together, these capabilities help organizations strengthen resilience, streamline change management, and manage updates on their own terms.</p><p>Resilience becomes less of a promise and more of an operating capability: protect critical work, recover what matters, and make maintenance more controlled.</p><h2>See the whole system</h2><p>Modern systems generate enormous amounts of telemetry. The challenge is not collecting data. It is understanding what that data means in the context of the application. MongoDB 9.0 brings database behavior and application behavior into clearer view. A redesigned <a href="https://www.mongodb.com/docs/atlas/metrics-ui-rollout/">Atlas Metrics UI</a> gives teams a more intuitive way to understand cluster health and workload performance, helping them detect and diagnose issues faster.</p><p>Enhanced native <a href="https://www.mongodb.com/docs/atlas/tutorial/otel-integration/?otel-integration-type=custom">OpenTelemetry integration</a> enables Atlas metrics, logs, and <a href="https://www.mongodb.com/docs/atlas/export-logs-external-sinks/">events</a> to stream directly to any OpenTelemetry-supported observability platform, including popular options such as Datadog, New Relic, Dynatrace, Prometheus/Grafana, Google Cloud, Azure, and AWS CloudWatch.</p><p>MongoDB 9.0 also expands <a href="https://www.mongodb.com/docs/atlas/query-shape-insights/#view-metrics-in-charts-and-tables">Query Shape metrics</a> beyond reads to include inserts, updates, and deletes. Teams can see a more complete picture of workload performance, resource consumption, and database activity across the full application lifecycle.</p><p>When something goes wrong, organizations should not have to wonder where to look first or translate their database signals before they can act.</p><h2>Modernize without starting over</h2><p>Modernization should not require organizations to discard the investments that already make their teams productive. MongoDB 9.0 lowers the cost of moving forward. The MongoDB extension for <a href="https://www.mongodb.com/docs/languages/java/mongodb-hibernate/current/">Hibernate ORM</a> enables Java developers to continue using familiar Hibernate APIs and Hibernate Query Language while working with MongoDB.</p><p>New <a href="https://www.mongodb.com/docs/upcoming/core/schema-validation/specify-validation-level/#specify-constraint-validation">schema constraints</a> make it easier to enforce application expectations directly in the database, providing teams with a shared, authoritative place for data rules.</p><p>Together, these capabilities create a more practical path to modernization: preserve familiar development patterns, reduce distributed validation, and gain the flexibility of MongoDB without rebuilding application logic from scratch.</p><h2>One foundation for what comes next</h2><p>The next generation of applications will combine operational workloads, search, analytics, and AI. Agents will continuously read and write data. Applications will need to respond faster, operate more reliably, and protect more sensitive information, all at the same time. That future does not need more fragmentation. It needs a stronger foundation.</p><p>MongoDB 9.0 gives organizations greater capacity to grow, more control as conditions change, greater visibility into production behavior, stronger protection for sensitive data, and a lower-friction path to modernization. It strengthens MongoDB as the foundation for applications, builders, and AI systems across Atlas, Enterprise Advanced, Community Edition, and self-managed environments, including regulated and air-gapped deployments.</p><p>Because the database should never be the bottleneck.</p><p>It should be the platform that makes everything else possible.</p><p>This is what a database should be.</p><p><em>Note: </em><em>Performance results are based on internal MongoDB testing comparing MongoDB 9.0 and MongoDB 8.0 using public benchmark methodologies. Results may vary by workload, deployment, hardware, and configuration.</em></p>]]></description>
      <pubDate>Mon, 05 Oct 2026 14:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/product-release-announcements/mongodb-9-0-this-is-what-a-database-should-be</link>
      <guid>https://www.mongodb.com/company/blog/product-release-announcements/mongodb-9-0-this-is-what-a-database-should-be</guid>
    </item><item>
      <title>Everything Announced at MongoDB.local NYC 2026</title>
      <description><![CDATA[<p>MongoDB.local NYC 2026 is officially a wrap, and what an event it was! </p><p>An array of analysts, builders, businesspeople, caterers, engineers, fire marshals, media members, photographers, and trained elephants* chose to spend the day with us at Pier 36 in downtown New York, and we couldn’t be more thrilled. We just hope everyone had half as much fun as we did (it was a lot of fun). </p><p>The theme of this year’s event was how developers and enterprises can build anything and change everything with MongoDB. We released capabilities that make building AI applications and agents easier and faster for customers of all sizes—proving that MongoDB is <em>the</em> intelligent data platform for modern applications in the multi-cloud and AI era. </p><p>Specifically, the general availability of <a href="https://www.mongodb.com/company/blog/product-release-announcements/ai-demand-constant-unpredictable-extreme-mongodb-is-built-for-it">MongoDB 9.0, and the public previews of Atlas Infinite</a> and <a href="https://www.mongodb.com/company/blog/product-release-announcements/how-atlas-agent-engine-powers-mongodbs-internal-ai-strategy">Atlas Agent Engine</a> represent the most significant expansion of our platform yet. Meanwhile, Voyage AI by MongoDB’s best-in-class retrieval capabilities—as measured by the <a href="https://huggingface.co/spaces/embedding-benchmark/RTEB">Retrieval Embedding Benchmark</a> (RTEB)—give agents and applications better accuracy at lower cost. </p><p>But those were hardly the only announcements we shared! Read on for details about everything launched at <a href="https://www.mongodb.com/events/mongodb-local/nyc">MongoDB.local NYC 2026</a>. </p><h2>MongoDB Atlas: The multi-cloud, intelligent data platform</h2><p>Built for real-time operational data, best-in-class retrieval (with hybrid search and models from <a href="https://www.mongodb.com/products/platform/ai-search-and-retrieval">Voyage AI by MongoDB</a>), and for running agents in production, MongoDB Atlas offers organizations a single platform to build, deploy, and manage AI applications and agents at any scale, across any cloud, on their terms.</p><p>Here’s everything we announced related to MongoDB Atlas:</p><ul><li><strong>Atlas Infinite (Public Preview)</strong></li><ul><li>Enterprise workloads are getting bigger, more variable, and harder to predict, especially as agentic applications introduce unpredictable demand. Customers need a data layer built for that reality, not one that&#39;s stretched to accommodate it. <a href="https://www.mongodb.com/company/newsroom/press-releases/mongodb-launches-mongodb-9-0-the-best-version-ever-built-and-atlas-infinite-for-ai-scale-demand"><strong>Atlas Infinite</strong></a> separates compute from storage so each can scale independently, giving every workload the elasticity, responsiveness, and retrieval accuracy necessary.</li></ul><li><p><strong>Atlas Agent Engine (Public Preview)</strong></p></li><ul><li>MongoDB Atlas is the intelligent data platform where agents act on real-time data, and <a href="https://www.mongodb.com/company/newsroom/press-releases/mongodb-launches-atlas-agent-engine-to-put-ai-agents-in-production-without-a-new-stack"><strong>Atlas Agent Engine</strong></a> is how you build, deploy, and govern those agents. Built-in memory and retrieval means agents remember, act on accurate context, and use tokens more efficiently. A single control plane governs every agent action with a verifiable identity, giving enterprise-grade oversight. It runs on the MongoDB Atlas infrastructure that leading enterprises trust, so your agents work on the data you already have, right where it lives.</li></ul><li><p><strong>Atlas Ephemeral Clusters (Public Preview) </strong></p></li><ul><li><a href="https://www.mongodb.com/products/tools/atlas-ephemeral-clusters"><strong>Atlas Ephemeral Clusters</strong></a> allow AI agents and developers to spin up temporary MongoDB Atlas databases, removing human-in-the-loop friction to accelerate building and prototyping applications. With Ephemeral Clusters, agents can create a database in seconds and immediately receive credentials and a connection string—allowing them to build without delay.</li></ul><li><p><strong>Atlas SQL Dedicated Cluster (GA)</strong></p></li><ul><li>Now generally available, <a href="https://www.mongodb.com/products/platform/atlas-sql-interface"><strong>Atlas SQL Dedicated Cluster</strong></a> gives your BI tools direct SQL access to your dedicated cluster, with predictable pricing tied to what you already spend on MongoDB Atlas.</li></ul><li><p><strong>New Metrics UI in Atlas (GA)</strong></p></li><ul><li>The new <strong>Metrics UI gives MongoDB Atlas</strong> operators a clear place to understand cluster health, reduce navigation overhead, and investigate issues faster and more confidently. </li></ul></ul><h2>MongoDB 9.0: The best version of MongoDB, ever</h2><p>MongoDB 9.0 is the best-performing version of the world&#39;s most popular document database. MongoDB 9.0 strengthens the foundation customers already run on, with major gains in performance, security, and scalability.</p><p>Here’s everything we announced related to MongoDB 9.0:</p><ul><li><strong>MongoDB 9.0 (GA)</strong></li><ul><li>Now generally available, <a href="https://www.mongodb.com/products/updates/version-release"><strong>MongoDB 9.0</strong></a> is the best version of MongoDB ever built, delivering up to 2x higher throughput along with major advances across performance, scalability, observability, security, and builder productivity. It’s a core pillar of MongoDB’s intelligent data platform for AI, raising the ceiling for the most demanding enterprise and AI-native workloads. MongoDB 9.0 also extends our industry-first Queryable Encryption and private networking so even the most regulated organizations can build on it.</li></ul><li><p><strong>Intelligent Workload Management (GA)</strong></p></li><ul><li>MongoDB 9.0 features <a href="https://www.mongodb.com/products/capabilities/auto-scaling"><strong>Intelligent Workload Management</strong></a> (IWM), a managed availability capability that keeps MongoDB Atlas clusters responsive and predictable even under overload. Only available via MongoDB Atlas, IWM queues transient spikes, keeps short-running operations moving and long-running operations stable, and protects cluster health with no application changes required. For sustained overload, customers can optionally enable Load Shedding to actively reject excess work. IWM is activated by default across all dedicated MongoDB 9.0 Atlas clusters at no extra charge.</li></ul><li><p><strong>Queryable Encryption prefix and suffix query support (GA)</strong></p></li><ul><li>A groundbreaking, industry-first technology, <a href="https://www.mongodb.com/docs/manual/core/queryable-encryption/"><strong>MongoDB Queryable Encryption</strong></a> enables customers to encrypt sensitive data—such as personally identifiable information—while running expressive queries directly on the data without requiring any decryption. Queryable Encryption now supports prefix, suffix, and substring searches directly on fully encrypted fields, so sensitive data stays protected throughout its full lifecycle without slowing applications down.</li></ul><li><p><strong>MongoDB Extension for Hibernate ORM (GA)</strong></p></li><ul><li>The <a href="https://www.mongodb.com/resources/languages/java"><strong>MongoDB Extension for Hibernate ORM</strong></a> gives Java developers the fastest path to building production-ready applications on MongoDB using the familiar Hibernate ORM programming model, the de facto standard ORM framework for many Java enterprise applications. Organizations can use existing Hibernate skills and patterns with MongoDB, making it easier to modernize applications, accelerate development, and reduce migration complexity.</li></ul></ul><h2>Best-in-class search and retrieval</h2><p>Every answer, decision, and action an AI agent takes depends on retrieving accurate, relevant information. Better retrieval helps agents understand enterprise data more accurately, consume fewer tokens, and act more confidently in production.</p><p>MongoDB is dedicated to empowering customers to build retrieval systems that agents can rely on. Today’s announcements build on that foundation, further improving retrieval accuracy, reducing operational overhead, and giving teams more control over where their content is processed.</p><p>Here’s everything we announced related to search and retrieval:</p><ul><li><strong>Voyage rerank-3 and rerank-3-lite (GA)</strong></li><ul><li><a href="https://www.mongodb.com/products/platform/ai-search-and-retrieval">rerank-3</a> is a pointwise reranker designed as a drop-in upgrade to rerank-2.5, offering improved performance across nearly all domains with a specific focus on long-context and code capabilities. rerank-3-lite matches the retrieval quality of <em>rerank-2.5</em> at 40% of the price.</li></ul><li><p><strong>Europe Data Residency for Atlas Embedding and Reranking (GA)</strong></p></li><ul><li>MongoDB Atlas customers can use Voyage AI’s embedding and reranking models for AI-powered search while relying on MongoDB to process submitted content within the Europe Geography.</li></ul><li><p><strong>Native Reranking (GA) </strong></p></li><ul><li>MongoDB now offers reranking functionality <a href="https://www.mongodb.com/products/platform/atlas-vector-search">directly in the aggregation pipeline</a> using Voyage AI’s best-in-class reranking models.</li></ul><li><p><strong>Accelerated Search Aggregations (Public Preview)</strong></p></li><ul><li>MongoDB is upgrading <a href="https://www.mongodb.com/products/platform/atlas-search">Atlas Search&#39;s facet feature</a> so customers can facet on multiple fields at once and get more than just counts—stats like min, max, sum, and average—all in a single query, using the same data already indexed for search.</li></ul></ul><h2>From thinking (and prototyping) to acting at scale </h2><p>The announcements we shared at MongoDB.local NYC 2026 help customers move from prototype to production quickly. </p><p>They also build on an already-rock-solid foundation—our platform serves more than three trillion queries a day, and ~75% of the Fortune 100 rely on MongoDB for critical applications. Together, the launches of MongoDB 9.0, Atlas Infinite, and Atlas Agent Engine (+ Voyage AI’s industry-leading models) make MongoDB the intelligent data platform for modern applications in the multi-cloud and AI era.  </p><p>*Note that there were no trained elephants at MongoDB.local NYC 2026, sadly. Next year!?</p>]]></description>
      <pubDate>Wed, 30 Sep 2026 19:00:01 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/product-release-announcements/everything-announced-mongodb-local-nyc-2026</link>
      <guid>https://www.mongodb.com/company/blog/product-release-announcements/everything-announced-mongodb-local-nyc-2026</guid>
    </item><item>
      <title>Context Engineering Has a Retrieval Issue: Introducing rerank-3 and Native Reranking</title>
      <description><![CDATA[<p>Every team building AI agents discovers one fundamental truth: without the right information, an agent cannot reliably answer a question or take the correct action. </p><p>As large language model context windows grew larger, it was tempting to assume that just giving an agent more information would improve its accuracy. In practice, more context makes agents slower and more expensive, while also reducing accuracy by burying useful signals among irrelevant information.</p><p>That’s why the success of an agent now relies on <em>context engineering</em>, the practice of selecting, organizing, and presenting an agent with only the information it needs to complete a task effectively. </p><p>And the core of that work happens in retrieval. The question isn&#39;t how much you can fit in context. It&#39;s which ten things out of ten million you choose.</p><p>MongoDB’s intelligent data platform brings together <a href="https://www.voyageai.com/">Voyage AI’s</a> best-in-class embedding and reranking models with a platform for building, operating, and evolving complex retrieval systems. With today’s introduction of the Rerank 3 series and $rerank in the aggregation pipeline, developers can improve the quality and ordering of retrieved context in the same system where their operational data lives. The result is a simpler way to build retrieval systems that give agents the context they need to take action.</p><h2>The retrieval stack</h2><p>Effective retrieval requires a coordinated system to find useful information, determine what matters most, and efficiently deliver it to the agent.</p><p>The strategy determines how the system searches its data. Keyword search can surface exact terms, while vector search finds conceptually similar content. Filters and hybrid approaches add precision and control, ensuring that only the relevant context is retrieved.</p><p>Models determine what relevance looks like for your data. A stronger embedding model helps vector search identify better candidates by understanding conceptual similarity and query intent. A reranker allows first-stage retrieval to optimize for recall, then separates the strongest matches from the candidate set.</p><p>The right engine brings these disparate technologies together, keeping data current and queries efficient as the system runs in production. </p><p>Without a unified platform to manage retrieval, the work gets complicated fast. You might use one provider for embeddings, another for reranking, and multiple database vendors for your operational, search, and vector data. That means more integrations, sync jobs, and API calls to maintain. It can also create silent problems: your vector search index may use one embedding model version while your application uses another, hurting relevance without causing an explicit error.</p><p><strong>Figure 1.</strong> The disconnected retrieval pipeline.</p><p>MongoDB brings these pieces together in a single platform. It supports the search strategies developers need, including text, vector, hybrid, and filtered retrieval, and pairs them with Voyage AI’s state-of-the-art embedding models and rerankers. <a href="https://www.mongodb.com/docs/vector-search/crud-embeddings/automated-embedding/">Automated Embedding</a> keeps vectors synchronized as data changes, while native rerank lets developers refine results in the same aggregation pipeline. The result is a single query that can search operational data, apply the right retrieval strategy, rerank the results, and return the context an agent needs. </p><p><strong>Figure 2.</strong> The unified retrieval pipeline powered by MongoDB.</p><h2>The models</h2><p>Today’s introduction of <strong>rerank-3 and rerank-3-lite </strong>offers improved accuracy across all tasks, with the largest gains on long documents and code. rerank-3 outperforms Cohere Rerank v4.0 Pro by 2.72% and Qwen3-Reranker-8B by 3.02% overall. If you&#39;re on rerank-2.5 today, upgrading is a one-line model-name change. Same API, same price.</p><p>rerank-3 improves relevance no matter how the initial candidate set is retrieved. The table below shows the accuracy lift across several common first-stage retrieval methods.</p><p><strong>Table 1.</strong> Accuracy comparisons.</p><h2>The engine</h2><p>MongoDB is the operational retrieval engine underneath all of this, and every strategy runs natively against the same data your application already writes to. Lexical search catches identifiers, error codes, and exact product names. Vector search catches concepts and paraphrases. Hybrid retrieval combines them, and metadata filters keep the candidate set small enough to stay fast. None of it requires moving data into a separate system or holding two copies in sync.</p><p>Automated Embedding handles the part that usually breaks. Vectors are generated and refreshed at the field level in near real time, with token consumption and index health visible in the Atlas UI. There&#39;s no embedding job to own, and no chance for a split between the model version your index was built on and the model version your queries run against.</p><p>$rerank, available today, adds the final ordering step to that same pipeline. It&#39;s an index-less stage that can take whatever candidate set the previous stage produced and rescore it with rerank-3 or rerank-3-lite. No separate vendor, no external API call, no reassembly step in application code — which matters when an agent is making several retrieval calls per task rather than one.</p><p><strong>Figure 3. </strong>$rerank in action.</p><h2>Gravity: What it looks like when this works</h2><p>Gravity is building an ad network that optimizes advertising for the AI era. Relevance isn&#39;t a nice-to-have there; it&#39;s the product. Their problem wasn&#39;t recall. Earlier embedding and reranking models returned relevance scores clustered too tightly together, so Gravity couldn&#39;t confidently separate a strong match from a weak one.</p><p>“The biggest thing we found in our benchmarks was the ability of Voyage AI to be discriminatory to candidates that are not a good match and really promote the ones that are a good match,” said Leo Martinez, Gravity&#39;s cofounder and CTO. Switching to Voyage AI cut retrieval latency by roughly 50% and improved accuracy as request volume climbed.</p><h2>Closing the gap</h2><p>Retrieval quality is one layer of what MongoDB is building for agents to run on. MongoDB 9.0 and Atlas Infinite are the performance and elastic-scale layer, absorbing the bursty traffic that agentic workloads create. Atlas Agent Engine is the memory and governance layer, giving agents persistent context and guardrails across sessions; retrieval is powered by <a href="https://www.mongodb.com/products/platform/atlas-vector-search">Atlas Vector Search</a> and Voyage AI. An agent decides what to retrieve before it decides what to do. Faster infrastructure over bad retrieval just means acting on the wrong thing sooner.</p><p>Getting retrieval right no longer requires complex architecture. Automated Embedding handles the embeddings, $rerank handles the ordering, and both run against your operational data directly in MongoDB. The models are also available standalone through the Atlas Embedding and Reranking API.</p>]]></description>
      <pubDate>Wed, 30 Sep 2026 16:44:42 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/product-release-announcements/introducing-rerank-3-and-native-rerank</link>
      <guid>https://www.mongodb.com/company/blog/product-release-announcements/introducing-rerank-3-and-native-rerank</guid>
    </item><item>
      <title>How Atlas Agent Engine Powers MongoDB’s Internal AI Strategy</title>
      <description><![CDATA[<p>I&#39;ve spent more than 25 years in technology, which means I&#39;m rarely surprised by new tech—I usually see it up close before the public does. As an IT leader, I never evaluate a new capability in isolation; it&#39;s always weighed against real enterprise use cases, and against the risks that come with them. These days, I tell people that being a CIO in the age of AI means holding two jobs at once: the engineer reinforcing the dam, and the operator who has to open the floodgates anyway.</p><p>This week, MongoDB announced the public preview of <a href="https://www.mongodb.com/company/newsroom/press-releases/mongodb-launches-atlas-agent-engine-to-put-ai-agents-in-production-without-a-new-stack"><strong>Atlas Agent Engine</strong></a>, and I couldn’t be more excited about what it promises for customers. Atlas Agent Engine offers a secure way of building, deploying, and governing AI agents in production. Because it has built-in memory and retrieval, Atlas Agent Engine indexes enterprise data where it lives and delivers precise context in real time improving accuracy while cutting token costs. It’s also open and flexible by design, which means teams can build with the LLM and framework of their choice (and soon in any environment of their choice). </p><p>Customers are already excited about the promise Atlas Agent Engine holds for their businesses. For example, <a href="https://www.paysafe.com/us-en/">Paysafe</a> uses MongoDB Atlas to power an agentic system for natural-language-to-SQL queries over transactional data—the first in a series of reusable workflow pipelines Paysafe plans to build as templates for future use cases. </p><p>Today, the company’s Snowflake MCP setup gives API clients only a limited understanding of the underlying data schema. MongoDB Atlas&#39;s flexible document architecture and reliable scale support an agent designed to replace that setup with a more capable, reusable pipeline that API clients can query directly in natural language.</p><p>“Investigating unusual activity in our payment network today means our analysts stitching together data from multiple systems by hand, often under time pressure,” said Jana Janarthanan, SVP of Payment Engineering, Paysafe. “We&#39;re excited about the potential for an intelligent agent, built on MongoDB&#39;s Atlas Agent Engine, to shrink the time between a problem emerging and our team acting on it, giving our analysts more time to focus on the judgment calls that matter most.” </p><p>When the MongoDB team first showed me Atlas Agent Engine, the phrase “secure and governed by design” got my immediate attention. Because if anything keeps me up at night, it’s the thought of agents running amok in MongoDB’s (or our customers’) systems.</p><p>Agent governance isn&#39;t just my concern. It&#39;s in the news, and it&#39;s something CIOs across the industry are wrestling with. Every conversation I have with my peers reinforces the same thing: demand for agents across the enterprise keeps growing, but IT leaders need a way to deploy them safely and securely—not just quickly.</p><p>At its core, this is a centralization-versus-decentralization story. Developers want the autonomy to ship agents fast with minimal friction; IT leaders want centralized control, visibility, and cost optimization levers over how agents behave at scale. The organizations that get this right will build an architecture that delivers both. </p><p>Software is becoming increasingly headless and agent-driven, and CIOs need options <em>now</em>. Put another way, the future is here, and our job is to shape it responsibly. </p><h2>Customer zero: Our internal AI strategy in action </h2><p>One of the ways we do that at MongoDB is by acting as “customer zero” for our products. The industry has many different names for this practice—“dogfooding” and “drinking your own champagne” are two—but the meaning is the same. Before releasing a product, we act as our own customer to test software in production, using real-world use cases and situations. </p><p>For example, when the company released MongoDB 8.0 in 2024, <a href="https://www.mongodb.com/company/blog/engineering/mongodb-8-0-raising-the-bar">my colleague Jim Scharf wrote a blog post</a> about how much 8.0 improved team performance. </p><p>With Atlas Agent Engine, our dogfooding took the form of <a href="https://www.mongodb.com/solutions/customer-case-studies/holly"><strong>Holly</strong></a>: a unified agentic workspace that gives MongoDB&#39;s sellers one stop for everything they need, instead of seven. Before Holly, prepping a single account meant hopping between seven disconnected tools, none of them sharing context with each other—4 to 6 hours per account, per deal cycle, burned on pure tool tax. Holly ends that. Seven tools become one agentic experience, and reps get that time back to spend where it counts: with customers.</p><h2>Holly: Cutting hours of work down to minutes</h2><p>MongoDB&#39;s GTM teams follow a standardized, step-by-step methodology for understanding a customer&#39;s current state, their goals, and what it&#39;ll take to get them there. Reps call it a &quot;spoke,&quot; and it isn&#39;t quick; MongoDB Strategic Account Executive Jack Bunkenburg says spokes eat up a day or two of his week, every week.</p><p>The problem was tooling, not process. Reps needed one tool that understands the full corpus of data they draw from, and one that carries memory across systems that had never talked to each other before.</p><p>Without that, working an account across seven different tools is a bit like seeing seven specialists for one condition—and having none of them able to see what the others found. Every visit starts over: you re-explain your symptoms, your history, and what the last doctor already learned. Each specialist might be excellent. But the system still fails you, because the context never travels. Only you do.</p><p>Before building anything, the team watched how the work actually happened—and the reality on the ground was, in Bunkenburg&#39;s words, &quot;quite a bit messier&quot; than the process on paper. Account research alone meant juggling multiple AI tools (ChatGPT, Claude, Gemini) that don&#39;t share context with each other or with MongoDB&#39;s systems, and that hand back generic, one-size-fits-all answers. Finding proof points was just as manual. So was filtering the results down to what actually mattered.</p><p>Holly is the fix—the shared context the other tools never had. One interface, zero tool-switching, that brings together everything a seller needs to research, prepare, and execute. Underneath it, Atlas Agent Engine does the heavy lifting—runtime, security, identity, orchestration, state, observability, and lifecycle management—so Holly&#39;s agents run in production, not just in a demo.</p><p><strong>Figure 1.</strong> Holly’s agent architecture. </p><p>In practice, that means Holly curates and summarizes meeting transcripts, drafts briefs, surfaces questions a rep hasn&#39;t answered yet, and helps write outreach. The result:<strong> reps using Holly have cut the time it takes to research and build an outbound prospecting list by roughly 95%, and prep that used to take hours now takes minutes.</strong> This means that reps walk into every conversation better prepared, not just faster.</p><p>“Prior to Holly, I was using a dozen different tools to perform research and outreach, so having everything in a single interface has been a real value add,” said Bunkenburg. “Many tools don’t understand MongoDB’s business or exactly what we’re trying to accomplish with those tools, but Holly does.”</p><h2>The intelligent data platform for the AI era</h2><p>Going forward, the vision is for Holly to become a fully integrated intelligence layer that deeply understands MongoDB, our customers, and individual accounts—helping the entire GTM org execute end-to-end workflows more effectively.</p><p>The part that excites me most is what’s underneath Holly itself. Holly runs on roughly 30 agents today, all built on the same Atlas Agent Engine architecture. That architecture doesn&#39;t get shakier as you add agents to it; it was designed to hold whether you&#39;re running 30 or 3,000. We didn&#39;t just build a tool for our GTM team. We proved out a blueprint—one that scales safely with every new agent an organization adds, instead of accumulating risk with each one.</p><p>That&#39;s the shift Atlas Agent Engine represents: moving beyond one-off agents toward a governed, reusable platform that isn&#39;t tied to a single cloud, model, or framework. It&#39;s the difference between hoping your agents behave and knowing they will, no matter how many you&#39;re running.</p><p>The launch of Atlas Agent Engine is one of three major announcements MongoDB made this week, alongside <a href="https://www.mongodb.com/products/updates/version-release">MongoDB 9.0</a> and <a href="https://www.mongodb.com/products/platform/atlas-database/deployment-options">Atlas Infinite</a>. The launches build on each other: MongoDB 9.0 strengthens the foundation every MongoDB customer already runs on, Atlas Infinite removes the limits on how that foundation can scale, and Atlas Agent Engine puts AI agents to work on top of both, governed and grounded in real-time data. </p><p>Builders have always chosen MongoDB because its document model fits the natural shape of application data and how AI systems represent and exchange information. That makes applications faster to build and easier to adapt. Companies increasingly choose MongoDB because it combines that native fit with live operational data, elastic scale, the freedom to run anywhere—and now, a platform purpose-built for the agentic era.</p><p>One platform. Any number of agents. Build, deploy, and run them where your data already lives—with MongoDB&#39;s intelligent data platform.</p>]]></description>
      <pubDate>Wed, 30 Sep 2026 12:59:19 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/product-release-announcements/how-atlas-agent-engine-powers-mongodbs-internal-ai-strategy</link>
      <guid>https://www.mongodb.com/company/blog/product-release-announcements/how-atlas-agent-engine-powers-mongodbs-internal-ai-strategy</guid>
    </item><item>
      <title>Your Database Just Became Your AI Control Point</title>
      <description><![CDATA[<p><em>This is a guest blog post, written by Devin Pratt, Research Director at IDC.</em></p><p>When I brief IT leaders today, the conversation flips. The question used to be which model to use. Now it is a question of whether their data platform can keep up with software that acts on its own. Generative AI answers questions. Agentic AI takes action, and that one shift changes everything about what a data platform has to do.</p><p>This is not a someday problem. According to IDC&#39;s April 2026 <em>Worldwide Data Management Survey</em> (n = 715), 30% of organizations already run agentic AI in production, and another 50% are investing behind it, with an established spending plan. Four in five enterprises are past deciding whether agents belong in their operations. They are working out how to run them safely.</p><p><strong>Figure 1. </strong>Agentic AI is already moving into production.</p><p><em>Q. Which best describes your organization&#39;s current state of evaluating or using agentic AI?</em></p><p><em>n = 715, Source: IDC&#39;s Worldwide Data Management Survey, April 2026</em></p><p>Here is the shift I keep coming back to. A platform built to analyze what already happened is not the same as a platform built to run what happens next. When an agent reads data, decides, and acts in real time, the database stops being a passive store of record. It becomes the control point where real-time context is served, the right information is retrieved, and policy is enforced at the exact moment the agent acts. Get that wrong, and a single bad read becomes a wrong action at machine speed, then repeats.</p><p>Real time is now the baseline, not the exception. In the same survey, 64.6% of enterprise data use cases already require real-time or near-real-time delivery; for streaming scenarios, 91.2% need end-to-end latency of under 200ms. Batch-oriented architectures are increasingly on the wrong side of that line.</p><p>So, what should IT leaders actually look for? When I work through this with teams, four requirements come up every time.</p><ul><li><strong>A real-time operational foundation that fits AI-shaped data: </strong>AI data is unstructured, fast-changing, and high in volume. The foundation has to fit that shape and serve it fast. That is why IDC forecasts non-schematic and data lake systems to outgrow the overall database market, even as relational stays the largest segment.</li></ul><ul><li><p><strong>Elastic scale for unpredictable, agent-driven demand: </strong>Agent traffic is bursty and hard to forecast. Teams want to grow on one foundation without the disruptive rebuilding that hard scaling ceilings force. That is the logic behind the move to consolidate on a core platform, with public cloud now at 64.6% of database revenue.</p></li><li><p><strong>Accurate, always-current retrieval: </strong>An agent is only as good as the context it can retrieve. Buyers know this. About 75% favor integrated vector databases over standalone ones, and 47% consider a consistent semantic layer critical for safe and trustworthy AI.</p></li><li><p><strong>A governed runtime to run agents in production: </strong>Durable memory, identity-bound policy, and observability enable a governance team to trust an agent to take real actions. By 2027, IDC expects 80% of agentic AI use cases to require real-time, contextual data access, pushing enterprises from gatekeeping toward federated access with centralized governance.</p></li></ul><p>Knowing the requirements is the easy part. Three things slow teams down in practice, and they are worth naming:</p><ul><li><p><strong>Lock-in worries: </strong>With about 95% of organizations reporting data-sovereignty requirements and 90% running open-source databases, enterprises want to run across clouds and on their own infrastructure, not bet the business on one stack.</p></li><li><p><strong>Governance of autonomous action:</strong> When software can act on its own, controllable and auditable access becomes mandatory. Until you can prove it, agents stall in pilot.</p></li><li><p><strong>Cost that runs away from you: </strong>Retrieval-heavy agents create bursts of consumption, and re-explaining context on every step quietly burns tokens. Cost should track use, not unused capacity.</p></li></ul><p>The encouraging part is that these are answerable. A platform that keeps retrieval close to the data, deploys anywhere, and governs agents by default addresses all three directly.</p><h2>The road ahead </h2><p>The pattern is already visible. IDC predicts that, by 2029, 60% of enterprise data platforms will unify transactional and analytical workloads in hybrid processing architectures to power agentic AI. The database is no longer where data waits. It is where agents act. Enterprises that treat it that way will move from pilots to production. Those who do not will watch the gap widen.</p><p>If you are mapping your own path, the requirements above are a good place to start: a real-time foundation, elastic scale, accurate retrieval, and a governed runtime, with the freedom to run anywhere.</p><h2>Keep reading</h2><p>For the full analysis, including the market data behind each of these four requirements, read IDC Spotlight <a href="https://www.mongodb.com/resources/solutions/use-cases/idc-spotlight-intelligent-data-platform-era-for-agentic-ai"><em>The Intelligent Data Platform Era: Preparing Enterprises for Agentic AI</em></a> (IDC #US54925526, September 2026), sponsored by MongoDB.</p>]]></description>
      <pubDate>Tue, 29 Sep 2026 16:56:57 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/news/your-database-just-became-your-ai-control-point</link>
      <guid>https://www.mongodb.com/company/blog/news/your-database-just-became-your-ai-control-point</guid>
    </item><item>
      <title>Europe Data Residency for Atlas Embedding and Reranking</title>
      <description><![CDATA[<p>Today, MongoDB is announcing the public preview of data residency in Europe and the US for the Embedding and Reranking API Service, also known as ERAS, on MongoDB Atlas. It’s a critical priority to make industry-leading Voyage AI models available wherever our customers operate, while supporting them in meeting their regulatory requirements. The introduction of geography-specific data residency builds on the strong foundation of <a href="https://www.mongodb.com/products/platform/atlas-database">MongoDB Atlas</a>’s enterprise-grade data privacy, security, and compliance features, and can help organizations operating in Europe achieve data sovereignty goals when building AI-powered search into their applications.</p><h2>Regions and Geographies</h2><p>When you provision a database cluster in Atlas, you choose a cloud provider region, and that determines where the cluster&#39;s data is stored and processed. With today’s update, we are introducing a second boundary called a Geography: a named group of cloud regions inside which MongoDB will process the content you submit for embedding, reranking, and related model calls. The first two supported Geographies are Europe and the United States, with the goal of expanding to additional Geographies over time.</p><p>The Europe Geography initially covers cloud provider regions in the European Economic Area, and the United States Geography initially covers cloud provider regions in the United States. The set of regions inside a Geography can change, which is why the boundary is drawn at this level rather than at the region level.</p><h2>How it works</h2><p>A Designated Service is a service that honors the Geography scope applied to your model API key. When you send a scoped request to a Designated Service, inference for that request runs inside the Geography.</p><p>When you select a Geography for a Designated Service, the service is designed to operate as follows:</p><ol><li><p>Inference on the content you submit runs on GPU-accelerated compute inside that Geography.</p></li><li><p>Request payloads we retain for logging are stored inside that Geography.</p></li><li><p>Every request is tagged with the Geography that served it, so usage records and invoices can be filtered and audited along that dimension.</p></li><li><p>If the Geography cannot serve a request, it is designed to fail rather than falling back somewhere else.</p></li></ol><p>The fourth commitment is deliberate and stricter than the common industry pattern, which allows an administrator to opt into cross-boundary processing when a service is unavailable locally. Under MongoDB’s new data residency  approach for ERAS, traffic sent to the Europe endpoint is designed to be served in Europe or not at all. The tradeoff is that a scoped endpoint depends on capacity in one Geography rather than a global pool, which is why scoping is something to turn on only where a requirement calls for it, rather than everywhere by default.</p><h2>Why boundaries use Geographies rather than Regions</h2><p>GPU-accelerated compute is not evenly distributed. It is concentrated in a subset of cloud regions, and we expect that to remain true for the foreseeable future. Committing at region granularity would mean either making do with a very short list of supported regions or making a commitment carrying enough exceptions to be worth little.</p><p>Committing at Geography granularity avoids that. It is a boundary we can hold as capacity moves between regions, without renegotiating the promise each time. It also matches how the regulatory frameworks customers commonly reference tend to be written. Key European data protection requirements are expressed at the European Union or EEA level (rather than at the level of individual member states), so a boundary drawn there is often the boundary that matters.</p><h2>Selecting and enforcing a Geography</h2><p>For direct API calls, scope is carried by the API key and expressed in the endpoint. Keys are immutable, so the scope is fixed at creation, and changing it means creating a new key. Existing keys continue to work unchanged against the general endpoint.</p><p>For enforcement, resource policies can restrict key creation to a chosen Geography across an organization, so a developer cannot create an out-of-scope key in the first place, and keys that fall outside a newly applied policy are flagged. Automated Embedding and Native Reranking will get equivalent mechanisms when they ship.</p><p>The general, unscoped endpoint remains the default recommended path for workloads without a residency requirement, and is where we aim to introduce global load-balancing in the future. Scoped processing carries a 10% price premium, reflecting the higher cost of accelerated compute that cannot draw on the global pool.</p><h2>Example request flow</h2><p>Here’s what an example request looks like, using Atlas ERAS on the Europe Geography:</p><ol><li><p>Your application calls an EU-scoped endpoint rather than the general one.</p></li><li><p>The request is routed into the inference stack for Europe.</p></li><li><p>The gateway ensures that your API key is scoped for Europe.</p></li><ol><li><p>Note: An API key and an endpoint must align in scope. An unscoped key cannot be used for explicit EU inference, and vice versa.</p></li></ol><li><p>Rate limits are applied for that scope.</p></li><li><p>The content is tokenized and dispatched to model servers running on accelerated compute inside Europe.</p></li><li><p>The response is assembled and returned. Any retained payload logging is written within Europe.</p></li></ol><p>Steps 3 through 6 all happen inside the boundary. The scope check is done twice, against the key prefix and against the key&#39;s stored attributes, so a misconfigured client cannot route content out of its intended Geography by accident.</p><h2>What applies globally, and what Geography scoping doesn’t cover</h2><p>A small set of account metadata is shared across Geographies so that one Atlas account works everywhere: org, project, and API key IDs and the scope attached to them, resource policies, rate limit configuration, and usage data. None of it contains the text, documents, or images you submit for inference. Those are processed and logged only within the Geography you selected.</p><p>Note, however, that Geography scoping is a processing boundary. It is separate from data retention, so if your requirement is that we retain nothing other than that we process locally, that is a different conversation and one worth having explicitly. It also does not cover in-country or single-region processing, air-gapped or self-managed deployment, or open-weight models you can audit yourself.</p>]]></description>
      <pubDate>Tue, 29 Sep 2026 15:06:20 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/product-release-announcements/europe-data-residency-for-atlas-embedding-reranking</link>
      <guid>https://www.mongodb.com/company/blog/product-release-announcements/europe-data-residency-for-atlas-embedding-reranking</guid>
    </item><item>
      <title>Same Query, Same Score: Consistent Ranking with StableTfl in Atlas Search</title>
      <description><![CDATA[<p>Suppose you run paginated search in your application, or a RAG pipeline where the top ten retrieved documents feed a model. One of your users searches for a recipe collection for &quot;chocolate cake.&quot; Page one ends with &quot;Flourless Chocolate Cake.&quot; They click next, and the first result on page two is &quot;Flourless Chocolate Cake&quot; again. Between the two requests, nothing about the query changed; only the requested page did. An Atlas Search customer running paginated search brought us this exact problem. The usual workarounds, such as pinning each user to one replica or holding an index snapshot open for every pagination session, require the system to store additional state per query, and they are either too cumbersome or don’t fully close the gap. We fixed it instead by building a new scoring function, StableTfl, that needs no extra state at all. It resolved their issue, and we have since contributed it to Apache Lucene, the open source search engine that powers Atlas Search, so any search system built on top of Lucene can use it.</p><p>The two requests were served by two different replicas of the same index, and the replicas ranked the same recipes in a different order. That one reordering produces two concrete failures. The first is the duplicate above: a result from the bottom of page one appears again at the top of page two. The second is a skipped result: the recipe ranked sixth by the first replica should have opened page two, but the second replica ranks it fifth, placing it inside a page one that the user never requested. That recipe never appears on either page.</p><p>Neither replica malfunctioned, and neither returned wrong data. The problem sits at the intersection of two things: a scoring function that assumes a single, fixed corpus (the full set of indexed documents), and a distributed system that cannot provide one.</p><p>In this blog post, we explore StableTfl, a scoring function we built for Atlas Search to keep search results consistent across replicas. Where BM25 relies on corpus statistics that drift between replicas, StableTfl scores a document from the query and the document alone, so every replica produces the same score for a given query and document, and users see the same results on every page and in every request with nothing extra to build.</p><h2>Why BM25 scores drift</h2><p>BM25 is the standard relevance function in lexical search and the default in Lucene. Given a query, BM25 assigns each matching document a score, and results are returned in descending score order. The formula combines three ideas:</p><ul><li><strong>Term frequency.</strong> A recipe that mentions &quot;chocolate&quot; ten times is more likely to be about chocolate than one that mentions it once, so more occurrences raise the score, with diminishing returns.</li><li><strong>Length normalization.</strong> A long document has more chances to match any given term simply by virtue of its length, so a document&#39;s score is discounted by its length relative to the corpus average.</li><li><strong>Inverse document frequency (IDF).</strong> Rare terms are more informative. In a query for &quot;flourless chocolate cake&quot;, a match on &quot;flourless&quot; indicates relevance more strongly than a match on &quot;chocolate&quot;, because far fewer recipes contain it. IDF measures this by counting how many documents contain each term.</li></ul><p><strong>Figure 1.</strong> The BM25 formula, with corpus-dependent inputs highlighted.</p><p>Term frequency is a property of the document alone. The other two are computed from the corpus: the average document length, the total number of documents, and the number of documents containing each term. BM25&#39;s score for one document, therefore, depends on every other document in the corpus.</p><p>Those corpus statistics describe one node at one moment, and in a live system, they do not stay fixed. Replicas index independently and converge only eventually, so at any instant their statistics disagree by whatever is still in flight. Even a single node&#39;s statistics change between two consecutive queries, as new documents commit and segment merges reclaim deletions. When the statistics move, scores move, and when two documents swap ranks across a page boundary, the result is the duplicate and the skip from the introduction.</p><p>BM25 itself is not at fault: on a single, static corpus, it is fully deterministic. The failure comes from the environment, and the standard mitigations accordingly try to restore a single fixed corpus. Sticky routing pins a user to one replica, but that replica&#39;s own statistics keep changing. Synchronizing statistics keeps replicas consistent with each other, but not with themselves over time. Index snapshots pin a point-in-time view of the index for the lifetime of a pagination session, but the pinned segments cannot be cleaned up, state accumulates per session, and the snapshot covers only one replica. Each mitigation adds a state somewhere. We took a different approach and removed corpus statistics from scoring entirely.</p><h2>Scoring without the corpus</h2><p>StableTfl (stable term frequency–length) is the scoring function Evan Darke and I built for <a href="https://www.mongodb.com/products/platform/atlas-search">MongoDB Atlas Search</a>. We have since contributed it to Apache Lucene as StableTflSimilarity, so it will be available to any system built on Lucene, not only Atlas Search. Its score depends on exactly three inputs: the query term, the term&#39;s frequency in the document, and the document&#39;s length. Nothing about the rest of the corpus enters the computation, so a document receives the same score on every node at every moment, and two replicas holding the same documents rank them identically.</p><p><strong>Figure 2.</strong> The StableTfl scoring formula.</p><p>The StableTfl formula shares a shape with BM25: it sums over the query terms and, for each term, multiplies a normalized term frequency, which rewards repeated occurrences with diminishing returns, by a rarity weight, which values uncommon terms more than common ones. </p><p>The frequency factor is nearly identical. BM25 normalizes the factor by the document’s length relative to the corpus average, so long documents with the same number of occurrences are scored lower. StableTfl normalizes against document length when computing term rarity.</p><p>The term rarity weight is where the two scoring functions differ fundamentally. BM25 uses IDF, which looks up how many documents contain the term, and a term found in fewer documents weighs more. StableTfl doesn’t use the corpus statistics. Instead, it estimates term rarity by term length and assigns a higher rarity to longer terms. This generally holds because of a pattern in natural language known as Zipf’s brevity law: frequent words tend to be short, and rare words tend to be long. For the query &quot;chocolate cake,&quot; BM25 asks how many recipes contain each word; StableTfl asks only how long each word is, and gives the longer &quot;chocolate&quot; more weight than &quot;cake.&quot; Although many individual words break this crude proxy, it holds well enough in aggregate that the cost, measured below, is only about three points of NDCG.</p><p>Concretely, StableTfl models p(t, d), the probability that a document of length |d| contains a term of length |t| at least once:</p><p>p(t, d) = 1 − (1 − m · 2^(−c · |t|))^|d|</p><p>A longer term is exponentially less likely to fill any one position, and a longer document has more positions to fill. A term with low p is rare and receives a high weight through the same log-shaped curve BM25 applies to IDF. Term length is counted in Unicode code points of the analyzed term rather than bytes, so &quot;café&quot; counts as four. The decay constant c = 0.917 was fit by modeling term frequency in English text, and k1 = 1.2 matches Lucene&#39;s BM25 default. A later Bayesian hyperparameter search over BEIR returned nearly identical values, so we kept the originals.</p><p><a href="https://www.mongodb.com/docs/search/query/score/get-details/#stabletfl">StableTfl</a> ships in Atlas Search as a per-field similarity option in the index definition, alongside bm25 and <em>boolean</em>.</p><h2>Precomputing term rarity</h2><p>The term rarity function involves a power and a logarithm, and a scoring function can run millions of times for a broad query over a large index. Evaluating transcendental functions for every scored document would be substantially more expensive than BM25&#39;s arithmetic.</p><p>The solution comes from a detail of Lucene&#39;s index format: document lengths are not stored exactly for scoring, but compressed into a single byte. For a given query, term rarity therefore has an input domain of exactly 256 values, and all of them can be computed up front:</p><p>Per document, scoring reduces to an array lookup keyed on that byte-encoded length, <em>cache[((byte) encodedNorm) &amp; 0xFF]</em>, plus one multiplication and one division, with no transcendental math. Beyond the scoring path, the integration is small: StableTfl is a stateless drop-in Lucene <em>Similarity</em>, and its <em>explain()</em> output mirrors BM25&#39;s structure, so existing debugging tools work unchanged.</p><h2>What it costs, and when to use it</h2><p>Corpus statistics carry information, and removing them costs relevance. We benchmarked StableTfl against BM25 on 21 datasets from BEIR, a standard benchmark suite for retrieval quality, using identical tokenization for both scorers. BM25 averaged 0.346 NDCG@10 and StableTfl 0.315, a drop of about three points, or 9% relative. NDCG@10 measures the ranking quality of the top ten results; higher is better. Recall@10 shows the same pattern: 0.388 against 0.350.</p><p><strong>Figure 3.</strong> NDCG@10 per BEIR dataset.</p><p>The direction is expected, since StableTfl computes with strictly less information than BM25. StableTfl is the right choice when consistency matters more than the last few points of relevance: multi-replica deployments serving paginated queries, RAG and hybrid pipelines that need reproducible retrieval, and systems where downstream logic depends on stable scores. BM25 remains the default in Atlas Search and the right choice when raw relevance is the top priority.</p><p>One further limitation is language. The constants were fit on English text, so other Latin-script languages may need them re-fit, and languages where a word is often a single character, such as Chinese or Japanese, break the term-length proxy entirely.</p><h2>Future work</h2><p>Two directions could narrow the quality gap. The constants can be re-fit for other languages and for specialized English domains such as biomedical or legal text. The analyzer also interacts with the model: stemming shortens tokens before the rarity function sees them, so analyzer choice affects the calibration.</p><p>The decision itself comes down to the trade described above. BM25 is the right default. StableTfl is for deployments where a duplicated result, or a retrieval set that changes between two identical queries, costs more than three points of NDCG.</p>]]></description>
      <pubDate>Fri, 25 Sep 2026 16:33:30 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/engineering/same-query-same-score-consistent-ranking-with-stabletfl-atlas-search</link>
      <guid>https://www.mongodb.com/company/blog/engineering/same-query-same-score-consistent-ranking-with-stabletfl-atlas-search</guid>
    </item><item>
      <title>Resilient Edge AI: Keeping Connected Vehicles Smart Offline</title>
      <description><![CDATA[<p>A warning light appears on the dashboard while a driver is navigating a tunnel, a remote area, or an underground garage. The driver asks the vehicle what is wrong and what to do next. In that critical moment, getting a helpful answer shouldn&#39;t depend on whether the car has cell service.</p><p>As vehicles become increasingly software-defined, drivers are beginning to expect the same digital assistance in their cars that they use everywhere else. But connected experiences are only valuable when they remain available at the moment they are needed most. More than 400 million connected vehicles are expected to be on the road worldwide[1], making the resilience of these experiences an increasingly important consideration for automakers.</p><p>This leads to a strategic question: should in-vehicle AI be designed around permanent connectivity, or should it be designed to remain useful when connectivity disappears?</p><p>The answer is increasingly clear. For software-defined vehicles, offline capability is not a fallback feature. It is a requirement for trustworthy in-vehicle AI.</p><p>This blog explores how automakers can meet that requirement through an offline-first approach. Intelligence and relevant vehicle knowledge remain available at the edge, while MongoDB Atlas provides the cloud foundation for shared knowledge, synchronization, and continuity when connectivity returns. Together, these capabilities balance local resilience with cloud scale, helping critical assistance remain available when drivers need it most.</p><h2>The connected-vehicle assumption is breaking down</h2><p>Cloud services are essential to the modern vehicle experience. They provide centralized knowledge, scalable processing, software updates, analytics, and a shared history across vehicles and users.</p><p>But a vehicle is not a smartphone in motion. It operates across tunnels, rural roads, underground parking facilities, border crossings, and areas with inconsistent network coverage. Connectivity can also be interrupted by temporary outages or changing network conditions.</p><p>Those interruptions are not merely technical inconveniences. They can occur precisely when a driver needs assistance: when a diagnostic code appears, a warning light turns on, a repair procedure is unclear, or a driver needs to understand what the vehicle is communicating.</p><p>A resilient vehicle experience, therefore, needs a different design principle: <strong>critical assistance should remain available locally, while the cloud provides continuity when connectivity returns.</strong></p><p>This is not an argument for moving every cloud capability into the vehicle. Instead, it defines which interactions are too important to risk on a network round-trip.</p><h2>Three principles for resilient in-vehicle AI</h2><h3>1 - Design for the moment of need</h3><p>Drivers do not think in terms of edge computing, synchronization, or service availability. They think in terms of a simple question: “Can my vehicle help me right now?”</p><p>A resilient assistant should be able to respond to common, high-value requests even when the vehicle is offline. That might include explaining a diagnostic code, answering a question from the digital manual, checking relevant vehicle information, or guiding a driver through a basic procedure.</p><p>The product implication is significant. Offline functionality should not be treated as a degraded mode that is added after the connected experience is complete. It should be considered when defining the experience itself.</p><p>This changes what teams optimize for. Instead of asking only how quickly a cloud service can answer, they must also ask which answers need to be available immediately, which knowledge should be stored locally, and how the experience should behave when the network is unavailable.</p><h3>2 - Turn vehicle knowledge into an evolving product asset</h3><p>A vehicle assistant is only as useful as the knowledge behind it. Digital manuals, diagnostic information, vehicle signals, and service procedures should not remain isolated sources that drivers must search manually.</p><p>They can become contextual knowledge that the assistant retrieves and explains in the language of the driver’s situation.</p><p>This knowledge also needs to evolve. New vehicle generations introduce new signals, features, and system relationships. Manufacturers may extend common vehicle models with their own requirements. Documentation changes as procedures and software change.</p><p>COVESA’s Vehicle Signal Specification (VSS) provides a shared way to describe vehicle signals and their relationships, while still allowing automakers to extend the model for their own platforms. That combination of common language and product-specific flexibility is important as vehicle software evolves.</p><p><strong>Figure 1.</strong> COVESA data model.</p><p>The broader lesson is that automakers should treat vehicle data and documentation as living product assets. Their value multiplies the moment they are connected, updated, searched, and delivered directly to the driver&#39;s context.</p><h3>3 - Separate availability from connectivity</h3><p>The most resilient architecture separates two responsibilities.</p><p>The vehicle edge is responsible for keeping critical interactions available. It can store the local knowledge and recent data needed to answer important questions, interpret requests, and support the driver without waiting for a round trip to the cloud.</p><p>The cloud is responsible for scale and continuity. It can provide centralized updates, shared knowledge, durable history, broader analytics, and synchronization across vehicles and services.</p><p>When connectivity returns, the local and cloud environments can reconcile changes and continue working as one system. This allows the vehicle to remain responsive without giving up the benefits of centralized platforms.</p><p>The important architectural insight is not that every capability belongs at the edge or in the cloud. It is that the boundary between them should be intentional.</p><h2>What this means for automakers</h2><p>An offline-first approach has implications beyond system architecture.</p><p><strong>It can build customer trust.</strong> A vehicle that remains helpful during a stressful moment feels more dependable than one that simply displays an error when connectivity is interrupted.</p><p><strong>It can create product differentiation.</strong> As software-defined vehicles become more common, the quality of assistance may become as important as the number of digital features. Reliability can become part of the experience that distinguishes one vehicle platform from another.</p><p><strong>It can improve the value of existing content.</strong> Manuals and diagnostic documentation become more useful when drivers can access the right information without navigating hundreds of pages or relying on a QR code and a network connection.</p><p><strong>It can support long-term software evolution.</strong> Vehicle signals, knowledge, and user interactions will change across model years. A data foundation that can evolve with those changes helps teams build new capabilities without losing historical context.</p><p><strong>It can support more deliberate data governance.</strong> Not every interaction needs to leave the vehicle immediately. Keeping selected data and capabilities local can improve resilience while allowing manufacturers to define what should be synchronized, when it should be synchronized, and where it should be stored.</p><p>These considerations require collaboration across vehicle software, cloud engineering, data teams, product management, and customer support. Offline-first AI is therefore not only a technical pattern. It is a product and operating model decision.</p><h2>A practical implementation pattern</h2><p>A reference implementation can combine a local application and model with a cloud data platform. On the edge, ObjectBox can provide local persistence for vehicle data, searchable knowledge, and recent interactions, allowing the assistant to continue operating when the vehicle is offline. When connectivity is available, ObjectBox Sync can synchronize local changes with <a href="https://www.mongodb.com/products/platform/atlas-database">MongoDB Atlas</a>, where centralized knowledge, updates, scalable storage, and durable history can be managed.</p><p>MongoDB Atlas provides the cloud data foundation for vehicle information, assistant knowledge, and synchronized interactions. <a href="https://www.mongodb.com/products/platform/atlas-vector-search">MongoDB Atlas Vector Search</a> helps retrieve relevant content, while the flexible document model can represent both structured vehicle signals and knowledge enriched with metadata. Together, ObjectBox at the edge and MongoDB Atlas in the cloud support a division of responsibility: keep critical interactions close to the driver while preserving continuity with cloud services.</p><p><strong>Figure 2.</strong> Reference architecture.</p><p>The specific technologies will vary by vehicle platform and use case. The enduring pattern is more important: keep the experience available at the edge, use the cloud for scale and coordination, adopt shared data-modeling approaches where they add value, and design the data model to evolve as vehicles evolve.</p><h2>The next competitive advantage is resilience</h2><p>The next generation of connected-vehicle experiences will be defined not by constant connectivity, but by how intelligently they operate when it disappears.</p><p>For automakers, this creates an opportunity to rethink in-vehicle AI around the moments that matter most. An assistant that can answer a question in a tunnel, explain a diagnostic code on a rural road, or surface the right manual content in an underground garage is doing more than demonstrating technology. It is building a vehicle that drivers can actually rely on when it matters most.</p><p>Offline-first design is not about recreating every cloud service inside the vehicle. It is about ensuring that critical assistance is available when drivers need it, while cloud connectivity continues to provide scale, updates, and continuity in the background.</p><p>That is the foundation for in-vehicle AI that drivers can trust.</p><p>[1] Axis Intelligence,<a href="https://axis-intelligence.com/connected-car-market/"> “Connected Car Market.”</a></p>]]></description>
      <pubDate>Thu, 24 Sep 2026 14:49:03 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/resilient-edge-ai-keeping-connected-vehicles-smart-offline</link>
      <guid>https://www.mongodb.com/company/blog/innovation/resilient-edge-ai-keeping-connected-vehicles-smart-offline</guid>
    </item><item>
      <title>17LIVE Scales Global AI Applications and Service Innovation via MongoDB Atlas Search</title>
      <description><![CDATA[<p>17LIVE 成立於 2015 年，致力於以「直播技術＋互動娛樂」的核心主軸，達成「To Empower Human Connections through Live Technology」的願景，目前已成為亞洲領先的即時互動直播串流娛樂平台。身為業界先行者，17LIVE 不僅是第一家以直播業務在新加坡成功上市的品牌，更在全球累積超過 5,000 萬註冊用戶，並在台灣、日本及亞洲多地設立辦事處，擁有超過 500 名專業員工。</p><p></p>]]></description>
      <pubDate>Wed, 23 Sep 2026 17:34:41 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/17live-scales-global-ai-applications-service-innovation-mongodb-atlas-search</link>
      <guid>https://www.mongodb.com/company/blog/innovation/17live-scales-global-ai-applications-service-innovation-mongodb-atlas-search</guid>
    </item><item>
      <title>How to test that a dozen MongoDB drivers, in a dozen languages, conform to a dozen specs</title>
      <description><![CDATA[<p>At MongoDB, we develop a dozen client libraries (&quot;drivers&quot;) in a dozen programming languages. A few drivers are wrappers around shared cores written in C or Java, but mostly they&#39;re rewrites in their target languages: the JavaScript Driver is pure JavaScript, the Rust Driver is pure Rust, and so on. Building the drivers this way is a big commitment. Lots of database companies just write their client in C and add thin wrappers in various languages. Our way is harder but, in my opinion, better. Our drivers are easier to install, their APIs are more idiomatic in each language, and they participate normally in each language&#39;s runtime: its threading model or async loop, its garbage collection, etc. This is only possible because we keep developing <em>native</em> drivers in each language.</p><p>But then, how do we ensure all our drivers&#39; behaviors and APIs are consistent? Obviously, Python methods are snake_cased and Java methods are camelCased, but MongoDB drivers should have the same basic API in all languages, spelling aside. Node concurrency is async and C concurrency uses threads, but the meaning of <a href="https://emptysqua.re/blog/how-to-use-mongodb-causal-consistency/">causal consistency</a> should be the same in all drivers.</p><p>At MongoDB we’ve figured out a way to test that drivers in many programming languages all conform to the same specs. We invented a <em>domain-specific test language</em> that’s based on YAML. All of our drivers have <em>test runners</em> that interpret this language. That means all our drivers can share one big test suite, which forces all of them to behave the same. The International Symposium on Software Reliability Engineering (ISSRE 2026) just accepted <a href="https://arxiv.org/abs/2608.18039">our paper</a> about this. Read the paper for the technical details; here, I’ll tell you the inside story.</p><p><em>MongoDB engineers juggling many implementations of many specs.</em></p><h2>In search of a tolerable test language</h2><p>I joined MongoDB as a Python driver engineer in November 2011. Looking back through my emails, I see that we were intensely debating how to standardize our drivers from the moment I arrived. Some engineers were writing Java Driver tests in Cucumber, a &quot;behavior-driven development&quot; syntax, like this:</p><p>My very first task at MongoDB was researching whether we could write test-runners for these Cucumber tests in Python, Ruby, and our other languages. I instantly learned that my second task was dealing with my colleagues&#39; revulsion to Cucumber&#39;s syntax. One engineer wrote that if we replaced his handwritten tests with Cucumber, he&#39;d “have no part in doing it or supporting the resulting disaster.” (I clarified that we weren&#39;t going to replace tests, only complement them.) Our founder Eliot Horowitz encouraged us to make a shared test suite, but he thought Cucumber specifically was “hilarious.” </p><p>We gave up on Cucumber. A few years later, I was involved in a new feature, <a href="https://specifications.readthedocs.io/en/latest/server-selection/server-selection/#localthresholdms">specifying how drivers measure and respond to network latency</a>. I observed that the English spec of the feature could be misunderstood, and some drivers implemented it differently. Once again, Eliot proposed a shared test suite. This time, we avoided Cucumber. We started to develop a custom test language on top of YAML instead. For details, see my <a href="https://www.youtube.com/watch?v=OBjU_xYtPmA">conference talk</a> or <a href="https://www.mongodb.com/company/blog/engineering/cat-herds-crook-yaml-test-specs-improve-driver-conformance">blog post about YAML tests</a>, with Samantha Ritter.</p><h2>The unreasonable effectiveness of YAML</h2><p>Testing drivers with YAML is one of the most successful projects I&#39;ve ever been part of. In the 11 years (nearly 12 now) since we started writing YAML tests, the MongoDB drivers have all converged to a shared API and shared set of behaviors. They&#39;re as similar as they should be, with consciously-chosen variations to fit each language&#39;s idioms and conventions. <a href="https://emptysqua.re/blog/choosing-the-adventurous-route-video/">I left the Drivers team a while ago</a>, but the specification and YAML testing process is going stronger than ever. They now have a Unified Test Format, built on YAML, that can test drivers&#39; conformance to a dozen different specs. The specs cover how drivers read and write documents, how they retry failed commands, how they start and end transactions, how they encrypt private fields client-side, and lots of other intricate behaviors. Nearly 1,500 YAML files ensure that all these independent code bases implement the same protocols.</p><p>Here&#39;s an example of a modern Unified Test Format file. It tests that a driver <a href="https://emptysqua.re/blog/driver-features-for-mongodb-3-6/#retryable-writes">auto-retries</a> the <em>update</em> command after a network error:</p><p>For each of our drivers, we implement a <em>test runner</em> which can interpret this syntax and call APIs on the driver being tested. The test runner creates two MongoClient objects: the MongoClient under test, and an “internal” MongoClient for sending side-channel commands to the server (see the <em>failPoint</em> below).</p><p><em>schemaVersion</em> tells the test runner which features the file uses, so an old runner can skip a file it wouldn&#39;t understand instead of failing it. We use JSON Schema to check each YAML test has the proper syntax for its version of the Unified Test Format.</p><p><em>runOnRequirements</em> tells the test runner to skip the file unless the MongoDB server deployment matches—here, a replica set running MongoDB 4.4 or later.</p><p><em>createEntities</em> builds an <em>entity map</em>: a client, a database, and a collection, named with YAML anchors (<em>&amp;client</em>) so later operations can refer to them by alias (<em>*client</em>). This not only avoids repetition, it means YAML test runners can store and retrieve objects in the entity map, like assigning objects to variables in a real programming language.</p><p><em>initialData</em> puts one document in the collection before the test starts. Then the operations run in order:</p><ul><li><p><em>failPoint</em> tells the server to close the connection the next time it receives an <em>update</em>. The test runner uses the internal MongoClient for this so it doesn&#39;t touch the MongoClient under test.</p></li><li><p><em>updateOne</em> tells the test runner to call the <em>updateOne</em> API on the MongoClient under test. In Python this is spelled <em>update_one</em>, in C it&#39;s <em>mongoc_collection_update_one</em>, etc. Each driver&#39;s test runner knows how to translate YAML into the driver&#39;s API. The <em>expectResult</em> field asserts what the call returns. In this test, the driver tries to update a doc, it gets a network error from the fail point, it reconnects and retries, and succeeds, returning <em>modifiedCount: 1</em>.</p></li><li><p><em>waitForEvent</em> blocks until the driver has noticed the server closed the connection. (In this test, that happens earlier during <em>updateOne</em>, so the test runner won&#39;t actually block on this line.) The driver handles the network error by marking the server&#39;s type as <em>Unknown</em>, meaning the driver has to figure out the server&#39;s status once it reconnects.</p></li><li><p><em>expectEvents</em> checks that the driver sent two <em>update</em> commands on the wire, meaning it retried the write exactly once, plus there was a <em>poolClearedEvent</em> showing the driver discarded all its connections after the network error.</p></li><li><p><em>outcome</em> reads the collection back to confirm <em>x</em> was incremented exactly once—the retry didn&#39;t apply the update again.</p></li></ul><p>This example shows lots of exciting features! The Unified Test Format lets all the drivers share a test suite. We can prove they all act the same by publishing tests they must all pass. We can update a spec, and force all the drivers to comply with the change, by publishing changes to the shared tests and watching all outdated drivers fail.</p><p>Additionally, this test is checking <em>hidden</em> behaviors that ordinary integration tests couldn&#39;t observe. We use <em>failPoint</em> to make the server close the connection, so we can exercise the driver&#39;s auto-retry logic. From the API surface, retries are invisible—that&#39;s the point. But this YAML test triggers a retry and tests three hidden behaviors: the driver retries exactly once, it marks the server type <em>Unknown</em>, and it clears its connection pool. We could assert the entire contents of the two update commands the driver sends on the wire, if we wanted to.</p><h2>Results</h2><p>The Unified Test Format has saved us tens of thousands of lines of code over the years, and it&#39;s probably saved us from scores of awful bugs. It enforces spec conformance so when you use MongoDB from several programming languages, you get a consistent API and predictable behavior.</p><p>Here are some numbers, starting with code savings. When we created the unified format in 2020, we generalized the YAML test format used by lots of different specs into one format to rule them all. Seven drivers replaced their per-spec test runners with a single Unified Test Format runner, and every one of these came out smaller. We cut 22,000 lines total. The Java Driver alone deleted 6,000 lines of test-runner code.</p><p><strong>Figure 1.</strong> Lines of code saved. </p><p><em>LOC deleted when switching to the unified format.</em></p><p>Meanwhile, we added more and more conformance tests. The Unified Test Format corpus went from about a thousand lines in 2021 to 124,000 today. The biggest jumps are when we mechanically ported tests from per-spec YAML formats into the unified format.</p><p><strong>Figure 2.</strong> Growth of the Unified Test Format corpus. </p><p><em>How the size of our YAML test repo grew.</em></p><p>Do the tests actually prevent bugs? We identified a natural experiment: Five drivers implemented the CRUD spec years <em>before</em> they adopted its YAML tests, which gives us a before and after to compare. We used Claude to classify every resolved ticket in those drivers—6,836 of them—and counted the ones that were genuine violations of the CRUD Spec. Four of the five drivers had a lower bug rate after adopting YAML tests. </p><p><strong>Figure 3.</strong> A natural experiment. </p><p><em>Rate of nonconformance bugs before/after adopting YAML tests.</em></p><p>Node.js is the embarrassing one: its bug rate went <em>up</em>. Years after it adopted the YAML tests we discovered that its <em>BulkWriteResult</em> and <em>BulkWriteError</em> classes were inconsistent with the specs and the other drivers. Its test runner hadn&#39;t asserted their contents rigorously enough. The Driver Team filed a bunch of bugs and changed the field names over two major releases, and now Node.js’s API conforms with the rest of our drivers.</p><p>The IEEE International Symposium on Software Reliability Engineering (ISSRE) just accepted my paper about YAML testing, “The Polyglot&#39;s Dilemma: Conformance Testing a Dozen Specs in as Many Languages.” Driver engineers Jeremy Mikola and Jeff Yemin are my coauthors. The paper has more detail about the history of our YAML tests, and it has plenty of stats and lessons. <a href="https://arxiv.org/abs/2608.18039">Check it out, it&#39;s only 6 pages</a>.</p><p></p><p><strong></strong></p><p><strong>Image sources:</strong></p><ol><li><p><a href="https://picryl.com/media/the-history-of-herodotus-a-new-english-version-ed-with-copious-notes-and-appendices-24de4e">https://picryl.com/media/the-history-of-herodotus-a-new-english-version-ed-with-copious-notes-and-appendices-24de4e</a></p></li><li><p><a href="https://www.rawpixel.com/image/12230556/image-art-watercolor-vintage">https://www.rawpixel.com/image/12230556/image-art-watercolor-vintage</a></p></li></ol>]]></description>
      <pubDate>Wed, 23 Sep 2026 16:05:43 GMT</pubDate>
      <link>https://www.mongodb.com/company/research/how-to-test-mongodb-drivers-conform-to-a-dozen-specs</link>
      <guid>https://www.mongodb.com/company/research/how-to-test-mongodb-drivers-conform-to-a-dozen-specs</guid>
    </item><item>
      <title>From 2D Drawings to 3D Models: Designing an AI Reconstruction Pipeline on MongoDB</title>
      <description><![CDATA[<p>Plenty of buildings exist only on paper. Small and mid-size building manufacturers still quote from 2D shop drawings, renovation firms inherit decades-old blueprints with no digital model, and archives everywhere hold plans for structures that were built long before BIM. Whenever one of these businesses needs a 3D model, to quote a job, visualize a change for a client, or plan a renovation, someone rebuilds the geometry by hand in a CAD tool. When the client asks to move a window or widen a wall, part of that manual work starts over, and on a competitive bid, those rework hours decide whether the quote goes out on time.</p><p>BIRD (Building Image Reconstruction and Dimensioning) is a research framework, developed and validated with complete building plans from an <a href="https://doi.org/10.1016/j.engappai.2024.109657">industry partner</a>, that automates this conversion. It accepts the five 2D perspective drawings (front, back, left, right, and the floor plan) as input and produces a proportionate, dimensioned 3D model of the building envelope as output. In this post, we walk through how the technique works and how it can be designed to run as a production service on MongoDB Atlas, with Amazon Simple Storage Service (S3) for drawing storage, <a href="https://www.mongodb.com/docs/atlas/atlas-stream-processing/">MongoDB Atlas Stream Processing</a> to coordinate the pipeline, and <a href="https://www.mongodb.com/docs/search/">MongoDB Search</a> and <a href="https://www.mongodb.com/docs/vector-search/">MongoDB Vector Search</a> for searching past project data.</p><h2>How does BIRD convert 2D Drawings into a 3D building envelope?</h2><p>Building plans are noisy. Annotations, dimension text, and symbols sit directly on top of the walls and openings that a reconstruction algorithm needs to trace. BIRD handles this with a dual-branch convolutional neural network: one branch produces a heatmap of genuine architectural line segments, the other produces a heatmap of the noise. Subtracting the noise map from the line map leaves a clean set of segments. A text recognition model then reads the measurements printed on the drawing and uses them to scale every segment to real-world inches. Finally, a novel wrapping algorithm folds the four elevation views around the floor plan, correctly handling angled walls and sharp corners, to produce the 3D envelope.</p><p><strong>Figure 1.</strong> How BIRD converts 2D building plans into a 3D envelope. Figure adapted from <a href="https://www.sciencedirect.com/science/article/pii/S0952197624018153">this research paper</a>.</p><p>Across the complete building plan sets evaluated in the <a href="https://www.sciencedirect.com/science/article/pii/S0952197624018153">research paper</a>, from small residential structures to a multi-story apartment complex, the framework achieved a median accuracy of roughly 93% in terms of visually aligning with the expected final visualization. Because construction demands exact output, BIRD is open enough to allow for interfaces where a drafter could inspect the extracted lines overlaid on each drawing, for example, nudge any segment that was missed, confirm the dimensions, and then trigger the projection.</p><h2>Storing BIRD output with MongoDB </h2><p>Each processed perspective yields predicted line segments, filtered noise segments, recognized text boxes, extracted measurements, and a growing history of human corrections. The volume varies between buildings, and there may be instances where the drawing contains components that are irrelevant for a visualization: in the published evaluation, the count of irrelevant detected lines (e.g., extracted from an architectural symbol) per perspective ranged from 0 to 137. A simple rectangular elevation produces a handful of segments while a complex facade produces hundreds, and each correction event adds more.</p><p>That variability maps naturally into MongoDB’s document model. One JSON project document could hold everything about the build: the metadata, an embedded entry for each of the five drawings with its array of segments, and eventually the final 3D geometry. Every segment carries its coordinates, its real-world length, its type (wall, window, door), and its correction lineage. In a relational database, this becomes a segments table with millions of narrow rows, join-heavy queries for every screen of the review interface, and schema migrations each time the research team adds a new attribute to the model output. In MongoDB, the document a drafter reviews on screen would be the document stored in the database, and the schema evolves with the model.</p><p>The following example shows a simplified document containing one complete perspective view in a project document; the remaining views are abbreviated for clarity:</p><p>Every manual correction is recorded with a timestamp, so the system keeps an audit trail of what the model predicted versus what the drafter approved. For a manufacturer, this serves two purposes: production traceability when a dimension is questioned later, and a steadily growing set of corrected examples for retraining the model.</p><h2>What a MongoDB Atlas reference architecture for BIRD looks like</h2><p>The proposed deployment has three parts, explained below.</p><p><strong>Figure 2.</strong> BIRD on MongoDB - a reference architecture.</p><p><strong>Object Storage for the raw data: </strong>The raw 2K-resolution drawing images and the exported 3D model files reside in an S3 bucket. Atlas stores only the bucket and key references, plus all extracted data, keeping the database lean and the images priced for large binaries.</p><p><strong>The inference service: </strong>BIRD can use a Python API. In production, it runs as a containerized service that pulls a drawing from S3, runs the dual-branch network and text recognition, and writes the resulting perspective document to Atlas.</p><p><strong>Event-driven workflow:</strong> A drawing upload triggers inference, and a project advances to 3D projection only when all five perspectives are approved. The flow runs like this:</p><ol><li><p><strong>Upload:</strong> The drafter uploads the five drawings through the upload service. The service writes each image to S3 and one small record per drawing (project ID, view, S3 key) to the uploads collection in MongoDB.</p></li><li><p><strong>Inference: </strong>The inference service watches the uploads change stream. For each new record, it downloads the image from S3, runs the BIRD models, and writes the extracted result (line segments, measurements, status) into that drawing&#39;s slot in the <em>projects</em> document. One project document holds all five drawings’ results.</p></li><li><p><strong>Review: </strong>The drafter reviews each drawing&#39;s result in the interface, corrects segments, and approves. Every correction and approval is written to the <em>projects</em> document, and each approval increments its approvedViews counter.</p></li><li><p><strong>Stream processing:</strong> MongoDB Atlas Stream Processing watches the <em>projects</em> change stream. When the fifth approval pushes approvedViews to 5, the processor writes one record to the projection_jobs collection.</p></li><li><p><strong>Projection:</strong> The 3D projection service picks up the record from projection_jobs, runs the wrapping algorithm, uploads the model file to S3, and writes the final 3D segment back to the <em>projects</em> collection document.</p></li></ol><p>At the end, the <em>projects</em> document holds everything about the build: results, corrections, approvals, and final geometry.</p><p>MongoDB Search can be used to search across the project history. We can also leverage Voyage AI models available through the <a href="https://www.mongodb.com/docs/voyageai/api-reference/overview/">Embedding and Reranking API</a> on MongoDB Atlas. MongoDB Search provides full-text search over project metadata, client names, drawing annotations, and the free-text notes drafters attach during review, so a user can type &quot;warehouse rafter detail&quot; and land on the right project. MongoDB Vector Search enables semantic search: for example, at ingestion, voyage-multimodal-3.5, used to vectorize visual data such as figures and technical drawings, encodes each drawing image into a vector stored on the project document, while voyage-4 embeds the review notes for semantic text retrieval. When a new project arrives, the system embeds the incoming floor plan and runs a $vectorSearch to surface the most geometrically similar past projects and a re-ranker model, rerank-2.5 ranks the shortlist before the drafter sees it. Using these MongoDB features, a drafter quoting a residential design can start from the corrected model of a near-identical build instead of a blank screen, which directly shortens quoting time on repetitive work. The $vectorSearch stage also supports pre-filtering on indexed metadata fields to reduce the candidates used in the search pipeline. </p><p><strong>Figure 3.</strong> MongoDB Search pipeline with Voyage AI models for embedding images and text.</p><p>Teams whose customers require self-hosted deployments are not locked out: MongoDB Search and Vector Search are generally available for MongoDB Enterprise Advanced and Community Edition, deployed as search nodes on Kubernetes, so the document model, change streams, $search, and $vectorSearch all carry over to self-hosted environments seamlessly.</p><h2>What does this MongoDB architecture enable for manufacturers?</h2><p>In the proposed approach, all the information and context live in one place: a single project document carries the extracted segments, the drafter&#39;s corrections, the approval trail, and the final 3D geometry, which gives the end user full traceability from uploaded drawing to exported model. The pipeline is event-driven end-to-end, with the stream processor doing the coordination, so there is no polling and no separate infrastructure to operate. The human review step is built in as well, and every correction the drafters make becomes labeled training data, so the system gets more accurate over time. And because the whole history is indexed with MongoDB Search and Voyage embeddings, each completed project makes the next quote faster.</p>]]></description>
      <pubDate>Wed, 23 Sep 2026 14:00:03 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/from-2d-drawings-3d-models-designing-ai-reconstruction-pipeline</link>
      <guid>https://www.mongodb.com/company/blog/innovation/from-2d-drawings-3d-models-designing-ai-reconstruction-pipeline</guid>
    </item><item>
      <title>Supporting a DPDPA-Compliant Ecosystem in India with MongoDB</title>
      <description><![CDATA[<p><em><strong>Disclaimer</strong></em><em>: This post is for informational purposes only and does not constitute legal advice. Organizations should work with qualified legal counsel to interpret the DPDPA and determine how its requirements apply to their specific circumstances.</em></p><p>India’s digital economy depends on applications that collect and process personal data every day, from payments and lending to healthcare, retail, and public services. As organizations prepare for the operational impact of the Digital Personal Data Protection Act (DPDPA), the challenge they face is no longer about policy interpretation. Organizations must now also tackle how teams implement privacy, security, and governance controls in the systems that handle personal data.</p><p>This post looks at the kinds of technical capabilities organizations may consider when building DPDPA-aligned applications and data architectures, and how MongoDB’s capabilities support those efforts.</p><h2>India&#39;s data governance framework, and why organizations should act now</h2><p>Made law in 2023 and brought into force in 2025, the Digital Personal Data Protection Act (DPDPA) establishes a legal framework for the collection, processing, storage, and protection of digital personal data in India. For many organizations, the practical impact of the law will extend beyond policy updates. It will require decisions about how consent is captured, how personal data is governed, how access is controlled, and how privacy-related requests are handled across applications and operational systems.</p><p>Rather than treating privacy as a downstream compliance task, many organizations are moving toward a privacy-by-design approach. In practice, that often means building controls for notice, consent, access, security, retention, and deletion into application and data-layer workflows from the start.</p><p>Failure to comply with DPDPA can result in significant penalties for certain violations, and the legislation raises the standard for how organizations manage personal data. </p><p>For business and technology teams, this means privacy readiness is not only a legal matter—it is also an operational and architectural issue that can have a real financial impact. As a result, systems should be designed so that privacy controls can be implemented consistently, evidenced clearly, and maintained as applications evolve.</p><h2>Key DPDPA entities and essential IT capabilities</h2><p>The DPDPA defines a set of key concepts and roles that shape how accountability is assigned across the personal data ecosystem:</p><ul><li><p><strong>Personal Data: </strong>Personal data means any data about an individual who is identifiable.</p></li><li><p><strong>Data Principal: </strong>The individual to whom the personal data belongs. The Act grants individuals rights over their personal data, including rights related to access, correction, updating, and erasure, subject to applicable provisions.</p></li><li><p><strong>Data Fiduciary: </strong>The organization or entity that determines why and how personal data is processed. It remains accountable for ensuring that processing is carried out in line with applicable obligations, including where certain functions are handled by third parties.</p></li></ul><p>To comply with DPDPA, Data Fiduciaries will need the practical capabilities to capture, govern, protect, and manage personal data throughout its lifecycle. Some of these capabilities can be built into existing applications. Others may require supporting services or changes to the underlying data architecture.</p><h3>Consent and notice management</h3><p>Data Fiduciaries will need a reliable way to capture a Data Principal’s consent, associate it with a purpose, maintain a history of changes, and reflect withdrawals or updates across relevant systems. Depending on the use case, applications may need to support age-related checks or guardian consents.</p><p>Data Fiduciaries may have some or all of the following obligations:</p><ul><li><p>Recording consent status together with purpose and relevant metadata</p></li><li><p>Maintaining an auditable history of consent changes</p></li><li><p>Tracking renewals, updates, and withdrawals over time</p></li><li><p>Propagating consent changes to downstream applications and services</p></li></ul><h3>Support for Data Principal requests</h3><p>Data Fiduciaries need workflows that allow individuals to view, correct, update, or request the deletion of a Data Principal’s<strong> </strong>personal data, subject to applicable legal and operational constraints. In practice, that often means reducing fragmentation so teams can identify relevant records, make consistent updates, and retain appropriate evidence of the action taken.</p><h2>Why relational data models make DPDPA compliance harder</h2><p>Many enterprise applications were not originally designed with modern privacy requirements in mind. In traditional architectures, customer information, consent records, preferences, and audit data are often spread across multiple tables, services, and applications. That makes it harder to answer basic operational questions, such as whether valid consent exists, where personal data is stored, or which downstream systems need to be updated when a privacy preference changes.</p><p>The same challenge appears when Data Fiduciaries need to respond to correction or deletion requests. They may have to locate data across multiple systems, coordinate changes across application boundaries, and maintain a reliable record of what was changed and when. As application estates grow, those workflows can become complex, more error-prone, and more expensive to operate.</p><h2>Simplifying DPDPA compliance with MongoDB</h2><p>Meeting DPDPA-related technical obligations often involves bringing data, consent state, security controls, and operational workflows closer together. </p><p>MongoDB’s capabilities—such as its flexible document model, change streams, in-use encryption, and MongoDB Search—can help consolidate privacy-relevant data and context, making it easier to implement and operationalize workflows for consent management, data access, correction, deletion, and auditability.</p><p><strong>Figure 1.</strong> The foundation of a DPDPA-compliant ecosystem.</p><p>MongoDB also offers different enterprise-ready deployment models depending on operational, residency, and control requirements. For example:</p><ul><li><p><a href="https://www.mongodb.com/products/platform/atlas-database"><strong>MongoDB Atlas</strong></a> is MongoDB’s fully managed intelligent data platform. It provides managed operations, scaling, security features, monitoring, backup options, and deployment flexibility across major cloud providers.</p></li><li><p><a href="https://www.mongodb.com/products/self-managed/enterprise-advanced"><strong>MongoDB Enterprise Advanced</strong></a> is MongoDB’s self-managed commercial offering for Data Fiduciaries that want to run MongoDB in their own environment, including on-premises, private cloud, or hybrid architectures, with enterprise support and management tooling such as Ops Manager.</p></li></ul><h2>How MongoDB can help achieve DPDPA compliance</h2><p>Table 1 below summarizes MongoDB capabilities that Data F,iduciaries may evaluate when designing systems to support DPDPA compliance. The exact implementation approach will depend on the application, deployment model and regulatory interpretation.</p><h2>Prepared for compliance, built for trust</h2><p>For most organizations, DPDPA readiness will come down to execution. Data Fiduciaries need to know where a Data Principal’s personal data lives, decide which controls belong in the application versus the data layer, and show that those controls can be operated consistently over time. MongoDB can help support that work by reducing data fragmentation and giving Data Fiduciaries a flexible foundation for building consent, security, resilience, and governance workflows into the systems they already run.</p><p>Organizations building digital services in India need a data infrastructure that can handle population-scale workloads, satisfy DPDPA compliance obligations, and enforce privacy controls without sacrificing agility.</p><p>MongoDB Atlas provides a flexible, secure, intelligent data platform with native capabilities like client-side field-level encryption, real-time change streams, and in-region deployment to simplify privacy-by-design architectures.</p>]]></description>
      <pubDate>Wed, 23 Sep 2026 01:00:02 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/supporting-dpdpa-compliant-ecosystem-in-india</link>
      <guid>https://www.mongodb.com/company/blog/innovation/supporting-dpdpa-compliant-ecosystem-in-india</guid>
    </item><item>
      <title>Introducing the Embedding and Reranking API on MongoDB Atlas</title>
      <description><![CDATA[<p>The next frontier for AI isn’t simply more capable models. It’s better context. As LLMs become embedded in every process and product, their accuracy and trust depend on grounding generation in the right data. Search and retrieval are foundational to this shift, powering everything from AI chatbots and assistants to fully autonomous agents. But building AI retrieval today means stitching together databases, vector search, and retrieval model providers—each introducing operational complexity.</p><p>To address this, we’re introducing the Embedding and Reranking API on MongoDB Atlas, now in public preview. This service gives developers direct access to Voyage AI’s state-of-the-art retrieval models within the Atlas ecosystem. Use it as a standalone API with any stack or combine it with MongoDB Atlas features like Vector Search to build complete retrieval pipelines on a single, enterprise-grade platform.</p><h2>Bringing frontier AI retrieval models to MongoDB Atlas</h2><p>Embedding and reranking models are core components of modern retrieval systems, driving the accuracy of recommendation, search, and RAG applications.</p><p>Yet selecting the right model is often overlooked. Results from the <a href="https://huggingface.co/spaces/embedding-benchmark/RTEB">Retrieval Embedding Benchmark (RTEB) </a>show that retrieval accuracy varies significantly across tasks, with performance gaps of up to nearly 50% between the strongest and weakest models. </p><p>Choosing the right retrieval models is critical for:</p><ul><li><p>Improving retrieval accuracy </p></li><li><p>Minimizing storage costs, latency, and context bloat </p></li><li><p>Addressing the needs of specific industries, such as law and finance.</p></li></ul><p>Voyage AI offers a comprehensive suite of state-of-the-art embedding and reranking models that consistently deliver the highest accuracy across categories on <a href="https://huggingface.co/spaces/embedding-benchmark/RTEB">RTEB</a>. The text embedding models support flexible dimensionality, ranging from 256 to 2048, as well as quantization, giving developers control over the quality-cost-latency tradeoff. Beyond general-purpose embeddings, Voyage offers models tailored for domain-specific applications (such as law, finance, and code), full-document understanding, multimodal use cases, and high-precision reranking for two-stage retrieval pipelines.</p><p>Voyage AI’s models are now natively available on MongoDB Atlas via the new Embedding and Reranking API, adding to the AI retrieval capabilities available through our platform. This serverless API offers simple token-based pricing and is open for use with any stack, not just MongoDB. </p><p>Today, we are also launching the <a href="https://blog.voyageai.com/2026/01/15/voyage-4/">Voyage 4 model series</a>, our most advanced embedding models yet. This new generation of models features an industry-first shared embedding space, making the models compatible with one another and giving developers more flexibility to optimize for accuracy, speed, and cost. You can now start building with the Voyage 4 series using the Embedding and Reranking API on MongoDB Atlas.</p><p></p><h2>MongoDB Atlas: A unified platform for AI retrieval</h2><p>MongoDB Atlas now offers the foundational operational database, advanced vector search capabilities, and state-of-the-art retrieval models needed to build AI applications on a single platform. Teams get consolidated and unified user management, monitoring, and billing, backed by enterprise-grade security and controls already trusted by tens of thousands of customers, including over 75% of Fortune 100 companies.</p><p>This matters for building production AI systems. Scaling LLM applications requires delivering the right context at the right time, which means tightly integrating operational data with high-performance search. MongoDB Atlas&#39;s industry-leading document database and built-in vector search capabilities already power retrieval systems across AI startups and large enterprises. The Embedding and Reranking API completes these capabilities, enabling teams to build end-to-end AI retrieval from data storage to vector search to embeddings and reranking entirely within MongoDB Atlas.</p><p></p><p>Better AI starts with better context. With Voyage AI&#39;s state-of-the-art models now accessible via the Embedding and Reranking API on MongoDB Atlas, teams can build complete retrieval pipelines on a proven platform—from data storage and vector search to embeddings and reranking. The API is available now in public preview.</p><p></p>]]></description>
      <pubDate>Tue, 22 Sep 2026 19:59:05 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/product-release-announcements/introducing-the-embedding-and-reranking-api-on-mongodb-atlas</link>
      <guid>https://www.mongodb.com/company/blog/product-release-announcements/introducing-the-embedding-and-reranking-api-on-mongodb-atlas</guid>
    </item><item>
      <title>Data Sovereignty by Design: Five Practical Evaluation Lenses for IT Leaders</title>
      <description><![CDATA[<p>For IT leaders evaluating sensitive or regulated workloads, data sovereignty can be explored through architecture and governance questions rather than treated as a single legal status. From a legal and policy perspective, the term should be treated as a market expression, not as a universally defined legal standard, certification, or conclusion about compliance. Data sovereignty refers to questions organizations may have about where data resides, who can access it, how it moves, and whether an organization retains meaningful control over it, especially across jurisdictions. </p><p>Depending on the organization’s circumstances, the assessment may include deployment location, access paths, encryption design, key custody, portability, operational resilience, support processes, and the treatment of associated metadata. These considerations and their relative importance can differ by country, industry, workload, contractual commitments, and risk posture. One practical question is therefore not whether a platform carries a universal “sovereignty” label, but which controls and operating boundaries an organization may want to evaluate for its own environment.</p><p>Europe illustrates why data sovereignty discussions cannot be reduced to storage location. GDPR (General Data Protection Regulation) is a data protection framework that can affect how organizations collect, use, protect, and transfer personal data. DORA (Digital Operational Resilience Act) addresses digital operational resilience and ICT (Information and Communications Technology) third-party risk for in-scope financial entities, while NIS2 (Network and Information Systems Directive 2) addresses cybersecurity risk and incident-related obligations for in-scope entities. These frameworks are different in purpose, scope, and application. They may influence how an organization evaluates deployment, access, encryption, operational resilience, portability, and evidence, but no conclusion is drawn here about their requirements or whether a particular architecture satisfies them. Organizations should assess the relevant legal and regulatory context with qualified counsel and their internal compliance teams.</p><p>Similar questions arise in other markets, although the relevant frameworks are not interchangeable. Examples include India’s DPDP (Digital Personal Data Protection) Act, China’s PIPL (Personal Information Protection Law), Brazil’s LGPD (Lei Geral de Proteção de Dados), and the UAE’s Federal Data Protection Law. These examples illustrate that organizations operating across APAC, LATAM, the Middle East, and other regions may need to consider different combinations of data protection, localization, transfer, cybersecurity, sector, and operational requirements. The existence or scope of a framework does not by itself establish a common global definition of data sovereignty, and no legal obligations are characterized here as applicable to any particular organization.</p><p>That context can become more complex when provider jurisdiction and potential extraterritorial access are part of the risk analysis. Laws such as the US CLOUD Act (Clarifying Lawful Overseas Use of Data Act), alongside data protection, cybersecurity, and operational resilience frameworks, illustrate why organizations may choose to design solutions that are secure, flexible, and measurable against their own data sovereignty objectives. The challenge is translating those objectives into an architecture whose controls and dependencies can be examined in practice. The next section explores that challenge, followed by five illustrative areas intended as a practical reference for evaluating architectures, not as a legal test, certification checklist, or guarantee of sovereignty.</p><h2>The challenge: Translating sovereignty objectives into technical questions</h2><p>Physical location remains an important consideration, but it is only one part of a broader control boundary. Who operates the service, who can access plaintext, where key custody sits, and whether management or support functions extend beyond the deployment region can all influence an organization’s assessment. An architecture addressing these questions may consider the full operating model, not just storage geography.</p><p>A jurisdiction-by-jurisdiction response can create parallel platforms, fragmented operations, and duplicated control processes. The architectural challenge is to support different levels of control without multiplying unnecessary complexity. A flexible platform model can give organizations options for evaluating placement, encryption, access governance, portability, and operational resilience according to each workload and risk profile.</p><p>Regulatory and geopolitical conditions can change over time, making it important to consider whether an architecture can adapt as an organization’s risk posture, provider relationships, or jurisdictional needs change. These pressures make the underlying architecture the next question: which capabilities can organizations evaluate to design a secure, flexible, and measurable approach to data sovereignty?</p><h2>Key capabilities for sovereignty by design</h2><p>To turn these ideas into practical design questions, the following sections explore five illustrative technical areas that organizations may evaluate when considering data sovereignty objectives. They offer one way to compare deployment options, understand trade-offs, and identify where technical, contractual, security, compliance, or legal review may be needed. This is a practical guide for architecture decisions, not a legal test, certification checklist, or guarantee of data sovereignty.</p><p><strong>Figure 1.</strong> Core technical pillars of data sovereignty.</p><p><strong>Jurisdiction-native data placement:</strong> Organizations may evaluate whether data-placement controls operate at the infrastructure layer, rather than only at the application layer. Relying on application code for regulatory requirements can lead to risks like misconfigurations, data being stored or processed outside the permitted jurisdiction, or unauthorized access to sensitive data. These issues can result in regulatory violations, reputational damage, and loss of customer trust.</p><p><strong>In-use encryption that can reduce plaintext exposure:</strong> Encryption at rest and in transit is table-stakes. In-use encryption can protect configured PII (Personally Identifiable Information) and sensitive fields from plaintext access by the database server during supported query processing. This may reduce provider-level plaintext exposure for protected fields, depending on the encryption configuration, key-management model, and organization’s threat model.</p><p><strong>Customer-held encryption keys outside the provider&#39;s reach:</strong> Keys accessible by the platform provider extend the provider&#39;s access to the customer&#39;s data. Key-management requirements and provider access controls depend on the organization’s deployment model, threat model, and stated requirements.</p><p><strong>Network isolation and identity-based access governance:</strong> Private connectivity options, multi-factor authentication, federated identity, and least-privilege controls can be evaluated according to the deployment model and the organization’s access requirements.</p><p><strong>Forensic-grade audit evidence:</strong> Organizations may evaluate whether authentication, access, configuration, schema, and key-management events can be captured and integrated with centralized security monitoring, subject to product configuration and scope.</p><h2>How MongoDB capabilities can support the evaluation</h2><p>MongoDB offers deployment options for different operational contexts. This article does not simply focus on workload portability. It outlines five sovereignty capabilities that enterprises can consider to evaluate platforms, while enabling teams to select the appropriate operating model for each jurisdictional risk profile:</p><ul><li><p><a href="https://www.mongodb.com/products/platform/atlas-database"><strong>MongoDB Atlas</strong></a><strong>:</strong> Fully managed cloud database service, available in AWS, Azure, and GCP; MongoDB manages infrastructure, patching, and high availability.</p></li><li><p><a href="https://www.mongodb.com/products/self-managed/enterprise-advanced"><strong>MongoDB Enterprise Advanced (EA)</strong></a><strong>:</strong> Self-managed deployment for organizations seeking direct infrastructure control, including on-premises, private-cloud, and air-gapped environments.</p></li><li><p><a href="https://www.mongodb.com/products/self-managed/community-edition"><strong>MongoDB Community Edition</strong></a><strong>:</strong> Open-source edition for development and evaluation workloads.</p></li></ul><p>Atlas holds third-party certifications, including SOC 2 (System and Organization Controls 2), ISO 27001, PCI DSS (Payment Card Industry Data Security Standard), and a HIPAA (Health Insurance Portability and Accountability Act) Business Associate Agreement. It also provides public documentation and guidance on product capabilities, deployment considerations, and security controls to help organizations assess alignment with regulatory obligations such as GDPR, DORA, and NIS2.</p><p>Enterprise Advanced supports many of the same security and deployment control patterns, but the relevant certifications, attestations, and audit outcomes depend on the customer’s own infrastructure, operations, and assessment scope.</p><p><strong>Jurisdiction-native data placement:</strong> Atlas enables strict technical boundaries for data placement by enforcing Resource Policies that block cluster creation outside approved regions at the platform level, regardless of who initiates the operation, while zone-based sharding automatically routes specific customer populations to designated geographic regions without requiring application changes. These platform constraints form a robust baseline for data residency, but achieving data sovereignty requires evaluating broader legal and operational dimensions, as it ultimately depends on how an organization defines sovereignty and the specific regulations to which it is exposed. Variables such as control plane dependencies, cross-region support access, cloud provider jurisdiction, and applicable frameworks like the US CLOUD Act must be individually assessed based on the organization&#39;s unique requirements.</p><p><strong>In-use encryption:</strong> Atlas supports Queryable Encryption (QE) and Client-Side Field Level Encryption (CSFLE) as two in-use encryption approaches. Both can encrypt selected sensitive fields in the client before data reaches the database server. They can be used in the same application or deployment, but not together in the same collection. For configured encrypted fields, the database server receives encrypted values and cannot decrypt them without access to the relevant keys. While this technical control does not entirely resolve jurisdictional challenges like the US CLOUD Act on its own, as compliance depends on a broader set of governance factors, including key custody, metadata handling, control plane access, and organizational risk management, it serves as an effective mechanism to mitigate plaintext data exposure under strict extraterritorial disclosure requests.</p><p><strong>Customer-held encryption keys: </strong>Atlas integrates BYOK (Bring Your Own Key) with AWS (Amazon Web Services) KMS (Key Management Service), Azure Key Vault, GCP KMS (Google Cloud Platform Key Management Service), and any KMIP (Key Management Interoperability Protocol)-compliant key management infrastructure. Key custody through the customer’s KMS ensures that encryption keys remain under the customer&#39;s control, providing audit evidence that bridges the gap between contractual commitments and technical enforceability.</p><p><strong>Network isolation and access governance: </strong>Atlas provides private connectivity options, including Private Endpoints and VPC (Virtual Private Cloud) peering, that can reduce or avoid public exposure for database connections, subject to the deployment and supporting services. Role-based access control (RBAC), multi-factor authentication (MFA), and identity federation via LDAP (Lightweight Directory Access Protocol) and OIDC (OpenID Connect) govern all access at the platform layer.</p><p><strong>Forensic-grade audit evidence:</strong> Atlas provides audit and activity evidence for relevant authentication, access, configuration, and security events, with integration into SIEM (Security Information and Event Management) platforms, subject to configuration and scope.</p><p><strong>MongoDB Enterprise Advanced for customer-controlled and air-gapped deployment models:</strong> EA serves as an architectural option for organizations requiring direct control over their deployment environment, particularly when regulatory-defined infrastructure perimeters, complete network isolation, or self-managed control planes are preferred. While cloud-managed services satisfy many compliance standards, self-hosted deployments like EA provide the flexibility to operate within fully isolated networks or custom sovereign boundaries. This approach highlights the practical value of geopatriation, allowing organizations to maintain application continuity while shifting to a fully customer-governed operational boundary when specific legal or risk requirements demand it.</p><p>One critical caveat applies to all Atlas deployments: the Atlas control plane and the MongoDB support team, responsible for cluster provisioning, monitoring, and operational management, operate across a broader infrastructure footprint than the data plane. Organizations with requirements that restrict data or metadata movement may evaluate Enterprise Advanced and Atlas-specific configuration controls separately, together with technical and legal review of the relevant limitations. This illustrates the distinction between controls that support selected residency objectives and broader organizational objectives covering data, access, operations, and evidence.</p><h2>Potential business considerations</h2><p>When organizations address these considerations early in platform architecture, they may identify several potential operational and business benefits.</p><p><strong>Faster market entry and reduced cost:</strong> Addressing placement, access, encryption, and evidence requirements early may simplify some procurement and architecture-review activities, depending on the organization’s requirements and implementation. A common platform with centralized monitoring, consistent encryption policies, and consolidated audit logging may reduce some operational duplication, although regional requirements may still require separate deployments or processes. A flexible architecture may make it easier to adapt as country-specific requirements, regulations, or provider relationships change.</p><p><strong>Reduced operational overhead:</strong> A common operating model may reduce the need to maintain separate monitoring and incident-response processes, subject to workload and jurisdictional needs. The engineering capacity previously consumed by maintaining parallel regional clusters returns to product and AI feature development.</p><p><strong>Accelerated AI delivery and defensible procurement posture</strong>: A consistent governance model may support data and AI initiatives across markets, subject to each workload’s access, transfer, and data-use requirements. An architecture that limits plaintext access for configured protected fields, applies an appropriate key-management model, and considers portability can provide a stronger basis for evaluating provider and jurisdictional risk. Application impact during a provider or deployment change depends on the architecture.</p><h2>Final thoughts </h2><p>Sovereignty objectives can be translated into observable technical and operational controls. If an architecture cannot demonstrate its placement, plaintext-exposure, key-management, access, and evidence controls, organizations may find it more difficult to assess the architecture against their stated objectives. MongoDB provides a practical path across managed and self-managed deployment models, but the differentiator is disciplined implementation: explicit control boundaries, control-plane-aware design, and evidence-backed operations from day one.</p><h2>Disclaimer </h2><p>This content is for informational purposes only and does not constitute legal advice. Regulatory requirements vary by jurisdiction and industry. Organizations should consult qualified legal counsel and their internal compliance teams to understand their specific obligations.</p>]]></description>
      <pubDate>Tue, 22 Sep 2026 14:48:25 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/data-sovereignty-by-design-five-practical-evaluation-lenses-for-it-leaders</link>
      <guid>https://www.mongodb.com/company/blog/innovation/data-sovereignty-by-design-five-practical-evaluation-lenses-for-it-leaders</guid>
    </item><item>
      <title>Financial Crime Mitigation with MongoDB / Part III: Behavioral Risk Modeling for Event-Driven Fraud Detection</title>
      <description><![CDATA[<p>Welcome back to our series on Building a Financial Crime Mitigation Platform, in which we demonstrate how MongoDB ideally supports the technical capabilities of modern digital financial operations as a unified data platform. In case you missed it, be sure to check out <a href="https://www.mongodb.com/company/blog/innovation/building-financial-crime-mitigation-platform-with-mongodb-series-overview">the series overview</a>.</p><p>Modern financial institutions are increasingly constrained by architectural debt. Legacy systems, built on rigid schemas and batch-oriented processing, create significant data gravity that hinders real-time response. As an event-driven backbone, MongoDB allows architects to move beyond rule-based systems that lack the contextual richness required for comprehensive fraud analysis.</p><p>By combining a <a href="https://www.mongodb.com/company/blog/innovation/building-a-dynamic-customer-profile-using-mongodb">dynamic customer profile</a> with continuously updated risk models, we can drastically improve fraud detection latency and lower the total cost of ownership (TCO) by reducing manual intervention. Let’s examine the implementation.</p><h2>Behavioral risk modeling</h2><p>Rule-based systems alone are no longer enough for today’s world. Modern financial services, like instant payments, real-time onboarding, and cross-border transfers, require a comprehensive analysis that combines rules and policies with transactional and customer context to answer more complex questions: Where is this transaction coming from? Is this the average/standard deviation amount from this customer’s profile? Is the biometric information in line with the customer&#39;s usual behavior? And more importantly: Is this a transaction that can be approved automatically, or does it need further investigation?</p><p>Successful modern solutions are the ones that combine the best of both worlds: maintaining rule-based applicable policies along with probabilistic reasoning, either with similarity search or by integrating with advanced machine learning solutions.</p><p>In practical terms, you can rely on MongoDB’s flexible data model to create a rule-based system, adding MongoDB’s change streams for asynchronous, decoupled processing of new events. This decoupled architecture enhances system resilience by isolating risk evaluation from the core transactional path. Let’s take the example of our <a href="https://github.com/mongodb-industry-solutions/fsi-aml-fraud-detection">demo prototype</a>:</p><p><strong>Figure 1. </strong>Behavioral risk model factors using MongoDB’s document data model.</p><p>(Image taken from our <a href="https://github.com/mongodb-industry-solutions/fsi-aml-fraud-detection">demo prototype</a>. Disclosure: The look and feel is from a custom UI developed for demo purposes. It is not part of MongoDB’s offering.)</p><p>As shown in the figure, MongoDB captures behavioral events such as unusual typing or mouse patterns, as well as device IP addresses that match expected geographic locations already registered in the customer profile. MongoDB captures these real-time events through <a href="http://mongodb.com/docs/manual/changestreams/">change streams</a>. Change streams allow applications to access data changes as they occur and react immediately, without relying on legacy database updates, triggers, or brittle production scripts. This approach helps architects deploy new business rules quickly, enforce schema validation, and maintain a non-blocking, event-driven flow</p><p>MongoDB’s multi-modal document model also aggregates transactional, operational, unstructured (vectorized), time series, and geospatial data into a single dataset. This allows financial institutions to build behavioral risk models on a broader and more contextual data foundation. Figure 2 shows a practical example of this approach by illustrating how new risk factors can be added on the fly.</p><p><strong>Figure 2. </strong>Real-time updates for the behavioral risk model. </p><p>(Image taken from our <a href="https://github.com/mongodb-industry-solutions/fsi-aml-fraud-detection">demo prototype</a>. Disclosure: The look and feel is from a custom UI developed for demo purposes. It is not part of MongoDB’s offering.)</p><h2>Event-driven fraud detection</h2><p>With a dynamic risk model that combines rule-based and behavioral assessment, financial institutions can analyze fraud in real time.</p><h3>Customer behavioral analysis</h3><p>As discussed in this series’ previous blog, <a href="https://www.mongodb.com/company/blog/innovation/building-a-dynamic-customer-profile-using-mongodb">building a customer dynamic profile</a>, MongoDB’s document model makes this approach technically feasible. MongoDB can aggregate data from different sources and schemas into a dynamic profile that updates in an event-driven way. </p><p>Based on the captured information, financial institutions can define a behavioral profile like this:</p><p><strong>Figure 3. </strong>Dynamic behavioral profile. </p><p>(Image taken from our <a href="https://github.com/mongodb-industry-solutions/fsi-aml-fraud-detection">demo prototype</a>. Disclosure: The look and feel is from a custom UI developed for demo purposes. It is not part of MongoDB’s offering.)</p><p>Beyond capturing event-driven signals, financial institutions can use MongoDB to incorporate derived features such as moving averages and standard deviations to build a truly multi-dimensional behavioral profile.</p><h3>Transactional assessment</h3><p>Using this profile, MongoDB can assess each incoming transaction through similarity search. MongoDB Vector Search compares the vectorized representation of an incoming transaction with prior transactions labeled as authorized or declined. This helps identify suspicious activity and route high-risk transactions to an advanced analytics solution for further investigation.</p><p>A vectorized representation of a transaction should include customer profile information, transaction information, applicable policies and regulatory rules, and the risk model described earlier. With this foundation, vector search can evaluate each transaction against relevant historical patterns.</p><p><strong>Figure 4. </strong>Real-time transaction screening using Atlas Vector Search.</p><p>Architecturally, MongoDB Vector Search serves as an intelligent filter that separates low-risk, legitimate transactions from suspicious ones. This helps financial institutions reduce false positives and optimize the workload for downstream due diligence systems.</p><h2>Reducing false positives</h2><p>Let’s take a look at a practical example of using MongoDB’s vector to assess a fraudulent transaction.</p><p>If a customer has an average transaction amount of a few hundred dollars, usually transacts from a known location, and uses a registered device, the incoming transaction is likely to show high similarity to previous legitimate transactions. Conversely, a transaction that is far above the average amount, comes from an unknown location, and originates from an unregistered device is likely to show higher similarity to previous suspicious transactions.</p><p><strong>Figure 5. </strong>Similarity detection results: valid vs. suspicious transaction assessment.</p><p>(Image taken from our <a href="https://github.com/mongodb-industry-solutions/fsi-aml-fraud-detection">demo prototype</a>. Disclosure: The look and feel is from a custom UI developed for demo purposes. It is not part of MongoDB’s offering.)</p><p>One important consideration for similarity detection is that, while vector search captures behavioral features such as merchant category and location, it does not evaluate numerical data such as transaction amount. Financial institutions can assess those values through traditional risk scoring. This shows that a true comprehensive risk assessment is one that combines rule-based and contextual analysis.</p><p><strong>Figure 6. </strong>The vector embedding process.</p><p>(Image taken from our <a href="https://github.com/mongodb-industry-solutions/fsi-aml-fraud-detection">demo prototype</a>. Disclosure: The look and feel is from a custom UI developed for demo purposes. It is not part of MongoDB’s offering.)</p><h2>Takeaways</h2><p>MongoDB makes behavioral risk models and contextual fraud detection technically feasible through several core capabilities:</p><ul><li><p>Its <strong>schema flexibility</strong> lets risk managers add heterogeneous risk factors on-the-fly without complex migrations or downtime.</p></li><li><p><strong>Change streams</strong> update risk models in real time through an event-driven approach. This eliminates the need for periodic refreshes, API polling, or traditional scripts.</p></li><li><p><strong>Version control, schema enforcement, auditing, and rollback </strong>capabilities make risk model management more efficient without downtime.</p></li><li><p><strong>MongoDB Vector Search</strong> assesses incoming transactions in near real time through similarity search. It compares transactions against common patterns to help isolate suspicious activity.</p></li></ul><p><em>In the next article in this series, we dive deeper into how MongoDB’s platform capabilities can enable Agentic AI systems for streamlining case management processes. Read the fourth part of the series </em><a href="https://www.mongodb.com/company/blog/innovation/financial-crime-mitigation-part-iv-agentic-ai-for-case-management"><em>here</em></a><em>.</em></p>]]></description>
      <pubDate>Mon, 21 Sep 2026 16:53:39 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/financial-crime-mitigation-part-iii-behavioral-risk-modeling-for-event-driven-fraud-detection</link>
      <guid>https://www.mongodb.com/company/blog/innovation/financial-crime-mitigation-part-iii-behavioral-risk-modeling-for-event-driven-fraud-detection</guid>
    </item><item>
      <title>Financial Crime Mitigation with MongoDB / Part II: Comprehensive Analysis</title>
      <description><![CDATA[<p>Welcome back to our series on Building a Financial Crime Mitigation Platform, in which we show how MongoDB ideally supports the demands from modern digital financial operations as a unified data platform. In case you missed it, be sure to check out <a href="https://www.mongodb.com/company/blog/innovation/building-financial-crime-mitigation-platform-with-mongodb-series-overview">the series overview</a>.</p><p>As part of onboarding new entities, financial institutions are required to run a comprehensive analysis in order to comply with KYC (Know-Your-Customer) regulations. In our previous <a href="https://www.mongodb.com/company/blog/innovation/building-a-dynamic-customer-profile-using-mongodb">blog post</a>, we covered building a unified single view of the customer. The next step is to go through different checks to make sure the prospect is legally entitled to become a customer.  </p><h2>Complying with financial crime regulations</h2><p>Whenever a financial institution is onboarding a new prospective customer, it needs to comply with the so-called FATC (Financial Action Task Force) Recommendations. Among all the guidelines, the most important ones are:</p><ul><li><strong>Customer due diligence (CDD)</strong>: Identifying and verifying the customer and “beneficial owners” (who really own the money).</li><li><strong>Sanctions screening</strong>:<strong> </strong>“Enhanced” scrutiny beyond the basic one, applicable for high-risk customers with higher exposure (e.g., offshore account holders), clients listed in OFAC (The Office of Foreign Assets Control) lists, or those considered Politically Exposed Persons (PEPs).</li><li><strong>Record keeping &amp; perpetual monitoring</strong>: Maintaining transaction records for at least five years. Making sure it is constantly updated in an “event-driven” mode (updating customer information based on events).</li></ul><p>Each country or region is responsible for implementing these recommendations in line with its local regulations. Around the world, many jurisdictions have established anti-money laundering and counter-terrorist financing (AML/CFT) frameworks aligned with international standards. These include the United States, the European Union, the United Kingdom, Singapore, Hong Kong, Japan, South Korea, and several Latin American countries.</p><p>Throughout the years, these screening and compliance checks have become a bottleneck, preventing financial institutions from providing a fast and efficient onboarding process that would improve the overall customer experience. Mainly due to its lengthy, manual checks. Furthermore, having human risk analysts not only includes the human-error factor but also limits their ability to foresee potential risk beyond the visible ones. </p><h2>Agentic AI to the rescue</h2><p>Here is the transformational power of AI in the financial crime mitigation space: </p><ul><li><strong>Enhanced fraud detection:</strong> AI Agents can use similarity search of known patterns for minimizing false positives. </li><li><strong>Advanced transaction monitoring</strong>: AI models can use synthetic data for evaluating the likelihood of potential different scenarios.</li><li><strong>Behavioral risk scoring</strong>: Smart agents can use graph neural networks for analyzing a complex web of relations and unnoticeable events. </li><li><strong>Real-time responses &amp; automation:</strong> <a href="https://www.mongodb.com/resources/basics/artificial-intelligence/large-language-models">LLM models</a> can be used for generating due diligence case reports, serving as a copilot/assistant to human risk analysts. </li></ul><h2>MongoDB as the agentic AI enabler</h2><p>For each of the described capabilities, AI Agents would require a unified, traceable single-source of truth database that can serve as the contextual data store, but also as the memory/semantic cache for executing each specific action:</p><p><strong>Figure 1. </strong>MongoDB as an Agentic AI Enabler through an onboarding process.</p><p>Besides providing the contextual data store and the memory semantic cache, MongoDB is an enterprise-grade data platform enabling query and search capabilities as tools to be invoked by agents to fulfill the corresponding business operations.</p><p><strong>Figure 2. </strong>MongoDB platform services available as tools for Agentic workflows.</p><h2>Use Case: Applying agentic AI powered by MongoDB for enhanced due diligence (EDD)</h2><p>With the regulatory and architectural foundations in place, financial institutions can combine agentic AI with MongoDB to streamline enhanced due diligence (EDD) and case management. In this section, we focus on three core stages of the EDD process: network analysis, AI‑powered classification, and case investigation and reporting.</p><p><strong>Figure 3. </strong>Demo workflow process for Entity Resolution/KYC as part of the onboarding process.</p><h3>1. Network analysis</h3><p>EDD starts by understanding how a prospective customer connects to existing entities and transactions. Using <a href="https://www.mongodb.com/products/platform/atlas-vector-search">MongoDB Atlas Vector Search</a>, risk teams can retrieve the most similar profiles and construct an ‘on‑the‑fly’ relationship graph directly from the operational data store.</p><p>Rather than relying on precomputed graph tables or separate graph databases, MongoDB’s aggregation framework builds this network view at query time, combining similarity scores, shared attributes, and historical interactions into a dynamic picture of the entity’s risk context.</p><p><strong>Figure 4. </strong>Top entity analysis brought by similarity search using MongoDB Vector Search.</p><p>Image taken from our <a href="https://github.com/mongodb-industry-solutions/fsi-aml-fraud-detection">demo prototype</a>. Disclosure: The look and feel is from a custom UI developed for demo purposes. It is not part of MongoDB’s offering.</p><h3>2. AI-powered classification</h3><p>Once the closest entities and their relationships are identified, their attributes and behavioral patterns can flow into an LLM‑based classification workflow(in this case: Claude Sonnet 4 running on Amazon Bedrock) to classify the prospective customer, and determine what should the best course of action:</p><p><strong>Figure 5. </strong>Prompt Engineering for AI entity classification.</p><p>Image taken from our <a href="https://github.com/mongodb-industry-solutions/fsi-aml-fraud-detection">demo prototype</a>. Disclosure: The look and feel is from a custom UI developed for demo purposes. It is not part of MongoDB’s offering.</p><p>Because this workflow runs on top of MongoDB as the unified data store, the model works with full context: network relationships, historical transactions, sanctions hits, and prior alerts reside in one place, instead of being scattered across disconnected systems.</p><h3>3. Case investigation</h3><p>When the model flags an entity as higher risk—for example, by categorizing them as a Politically Exposed Person (PEP) or surfacing high‑risk behavioral patterns—the workflow can automatically open a case investigation with clear, explainable next steps. Furthermore, investigators can systematically review identity information across all connected entities, re‑run targeted checks, and enrich the case with additional context, all from a single, entity‑centric view (go beyond the visible).</p><p><strong>Figure 6. </strong>Example of next best recommendation provided by the AI model.</p><p>Image taken from our <a href="https://github.com/mongodb-industry-solutions/fsi-aml-fraud-detection">demo prototype</a>. Disclosure: The look and feel is from a custom UI developed for demo purposes. It is not part of MongoDB’s offering.</p><p>Backed by MongoDB as the data platform, investigators can systematically review identity information across all connected entities, re‑run targeted checks, and enrich the case with additional context, all from a single, entity‑centric view. In parallel, LLMs can generate human-readable case summaries that bring together network analysis, classification results, and recommended actions into a structured report ready for review and filing.</p><p><strong>Figure 7. </strong>Example of a case report generated by the LLM model.</p><p>Image taken from our <a href="https://github.com/mongodb-industry-solutions/fsi-aml-fraud-detection">demo prototype</a>. Disclosure: The look and feel is from a custom UI developed for demo purposes. It is not part of MongoDB’s offering.</p><h2>Takeaways</h2><p>AI is a transformative technology that can significantly improve due diligence and case investigation processes. It can reduce false positives by identifying known patterns, uncovering hidden relationships, simulating what-if scenarios with synthetic data, and using LLMs to generate case reports and assist risk analysts.</p><p>According to McKinsey &amp; Company, banks often dedicate 10–20% of their workforce to KYC and AML activities, while still struggling with low automation rates, fragmented data sources, and unstandardized datasets. These challenges create inefficient manual processes and slow, frustrating onboarding experiences for customers.</p><p>By introducing AI-driven automation and intelligent analysis, financial institutions can streamline traditionally lengthy and error-prone workflows, improve analyst productivity, strengthen financial crime controls, and reduce operational costs.</p><p><em>In the next article in this series, we dive deeper into how MongoDB’s platform capabilities can improve fraud detection, transaction monitoring, and behavioral risk assessment. Read the third part of the series </em><a href="https://www.mongodb.com/company/blog/innovation/financial-crime-mitigation-part-iii-behavioral-risk-modeling-for-event-driven-fraud-detection"><em>here</em></a><em>.</em></p><p><em>1 </em><em> Alexander Verhagen, Angela Luget, Olivia Conjeaud, and Vasiliki Stergiou, “</em><a href="https://www.mckinsey.com/capabilities/risk-and-resilience/our-insights/how-agentic-ai-can-change-the-way-banks-fight-financial-crime"><em>How Agentic AI Can Change the Way Banks Fight Financial Crime</em></a><em>,” McKinsey &amp; Company, August 7, 2025.</em></p>]]></description>
      <pubDate>Mon, 21 Sep 2026 16:52:46 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/financial-crime-mitigation-with-mongodb-part-ii-comprehensive-analysis</link>
      <guid>https://www.mongodb.com/company/blog/financial-crime-mitigation-with-mongodb-part-ii-comprehensive-analysis</guid>
    </item><item>
      <title>Financial Crime Mitigation with MongoDB / Part I: Dynamic Customer Profile</title>
      <description><![CDATA[<p>Welcome to our series on Building a Financial Crime Mitigation Platform using MongoDB as the unified data platform able to support the demands from modern digital financial operations. In case you missed it, be sure to check out <a href="https://www.mongodb.com/company/blog/innovation/building-financial-crime-mitigation-platform-with-mongodb-series-overview">the Series overview</a>.</p><p>We’ll kick off our journey in the stage where every customer experience begins: <strong>Onboarding a new customer</strong>, or as it is known in the risk management world, a new “entity” (to unify the concepts of individuals and corporations). Let’s explore the steps involved in the process!</p><h2>Step 1: Capturing prospective customer data</h2><p>In the pursuit of converting a new prospect into a customer, financial institutions start by capturing required data: from basic (demographical) data, through legal identification and tax information, to capturing any relevant data related to the financial life of the prospective customer (credit bureau/FICO scores, assets, and potential collaterals). </p><p>As soon as these data points are captured, you need to build a dynamic profile that will be continuously updated in an “event-driven” way. Building a dynamic profile aims to accomplish two goals: complying with Know-Your-Customer (KYC) regulations, while at the same time segmenting the customer for commercial purposes (i.e., finding the best offering).</p><p>Technically speaking, this represents a major challenge: to have a dynamic profile, we need to aggregate data coming from different sources and schemas. This is where MongoDB’s flexible data model shines.</p><p><strong>Figure 1.</strong> From static to perpetual monitoring.</p><p>MongoDB’s data model is able to aggregate all incoming data seamlessly. It also provides data platform services natively integrated and exposed in a unified API that can be consumed by customer-facing applications, or by support and operational systems.</p><p><strong>Figure 2. </strong>Converged data store for KYC.</p><h2>Step 2: Candidate basic checks</h2><p>Once prospective customer data has been captured, financial crime mitigation checks start with a deceptively simple question: who is this entity? In compliance check programs, the answer is rarely straightforward. A single real-world person or business can appear across systems with different names, addresses, identifiers, and relationships, sometimes due to benign data quality issues, sometimes as a deliberate attempt to evade detection.</p><p>Thus, a comprehensive comparison is required (beyond just text). Again, MongoDB’s capabilities shine. We can combine text and contextual (semantic) data to get better results; this is called hybrid search using the MQL <em>$rankFusion</em> operator.</p><p><strong>Figure 3. </strong>Example of parallel search results showing MongoDB’s advanced search capabilities.</p><p>(Image taken from our <a href="https://github.com/mongodb-industry-solutions/fsi-aml-fraud-detection">demo prototype</a>. Disclosure: The look and feel is from a custom UI developed for demo purposes. It is not part of MongoDB’s offering.)</p><p>The greatest benefit of using MongoDB is having all these advanced search capabilities integrated and available within the same MongoDB cluster, without the need to move the data elsewhere or having to use third-party external search engines.</p><h2>Step 3: Compliance verification</h2><p>After identifying similar profiles, we must now run compliance checks. The main goal is to analyze the entity’s relationships, and for this we need to scan through all potential links with existing bank’s customers and high-amount transactions. Technically speaking, we need to a network graph of all possible relationships:</p><p><strong>Figure 4. </strong>Example of an entity’s network graph.</p><p>(Image taken from our <a href="https://github.com/mongodb-industry-solutions/fsi-aml-fraud-detection">demo prototype</a>. Disclosure: The look and feel is from a custom UI developed for demo purposes. It is not part of MongoDB’s offering.)</p><p>Building this network graph is possible using MQL <em>$graphLookup</em>, an operator available through MongoDB’s aggregation pipeline. The biggest benefit of using MongoDB is that whenever you need to adjust to a higher confidence level, it can rebuild the network instantly as you adjust depth and confidence filters with no pre-computed graph tables or cache invalidation required.  </p><p>Instantaneously, you can unveil the different possible entity relationships, each with the corresponding degree of confidence.</p><p><strong>Figure 5. </strong>Example of the relationship analysis.</p><p></p><p>(Image taken from our <a href="https://github.com/mongodb-industry-solutions/fsi-aml-fraud-detection">demo prototype</a>. Disclosure: The look and feel is from a custom UI developed for demo purposes. It is not part of MongoDB’s offering.)</p><p>This output sets the foundation for a behavioral analysis that will converge into a single view of the customer profile.</p><h2>Final Step: Building a single customer view</h2><p>After gathering these data points, the final step (for now) is to aggregate them into one single view of the customer profile. Here, MongoDB’s data model brings the flexibility required to centralize all the dynamic data that will be captured not once, but in a continuous way.</p><p><strong>Figure 6. </strong>Example of an entity stored in MongoDB’s document structure.</p><p>(Image taken from our <a href="https://github.com/mongodb-industry-solutions/fsi-aml-fraud-detection">demo prototype</a>. Disclosure: The look and feel is from a custom UI developed for demo purposes. It is not part of MongoDB’s offering.)</p><p>MongoDB’s data model excels in a single-view model by being able to combine structured data, along with unstructured data that could potentially coexist with a vectorized representation of the profile, which will help to find similar profiles, and cluster customer profiles more effectively.</p><p><strong>Figure 7. </strong>Example of similarity search results. </p><p>(Image taken from our <a href="https://github.com/mongodb-industry-solutions/fsi-aml-fraud-detection">demo prototype</a>. Disclosure: The look and feel is from a custom UI developed for demo purposes. It is not part of MongoDB’s offering.)</p><h2>Takeaways</h2><p>Onboarding a new entity as a customer (whether individual or corporate prospect) requires a modern data platform that can capture incoming data from different sources, in different formats and schemas. </p><p>The most critical factor for a successful anti-financial crime operation is building a dynamic customer profile. Hence, capturing and processing all possible data points is crucial. We also need to understand the entity’s potential relationships with existing customers or with known transactions. For this, MongoDB aggregation pipeline capabilities—like creating an “on-the-fly” network graph—can unveil unnoticeable behavior.</p><p>Finally, the data and analyses must converge in a single view. Here, MongoDB’s data model’s flexibility is a game-changer. It is able to store—at scale—structured and unstructured data in a single instance. It can also combine that with a vectorized representation of the profile to run similarity searches accurately. </p><p><em>In the next article of this series, we dive deeper into how AI can enhance due diligence processes as part of a comprehensive due diligence using the customer behavioral profile. Read the second part of the series </em><a href="https://www.mongodb.com/company/blog/financial-crime-mitigation-with-mongodb-part-ii-comprehensive-analysis"><em>here</em></a><em>. </em></p>]]></description>
      <pubDate>Mon, 21 Sep 2026 16:51:58 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/building-a-dynamic-customer-profile-using-mongodb</link>
      <guid>https://www.mongodb.com/company/blog/innovation/building-a-dynamic-customer-profile-using-mongodb</guid>
    </item><item>
      <title>How Real-Time Rewards Drive 2.5x Higher Customer Spend</title>
      <description><![CDATA[<p>Imagine finishing a purchase, checking your loyalty balance moments later, and finding it unchanged. No confirmation, no reward, no sense that the transaction even registered. For millions of shoppers across the world&#39;s largest loyalty programs, this isn&#39;t hypothetical; it&#39;s the norm. Some balances take up to 72 hours to post. Others can take upwards of 10 business days after checkout. These delays aren&#39;t edge cases. They represent how most retail loyalty platforms operate today, revealing a widening gap between what customers expect and what legacy architecture can deliver.</p><p>Loyalty programs exist to reward behavior the moment it happens. When the reward gets delayed, the emotional connection between purchase and payoff whittles, and with it, the retailer&#39;s best opportunity to keep the customer engaged. Closing that gap isn&#39;t a matter of better marketing. It&#39;s a data architecture problem, something MongoDB can uniquely solve.</p><h2>Batch processing is a loyalty liability</h2><p>Most retail loyalty systems run on relational databases that credit points through nightly batch jobs. After a customer completes a transaction, it sits in a queue until an overnight process reconciles it against their account. During that window—sometimes hours, sometimes over a week—the customer has no idea whether their purchase was recognized or accounted for. This erodes trust and forfeits the single highest-intent moment in the customer journey: the moments immediately following checkout.</p><p>The market data underscores how costly this delay has become. Nearly 75% of customers say they&#39;re more likely to engage with loyalty programs offering instant rewards, and 82% of Gen Z and Millennial shoppers now expect real-time responsiveness from the brands they support (1). Instant gratification is no longer a differentiator; it&#39;s the baseline expectation. Retailers that fail to meet that actively train customers to disengage. Every point of friction increases the risk of a customer walking away from the program entirely. It should be a slam dunk in the customer relationship cycle, but many times it becomes the moment you lose that customer.</p><p>The business case is equally compelling. Customers who redeem loyalty rewards spend 2.5 times more than non-members, and instant credit has been shown to increase basket size by as much as 36% (2). Starbucks&#39; Rewards program, which contributes nearly 60% of total revenue, is built around real-time visibility into balances and progress. The lesson? Real-time loyalty isn&#39;t a nice-to-have. It&#39;s a proven revenue driver.</p><p>The root of the problem lies in how relational systems get built. Crediting points instantly requires writing across multiple tables, transactions, customer profiles, balances, and tier status, all in a single atomic operation. On a normalized relational schema, this kind of cross-system write is expensive and difficult to scale, which is exactly why retailers fall back on nightly batch processing. Layering microservices on top doesn&#39;t solve this either; it simply distributes the same fragmented data across more systems, adding latency instead of removing it.</p><h2>A data foundation built for the instant reward</h2><p>MongoDB&#39;s flexible document model addresses this rewards lag challenge at its source. Rather than distributing a customer&#39;s transaction history, loyalty balance, tier status, and multiplier eligibility across separate relational tables, MongoDB stores the complete loyalty profile within a single, unified document. When a purchase completes, one atomic write updates that entire profile simultaneously. No joins to resolve. No waiting for batch windows. The balance simply updates as soon as the transaction closes.</p><p><strong>Figure 1.</strong> Real-time loyalty engine: from purchase to instant rewards.</p><p>This same model extends naturally to the rest of the retailer&#39;s operational data. Instead of maintaining separate databases for transactions, customer profiles, loyalty balances, and product catalogs, all of it can live within a single <a href="https://www.mongodb.com/products/platform">MongoDB Atlas</a> cluster without any synchronization delays. This is the operational data layer in practice: One platform supports both the sub-millisecond queries required for real-time crediting and the personalized, post-checkout recommendations that keep customers engaged post-sale.</p><p>Real-time behavior is only half of the equation. Retailers also need the ability to change promotional rules on the fly, which is where <a href="https://www.mongodb.com/docs/atlas/atlas-ui/triggers/database-triggers/">MongoDB Triggers</a> and <a href="https://www.mongodb.com/docs/manual/changestreams/?language-no-dependencies=shell">MongoDB Change Streams</a> become essential. Triggers fire the instant a transaction is written, applying multiplier logic—1x, 2x, or more—without any separate batch recalculation. This means shifting a promotion from a standard rate to a double-point weekend becomes a single rule update rather than a redeployment. </p><p>Change Streams then push the updated balance directly to the customer&#39;s app in real time, eliminating the need for constant polling. Aggregation pipelines round out the architecture, computing multiplier eligibility and fraud checks, such as confirming a customer hasn&#39;t already claimed a bonus in the same session, without ever leaving the database layer.</p><p>Where a relational approach would normally require a separate ETL layer, a dedicated recommendation engine, an external event broker, and a standalone search index, MongoDB consolidates all of these capabilities into one platform. This is the difference between a loyalty program that reacts overnight and one that reacts in the moment. Why would you choose the former?</p><p><strong>Figure 2.</strong> Atlas unifies customer, transaction, and product data with a flexible schema, while Change Streams, Aggregation Pipelines, and Triggers drive real-time updates to balances and tiers.</p><h2>One platform means great benefits for retailers</h2><p>For retailers, the shift to real-time crediting turns a known point of friction into a durable competitive advantage. Capturing the post-purchase moment matters because it&#39;s the highest-intent window in the customer journey, and real-time rewards convert that moment before it closes.</p><p>Real-time architecture also gives retailers a level of promotional agility that batch systems can&#39;t match. Multiplier events that once required engineering support, testing windows, and coordinated releases can now be adjusted live. It’s a single rule change in MongoDB Triggers with no redeployment or batch recalculation. Marketing and merchandising teams can respond to real-time demand signals, a slow Tuesday afternoon, an inventory surplus, or a competitor promotion by quickly launching or adjusting a points event. This frees up IT teams from being a bottleneck for every promotional change.</p><p>Retailers also benefit from consolidation. Replacing fragmented loyalty, transaction, and catalog databases with a single Atlas cluster reduces infrastructure overhead, simplifies data governance, and lowers the total cost of maintaining the loyalty platform. Fewer systems means fewer integration points and fewer points of failure. This ultimately creates a faster path to launching new loyalty mechanics, tiered rewards, cross-brand redemption, or partner integrations, as the program matures. Finally, eliminating delayed-crediting confusion directly lowers customer support volume, since accurate, real-time balances remove one of the most common sources of loyalty-related service inquiries.</p><h2>What customers have been waiting for</h2><p>For customers, the benefit is immediate, visible, and emotionally resonant. Points appear in their balance within milliseconds of a purchase, visible before they&#39;ve even left the app or put away their card. There&#39;s no ambiguous waiting period, no wondering whether the transaction was registered, and no need to contact support to confirm a reward was earned. The moment of purchase and the moment of reward happen together, reinforcing that the loyalty program is responsive and trustworthy rather than an afterthought bolted onto checkout.</p><p>That immediacy also changes how customers use their rewards. Rather than earning points that sit dormant for days, customers can act on them immediately by: </p><ul><li>Applying points toward a new purchase directly within their digital receipt.</li><li>Browsing AI-powered recommendations priced in both cash and points equivalents.</li><li>Completing a hybrid payment if their balance doesn&#39;t cover the full amount. </li></ul><p>This all turns the loyalty program into an active part of the shopping experience rather than a static rewards ledger.</p><p>Transparency compounds the effect. Real-time banners communicate active multiplier promotions the moment they go live so customers know what they&#39;re earning before they buy, not after. Visible tier progression—moving from silver to gold to platinum—gives customers an ongoing sense of momentum tied directly to their purchase history. Together, these elements replace the passive, often confusing experience of legacy loyalty programs with one more modern that feels responsive, transparent, and genuinely rewarding in the moment it matters most.</p><h2>Ready to make loyalty instant?</h2><p>Real-time loyalty is fast becoming the baseline expectation for how any modern loyalty program should function. Retailers still running on nightly batch cycles are training their most engaged customers to expect less and eventually to disengage. Those who move first to modernize will set the standard others are measured against, capturing the post-purchase moment before competitors realize what they’re losing.</p><p>MongoDB Atlas gives IT leaders the architectural foundation to make that shift without rebuilding their entire technology stack. By unifying transactions, customer profiles, and loyalty balances into a single, atomically updated document—and using Triggers and Change Streams to drive instant crediting and live promotional agility—retailers can eliminate the delay that has quietly undermined loyalty programs for years. The result: A program that rewards customers the instant they earn it, and a retailer positioned to compete on an increasingly non-negotiable experience. </p><h3>References</h3><ol><li><p>Real-Time Rewards: Leveraging AI for Instant Gratification in Loyalty Programs <a href="https://www.novus-loyalty.com/blog/real-time-rewards-leveraging-ai-for-instant-gratification-in-loyalty-programs/">https://www.novus-loyalty.com/blog/real-time-rewards-leveraging-ai-for-instant-gratification-in-loyalty-programs/</a></p></li><li><p>68 statistics about customer loyalty programs — and what you can learn from them in 2026
<a href="https://loyaltylion.com/blog/35-loyalty-stats-and-benchmarks-for-2022-and-beyond">https://loyaltylion.com/blog/35-loyalty-stats-and-benchmarks-for-2022-and-beyond</a></p></li></ol>]]></description>
      <pubDate>Wed, 16 Sep 2026 14:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/how-real-time-rewards-drive-2-5x-higher-customer-spend</link>
      <guid>https://www.mongodb.com/company/blog/innovation/how-real-time-rewards-drive-2-5x-higher-customer-spend</guid>
    </item><item>
      <title>From Curiosity to Impact: Inside the MongoDB Intern Experience</title>
      <description><![CDATA[<p>What does it look like to intern at MongoDB? The answer depends on the team, the project, and the people you meet along the way.</p><p>For Aashcharya Gorakh, the summer meant building and testing AI agents to help automate platform support. For Maria Jose Igartua, it meant creating an end-to-end solution for the energy industry and creating a demo. For Tyler Arcinaga, it meant working on a complex storage challenge while learning how to make design decisions, respond to feedback, and take ownership of the work. For Cristina Sánchez Sánchez, it meant simplifying local development while refining her professional skills.</p><p>Across different teams and experiences, one theme came through clearly: an internship is not just about completing an assignment. It’s an opportunity to learn from others, contribute to meaningful work, and become more confident in the way you approach problems.</p><h2>Mentorship and growth</h2><p>The best learning happens when someone takes the time to explain not only what needs to be done, but why it matters. At MongoDB, every intern is paired with a team mentor who serves as their primary support. Beyond team mentorship, interns can join the Intern Bridge Building Program to be paired with an Inclusion Guide from an employee resource or affinity group, and connect with their Early Talent Program Advisor in ongoing check-ins. </p><p>Through regular 1:1s, big-picture discussions, and informal coffee chats, this multi-layered support network helps make the transition from university to a corporate environment feel natural and empowering.</p><p>“They helped me understand not just what needed to be done, but why it mattered and how to think about creating something valuable for the users,” said Gurgaon-based software engineering intern Aashcharya about his team.</p><p>Cristina, a Dublin-based software engineering intern, saw how each form of mentorship played a distinct role in her growth: “Together with my manager, he&#39;s helped me identify areas where I can grow, so I can build more independence and sharpen my skills over time. On top of that, I have an Inclusion Guide from a completely different part of the business who helps me stay focused on my well-being and is someone I can talk to about anything. Finally, my Early Talent Program Advisor checks in with me regularly to make sure I feel comfortable on my team and have the support I need to keep growing at MongoDB.”</p><p>For Tyler, a software engineering intern based in New York City, growth came through a difficult code review. When feedback revealed downstream issues in a design he felt confident about, he had to rethink part of his approach. His mentor, Gayathri Padmanabhan, offered a simple perspective that stayed with him: “It’s just code at the end of the day, we can always change it.”  </p><p>“That one line reframed everything for me; a true engineer isn&#39;t someone who gets it right the first time, it&#39;s someone who can take feedback, refactor, and improve an idea. Growth this summer meant learning to see revision as the job itself, not a failure of it, and iterating toward the best viable product rather than defending my first draft. I carry that with me now in every piece of work I do, treating each version as a starting point rather than a finish line,” Tyler reflected. </p><h2>Community and culture</h2><p>An internship at MongoDB is defined as much by technical growth as by the connective moments that happen outside the project plan. </p><p>Connection starts on day one. For Aashcharya, that sense of belonging began with a welcome lunch on his first morning. An intern outing filled with bowling and games soon followed, giving interns and their teams space to bond beyond daily tasks. In Austin, industry solutions intern Maria experienced that same collaborative spirit during an evening of pizza and games at Cidercade. &quot;It was very meaningful to me because other internships I&#39;ve had usually prioritized individual work, and I never got to develop strong connections with other teammates. From the very first moment at MongoDB, it was all about team collaboration instead,&quot; Maria shared.</p><p>Shared experiences naturally turn peers into real friends. For Tyler, the highlight of the summer was a bagel-making class. While shaping dough was fun, the real value was seeing how closely the group connected. &quot;It doesn’t feel cliquey at all,&quot; Tyler reflected. &quot;I can sit down with pretty much anyone and have a great conversation.&quot;</p><p>These events also create unique bridges to leadership. During National Intern Day in Dublin, Cristina gathered with her peers and teammates for games and food. The celebration took an exciting turn when MongoDB’s Chief Marketing Officer, May Petry, joined for an impromptu ‘Ask Me Anything’ session. &quot;Her genuine interest in our experiences made me feel that interns here are truly valued and heard,&quot; Cristina recalled.</p><h2>Impact and project work</h2><p>Interns contribute in different ways, but each project begins with a real problem to solve.</p><p><em><strong>Making platform support more efficient </strong></em>- Aashcharya, Enterprise Advanced
Aashcharya worked on automating the platform support process for the Enterprise Advanced agent. The project involved building and testing AI agents, with each test helping make the system more efficient.</p><p>“It gave [me a] chance to work on real engineering problems, learn how large-scale systems operate, and contribute to something that could make workflows more efficient.”</p><p><em><strong>Simplifying local development with Python </strong></em>- Cristina, Atlas API Experience</p><p>Cristina built an open-source Python binding for Atlas Local that makes it frictionless for AI developers to use Atlas Local. This lets people copy our AI Python notebook examples, including auto-embedding via Voyage, LangChain, RAG, and vector search, straight from the website and run them without needing any special setup on their machine.</p><p>“I’m excited that my work can simplify development for people experimenting with AI applications, Vector Search, or auto-embeddings, helping them skip the setup and get straight to building.”</p><p><em><strong>Building an energy industry solution from the ground up</strong></em> - Maria, Industry Solutions</p><p>Maria worked on an end-to-end solution for the energy industry, an area that was new to her. “I got to build this solution from scratch all the way to the demo and content assets that will be shared around the MongoDB social channels.”</p><p>The project brought together research, problem-solving, technical work, communication, and collaboration. “This experience has helped me better understand how MongoDB creates impact beyond the technology itself, and centers around the customer journey, which I found very valuable”</p><p><em><strong>Helping move toward a more elastic storage layer </strong></em>- Tyler, Storage Layer Services</p><p>Tyler worked on a way to change which page servers a log span is mapped to while continuing to serve reads, avoiding data loss, moving data efficiently, and recovering from crashes.</p><p>In simpler terms, the project supported a larger goal: helping the storage layer become more flexible as systems change. Tyler also had the opportunity to discuss tradeoffs with senior engineers, own critical design decisions, and earn buy-in for his approach before implementation began.</p><p>“That’s when ‘<a href="https://www.mongodb.com/company/leadership-principles"><em>leaders act like owners</em></a>’ stopped being just a noted leadership principle and started being something I actually felt in my day-to-day work.”</p><h2>Reflections and advice</h2><p>Looking back on their summer, MongoDB interns gained far more than technical knowledge; they learned how to collaborate in a global corporate workforce and take full ownership of impactful work.</p><p>For Aashcharya, the summer shifted his perspective on what engineering really means: “I learned how important it is to truly understand requirements, communicate clearly, and make sure everyone is aligned on what success looks like.”</p><p>Maria learned the importance of sustainable ways of working. Her mentor encouraged her to work within reasonable hours and communicate when priorities felt too heavy.</p><p>“I learned that in order to be a good team player, you have to care about the balance you put in. Having enough rest, doing activities you enjoy, and caring about your health will ultimately lead you to better results,” explained the Industry Solutions intern.</p><p>Tyler’s biggest takeaway was ownership. He was trusted to participate in design decisions, discuss tradeoffs with experienced engineers, and help shape the direction of his project.</p><p>Cristina details MongoDB as a great place to transition from university into a professional career. From the interview process to throughout the internship, she was provided an environment to receive and grow from feedback, while internalizing that you don’t need to know everything. Cristina highlights communication skills in her internship: “What matters more is communicating openly, so you can get unstuck quickly and keep learning along the way.”</p><p>Their experiences offer a useful message for future interns: bring curiosity, ask questions, stay open to feedback, and look for opportunities to contribute beyond the task immediately in front of you.</p>]]></description>
      <pubDate>Tue, 15 Sep 2026 14:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/culture/from-curiosity-impact-inside-intern-experience</link>
      <guid>https://www.mongodb.com/company/blog/culture/from-curiosity-impact-inside-intern-experience</guid>
    </item><item>
      <title>Stop Rubber-Stamping AI: A Contestable AI Framework for Regulated Industries</title>
      <description><![CDATA[<p>Most AI deployed in regulated industries is neither explainable nor contestable. In those systems, AI may return a recommendation or a confidence score with no way for you to contest the results. This creates a barrier to deploying AI in regulated industries such as healthcare and manufacturing because the people responsible for outcomes have no meaningful way to participate in the decision.</p><p>For example, in a family medical clinic, a general practitioner (GP) may get insights from a black box multi-agent system about a patient care plan. If they do not agree with that intel, there is no way to contest or understand why the system suggested what it did. Some systems provide an audit trail, but that comes in the form of a verbose log file, readable only by developers. In many cases, the audit trail shows only the output, not the reasoning that produced it.</p><p>This post makes the case for contestable AI as an implementable architectural pattern, not a governance aspiration, and walks through what that looks like in two regulated-industry scenarios: a clinical care plan and a manufacturing sensor classification. The pattern is domain-agnostic, but making it work depends on the data layer underneath it. MongoDB&#39;s document model stores the AI&#39;s arguments, the human&#39;s overrides, and the resulting decision together, so the full reasoning and intervention history is retrievable in a single query rather than reconstructed after the fact.</p><h2>Contestable AI in healthcare</h2><p>Here is how this human-agent debate works in practice, using a patient care scenario:</p><p><strong>Figure 1.</strong> Patient care contestable AI workflow: patient analyzer agent, specialist debate, GP review, care plan generation.</p><p>A patient analyzer agent scores clinical complexity and retrieves similar historical cases via vector search. A team of specialist agents representing endocrinology, geriatrics, sleep medicine, and cardiology then argues for and against each care option using structured, scored arguments. The GP reviews the full argument set, challenges anything that conflicts with their clinical judgment, and the system re-scores in real time. The final care plan carries both the AI analysis and the clinician&#39;s interventions, and the full decision lineage is retrievable in a single query from MongoDB.</p><h2>Contestable AI in manufacturing</h2><p>The same pattern applies in manufacturing. On a medical device assembly line, an AI vision system flags a weld as out-of-spec. A quality assurance engineer reviews the argument, overrides it with context the model lacked—for instance, a known fixture offset that shifts that measurement by 0.3mm—and the override is stored alongside the original flag, ready for the next audit. 
The same framework holds up in the field, too. For example, on an IoT platform managing HVAC units, where one of the hardest problems is classifying sensors on a newly onboarded unit.</p><p>Modern industrial equipment uses proprietary internal sensor labels that are meaningless without the original documentation. In the case of HVAC systems, when a new unit is onboarded, every sensor point needs to be correctly classified before it can feed into building management or analytics systems. If the setup is done incorrectly, downstream systems end up reading the wrong data. Manual classification requires more time and ontology expertise, neither of which is not scalable.</p><p>To solve this, set up a contestable AI workflow. A site reader agent first ingests the equipment point list and runs a vector search against previously verified sensor mappings to ground the debate in documentation and precedent. Two specialist agents then analyze the sensor label and the equipment manual, debate multiple possible classifications against a standard equipment ontology (for example, <a href="https://brickschema.org/">Brick Schema</a>), and surface a recommendation. A domain expert reviews every argument, overrides the ones they disagree with, and the system re-scores in real time, producing a verified sensor record that is stored in MongoDB.</p><p><strong>Figure 2. </strong>HVAC sensor classification contestable AI workflow: site reader agent, multi-agent argumentation, human contestation, equipment record generation.</p><p>This approach scales naturally. As more sensors are classified and verified, their classification gets stored in the database, enriching the vector search library that Phase 1 in Figure 2 draws from. Each new HVAC unit onboarded makes the next one faster and more accurate because the system is reasoning from a growing base of verified precedent rather than starting from scratch each time.</p><p>The structure is identical to the clinical scenario described above. Here we have a different domain and a different number of agents (the healthcare use case used six), but the same overall workflow. A physician contesting a care recommendation and an engineer contesting a sensor classification are structurally the same act in practice. A qualified human provides context that the LLM/agents did not have access to, and that intervention is stored as part of the final decision record. This is what makes contestable AI a pattern rather than a product. The framework does not change, no matter the domain. </p><h2>Why MongoDB for contestable AI </h2><p>Contestable AI only works if the data underneath it holds together, which is MongoDB’s role. IoT telemetry from a factory floor and structured argument scores are different shapes of data, and the document model stores both without forcing either into a rigid schema. Time series collections handle the high-speed sensor ingestion directly, with automatic bucketing and window functions built in rather than bolted on. <a href="https://www.mongodb.com/products/platform/atlas-vector-search">Vector search</a> sits inside the same database, so unstructured data—such as patient history summaries and equipment manuals—gets embedded and retrieved for <a href="https://www.mongodb.com/docs/vector-search/tutorials/rag/?embedding=auto&amp;language-no-interface=python&amp;embedding-model=voyage&amp;llm=openai">RAG</a> without standing up a separate vector store. The argumentation structure itself—arguments, support, and attack relations, and scores—maps naturally onto nested documents. Then every human edit gets embedded as a subdocument that becomes part of agent&#39;s memory for future use. The final output, the arguments behind it, the human edits, and the confidence scores all live together in one rich document, so a single query reconstructs the full decision lineage instead of joining data across five different systems.</p><p>Regulatory bodies are moving toward requiring this kind of documented human oversight by design. Building it into the data and reasoning layer now means you meet that requirement with evidence rather than assertions. The framework does not change with the domain, but the data layer decides whether it holds together. </p>]]></description>
      <pubDate>Mon, 14 Sep 2026 14:00:01 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/stop-rubber-stamping-ai-contestable-framework-regulated-industries</link>
      <guid>https://www.mongodb.com/company/blog/innovation/stop-rubber-stamping-ai-contestable-framework-regulated-industries</guid>
    </item><item>
      <title>Analyze MongoDB Atlas Data in OpenAI ChatGPT Work</title>
      <description><![CDATA[<p><a href="https://www.mongodb.com/products/platform/atlas-database">MongoDB Atlas</a> is now a connected data source in OpenAI&#39;s <a href="https://openai.com/business/plugins/data/">Data Plugin</a>, powered by the <a href="https://www.mongodb.com/products/tools/mcp-server">MongoDB Atlas Managed MCP Server</a>. Analysts and business teams can point the Data agent in ChatGPT Work at the data in their Atlas clusters and ask what changed in the moment, why it changed, and what to look at next, then turn the answer into a report or real-time dashboard without leaving the conversation.</p><p>MongoDB Atlas is the data platform applications run on, and where orders, sessions, and events land in real time. Connecting Atlas to the Data agent means an analyst can question the real-time system of record instead of waiting on last night&#39;s ETL job to finish. When a metric moves at 2 p.m., the answer doesn&#39;t have to wait for tomorrow&#39;s refresh.</p><h2>Turning questions into actions</h2><p>Here&#39;s what this looks like in practice. With the Data agent for ChatGPT Work, you can:</p><ul><li><p>Monitor how the checkout update you shipped at 2 p.m. is impacting conversion minutes and hours later. You can also see where users are dropping off, and decide whether to roll the update back.</p></li><li><p>Find orders stuck in payment pending over the last hour, see what they have in common, and hand the list of affected customers to support. </p></li><li><p>Mid-sale, compare this hour to the same hour of the last sale, spot the region that&#39;s lagging, and move promotion and inventory before the sale ends.</p></li><li><p>See what a customer did in the app in the ten minutes before they call support.</p></li><li><p>Turn these insights into live data charts and dashboards for teams to view in real time.</p></li></ul><p>MongoDB Atlas supports these use cases as a fully managed, real-time operational data layer that runs across cloud providers and operates as the live system of record for their mission-critical applications. Consequently, the data most worth interrogating tends to live in Atlas first. Teams that already trust MongoDB Atlas to run applications in production can now question their data directly.</p><p>Meanwhile, end-user access respects the controls already on the cluster. Access is granted through an OAuth sign-in to MongoDB Atlas with no connection strings or credentials to self-manage. Organization owners choose whether to enable AI client access (it&#39;s off by default), can restrict it to read-only, and every query runs with the permissions of the user who connected.</p>]]></description>
      <pubDate>Thu, 10 Sep 2026 15:43:46 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/product-release-announcements/analyze-atlas-data-openai-chatgpt-work</link>
      <guid>https://www.mongodb.com/company/blog/product-release-announcements/analyze-atlas-data-openai-chatgpt-work</guid>
    </item><item>
      <title>Go from 0 to 1 to Enterprise-Ready with MongoDB Atlas and LLMs</title>
      <description><![CDATA[<p></p><p></p><p>Creating compelling, truly differentiated experiences for your customers from generative AI-enriched applications means grounding artificial intelligence in truth. That truth comes from your data, more specifically, your most up-to-date operational data. Whether you’re providing hyper-personalized experiences with advanced semantic search or producing user-prompted content and conversations, MongoDB Atlas unifies operational, analytical and vector search data services to streamline embedding the power of LLMs and transformer models into your apps.</p><p>Everyday, developers are building the next groundbreaking, transformative generative AI powered application. Commercial and open source LLMs are advancing at breakneck speed. The frameworks and tools to build around them are plentiful and democratize innovation. And yet taking these applications from prototype to enterprise-ready is the chasm development teams must cross. First, these large models can provide incorrect or uninformed answers, because the data they have access to is dated. There are two options to solve uninformed answers -  fine-tuning a large model or providing it with long-term memory. However, doing so begets a second barrier - deploying an application around an informed LLM with the right security controls in place, and at the scale and performance users expect.</p><p>Developers need a data platform that has the data model flexibility to adapt to the constantly changing unstructured and structured data that informs large models without the hindrance of rigid schemas. While fine-tuning a model is an option, it’s a cost-prohibitive one in terms of time and computational resources. This means developers need to be able present data as context to large models as part of prompts. They need to give these generative models long-term memory. We discuss a few examples of how to do so with various LLMs and generative AI frameworks below.</p><p></p><h2>Five resources to get started with MongoDB Atlas and Large Language Models</h2><p>MongoDB Atlas makes it seamless to integrate leading generative AI services and systems such as the hyperscalers and open source LLMs and frameworks. By combining document and vector embedding data stores in one place via <a href="https://www.mongodb.com/products/platform/atlas-database">Atlas Database</a> and <a href="https://www.mongodb.com/products/platform/atlas-vector-search">Atlas Vector Search</a> (preview), developers can accelerate building their generative AI-enriched applications that are grounded in the truth of operational data. Below are examples with how to work with popular LLM frameworks and MongoDB:</p><h3>1. Get started with Atlas Vector Search (preview) and OpenAI for semantic search</h3><p>This tutorial walks you through the steps of performing semantic search on a sample movie dataset with MongoDB Atlas. First, you’ll set up an Atlas Trigger to make a call to an OpenAI API whenever a new document is inserted into your cluster, so as to convert it into a vector embedding. Then, you’ll perform a vector search query using Atlas Vector Search. There’s even a special bonus section for leveraging HuggingFace models.</p><h3>2. Build a Gen AI-enriched chat app with your proprietary data using Llamalndex and MongoDB</h3><p>LlamaIndex provides a simple, flexible interface to connect LLMs with external data. This joint blog from LlamaIndex and MongoDB goes into more detail about why and how you might want to build your own chat app. The attached notebook in the blog provides a code walkthrough on how to query any PDF document using English language queries. <a href="https://medium.com/llamaindex-blog/build-a-chatgpt-with-your-private-data-using-llamaindex-and-mongodb-b09850eb154c">Read the blog</a>.</p><h3>3. See the docs for how to use Atlas Vector Search (preview) as a vector store with LangChain</h3><p>As stated in the partnership announcement blog post, LangChain and MongoDB Atlas are a natural fit, and it’s been demonstrated by the organic community enthusiasm which has led to several integrations in LangChain for MongoDB. In addition to now supporting Atlas Vector Search as a Vector Store there is already support to utilize MongoDB as a chat log history. Read the docs: <a href="https://python.langchain.com/v0.2/docs/integrations/vectorstores/mongodb_atlas/">python</a>, <a href="https://js.langchain.com/docs/modules/indexes/vector_stores/integrations/mongodb_atlas">javascript</a>.</p><h3>4. Generate predictions directly in MongoDB Atlas with MindsDB AI Collections</h3><p>MindsDB is an open-source machine learning platform that brings automated machine learning to the database. In this blog you’ll generate predictions directly in Atlas with MindsDB AI Collections, giving you the ability to consume predictions as regular data, query these predictions, and accelerate development speed by simplifying deployment work-flows. <a href="https://www.mongodb.com/company/blog/turning-mongodb-into-predictive-database">Read the blog</a>.</p><h3>5. Integrate HuggingFace transformer models into MongoDB Atlas with Atlas Triggers</h3><p>HuggingFace is an AI community that makes it easy to build, train and deploy machine learning models. Leveraging Atlas Triggers alongside HuggingFace allows you to easily react to changes in operational data that provides long-term memory to your models. Learn how to set up Triggers to automatically predict the sentiment of new documents in your MongoDB database and add them as additional fields to your documents. See the <a href="https://github.com/philschmid/huggingface-mongodb-example">GitHub Repo</a>.</p><h2>From prototype to production with MongoDB for generative AI-enriched apps</h2><p>MongoDB’s modern database provides a modern, optimized developer experience while also being battle tested by thousands of enterprises globally to perform at scale and securely.</p><h2>Whether you are building the next big thing at a startup or enterprise, Atlas enables you to:</h2><ul><li><p>Accelerate building your generative AI-enriched applications that are grounded in the truth of operational data.</p></li><li><p>Simplify your app architecture by leveraging a single platform that allows them to store app and vector data in the same place, react to changes in source data with serverless functions, and search across multiple data modalities for improving relevance and accuracy in responses that their apps generate.</p></li><li><p>Easily evolve your gen AI-enriched apps with the flexibility of the document model while maintaining a simple, elegant developer experience.</p></li><li><p>Seamlessly integrate leading AI services and systems such as the hyperscalers and open source LLMs and frameworks to stay competitive in dynamic markets.</p></li><li><p>Build gen AI-enriched applications on a high performance, highly scalable operational database that&#39;s had a decade of validation over a wide variety of AI use cases.</p></li></ul><p>While these examples are the building blocks for something more innovative, MongoDB can help you go from concept to production to scale. Get started today by <a href="https://www.mongodb.com/cloud/atlas/register">signing up</a> for MongoDB Atlas free tier and integrating with your preferred frameworks and LLMs. If you’re interested in working with us more closely, check out our <a href="https://www.mongodb.com/solutions/startups">MongoDB AI Innovators program</a>, which enables Artificial Intelligence innovation and showcases cutting-edge solutions from startups, customers, and partners.</p>]]></description>
      <pubDate>Thu, 10 Sep 2026 15:01:28 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/product-release-announcements/going-from-zero-to-one-enterprise-ready-mongodb-llms</link>
      <guid>https://www.mongodb.com/company/blog/product-release-announcements/going-from-zero-to-one-enterprise-ready-mongodb-llms</guid>
    </item><item>
      <title>Introducing Atlas Gen2 on AWS and GCP for M30+ Dedicated Clusters</title>
      <description><![CDATA[<p>Today, we’re introducing <a href="https://dochub.mongodb.org/core/atlas-gen2-clusters">Gen2 for Atlas M30+</a> Dedicated Clusters on Amazon Web Services (AWS) and Google Cloud Provider (GCP): a major step forward in performance, cost control, and infrastructure flexibility for teams running production workloads on <a href="https://www.mongodb.com/products/platform/atlas-database">MongoDB Atlas</a>.</p><p>For many teams, improving database performance comes with an expensive compromise: needing more IOPS often means buying more storage, whether you need that storage or not. The result? Overprovisioned clusters, higher cloud bills, and infrastructure that’s sized around platform limitations instead of workload requirements.</p><p>Atlas Gen2 changes that. By combining significant performance improvements with the ability to scale IOPS independently from storage, Gen2 gives teams a more efficient way to run MongoDB on AWS and GCP, without application changes, migrations, or operational disruption.</p><h2>More performance without more infrastructure </h2><p>Atlas Gen2 on AWS and GCP runs on the newer ARM-based processors, delivering significant performance improvements compared to the previous generation used by many Atlas clusters. In an internal pilot evaluating Atlas clusters migrated to Gen2 infrastructure, MongoDB observed a statistically significant 15–20% reduction in CPU utilization, improved memory efficiency, and approximately 45% lower read and write latency.</p><p>For organizations, these gains can translate into faster response times, higher transaction throughput, and the ability to handle peak demand without adding infrastructure. The additional performance headroom helps teams accommodate growing workloads without automatically moving to larger cluster tiers, and in some cases, customers may be able to achieve performance targets on smaller clusters, improving efficiency and lowering the total cost of ownership.</p><p>Simply put: teams get more performance from the infrastructure they are already paying for.</p><h2>End the storage-for-IOPS tradeoff</h2><p>Performance gains are only part of the story. Atlas Gen2 introduces extended standard IOPS, allowing customers to provision IOPS independently from storage capacity.</p><p>This addresses one of the most common and costly inefficiencies in cloud database infrastructure: overprovisioning storage just to get the disk performance a workload requires. Historically, many teams have had to purchase additional storage solely to unlock the disk performance their workloads required—even when that storage sat largely unused. With Gen2, storage and performance can scale independently.</p><p>That means:</p><ul><li><p>Provision storage based on capacity needs, not performance requirements</p></li><li><p>Increase IOPS without overprovisioning storage</p></li><li><p>Gain more precise control over infrastructure costs</p></li></ul><p>For platform teams and DBAs, it’s a simpler way to optimize clusters. For engineering leaders, it’s a clearer path to reducing infrastructure waste.</p><h2>Better price-performance without the migration</h2><p>Gen2 is an important step in strengthening Atlas’s price-performance on AWS and GCP and reflects MongoDB’s ongoing commitment to helping customers get more value from their infrastructure investments. By continuously listening to customer feedback and investing in platform innovation, MongoDB is focused on delivering higher performance, greater efficiency, and lower operating costs without increasing operational complexity.</p><p>Customers can capture these benefits without taking on the cost and risk of migration—there are no application changes required, no vendor switch, and no rearchitecture. Teams keep the same Atlas API, connection strings, and operational model while benefiting from newer infrastructure underneath. Atlas Gen2 is now broadly available across <a href="https://www.mongodb.com/docs/atlas/reference/amazon-aws/#aws-gen2-dedicated-clusters">AWS regions</a> that support the underlying infrastructure, making it easier for customers to take advantage of improved performance and independent IOPS scaling. MongoDB has also expanded Gen2 availability on <a href="https://dochub.mongodb.org/core/atlas-gcp-reference-gen2-clusters">GCP</a>, with support across APAC and Europe and limited availability in select U.S. regions.<strong> </strong></p><h2>Built for long-term growth</h2><p>Gen2 also helps customers move to newer AWS and GCP infrastructure designed to support future growth and avoid the capacity constraints that can emerge on older hardware generations.</p><p>Customers retain access to the Atlas capabilities they rely on today, including Global Clusters, autoscaling, PrivateLink, and VPC peering, while benefiting from the latest generation of infrastructure.</p><p>As Gen2 continues to expand across cloud providers and regions, customers can standardize on the latest Atlas infrastructure while maintaining the operational experience and platform capabilities they rely on today.</p><h2>Availability: A smarter way to scale</h2><p><a href="https://www.mongodb.com/docs/atlas/reference/amazon-aws/#aws-gen2-dedicated-clusters">Atlas Gen2 for M30+ Dedicated Clusters on AWS</a> is available in supported regions across APAC and Europe. For customers creating new clusters, Gen2 is the recommended default infrastructure where available. Existing customers running eligible M30+ clusters on AWS can evaluate upgrade opportunities and determine where Gen2 can deliver better performance and smarter cost optimization.</p><p><a href="https://dochub.mongodb.org/core/atlas-gcp-reference-gen2-clusters">Atlas Gen2 for M30+ Dedicated Clusters on GCP</a> is available in supported regions across APAC and Europe, with limited availability in select U.S. regions, extending Gen2’s performance and infrastructure benefits to more customers globally.</p>]]></description>
      <pubDate>Thu, 10 Sep 2026 13:47:50 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/product-release-announcements/introducing-atlas-gen2-on-aws-m30-dedicated-clusters</link>
      <guid>https://www.mongodb.com/company/blog/product-release-announcements/introducing-atlas-gen2-on-aws-m30-dedicated-clusters</guid>
    </item><item>
      <title>Build a Fraud Review Agent with MongoDB Atlas and Claude Managed Agents</title>
      <description><![CDATA[<p>Claude Managed Agents lets you run Anthropic&#39;s Claude as a fully hosted agent, without standing up your own inference or orchestration infrastructure. Pairing Claude Managed Agents with MongoDB Atlas gives your agents fast, secure access to operational and vector data right where it lives, so you can ship agentic workflows without gluing together separate retrieval and hosting layers.</p><p>This tutorial shows you how to build a human-in-the-loop fraud review agent that runs on Anthropic’s Claude Managed Agents and uses <a href="https://www.mongodb.com/products/platform/atlas-database">MongoDB Atlas</a> as its retrieval engine, graph store, and system of record. The agent reviews flagged payment transactions, pulls precedent and relationship signals out of Atlas, pauses for a human reviewer on the risky cases, and writes an immutable verdict back to the same cluster it read from. </p><p>By the end of the tutorial, you’ll be able to wire a credential-safe MongoDB data path into a managed agent, run four retrieval patterns against a single collection, gate risky decisions behind a durable human pause, and make one cluster the agent&#39;s audit backbone.</p><p>Most agent stacks assemble this out of three or four systems: a vector database for semantic search, a separate engine for keyword matching, a graph store for relationships, and an operational database for the records themselves. Every seam between them adds an integration to maintain and a credential to manage, and adds one more place the agent&#39;s view of the world can drift out of sync. MongoDB Atlas runs all four access patterns (vector, full-text, hybrid, and graph) over the same documents in the same cluster, reached through one pymongo connection. Fraud review exercises all of it at once: a reviewer needs semantic precedent, an exact-match lookup, and network traversal on the same case, and the decision has to land somewhere that an auditor can read later.</p><h2><strong>What each side handles</strong></h2><p>Claude Managed Agents and MongoDB Atlas do different jobs here, and keeping the boundary between them clear is what makes the pattern safe to run.</p><p>Managed Agents runs the agent loop on Anthropic&#39;s infrastructure: the model&#39;s reasoning, the sequence of tool calls, and the native human-in-the-loop pause. Your process controls the data path. When the agent decides it needs data, it calls a <em>custom</em> tool; the session goes idle with <em>stop_reason: requires_action</em>; your code runs the <em>pymongo</em> query host-side and posts the result back; the session resumes. The MongoDB connection string stays in your environment and your handler functions. It never enters the agent context or the sandbox.</p><p>MongoDB here is your operational data store, retrieval engine, and system of record—the data your application controls. That is a distinct role from the memory features that Managed Agents manages natively on the platform. The two are complementary: Managed Agents remembers how it has interacted; MongoDB Atlas holds the transactions, precedents, decisions, and audit trail.</p><p>The credential boundary described above is the property of the recommended integration path (the notebook calls it Path A, the host-side custom tool). Two other connection paths exist, and the notebook compares them, but the host-side custom tool is the one that keeps the secret on your side, which is why it is the default for anything touching production data.</p><p><strong>Figure 1. </strong>The division of labor between Claude Managed Agents and MongoDB Atlas. </p><h2>Connect to MongoDB without handing over the credentials</h2><p>The wiring has two halves: custom tools declared on the agent, and a host-side loop that services their calls. A tool is a JSON schema that the agent can call, a Python function that runs the query host-side, and one line registering the two. </p><p>Here is <em>get_transaction</em> end-to-end; the other five tools follow the same shape.</p><p>The schema is all the agent sees. The function runs in your own process, so the <em>coll.find_one</em> and the connection behind it never reach the sandbox.</p><p>The second half is the loop that dispatches each call. Every <em>agent.custom_tool_use</em> event names a tool and its input, and the session then idles with <em>stop_reason: requires_action</em> until you answer. You look the tool up in <em>HANDLERS</em>, run it host-side, and post the result back:</p><p><em>MONGO_URI</em> is read once, on your side, and never travels to Anthropic. A free M0 Atlas cluster is enough to run everything in this tutorial.</p><h2>One collection, four retrieval patterns</h2><p>The agent&#39;s evidence comes from four retrieval patterns, each a plain aggregation pipeline against the same <em>transactions</em><em> </em>collection. In fraud review, they answer different questions:</p><p><strong>Figure 2. </strong>One collection, four retrieval patterns.</p><p>Hybrid is the production default. <a href="https://www.mongodb.com/docs/manual/reference/operator/aggregation/rankFusion/"><em>$rankFusion</em></a> (available in MongoDB 8.0 and later, including free M0 clusters) runs a vector branch and a lexical branch and fuses them by reciprocal rank in a single server-side aggregation:</p><p>Both branches read the same documents and the same embedding field. There is no vector database to sync against a separate search index, because they are one index surface on one collection. To weight semantic over lexical, add a combination.weights clause; the default treats both branches evenly. The notebook ships precomputed vectors and passes qvec in, so it runs without an embedding-provider key. In production, you can use Atlas Automated Embedding instead: select a Voyage AI model when you configure the vector index, and Atlas generates the embeddings and keeps them in sync as documents change. No embedding pipeline to run alongside the cluster.</p><p>Graph traversal is the pattern most agent tutorials skip, and it is the one a financial-crime reviewer will look for. <a href="https://www.mongodb.com/docs/manual/reference/operator/aggregation/graphLookup/"><em>$graphLookup</em></a> walks the sender-to-recipient chain out of a seed account, following each recipient into the next transaction&#39;s sender:</p><p>A helper reads the resulting chain for the signals that matter: money that flows in a circle back to the seed account, layering (many small transfers), and the size of the network. Relationship signals are orthogonal to content similarity: a mule chain can be five plausible-looking individual payments that each pass every similarity check on their own, which is why <a href="https://www.mongodb.com/docs/atlas/atlas-vector-search/vector-search-stage/"><em>$vectorSearch</em></a> and <a href="https://www.mongodb.com/docs/atlas/atlas-search/query/text/"><em>$search</em></a> find similar transactions while $graphLookup finds connected ones.</p><h2>The agent: Verify, retrieve, decide, escalate</h2><p>Each of those pipelines becomes a custom tool. The agent also gets a hard gate at the front of the flow: before any behavioral analysis, it verifies a cryptographically signed authorization mandate (the open <a href="https://github.com/google-agentic-commerce/AP2">AP2</a> protocol) and rejects immediately on an invalid signature, an unmet constraint, or a double-spend. The system prompt fixes the order and the escalation rules:</p><p>The escalation rules encode real financial crime triggers. A deposit of $4,950 sits just under the $5,000 currency-transaction-report threshold—the classic structuring signature. A $50,000 wire may be legitimate and still requires a human under policy. A ring signal from $graphLookup is not something to auto-approve. In each of those cases, the agent calls escalate instead of deciding.</p><p><strong>Figure 3. </strong>The fraud-review flow.</p><p>That escalation runs through Managed Agents&#39; native human pause. <em>escalate</em> is a custom tool like the others, but its handler routes to a human reviewer rather than to <em>pymongo</em>. The session idles at <em>requires_action</em> and holds—the state lives on Anthropic&#39;s side, so it survives whatever your process is doing. This is a durable gate, not a fragile <em>input()</em> call blocking a script. When the human responds, the agent records the final decision with <em>escalated=true</em> and both verdicts preserved: what it recommended, and what the human decided.</p><p>With the tools and the system prompt in place, create the agent, open a session, and hand the event stream to the gate loop:</p><p>In a representative run over five flagged transactions, the agent clears the two clear-cut cases on its own and escalates the structuring, high-value, and ring cases to a human, servicing on the order of two dozen tool calls along the way. Exact counts vary by model and run, though the sequence of steps is the same each time.</p><h2>One cluster as the system of record and audit trail</h2><p>Everything the agent did is durable in the same cluster it retrieved from. Four collections carry the write side:</p><ul><li><p><em>transactions</em>: the operational record; each case advances from <em>pending</em> to <em>approved</em> or <em>rejected</em>.</p></li><li><p><em>transaction_decisions</em>: append-only verdicts with reasoning, confidence, and risk factors.</p></li><li><p><em>audit_events</em>: an append-only trail; escalations record both the agent&#39;s recommendation and the human&#39;s call.</p></li><li><p><em>mandate_receipts</em>: AP2 receipts that power double-spend detection on later runs.</p></li></ul><p>There is no separate audit system, event bus, or second database to reconcile against. <em>record_decision</em> makes those writes in a single host-side handler: it inserts the immutable verdict, appends the matching audit event, and advances the case from pending to a decided status.</p><p>(<em>build_decision_doc</em> and <em>build_audit_event</em> shape the persisted documents; both live in the notebook&#39;s helper module.)</p><p>Reading the same case back shows the operational status, the decision record, and the audit trail in one place:</p><p>For a fraud-review workflow, the audit trail is the same set of writes the agent already makes, sitting in the same cluster the examiner queries. Retrieving what was decided, by whom, and against which precedent is an ordinary query.</p><h2>Run it yourself</h2><p>The full runnable notebook is in the <a href="https://platform.claude.com/cookbook/managed-agents-cma-with-mongodb-atlas">Claude Cookbooks</a>: <a href="https://github.com/mongodb-partners/claude-cookbooks">managed_agents/Claude Managed Agents_with_mongodb_atlas.ipynb</a>. It ships the seed data with precomputed embeddings, the AP2 signing helpers, the index setup, and all six tools. A free M0 cluster and an Anthropic API key run everything, because the seed ships precomputed vectors; no embedding-provider key is needed to try it. The default model is claude-haiku-4-5, overridable through <em>COOKBOOK_MODEL</em>.</p><p>If you are new to the human-in-the-loop custom-tool gate, start with <a href="https://github.com/mongodb-partners/claude-cookbooks">Managed Agents_gate_human_in_the_loop.ipynb</a>—it teaches the pause pattern this notebook builds on. When you are ready to move past a single-process streaming loop, <a href="https://github.com/mongodb-partners/claude-cookbooks">Managed Agents_operate_in_production.ipynb</a> covers webhooks for session status, MCP toolsets, and vault integration.</p><p>The same shape carries to other domains. Swap the collection and the tool set for your own, keep the credential on your side, and the retrieval, the human gate, and the audit trail come with it.</p>]]></description>
      <pubDate>Wed, 09 Sep 2026 14:00:03 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/technical/build-fraud-review-agent-atlas-claude-managed-agents</link>
      <guid>https://www.mongodb.com/company/blog/technical/build-fraud-review-agent-atlas-claude-managed-agents</guid>
    </item><item>
      <title>Benchmark Shows MongoDB Atlas Manages Thousands of Payments Per Second with Zero Data Loss</title>
      <description><![CDATA[<p>As instant payment rails replace legacy batch systems worldwide, banks need public proof that modern data architectures can scale without compromising resilience. We recently put the Icon Payments Framework (IPF), trusted by Tier 1 banks including Citi, NatWest, and BNP Paribas, through a series of extreme load and failure tests on <a href="https://www.mongodb.com/products/platform/atlas-database">MongoDB Atlas</a>.</p><p>The results speak for themselves: 6,000 end-to-end payments per second, sub-second payment transaction latency, 430,000 database operations per second, and zero data loss during node failures. Below is a preview of the benchmark highlights, with full architectural breakdowns and testing methodologies available in our upcoming report.</p><h2>Pushing the limits of scale and latency</h2><p>To understand how the platform handles these extreme demands, we evaluated key performance metrics across a rigorous ladder test. At peak load, MongoDB Atlas comfortably supported 6,000 end-to-end payment transactions per second. This required the system to handle approximately 430,000 simultaneous database operations per second: roughly 236,000 operations on the IPF Event Journal and 196,000 operations on the Operational Data Store.</p><p><strong>Figure 1.</strong> Deployment setup.</p><p>Despite this massive throughput, persistence latency remained below 30 milliseconds. This efficiency supported a mean end-to-end payment latency of just 0.51 seconds. Upgrading the database version played a significant role here; moving from MongoDB Atlas 8.0 to 8.3 reduced persistence latency by approximately 50%. For example, at 4,000 payment transactions per second, persistence latency dropped from 40 milliseconds to approximately 20 milliseconds. Across the entire test range of 500 to 6,000 transactions per second, throughput scaled predictably in near-linear lockstep, latency remained flat until the absolute peak, and hot-shard CPU utilization sat at only about half. </p><h2>Engineered for extreme resilience</h2><p>Sheer speed is irrelevant if the system breaks under failure. To validate high availability, we simulated real-world disaster conditions. During a MongoDB Atlas primary failover test, a new primary node was elected in an average of five seconds. Payment processing continued seamlessly without a single lost payment or the need for an application restart.</p><p>We also tested an unplanned application node failure. </p><p><strong>Figure 2.</strong> Shard rebalancing mechanism to enable seamless recovery.</p><p>When a node went down, the system automatically and temporarily reduced throughput while redistributing traffic across the remaining nodes. The application returned to a stable 3,500 transactions per second in approximately 90 seconds. Most importantly, every single transaction reached a terminal state with absolutely zero data loss.</p>]]></description>
      <pubDate>Wed, 09 Sep 2026 13:00:03 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/news/benchmark-shows-atlas-manages-thousands-of-payments-per-second-zero-data-loss</link>
      <guid>https://www.mongodb.com/company/blog/news/benchmark-shows-atlas-manages-thousands-of-payments-per-second-zero-data-loss</guid>
    </item><item>
      <title>Leading Indian Organizations Are Driving India’s AI Future With MongoDB</title>
      <description><![CDATA[<p>Millions of Indians now use AI on a daily basis. It’s been said before, but the technology’s possibilities are incredible, whether you’re using AI to build an app with just a few sentences, or whether a virtual assistant is not only answering your questions but actually anticipating your needs. </p><p>But moving from a great idea to an AI product or feature that works—and that can be used by millions of users—isn’t easy. For every successful AI use case, there are hundreds of stalled or failed projects, and most of the time, this is due to the data foundations powering AI workflows.  </p><p><a href="https://www.mongodb.com/resources/winning-in-the-age-of-ai">According to IDC</a>, almost half of Indian organizations (46%) think that their existing architecture makes it impossible to build new applications. Specifically, rigid legacy architectures lack the flexibility and scalability to handle the high volume of unstructured data required for AI success.</p><p>Meanwhile, forward-thinking leaders are taking another approach: they are modernizing their data infrastructure and investing in data platforms that have been built for AI. This is the case of six leading Indian organizations that are using the <a href="https://www.mongodb.com/resources/products/capabilities/features">flexibility of the document model</a> and the power of the <a href="https://www.mongodb.com/products/platform">MongoDB platform</a> to take AI from prototype to production at scale. </p><p>Speaking at the <a href="https://www.youtube.com/playlist?list=PLdZHbuVOoAyM">MongoDB .local Bengaluru event in June 2026</a>, these six organizations shared how they are using the power of the MongoDB platform to remove complexity, gain speed, quickly move from AI prototype to production, and to scale. Here are their stories! </p><h2>Emergent Labs unleashed the power of vibe coding with MongoDB Atlas</h2><p>Emergent Labs uses MongoDB to enable anyone without a programming background or technical knowledge to build production-ready applications using natural language prompts. Through “vibe coding”, autonomous AI agents write, test, and iterate on application code based on user feedback. And they are doing all of that using <a href="https://www.mongodb.com/products/platform/atlas-database">MongoDB Atlas</a>. </p><p>Moving away from traditional relational databases, including PostgreSQL, and onto MongoDB’s flexible document model was a game-changer. It allowed Emergent Labs to rapidly adapt applications as customer requirements evolved, allowing them to iterate without the constraints, complexity, or delays typically associated with rigid schemas. And most importantly, it helped Emergent Labs scale: the company has now powered the creation of nearly 12 million applications across 180 countries, including hundreds of thousands of apps deployed in production. </p><p>Munkud Jah, Founder and CEO of Emergent Labs, said: “We saw a lot of our early competitors get stuck in migration loops where database operations would be stuck. One of our competitive advantages early on was using MongoDB, and we have been scaling on MongoDB ever since. We also believe that MongoDB is the best database for agentic coding.” </p><h2>Zomato sets a new standard for AI-driven customer support with Nugget</h2><p>Zomato has used <a href="https://www.mongodb.com/products/platform/atlas-database">MongoDB Atlas</a> to build Nugget, an <a href="https://www.mongodb.com/company/blog/innovation/zomato-ai-solution-nugget-reduces-support-costs">AI-powered customer support platform that has transformed its operations.</a> Less than four months after launch, Nugget has improved human-agent efficiency by 40%. </p><p>Now, with <a href="https://www.mongodb.com/products/platform/atlas-stream-processing">MongoDB Atlas Stream Processing</a> and<a href="http://mongodb.com/docs/manual/changestreams/"> MongoDB Change Streams</a>, Zomato can perform lightweight, real-time data transformations on the fly using stream aggregation pipelines, instead of having to write and maintain separate data-transformation jobs. It can also perform automatic scaling without manual intervention or grouping collections, so Nugget can keep growing and expanding without adding more architecture complexity or impacting performance. </p><h2>Leena AI scales virtual AI assistants in a secure environment</h2><p>Leena AI’s AI-first enterprise employee experience platform serves over 500 global enterprises and millions of employees. Using <a href="https://www.mongodb.com/products/platform/atlas-database">MongoDB Atlas</a>, Leena AI’s agentic AI platform is able to handle high-volume operational queries and ticket resolutions in real-time—the company’s virtual assistants can quickly retrieve relevant contextual policy details to resolve employee requests instantly. </p><p>MongoDB was chosen by Leena AI because it was built for AI: “You can’t have an AI strategy without a data strategy. And to do Agentic AI well, you need a document store, a document retrieval, a hybrid search engine, vectors, embeddings, and reranking,” said Mayank Kapoor, Senior Vice President for Leena AI. “You can have different databases doing these things, but then you have to make sure all these databases are in sync so the AI agents can have access to the latest information. Having everything in one single place is a huge help, and that’s what helped our velocity, too.”</p><p>Deployed across international enterprise environments, MongoDB Atlas also ensures that the platform scales smoothly under sudden spikes in employee ticket volume, all while maintaining multi-region security and operational performance. </p><h2>Brahma AI orchestrates complex agentic AI workflows with MongoDB</h2><p>Brahma AI uses <a href="https://www.mongodb.com/products/platform/atlas-database">MongoDB Atlas</a> as the intelligent, unified data foundation behind its enterprise AI platform that manages, creates, and distributes content—Brahma AI Core turns assets into structured, high-fidelity data, enabling faster search, seamless collaboration, and automated delivery across workflows, while Brahma AI Studio provides advanced AI creation capabilities so organizations can train brand-specific models and integrate third party audio and video generation systems within a secure, governed framework.</p><p>“We were born out of the world&#39;s most demanding industries—media, sports, entertainment—where scale, quality, speed, and accountability are non-negotiable,” said Venkatesan J, Senior Enterprise Architect and Head of Product Engineering, Brahma AI. “A platform like MongoDB enables faster development, and we don’t have to worry about rethinking RTOs and RPOs again and again. Our developers can focus on the business needs, instead of spending more time debugging outdated systems.” </p><h2>Observe AI takes AI-driven contact centers to the next level with powerful search capabilities </h2><p><a href="https://www.mongodb.com/products/platform/atlas-database">MongoDB Atlas</a> is the foundational database layer for Observe AI’s AI-driven contact center and conversational analytics platform, which handles millions of customer service interactions, voice calls, and real-time transcripts. Observe.ai uses MongoDB to ingest, analyze, and store all this high-volume, unstructured conversational telemetry.</p><p>“We chose MongoDB because it was a natural fit for the data we have—we need to extract a lot of insights and intelligence from raw conversations. Secondly, it’s all about the flexibility: we don’t want our engineers to spend too much time changing schemas, we need to be able to iterate fast,” said Jithendra Vepa, CTO and Co-Founder, Observe AI. “MongoDB really sits nicely between our data layer and the orchestration layer, and we were able to scale enormously over the years, all while keeping trust and security.”</p><h2>Gnani AI scales its conventional CX platform across 40+ languages </h2><p>MongoDB has been instrumental in powering and scaling <a href="http://www.gnani.ai/">Gnani AI’s</a> agentic conversational and voice-first customer experience platform. The flexibility of <a href="https://www.mongodb.com/products/platform/atlas-database">MongoDB Atlas</a> means that Gnani AI can seamlessly manage unstructured data, including millions of voice calls, real-time analytics, and automated workflows across 40+ languages. </p><p>Gnani AI has deployed close to about 1,000+ AI agents that handle calling for its customers across a range of industries, including highly regulated sectors such as financial services. </p><p>MongoDB has helped Gnani AI manage the data complexity that comes from operating so many agents. MongoDB Atlas’s flexibility means that the company can seamlessly handle different agents that operate with different schemas. Furthermore, MongoDB’s built-in security capabilities ensure that Gnani AI’s data stays in a safe and secure environment. </p><p>With built-in capabilities including <a href="https://www.mongodb.com/products/platform/atlas-search">MongoDB Search</a>, <a href="https://www.mongodb.com/products/platform/atlas-vector-search">MongoDB Vector Search</a>, and <a href="https://www.mongodb.com/products/platform/ai-search-and-retrieval">Voyage AI</a>, MongoDB Atlas is <em>built</em> for powering AI-driven use cases. No need to add complexity by using disparate systems for search, retrieval, and embeddings—Indian organizations like Emergent Labs, Zomato, Leena AI, Brahma AI,  Observe AI, and Gnani AI are examples of what combining great tech talent and forward-thinking organizations with the right technology can achieve. </p>]]></description>
      <pubDate>Tue, 08 Sep 2026 11:53:18 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/leading-indian-organizations-are-driving-indias-ai-future</link>
      <guid>https://www.mongodb.com/company/blog/innovation/leading-indian-organizations-are-driving-indias-ai-future</guid>
    </item><item>
      <title>Navigating the AI Revolution: The Importance of Adaptation</title>
      <description><![CDATA[<p>In 1999, Steve Ballmer gave a famous speech in which he said that the “key to industry transformation, the key to success is developers developers developers developers developers developers developers, developers developers developers developers developers developers developers! Yes!”</p><p>A similar mantra applies when discussing how to succeed with AI: adaptation, adaptation, adaptation! Artificial intelligence has already begun to transform how we work and live, and the changes AI is bringing to the world will only accelerate.</p><p>Businesses rely ever more heavily on software to run and execute their strategies. So, to keep up with competitors, their processes and products must deliver what end-users increasingly expect: speed, ease of use, personalization—and, of course, AI features. Delivering all of these things (and doing so well) requires having the right tech stack and software foundation in place and then successfully executing.</p><p>To better understand the challenges organizations adopting AI face, MongoDB and Capgemini recently worked with the research organization TDWI to assess the state of AI readiness across industries.</p><h2>The road ahead</h2><p>Based on a survey “representing a diverse mix of industries and company sizes,” <a href="https://www.mongodb.com/resources/solutions/use-cases/the-state-of-data-and-operational-readiness-for-ai">TDWI’s “The State of Data and Operational Readiness for AI</a>” contains lots of super interesting findings. One I found particularly compelling is the percentage of companies with AI apps in production: businesses largely recognize the potential AI holds, but only 11% of survey respondents indicated that they had AI applications in production. Still only 11%!</p><p></p><p>There’s clearly work to be done; data readiness challenges highlighted in the report include managing diverse data types, ensuring accessibility, and providing sufficient compute power. Less than half (39%) of companies surveyed manage newer data formats, and only 41% feel they have enough compute.</p><p>The report also shows how much AI has changed the very definition of software, and how software is developed and managed. Specifically, AI applications continuously adapt, and they learn and respond to end-user behavior in real-time; they can also autonomously make decisions and execute tasks.</p><p>All of which depends on having a solid, flexible software foundation.</p><p>Because the agility and adaptability of software are intrinsically linked to the data infrastructure upon which it&#39;s built, rigid legacy systems cannot keep pace with the demands of AI-driven change. So modern database solutions (like, ahem, MongoDB)—built with change in mind—are an essential part of a successful AI technology stack.</p><h2>Keeping up with change</h2><p>The tech stack can be said to comprise three layers: at the “top,” the interface or user experience layer; then the business logic layer; and a data foundation at the bottom.</p><p>With AI, the same layers are there, but they’ve evolved: Unlike traditional software applications, AI applications are <em>dynamic</em>. Because AI-enriched software can reason and learn, the demands placed on the stack have changed. For example, AI-powered experiences include natural language interfaces, augmented reality, and those that anticipate user needs by learning from other interactions (and from data). In contrast, traditional software is largely static: it requires inputs or events to execute tasks, and its logic is limited by pre-defined rules.</p><p>A database underpinning AI software must, therefore, be flexible and adaptable, and able to handle all types of data; it must enable high-quality data retrieval; it must respond instantly to new information; and it has to deliver the core requirements of all data solutions: security, resilience, scalability, and performance.</p><p>So, to take action and generate trustworthy, reliable responses, AI-powered software needs access to up-to-date, context-rich data. Without the right data foundation in place, even the most robust AI strategy will fail.</p><p></p><p>Keeping up with AI can be head-spinning, both because of the many players in the space (the number of AI startups has jumped sharply since 2022, when ChatGPT was first released1), and because of the accelerating pace of AI capabilities.</p><p>Organizations that want to stay ahead must evolve faster than ever. As the figure above dramatically illustrates, this sort of adaptability is essential for survival.</p><h2>Execution, execution, execution</h2><p>But AI success requires more than just the right technology: expert execution is critical.</p><p>Put another way, the difference between success and failure when adapting to any paradigm shift isn’t just having the right tools; it’s knowing how to wield those tools. So, while others experiment, MongoDB has been delivering real-world successes, helping organizations modernize their architectures for the AI era, and building AI applications with speed and confidence.</p><p>For example, MongoDB teamed up with the Swiss bank <a href="https://www.mongodb.com/press/mongodb-collaborates-with-lombard-odier-to-modernize-core-banking-technology">Lombard Odier</a> to modernize its banking tech systems. We worked with the bank to create customizable generative AI tooling, including scripts and prompts tailored for the bank’s unique tech stack, which accelerated its modernization by automating integration testing and code generation for seamless deployment.</p><p>And, after <a href="https://www.mongodb.com/solutions/customer-case-studies/victorias-secret#outcome">Victoria’s Secret</a> transformed its database architecture with <a href="https://www.mongodb.com/products/platform/atlas-database">MongoDB Atlas</a>, the company used <a href="https://www.mongodb.com/products/platform/atlas-vector-search">MongoDB Atlas Vector Search</a> to power an AI-powered visual search system that makes targeted recommendations and helps customers find products.</p><p>Another way MongoDB helps organizations succeed with AI is by offering access to both <a href="https://cloud.mongodb.com/ecosystem?filter=ai%2Fml">technology partners</a> and professional services expertise. For example, MongoDB has integrations with companies across the AI landscape—including leading tech companies (AWS, Google Cloud, Microsoft), system integrators (Capgemini), and innovators like Anthropic, LangChain, and Together AI.</p><h2>Adapt (or else)</h2><p>In the AI era, what organizations need to do is abundantly clear: modernize and adapt, or risk being left behind.</p><p>Just look at the history of smartphones, which have had an outsized impact on business and communication. For example, in its Q4 2007 report (which came out a few months after the first iPhone’s release), Apple reported earnings of $6.22 billion, of which iPhone sales comprised less than 2%2; in Q1 2025, the company reported earnings of $124.3 billion, of which 56% was iPhone sales.3 The mobile application market is now estimated to be in the hundreds of billions of dollars, and there are more smartphones than there are people in the world.4 The rise of smartphones has also led to a huge increase in the number of people globally who use the internet.5</p><p>However, saying “you need to adapt!” is much easier said than done. TWDI’s research, therefore, is both important and useful—it offers companies a roadmap for the future, and helps them answer their most pressing questions as they confront the rise of AI.</p><p></p><p>P.S. ICYMI, here’s Steve Ballmer’s famous “developers!” speech.</p><p></p><p>1 <a href="https://ourworldindata.org/grapher/newly-funded-artificial-intelligence-companies">https://ourworldindata.org/grapher/newly-funded-artificial-intelligence-companies</a></p><p>2 <a href="https://www.apple.com/newsroom/2007/10/22Apple-Reports-Fourth-Quarter-Results/">https://www.apple.com/newsroom/2007/10/22Apple-Reports-Fourth-Quarter-Results/</a></p><p>3 <a href="https://www.apple.com/newsroom/pdfs/fy2025-q1/FY25_Q1_Consolidated_Financial_Statements.pdf">https://www.apple.com/newsroom/pdfs/fy2025-q1/FY25_Q1_Consolidated_Financial_Statements.pdf</a></p><p>4<a href="https://www.weforum.org/stories/2023/04/charted-there-are-more-phones-than-people-in-the-world/"> https://www.weforum.org/stories/2023/04/charted-there-are-more-phones-than-people-in-the-world/</a></p><p>5 <a href="https://ourworldindata.org/grapher/number-of-internet-users">https://ourworldindata.org/grapher/number-of-internet-users</a></p>]]></description>
      <pubDate>Thu, 03 Sep 2026 21:21:24 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/announcing-a-modernization-toolkit</link>
      <guid>https://www.mongodb.com/company/blog/innovation/announcing-a-modernization-toolkit</guid>
    </item><item>
      <title>MongoDB 8.0: Improving Performance, Avoiding Regressions</title>
      <description><![CDATA[<p>MongoDB 8.0 is the most secure, durable, available and performant version of MongoDB yet: it’s 36% faster in read workloads and 32% faster in mixed read and write workloads than MongoDB 7.0  In addition to benefitting customers, MongoDB 8.0’s performance has also brought significant benefits to our own internal applications, as my colleague Jonathan Brill recently noted in <a href="https://www.mongodb.com/company/blog/engineering/mongodb-8-0-eating-our-own-dog-food">his own blog post</a>.</p><p>To achieve these improvements, we created an 8.0 multi-disciplinary tiger team focused on performance, and eventually expanded this team into a broad “performance army.” The work by these engineers led to new ideas on how to process simple queries and how writes are replicated. Combined with a new way of measuring performance, we also added a new way to catch the gradual performance loss over time due to many miniscule regressions.</p><h2>Benchmarking at MongoDB</h2><p>The MongoDB Engineering team runs a set of benchmarks internally to measure MongoDB’s performance. Industry standard benchmarks like YCSB, Linkbench, TPCC, and TPCH are run periodically on a variety of configurations and architectures, and these benchmarks are augmented by custom benchmarks based on customer workloads. By running these benchmarks in our continuous integration system, we ensure that developers do not make commits that are detrimental to performance. For instance, if any commit would regress a benchmark by more than 5% for our most important workloads, we would revert the commit. However, this threshold does not detect regressions of 0.1%, and there are thousands of commits per release (e.g., more than 9000 in MongoDB 8.0).</p><p>During the release of MongoDB 7.0, we started to take this gradual accumulation of performance loss by tiny regressions of release over release regressions seriously, so we changed the rules of the game. We decided we could not ship MongoDB 7.0 unless it at least matched MongoDB 6.0’s performance on the most important benchmarks.</p><p>We began investigating regressions and made changes to get performance back. Typically, we use tools like Intel VTune and Linux perf to find regressions across releases. With the release of MongoDB 7.0 approaching, engineers limited the scope of these fixes to reduce their risk to the release. Some proposed fixes were considered too risky. Other fixes didn’t deliver statistically significant performance improvements (Z-score &gt; 1). Unfortunately, MongoDB lost performance with many tiny cuts at a time, and our team realized that it would take many tiny steps to improve it. We got performance back to MongoDB 6.0’s levels, but we weren&#39;t quite satisfied. We knew that what we started with MongoDB 7.0 would need to continue into MongoDB 8.0 as a first-tier concern from the start.</p><h2>The MongoDB 8.0 performance push</h2><p>For the release of MongoDB 8.0, we increased the priority of performance over other work and set the goal of matching MongoDB 4.4’s performance at the start. This release was chosen because it switched the default to Write Concern Majority for replica sets. This change in write concern improved MongoDB’s default durability guarantees but came with a loss in performance since the primary needs to wait for a second write on a second machine to be performed.</p><p>Before the release of MongoDB 5.0, the default write concern was w:1; when a client inserted a document, the response was returned to the client as soon as the write was journaled to the local disk. With write concern majority, the MongoDB server waits for a majority of the nodes to write the document to disk before returning a response. On the primary, MongoDB server inserts the document in the collection, journals this change to disk, sends the change to the secondary where it also journals the document to disk and then inserts the document into its collection. Applying the change immediately to collection on the secondary minimizes the latency for the secondary reads.</p><p>To start our journey to improving the performance of MongoDB 8.0, we created a multi-disciplinary tiger team of 10 people in August 2023, with myself as the leader. The team comprised two performance engineers, three staff engineers, two senior staff engineers, a senior lead, and one technical program manager. Our team of ten worked together to generate ideas, proofs of concept, and experiments.</p><p>The team’s process was different from our normal process, as we focused on idea experimentation, versus making ideas production-ready. I gave the team free reign to make any changes they thought could help, and I encouraged experimentation—the MongoDB 8.0 performance tiger team was a safe space. This spirit of experimentation was both important and successful, as it led to new ideas that delivered several big improvements (which are highlighted below). We were able to try quick hacks and measure their performance without having to worry about making our work production quality.</p><h2>The big improvements</h2><p>Two of the big improvements we made to MongoDB 8.0 came out of this team: simple finds and replication latency.</p><p>MongoDB supports a rich query language, but a lot of queries are simple ones to look up a document by a single _id field; the _id field always has a unique index. MongoDB optimized this with a special query plan stage called IDHACK—a query stage optimized to retrieve a single document with a minimal code path. When the tiger team looked at this code, we realized that it was spending a lot of time going through the general purpose query planning code paths before choosing the IDHACK plan.</p><p>So, a tiger team member did an experiment to bypass the entire query planner and hard code reading from the storage engine. When this delivered significant improvements to the YCSB 100% read, we knew we had a winner. While we knew it could not be committed as-is, it did serve as motivation to improve the IDHACK code path in the server in a new code path called ExpressPlan. The query team took this idea and ran with it by expanding it further for updates, deletes, and other unique index lookups.</p><p>Here are traces for MongoDB from <a href="https://llvm.org/docs/XRay.html">LLVM XRay</a> and <a href="https://perfetto.dev">Perfetto</a>. The highlighted red areas show the difference between 7.0 and 8.0 for query planning for a db.coll.find({_id:1}).</p><p>The second big change was how we viewed replicating changes in a cloud database. As explained above, on secondaries, MongoDB journals the writes and then applies it to the collection before acknowledging it back to the primary.</p><p>During a team brainstorming session, a tiger team member asked, “what if we acknowledge the write as soon as it is journaled, but before we applied it to the collection in-memory?” This reduces the latency of the primary and speeds up writes in a replica set while still maintaining our durability guarantees. A second engineer ran with this idea, prototyped it quickly, and proved that it provided a significant performance boost in a week.</p><p>Now that the idea was proven to be beneficial, we handed it to the replication team to ship this work. Shipping this change took three months because we had to prove it was correct in the TLA+ models for our replication system and all corner cases before we could ship it.</p><h2>Catching very small regressions</h2><p>To detect small regressions, it is important to have benchmarks with no or low noise. But if the threshold is too small, this creates needless noise and creates a very noisy or flakey test that developers will learn to ignore.</p><p>Given the noisiness of various metrics such as latency and throughput, a tiger team member came up with the idea of simply counting instructions via Linux perf_event_open syscall. In this test, the code exercises the request processing code to do a simple MongoDB ping command. We run the ping command in a loop on a CI machine a few times and report the average instruction count. This test has a 0.2% tolerance and uses a hard code number. Developers can adjust the threshold up or down as needed, but this test has been a huge success as it allows us to detect regressions without spurious noise. Check out the <a href="https://github.com/mongodb/mongo/blob/v8.0/src/mongo/db/service_entry_point_common_bm.cpp">benchmark on GitHub</a>.</p><h2>From tiger team to (tiger) army</h2><p>A small tiger team can only do so much, and we didn’t want to create a situation in which one team ships features only for another team to clean up their work later. For example, the MongoDB 8.0 performance tiger team focused on a subset of benchmarks, but MongoDB’s performance is measured with dozens of benchmarks. From November 2023 to January 2024, we started implementing all the performance ideas that the tiger team implemented, but more work remained to improve performance.</p><p>This was when we built a performance “army”—we enlisted 75 people from across the 11 MongoDB server teams to work on performance. In this phase of the project, engineers were charged with idea generation, and fixing performance issues allowed us to accomplish even more than the tiger team; the larger team finished eight performance projects and 140 additional tickets as part of this work.</p><p>By bringing in additional team members, we were able to draw on ideas from a larger pool of database experts. This led to improvements in a wide variety of areas—like parsing of large $in queries, improvements to query yielding, making config.transactions a clustered collection, reworking locking in count less places, micro optimizations in authorization checks, and a change to a new TCMalloc memory allocator with lower fragmentation. Engineers also looked at improving common code such as namespace string handling, our custom code generation (we found tries helped speed up generated parsers), reducing memory usage, and choosing better data structures in some cases.</p><p>To give people the time and space they needed to succeed, we gave them dedicated weeks of time to focus on this work in lieu of adding new features. We encouraged both experimentation and for people to go with their gut feelings for small improvements that didn’t appear to move the needle on performance. Because not every experiment succeeded, it was important to encourage each other to keep experimenting and trying in the face of failure.</p><p>For example, in one failed experiment two engineers tried to use restartable sequences on Linux, but the change failed to deliver the improvements we wanted given their cost and complexity. On the other hand, custom containers and reader writer mutexes did deliver. For my part, the most impactful thing I did during this phase was to be a cheerleader and to support the team’s efforts in our performance push. Being positive and optimistic helped people push forward in their performance work even when ideas didn’t work out.</p><h2>Performance improvements take a village</h2><p>Overall, MongoDB 8.0 was our most successful release ever in terms of performance. Concerted, innovative work by a passionate team—and later an army—of engineers led to new ideas for performance and new ways of thinking. Performance work is neither easy nor straightforward. But by building a sense of community around our performance push, we supported each other and encouraged each other to deliver great performance improvements for MongoDB 8.0.</p><p>To read more about how MongoDB raised the bar with the release of MongoDB 8.0, check out our Chief Technology Officer <a href="https://www.mongodb.com/blog/post/mongodb-8-0-raising-the-bar?tck=8_0_performance_blog">Jim Scharf’s blog post</a>. And please visit the <a href="https://www.mongodb.com/products/updates/version-release?tck=8_0_performance_blog">MongoDB 8.0 page</a> to learn more about all of its features and upgrades.</p>]]></description>
      <pubDate>Thu, 03 Sep 2026 20:03:13 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/engineering/mongodb-8-0-improving-performance-avoiding-regressions</link>
      <guid>https://www.mongodb.com/company/blog/engineering/mongodb-8-0-improving-performance-avoiding-regressions</guid>
    </item><item>
      <title>MongoDB Enterprise Advanced for AI-Ready Operational Insights in Manufacturing</title>
      <description><![CDATA[<p>Asset downtime and unplanned maintenance continue to impact manufacturing operations. According to Siemens, every unproductive hour in the automotive sector now costs $2.3 million[1]. The cost impact extends beyond immediate throughput loss, as a single equipment failure can also trigger contractual penalties and force costly expedited logistics. Most manufacturers have invested in condition monitoring and basic failure prediction, but predictive maintenance is not one single step, but a series of steps that include prediction, root cause identification, work order creation, and scheduling. </p><p>Existing systems typically operate in isolation, and because of that, mean equipment recovery times have increased from 49 to 81 minutes per incident [1]. A persistent workforce shortage compounds the problem as the Manufacturing Institute reports that the sector will need around 3.8 million new employees in the next 10 years, with 26% of the existing workforce expected to retire by 2030 [2]. Every workflow that depends on institutional knowledge becomes a point of failure when the people who hold that knowledge have left the floor.</p><p>These pressures are not mutually exclusive. An equipment failure has a larger impact when no one is available to repair it in time. Traditional approaches such as periodic risk reviews and manual workflows are no longer sufficient. Manufacturers need a system of action that agents can use to run flexible workflows and resolve disruptions at a faster pace. We believe this is a role that multi-agent systems are designed to fill, and MongoDB is the right database to build a scalable multi-agent platform for manufacturing operations.</p><h2>From agents to multi-agent systems in manufacturing</h2><p>An AI agent is an operational application that attempts to achieve a goal by observing the world and acting upon it using the data and tools it has at its disposal. Unlike a traditional chatbot, an AI agent operates through a workflow defined via a large language model (LLM) that includes reasoning, planning, and taking action. </p><p>In manufacturing, the tools an agent accesses can include connections to manufacturing execution systems (MES), supervisory control and data acquisition (SCADA) systems, or Internet of Things (IoT) sensor streams. A single agent in manufacturing has limited utility as the workflows rarely map to a single domain. A multi-agent system is a coordinated group of AI agents, each with their own specialized role, that collaborate to solve complex tasks. Each agent operates within its own guardrails and has its own set of tools, but they share context through a common data layer and communicate through a common orchestration pattern. </p><p>It is important to note that in manufacturing, not every operational problem benefits from an agent. Deterministic workflows that follow a fixed sequence are better served with traditional automation logic. The workflows that benefit the most from agentic systems are the ones where rich context is needed to arrive at a decision, or workflows that involve adapting to changing conditions on the shop floor. Figure 1 maps four core agent capabilities to practical manufacturing applications.</p><p><strong>Figure 1.</strong> Use cases of AI Agents in manufacturing.</p><p>Deploying agents in industrial environments presents challenges that go beyond typical enterprise software deployments. Integration with Brownfield OT systems speaking industrial protocols like Modbus and PROFINET is complex. Therefore, the following is required:</p><ul><li><p>Real-time observability with a human-in-the-loop for critical decisions</p></li><li><p>Industrial environments that demand strict security policies and governance models</p></li><li><p>LLM latency constraints limit which use cases are viable for fast-response scenarios </p></li><li><p>Agents require flexible data storage that can handle profiles, memory, and time series sensor data simultaneously </p></li><li><p>Technical debt accumulates quickly as the number of tools and platforms increases  </p></li><li><p>Industrial environments demand near-zero downtime, making system resilience essential [3].</p></li></ul><h2>Why use MongoDB for multi-agent systems in manufacturing</h2><p>An agent needs to read a stream of operational data in real time, take action, generate a memory of that action, and record the action taken back into that operational database. It also needs to understand user intent, translate it into a search query, and perform semantic search over unstructured data. </p><p>Most agentic architectures today get built on a patchwork of specialized databases. For example, that could be a vector database for embeddings, a relational database for structured records, or a time series database for sensor telemetry. In manufacturing, this fragmentation creates a big hurdle in deploying agents in production. It directly undermines the goal of increasing operational resilience by introducing cross-system collaboration issues, thus recreating the same problem the agents were supposed to solve. </p><p>MongoDB addresses this issue by providing a unified data platform where operational data, vector embeddings, time series telemetry, agent memory, and agent outputs all live in the same database, queryable through the same interface [11]. In addition to the database, MongoDB offers tools for the agent, such as <a href="https://www.mongodb.com/products/platform/atlas-vector-search">vector search</a>, <a href="https://www.mongodb.com/docs/manual/text-search/">full-text search</a>, and <a href="https://www.mongodb.com/products/platform/atlas-stream-processing">stream processing</a>, which the agent can use to transform and search across both structured and unstructured data. </p><h2>A document model is a natural fit for agent data</h2><p>AI agents work with diverse, semi-structured data. This includes agent profiles, conversation histories, tool call metadata, sensor readings, supplier records, and work orders. Relational databases struggle with this diversity because each new data shape requires a schema redesign or forces adding a new specialized database. MongoDB&#39;s document model handles it naturally [4]. An agent&#39;s session, including its messages, tool calls, and referenced data, can all be stored and read as a single JSON document:</p><p>The document model provides the storage foundation for agent data, but the real architectural advantage of MongoDB is how it can transform a scattered system of record into a unified system of action. In a typical manufacturing plant, production data lives in MES, inventory and procurement data lives in ERP, equipment health data in a central maintenance management system (CMMS), and an array of PDF files and spreadsheets stored in various file systems also exist. Agents cannot reason over such a vast data estate. MongoDB is the converged data store that sits between the existing systems of record and the AI agents that act on that data. </p><p><strong>Figure 2.</strong> MongoDB is a closed-loop operational layer that converts data into decisions and actions.</p><h2>Using hybrid search with MongoDB</h2><p>Agents in manufacturing need to do more than query structured fields. When a maintenance agent receives an alert about abnormal vibration on a spindle bearing, it needs to find similar historical failure patterns, relevant sections from equipment manuals, and past maintenance reports that describe analogous symptoms. Some of this retrieval is a semantic search problem, and some requires a keyword search, such as finding a specific alarm code, part number, or defect classification exactly. </p><p>MongoDB supports both search modes and allows them to be combined within the same query against the same data [4]. MongoDB Vector Search enables semantic retrieval by storing vector embeddings alongside the operational data they represent. MongoDB full-text search complements this by using traditional keyword-based retrieval with autocomplete and faceted search features included.</p><h2>Time series collections for ingesting sensor telemetry at scale</h2><p>Manufacturing agents depend on high-frequency sensor data. Vibration, temperature, pressure, current draw, and acoustic emission data flow continuously from equipment on the factory floor. MongoDB&#39;s time series collections are purpose-built for this workload. They use a columnar storage format optimized for time-stamped data, delivering efficient compression and fast range queries [5]. A predictive maintenance agent monitoring a fleet of machines can query the last 24 hours of vibration data for a specific spindle, compute trends, and compare them against baseline thresholds.</p><h2>Change streams for event-driven apps</h2><p>Multi-agent systems cannot rely solely on polling or scheduled queries. When a sensor reading crosses a critical threshold, agents need to react immediately. MongoDB change streams allow an agent to subscribe to a collection and receive real-time notifications whenever a document is inserted or updated [5]. This event-driven architecture ensures agents activate only when relevant events occur, which is both more efficient and more responsive than periodic batch processing. </p><h2>Voyage AI embedding models and rerankers</h2><p>Vector search requires embedding models to convert text and documents into numerical vectors. In restricted or air-gapped environments where external API calls are not permitted, <a href="https://www.mongodb.com/products/platform/ai-search-and-retrieval">MongoDB&#39;s Voyage AI</a> offers voyage-4-nano, an open-weight embedding model designed for local deployment [6]. Voyage Nano runs entirely on local infrastructure without requiring connectivity to any cloud service, making it suitable for secure operational environments. It can be used to generate embeddings for maintenance logs, shift notes, equipment manuals, and work orders at ingest time, and to embed agent queries at search time, all within the facility&#39;s own network boundary.</p><h2>Agent memory: short-term and long-term</h2><p>Anthropic research found that multi-agent coordination breaks down without sophisticated memory distribution across agents [7]. A predictive maintenance agent that cannot remember what it diagnosed yesterday will repeat the same analysis, miss new patterns, and lose the trust of its users. MongoDB supports both short-term and long-term agent memory. Short-term memory, typically implemented through a checkpointing technique, maintains context within a single conversation thread so the agent remembers what it asked, what tools it called, and what the user said earlier in the session [8]. Long-term memory allows agents to retain and retrieve knowledge across sessions. This means a supply chain disruption agent can remember that Supplier X had a two-week delay last quarter and that the backup supplier for Component Y requires a six-week lead time. These memories are stored as documents in MongoDB, indexed for fast retrieval, and can be shared across agents in a multi-agent system through a shared memory namespace. </p><h2>Use case: Multi-agent predictive maintenance</h2><p>The architecture shown in figure 3 demonstrates how to build a multi-agent predictive maintenance system using MongoDB.</p><p><strong>Figure 3.</strong> High-level architecture of a multi-agent predictive maintenance system.</p><p>The architecture follows a supervisor-agent pattern using MongoDB Enterprise Advanced as the agentic data layer and LangGraph for agent orchestration. The supervisor coordinates tasks and delegates to three specialized agents: </p><ul><li><p>A root cause analyst (RCA) agent who generates incident reports </p></li><li><p>A work order agent (WOA)  that drafts maintenance work orders </p></li><li><p>A planning agent (PA) that identifies the optimal time slot for the maintenance task based on availability and production constraints [9]</p></li></ul><p>The process begins with an alert, something unusual in the machine data or logs that could point to a potential failure. The supervisor agent then notifies the RCA agent that generates a concise incident report and shares it with the supervisor agent, which then moves the workflow forward. </p><p>The  WOA receives the incident report and drafts a comprehensive maintenance work order. It pulls from previous similar tasks to estimate time requirements, identify the necessary materials, and ensure the right skill sets are listed. This step includes a human-in-the-loop checkpoint; technicians or supervisors can review and modify the draft before it is finalized. </p><p>Once the work order is approved, the PA schedules the maintenance activity. The agent queries the production calendar, checks staff shift schedules, and verifies inventory availability for required materials to find the most efficient time slot. </p><p>This entire workflow can run on a single MongoDB Enterprise Advanced deployment as the same database stores the sensor telemetry, the agent memory, the equipment knowledge base, the work order history, and the production schedule. This architecture can also be extended to other use cases, such as spare parts procurement or production scheduling.</p><h2>Deployment considerations for secure environments</h2><p>MongoDB Enterprise Advanced is designed for self-managed deployments where organizations require full control over their infrastructure, data, and security posture. For secure and regulated environments, several characteristics are particularly relevant. MongoDB EA runs entirely on-premise or within an organization&#39;s own data center with no dependency on external cloud services. All data, including sensor telemetry, agent memory, vector embeddings, and operational records, remains within the facility&#39;s network boundary. </p><p>Voyage Nano, the open-weight embedding model, runs locally and generates embeddings without any external API calls, which is essential for air-gapped or network-restricted environments [6]. MongoDB EA includes enterprise-grade security features such as LDAP and Kerberos authentication, encryption at rest and in transit, field-level encryption, and comprehensive audit logging. </p><p>Because all the capabilities described in this document, such as the document model, vector search, full-text search, time series collections, change streams, and agent memory storage, exist within a single MongoDB deployment, organizations avoid the operational complexity and security surface area that comes with managing multiple specialized databases. One platform means one security model, one set of access controls, and one audit trail.</p><h3>References </h3><p>[1] Siemens, &quot;The True Cost of Downtime 2024,&quot; Senseye Predictive Maintenance:<a href="https://assets.new.siemens.com/siemens/assets/api/uuid:1b43afb5-2d07-47f7-9eb7-893fe7d0bc59/TCOD-2024_original.pdf"> https://assets.new.siemens.com/siemens/assets/api/uuid:1b43afb5-2d07-47f7-9eb7-893fe7d0bc59/TCOD-2024_original.pdf</a></p><p>[2] Deloitte &amp; The Manufacturing Institute, &quot;Taking charge: Manufacturers support growth with active workforce strategies&quot; (2024):<a href="https://www.deloitte.com/us/en/insights/industry/manufacturing-industrial-products/supporting-us-manufacturing-growth-amid-workforce-challenges.html"> https://www.deloitte.com/us/en/insights/industry/manufacturing-industrial-products/supporting-us-manufacturing-growth-amid-workforce-challenges.html</a></p><p>[3] LangChain, &quot;2026 State of Agent Engineering&quot;:<a href="https://www.langchain.com/state-of-agent-engineering"> https://www.langchain.com/state-of-agent-engineering</a></p><p>[4] MongoDB, &quot;Building Intelligent AI Agents with MongoDB Atlas: A Bidirectional Data Flow Architecture&quot;:<a href="https://dev.to/mongodb/building-intelligent-ai-agents-with-mongodb-atlas-a-bidirectional-data-flow-architecture-2obl"> https://dev.to/mongodb/building-intelligent-ai-agents-with-mongodb-atlas-a-bidirectional-data-flow-architecture-2obl</a></p><p>[5] MongoDB, &quot;Building Gen AI-Powered Predictive Maintenance with MongoDB&quot;:<a href="https://www.mongodb.com/company/blog/innovation/building-gen-ai-powered-predictive-maintenance-mongodb"> https://www.mongodb.com/company/blog/innovation/building-gen-ai-powered-predictive-maintenance-mongodb</a></p><p>[6] MongoDB, &quot;Voyage AI: Embedding Models and Rerankers&quot;:<a href="https://www.mongodb.com/products/platform/ai-search-and-retrieval"> https://www.mongodb.com/products/platform/ai-search-and-retrieval</a></p><p>[7] Anthropic, &quot;Building a Multi-Agent Research System&quot;:<a href="https://www.anthropic.com/engineering/built-multi-agent-research-system"> https://www.anthropic.com/engineering/built-multi-agent-research-system</a></p><p>[8] MongoDB, &quot;Powering Long-Term Memory For Agents With LangGraph And MongoDB&quot;:<a href="https://www.mongodb.com/company/blog/product-release-announcements/powering-long-term-memory-for-agents-langgraph"> https://www.mongodb.com/company/blog/product-release-announcements/powering-long-term-memory-for-agents-langgraph</a></p><p>[9] MongoDB, &quot;Unlock Multi-Agent AI Predictive Maintenance&quot;:<a href="https://www.mongodb.com/company/blog/innovation/unlock-multi-agent-ai-predictive-maintenance"> https://www.mongodb.com/company/blog/innovation/unlock-multi-agent-ai-predictive-maintenance</a></p>]]></description>
      <pubDate>Thu, 03 Sep 2026 17:13:26 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/enterprise-advanced-ai-ready-operational-insights-manufacturing</link>
      <guid>https://www.mongodb.com/company/blog/innovation/enterprise-advanced-ai-ready-operational-insights-manufacturing</guid>
    </item><item>
      <title>MongoDB VFS for LangChain Deep Agents: A Searchable Filesystem for Agents</title>
      <description><![CDATA[<p>Modern AI agents are no longer expected to answer a question alone. They&#39;re expected to complete real work: plan a multi-step task, inspect source material, produce intermediate artifacts, and hand off pieces of the problem to other agents, compressing work that used to take days into hours. That shift raises the bar on what an agent needs underneath it. An agent can only plan and execute at that speed if it can reliably navigate, search, read, and update the filesystem it&#39;s working with along the way.</p><p>The MongoDB virtual filesystem (VFS) for LangChain Deep Agents connects that filesystem experience to <a href="https://www.mongodb.com/products/platform/atlas-database">MongoDB Atlas</a> and your underlying object store (e.g., S3 bucket). It gives Deep Agents a familiar virtual filesystem, providing agents with a searchable workspace that persists across sessions, deployments, and sub-agents. Developers building on Deep Agents can now use MongoDB Atlas as the data platform for their agents, including <a href="https://www.mongodb.com/products/platform/atlas-search">MongoDB Search</a>, <a href="https://www.mongodb.com/products/platform/atlas-vector-search">Vector Search</a>, and <a href="https://www.mongodb.com/resources/products/capabilities/hybrid-search">hybrid search</a>, without changing how their agent code reads or writes files. This architecture lets an agent plan, inspect source material, create intermediate artifacts, and return to work that may span hours or days without loading an entire corpus into its context window.</p><p>This post explains what Deep Agents and a virtual filesystem are, how the MongoDB backend integration works in an agentic application, and where the pattern can be useful in enterprise agent systems.</p><h2>How LangChain Deep Agents use a virtual filesystem</h2><h3>What are LangChain Deep Agents?</h3><p><a href="https://docs.langchain.com/oss/python/deepagents/overview">LangChain Deep Agents</a> are an agent harness built on LangChain and LangGraph for complex, multi-step work. They add capabilities such as planning, subagents, and filesystem-oriented tools, so an agent can break a large task into smaller actions rather than trying to solve everything in a single context window.</p><p>A Deep Agent can work with operations such as:</p><ul><li><p><em>Is</em> to understand the directory structure</p></li><li><p><em>glob</em> to find files by path pattern</p></li><li><p><em>grep</em> to search file content</p></li><li><p><em>read</em> to retrieve a file</p></li><li><p>write and edit to create or modify artifacts</p></li><li><p><em>upload_files</em> and <em>download_files</em> for bulk file movement</p></li></ul><p>These tools are exposed through a backend contract. The agent does not need to know whether the files live on a local filesystem, in a LangGraph store, in an object storage, or behind another persistence layer. It calls the same filesystem interface, and the configured backend supplies the data.</p><p>For MongoDB-specific LangChain integrations, see the <a href="https://www.mongodb.com/docs/atlas/ai-integrations/langchain/">Integrate MongoDB with LangChain - Atlas</a> documentation.</p><h3>What is a virtual filesystem?</h3><p>A <a href="https://docs.langchain.com/oss/javascript/deepagents/overview#virtual-filesystem-access">virtual filesystem</a> is a logical, path-based view of data whose physical storage is abstracted away. An agent may see paths such as <em>docs/</em>, <em>reports/</em>, or <em>projects/customer-a/</em>, even when the underlying bytes reside in an object store and the searchable representation is stored in a database.</p><p>This abstraction matters for agents because filesystem navigation is naturally incremental. Instead of loading an entire corpus into the prompt, an agent can first list a directory, narrow the search with a filename pattern, search for a concept, read the relevant file, and then write its findings back as an artifact. This helps agents stay within context limits and reduce costs, since each step pulls in only the slice of the corpus it actually needs rather than the entire corpus.</p><p>The virtual filesystem is therefore more than a storage abstraction. It is a context-management interface for agentic work.</p><h2>What is the MongoDB virtual filesystem for LangChain Deep Agents?</h2><p>The <em>langchain-mongodb-deepagents-vfs</em> <a href="https://github.com/langchain-ai/langchain-mongodb/tree/main/libs/langchain-mongodb-deepagents-vfs#langchain-mongodb-deepagents-vfs">package</a> is a drop-in implementation of Deep Agents’ <em>BackendProtocol</em>. It presents an object store-backed corpus as a filesystem to the agent and routes operations to the system that is best suited for them:</p><ul><li><p>Search-oriented operations: <em>grep</em>, <em>glob</em>, and <em>ls</em> run with MongoDB Atlas.</p></li><li><p>File-byte operations: <em>read</em>, <em>write</em>, <em>edit</em>, <em>upload_files</em>, and <em>download_files</em> go directly to your object store.</p></li><li><p>A background synchronization layer keeps the MongoDB Search representation aligned with your object store.</p></li></ul><p>The result is a clean separation between the source of truth and the search index. Your object store owns the original documents. MongoDB Atlas stores the searchable chunks, embeddings, and path metadata needed to make the corpus discoverable.</p><p>It&#39;s worth asking why the search plane should be a separate system like Atlas rather than an S3-compatible platform that also offers search, vector search, and hybrid search on the same data. The two-plane split isn&#39;t a limitation; it&#39;s the point. Object storage is optimized for durable, low-cost, long-term storage of file bytes; it isn&#39;t built to maintain live indexes, rank hybrid queries, or serve low-latency structured metadata queries simultaneously. Atlas is built as an operational database with Search, Vector Search, and hybrid ranking as first-class, indexed capabilities, so the search plane runs on a system designed for exactly that job, while the object store keeps doing what it&#39;s already good at.</p><h3>Hybrid search for agent queries</h3><p>The package uses MongoDB Search and MongoDB Vector Search together for grep. Full-text search is good at exact terms, identifiers, filenames, and rare strings. Vector search is good at paraphrases and natural-language questions. Combining both signals lets an agent search for a literal token, such as <em>MAX_RETRIES</em>, or a conceptual question, such as &quot;where is retry behavior configured?&quot;, through the same interface.</p><p>The package combines the full-text and vector results with MongoDB’s <a href="https://www.mongodb.com/docs/manual/reference/operator/aggregation/rankfusion/"><em>$rankFusion</em></a> aggregation stage. This keeps ranking on the database side and avoids a separate client-side reranking layer, which would add an extra round trip between the agent and a separate reranking step. This also reflects a broader tradeoff in how the search plane is built. Getting full-text, vector, and hybrid ranking on an S3-compatible platform usually means wiring together separate specialized systems, a search engine for full-text, a vector database for embeddings, and a reranking layer to merge the two, each with its own indexing pipeline to keep in sync with the source data. Atlas runs all three in one engine, so $rankFusion can combine full-text and vector results natively in a single query instead of coordinating results across systems that don&#39;t know about each other.</p><p>The current implementation uses a token-aware chunking pipeline. Supported document formats include plain text and Markdown, PDFs, DOCX, XLSX, XLS, PPTX, and PPT. Chunks retain positional metadata such as source path, page number, character offsets, and line information, so results can be returned in a Deep Agents-compatible, line-oriented shape.</p><p>The default embedding path uses <a href="https://aws.amazon.com/bedrock/">Amazon Bedrock</a> embeddings, with an OpenAI option available through the package extras. Applications can also inject a LangChain-compatible embedding implementation directly.</p><p>A typical integration looks like this:</p><p>The agent can now use its normal filesystem tools without custom MongoDB or S3 tools in its reasoning loop.</p><h2>How the MongoDB VFS Backend separates storage and search</h2><p>The architecture can be understood as a two-plane system: object storage is the data plane for file bytes, while MongoDB Atlas is the control and search plane for metadata, chunks, and retrieval indexes.</p><p><strong>Figure 1.</strong> How the LangChain Deep Agents VFS backend routes file bytes through object storage and search operations through MongoDB Atlas.</p><h3>How the backend ingests files into MongoDB Atlas</h3><p>When <em>MongoFilesystemBackend</em> is constructed, initialization begins in the background. Index provisioning, the initial synchronization, and watcher startup run on a daemon thread. Pass-through file operations can be used immediately, while search operations wait until the initial synchronization is ready.</p><p>The ingestion path is:</p><ol><li><p>List objects in the configured S3 bucket and prefix.</p></li><li><p>Download each eligible object.</p></li><li><p>Extract text using the format-specific parser.</p></li><li><p>Split the text into chunks with positional metadata.</p></li><li><p>Generate embeddings.</p></li><li><p>Upsert chunks and metadata into MongoDB Atlas.</p></li><li><p>Provision or verify the MongoDB Search and Vector Search indexes.</p></li></ol><p>The current chunking strategy uses 512-token chunks with a 64-token overlap. ETags make initial sync and watcher ingestion idempotent: unchanged objects can be skipped rather than re-downloaded and re-embedded.</p><h3>How the backend routes file and search operations</h3><p>When the agent calls <em>ls</em>, the backend queries Atlas for path metadata and groups the results as directory entries. When it calls <em>glob</em>, the backend applies standard path-pattern semantics to find matching files. When it calls <em>grep</em>, Atlas combines full-text and vector retrieval over the chunk corpus and returns ranked matches.</p><p>When the agent calls <em>read</em>, the backend retrieves the current bytes from the object store rather than from the search index. That distinction is important: search results are optimized for discovery, while reads return the source document.</p><h3>How watchers keep the MongoDB Search Index current</h3><p>The package supports two watcher modes:</p><ul><li><p>Polling watcher: periodically checks the object store and requires no additional AWS event infrastructure. </p></li><li><p>SQS watcher: consumes S3 event notifications through <a href="https://aws.amazon.com/sqs/">Amazon SQS</a> and is intended for lower-latency production synchronization.</p></li></ul><p>The architecture is intentionally eventually consistent for search. A successful write reaches S3 first; the watcher then detects the change, re-chunks and re-embeds the object, and updates search indexes. As a result, <em>read</em> reflects the S3 state immediately, while <em>grep</em>, <em>glob</em>, and <em>ls</em> may lag until synchronization and search indexes are completed.</p><p>For collaborative workflows, this suggests a practical rule: use direct reads for hot shared state, use <em>edit</em> for optimistic concurrency on shared files, and use search for discovery across a settled corpus. Namespacing agent outputs, for example, <em>shared/outputs/&lt;agent_id&gt;/</em> can also reduce collisions between parallel workers.</p><h2>Enterprise use cases for a virtual filesystem backend</h2><h3>Codebase-aware coding agents</h3><p>A coding agent can explore a large repository progressively rather than receive a massive code dump. It can list the project structure, locate files with <em>glob</em>, search for a concept or identifier with hybrid <em>grep</em>, read the exact file, and apply an ETag-protected edit.</p><p>This pattern is useful for:</p><ul><li><p>Repository onboarding and code navigation</p></li><li><p>Incident investigation</p></li><li><p>Dependency and configuration analysis</p></li><li><p>Test discovery and targeted remediation</p></li><li><p>Documentation generation from source code</p></li></ul><h3>Private document intelligence</h3><p>Organizations often have large collections of policies, contracts, procedures, runbooks, product documents, and customer artifacts sitting in object storage. The backend provides an agent with a filesystem-like interface to that corpus.</p><p>For example, a document agent can search for &quot;refund policy for enterprise customers,&quot; locate the relevant passages even when the wording differs, read the source PDF or DOCX, and write a citation-ready summary or review artifact to a separate path.</p><p>This is a natural fit for <a href="https://www.mongodb.com/docs/vector-search/tutorials/rag/#std-label-avs-rag">retrieval-augmented generation</a> (RAG), where the agent needs to navigate rather than perform only one retrieval step.</p><h3>Multi-agent research and analysis</h3><p>A coordinator can delegate focused work to specialized subagents that share a common corpus:</p><ul><li><p>A security agent searches for dangerous code patterns.</p></li><li><p>A documentation agent finds deployment steps and configuration references.</p></li><li><p>A test agent locates relevant test files and produces coverage notes.</p></li><li><p>A synthesis agent reads the outputs and writes a consolidated report.</p></li></ul><p>The shared filesystem provides each subagent with a consistent namespace, while MongoDB provides an intelligent discovery layer over the corpus.</p><h3>Long-running monitoring over changing data</h3><p>Enterprise document stores are not static. New reports arrive, policies change, and operational artifacts are updated. The watcher keeps the MongoDB Search representation aligned with the underlying object store, so an agent invoked later can search the current corpus without rebuilding an index for every run.</p><p>This can support:</p><ul><li><p>Operational runbook assistants</p></li><li><p>Compliance and policy monitoring</p></li><li><p>Research assistants over continuously refreshed datasets</p></li><li><p>Support agents over product and troubleshooting documentation</p></li><li><p>Partner solution assistants over shared implementation artifacts</p></li></ul><h3>Durable workspaces for agent applications</h3><p>Deep Agents can create plans, intermediate notes, summaries, and generated deliverables as files. Persisting those artifacts in the object store while indexing them in Atlas gives an application a durable workspace that can survive process restarts and be inspected by people or other agents.</p><p>For production systems, access control, tenant isolation, data residency, retention, and audit requirements should be enforced through the application, storage configuration, and the metadata model. The current package’s core responsibilities are the Deep Agents-compatible filesystem contract and the Object Store-to-Atlas search path.</p><h2>How to contribute to the LangChain MongoDB integration</h2><p>The package lives in the <a href="https://github.com/langchain-ai/langchain-mongodb"><em>langchain-mongodb</em></a> repository, and contributions are welcome. Start with the repository contribution guidelines, then explore the package tests and the existing backend boundaries.</p><p>Potential contribution areas include:</p><ul><li><p>Additional object-store backends, such as Azure Blob Storage or Google Cloud Storage</p></li><li><p>New embedding providers and configurable embedding strategies</p></li><li><p>Additional document parsers and ingestion optimizations</p></li><li><p>Watcher reliability, backfill, and freshness improvements</p></li><li><p>Search quality, filtering, ranking, and metadata enhancements</p></li><li><p>Better examples, documentation, benchmarks, and deployment guidance</p></li></ul><p>A useful design principle is to keep storage-specific behavior behind the object-store interface. That allows the chunker, embedder, synchronization logic, and search router to remain focused on paths, bytes, metadata, and search rather than a particular cloud storage API.</p><h2>Key takeaways: A persistent virtual filesystem for LangChain Deep Agents</h2><p>LangChain Deep Agents provide an agent-native way to plan, delegate, navigate files, and produce durable work. The MongoDB virtual filesystem for LangChain Deep Agents connects that experience to an enterprise-friendly storage pattern: your object store remains the source of truth for file bytes, while MongoDB Atlas provides the metadata, full-text search, vector search, and hybrid ranking that agents need to find the right context.</p><p>The most important idea is the separation of concerns. Agents see one simple virtual filesystem. Applications can store large, heterogeneous documents in object storage. Atlas turns those documents into a searchable knowledge surface, and the synchronization layer keeps discovery aligned with the live corpus.</p>]]></description>
      <pubDate>Thu, 03 Sep 2026 14:14:39 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/technical/vfs-langchain-deep-agents-searchable-filesystem-agents</link>
      <guid>https://www.mongodb.com/company/blog/technical/vfs-langchain-deep-agents-searchable-filesystem-agents</guid>
    </item><item>
      <title>MongoDB 8.0: Raising the Bar</title>
      <description><![CDATA[<p>I recently received an automated reminder that I was approaching a work anniversary, which took me somewhat by surprise. It’s hard to believe that it’s already been a year (to the day) that <a href="https://www.mongodb.com/company/newsroom/press-releases/mongo-db-announces-jim-scharf-as-chief-technology-officer">I joined MongoDB</a>! So I thought I’d take a moment to reflect on my MongoDB journey so far, share some exciting product updates, and signal where we’re headed next.</p><h2>Our customers</h2><p>I joined MongoDB because it built a product developers love. The innovation of MongoDB’s document model empowered developers to simply build. No longer encumbered by having to formalize and denormalize their data schema before their application was even designed, MongoDB enabled developers to interact with data in an intuitive JSON format, and made it easy to evolve data structures as the life of their application evolved.</p><p>One of my first steps upon joining the company was to learn more about our customers. I was excited to learn that in addition to delighting developers, MongoDB had launched capabilities that enabled it to win mission-critical workloads from enterprise class customers—including 70% of the Fortune 100 and highly regulated global financial institutions, health care providers, and government agencies. I found it remarkable that customers could replicate data across AWS, Google Cloud, and Microsoft Azure in MongoDB Atlas (our fully-managed cloud database service) with just a few mouse clicks, and that some customers replicate data between the cloud and on premises using MongoDB Enterprise Advanced. This optionality struck me as powerful in the era of rapid advancements in AI, as it enables customers to easily bring their data to the best cloud provider for AI.</p><p>Soon after I joined MongoDB, the team was firming up the development roadmap for the next version of MongoDB, and they asked for my input on the plan. The team was debating whether to focus on features developers would love, or governance capabilities required by large enterprises. I knew that ideally we would please all of our customers, so we had to try to make this an “and” and not an “or.” While I was new to MongoDB, from my 17+ years at AWS I learned that all customers demand security, durability, availability, and performance (in that order) from any modern technology offering. If a product or service doesn’t have those four elements, customers won’t buy whatever you’re selling. So as a team, we agreed that our next release of MongoDB—MongoDB 8.0—had to raise the bar for all of our customers, delivering great security, durability, availability, and performance.</p><h2>The plan</h2><p>We had less than a year before our target launch, so we knew we had to get moving, fast. My team and I brought MongoDB’s product and engineering organizations together to align on the plan for our next release. We set goals around delivering significant improvements in security, durability, and availability. And we set a line in the sand—that we weren’t going to release MongoDB 8.0 unless it was the best-performing version of MongoDB yet.</p><p>Measuring the performance of a feature-rich database like MongoDB can be tricky, as customers run a wide range of workloads. So we decided to run a suite of benchmarks to simulate customer workloads. We also developed <a href="https://en.wikipedia.org/wiki/Andon_(manufacturing)">Andon cord</a>-inspired automation that would automatically roll back any code contributions that regressed our performance metrics. Finally, a set of senior engineering leaders met regularly to review our progress and immediately escalated any blockers that could jeopardize our launch, so that we could quickly fix things.</p><p>From my experience, I knew that great teams really respond when they’re given clear goals, and when they’re empowered to innovate, so I was excited to see what they would come up with. I’m proud to say that our product and engineering teams rose to the challenge.</p><h2>Announcing MongoDB 8.0</h2><p>Today, I’m thrilled to announce <a href="https://www.mongodb.com/products/updates/version-release">the general availability of MongoDB 8.0</a>—the most secure, durable, available, and performant version of MongoDB yet! The team came up with architectural optimizations in MongoDB 8.0 that have significantly reduced memory usage and query times, and have made batch processing more efficient than previous versions.</p><p>Specifically, MongoDB 8.0 features:</p><ul><li><p>36% better read throughput</p></li><li><p>56% faster bulk writes</p></li><li><p>20% faster concurrent writes during data replication</p></li><li><p>200% faster on complex aggregations of times series data</p></li></ul><p>In making these improvements, we&#39;re seeing benchmarks for typical web applications perform 32% better overall. Here’s a breakdown of how MongoDB 8.0 performs against some of our benchmarks:</p><p>Improved performance benefits all users of applications built atop MongoDB, and for MongoDB customers, it can mean reduced costs (due to an improved price/performance ratio).</p><p>In addition to significant performance gains, MongoDB 8.0 delivers a wide range of improvements, including (but not limited to):</p><ul><li><p>Improving availability by delivering sharding enhancements to distribute data across shards up to 50 times faster and at up to 50% lower starting cost, with reduced need for additional configuration or setup.</p></li><li><p>Improving support for a wide range of search and AI applications at higher scale and lower cost, via the delivery of quantized vectors—compressed representations of full-fidelity vectors—that require up to 96% less memory and are faster to retrieve while preserving accuracy.</p></li><li><p>Enabling customers to encrypt data at rest, in transit, and in use by expanding MongoDB’s Queryable Encryption to also support range queries. Queryable Encryption is a groundbreaking, industry-first innovation developed by the MongoDB Cryptography Research Group that allows customers to encrypt sensitive application data, store it securely as fully randomized encrypted data in the MongoDB database, and run expressive queries on the encrypted data—with no cryptography expertise required.</p></li></ul><p>You might wonder why we’re so confident that customers are going to love MongoDB 8.0. Well, we’ve been acting as our own customer, and have moved our own applications over to 8.0. This approach is generally called “<a href="https://en.wikipedia.org/wiki/Eating_your_own_dog_food">dogfooding</a>,” but we think that “eating our own pizza” sounds more appetizing. Our internal build system—which our software developers use daily—is built atop MongoDB, and when we upgraded to MongoDB 8.0 we saw query latencies drop by approximately 75%! This was a double win, as it improved the performance of our own tooling, and it set our performance chat room abuzz with excitement in anticipation of delighting external customers. While results may vary based on your particular workload, the point is that we just couldn’t wait to share MongoDB 8.0’s performance gains with customers.</p><p>Indeed, customers are also already seeing great results on MongoDB 8.0. For example, Felix Horvat, Chief Technology Officer at <a href="https://www.ocell.io/en-us/about-us">OCELL</a>, a climate technology company in Germany, said: “With MongoDB 8.0, we have seen an incredible boost in performance, with some of our queries running twice as fast as before. This improvement not only enhances our data processing capabilities but also aligns perfectly with our commitment to resource efficiency. By optimizing our backend operations, we can be more effective in our climate initiatives while conserving resources—a true reflection of our dedication to sustainable solutions.”</p><p>I encourage you to <a href="https://www.mongodb.com/products/updates/version-release">check out MongoDB 8.0</a> yourself. It’s available today via MongoDB Atlas, as part of MongoDB Enterprise Advanced for on-premises and hybrid deployments, and as a free download from <a href="https://www.mongodb.com/try">mongodb.com/try</a> with MongoDB Community Edition. In addition, customers upgrading from previous versions of MongoDB to 8.0 can find helpful <a href="https://www.mongodb.com/docs/manual/tutorial/upgrade-revision/">upgrade guides</a> on mongodb.com.</p><h2>What’s next?</h2><p>We’re excited for you to try MongoDB 8.0 and to share your feedback, as customer feedback helps us guide our roadmap for future releases.</p><p>Going forward, please watch this space. Over the next few weeks, we’ll be publishing a series of engineering blog posts that dig into MongoDB’s investments in the technology behind MongoDB 8.0. We’re also planning posts about horizontal scaling in MongoDB 8.0, and one that will look closely at <a href="https://www.mongodb.com/resources/products/capabilities/queryable-encryption-technical-paper">queryable encryption</a> (QE), but let me know what you’d like to hear more about.</p><p>It’s been an exciting year at MongoDB—I can’t wait to see what the next one has in store!</p><p>–Jim</p>]]></description>
      <pubDate>Tue, 01 Sep 2026 14:03:10 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/engineering/mongodb-8-0-raising-the-bar</link>
      <guid>https://www.mongodb.com/company/blog/engineering/mongodb-8-0-raising-the-bar</guid>
    </item><item>
      <title>The Shared View That Makes Insurance AI Fast and Safe</title>
      <description><![CDATA[<p>When a carrier can reduce a routine claims review from eight hours to eight minutes using AI, the era of &quot;wait and see&quot; has officially ended. Why? Agentic AI, technology that doesn&#39;t just answer questions but actively executes tasks, is transforming and speeding up claims processing, underwriting, and customer service. For insurance leaders, the question is no longer whether to adopt these autonomous agents; it’s how to deploy them without turning their existing data silos into operational liabilities.</p><p>This is why the real breakthrough in agentic AI for insurance isn&#39;t the technology itself. It&#39;s how you pair it with the right data architecture, one built to give agents and humans a single, current view of the business, which is exactly what <a href="https://www.mongodb.com/products/platform/atlas-database">MongoDB Atlas</a> is designed to do.</p><h2>Scattered systems, slower decisions</h2><p>That question of deploying <a href="https://www.mongodb.com/docs/vector-search/about/ai-agents/">agentic AI</a> matters because most insurance teams already operate on fragmented data. Policy details sit in one system. Claims history lives in another. Customer conversations get buried in email threads and spreadsheets that only one person understands. Fragmentation slows down everyday tasks and forces professionals to spend their time hunting for information instead of using it.
Adding AI agents to a fragmented environment doesn’t solve the problem—you just multiply it by adding another disconnected system. An agent with its own isolated copy of policy and claims data might move fast, but it’s working with an incomplete view that, with time, will show declining performance. The gap between what the agent sees and what your team sees becomes yet another problem.
This is why the real breakthrough in agentic AI for insurance isn&#39;t the technology itself. It&#39;s how we pair it with the appropriate data architecture that powers it.
Getting this right can lead to something similar to a control center for agentic operations. This would exist in a single environment where AI agents and human teams draw from the same shared context layer instead of a dozen disconnected sources. Every policy detail, every claim update, and every customer interaction lives in one place where people and AI agents read from and write to that same living record. The technical details are not that important. The impact, on the other hand, shows that developing a control center delivers both speed and safety.
<strong>Figure 1. </strong>The transition from fragmented data silos to a unified agentic control center.
</p><h2>Creating a single source of truth with MongoDB</h2><p>MongoDB Atlas powers this shared “control center” view by storing policy data, claims records, and the context layer that AI agents rely on, all in a single platform. MongoDB&#39;s flexible document model is built for exactly this kind of variety. Agent conversations, human approvals, and manual edits all differ in shape and detail, but they can live side by side in the same collection without forcing every entry into rigid, matching columns. </p><p>That flexibility means insurers can add new agents, new data types, and new use cases without redesigning their data architecture each time. In an era where the shape of your data changes constantly, whether it&#39;s a new agent&#39;s memory or a new claim field, that adaptability is the difference between a platform that keeps pace with AI and one that becomes the next bottleneck.</p><h2>A blueprint for the future of insurance operations</h2><p>When AI agents and your team share one source of truth, three critical advantages emerge:</p><ul><li><p><strong>Accelerated resolution:</strong> Information no longer travels through disparate systems to get resolved. An AI agent retrieves a policy, claims history, and prior conversation in a single motion. Your staff stops re-entering the same data across multiple platforms because it all lives on one platform.</p></li><li><p><strong>Seamless human oversight:</strong> A shared context layer keeps human decision-making built directly into agentic workflows. When an AI agent recommends a next step, a human reviewer evaluates it against the same record the agent used—not a separate, potentially outdated version. This shared visibility lets insurance teams safely hand routine work to AI agents while keeping high-stakes decisions—such as large payouts, coverage disputes, and policy modifications—firmly in human hands.</p></li><li><p><strong>Built-in compliance:</strong> When agents and people work from a single shared record, it creates an automatic trail of who performed what actions. It’s not a separate audit system layered on top of your workflow; it exists simply because all the work happens in one unified place.</p></li></ul><p><strong>Figure 2.</strong> Technical architecture of the agentic control center, featuring unified memory and database integration.</p><p>That&#39;s the real story behind agentic AI adoption in insurance. It isn&#39;t about choosing between moving fast and staying in control. A single shared view, powered by a unified context layer, delivers both. Insurers who build on this foundation position themselves to scale AI agents across claims, underwriting, and customer service without sacrificing the oversight that regulators, customers, and their own leadership expect. </p><p>As AI adoption accelerates across every industry, the companies that invest in the right data foundation now will be able to deploy AI agents safely and efficiently, at scale, for years to come.</p>]]></description>
      <pubDate>Tue, 01 Sep 2026 14:00:01 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/shared-view-that-makes-insurance-ai-fast-safe</link>
      <guid>https://www.mongodb.com/company/blog/innovation/shared-view-that-makes-insurance-ai-fast-safe</guid>
    </item><item>
      <title>The Cheapest Token You Never Send: Agentic AI Search on MongoDB + Voyage AI</title>
      <description><![CDATA[<h2>TL;DR</h2><p>The most expensive part of a production agentic AI application usually isn&#39;t the model you call — it&#39;s what you feed the model. Every chunk of retrieved context is an input token you pay for on every request, and low-relevance context doesn&#39;t just cost money; it <em>dilutes</em> the answer. This post walks through an agentic AI search pipeline built on <a href="https://www.mongodb.com/products/platform/atlas-vector-search">MongoDB Vector Search</a> and <a href="https://www.mongodb.com/products/platform/ai-search-and-retrieval">Voyage AI </a>embeddings and re-rankers, and shows how each stage — embed, retrieve, rerank, iterate — simultaneously lowers token cost, speeds up search, and improves answer quality. The through-line is simple: better retrieval is the cheapest lever you have.</p><h2>1. The hidden token tax in AI search</h2><p>A typical first-generation AI search app works like this: embed the user&#39;s question, pulls back the top <em>N</em> nearest chunks, staples them into the prompt, and sends it all to the LLM. It works in a demo. Then it hits production, and three problems show up at once:</p><ul><li><p><strong>Cost:</strong> If you retrieve 20 chunks of ~500 tokens each &quot;to be safe,&quot; you&#39;re paying for ~10,000 input tokens on <em>every</em> call — most of which the model doesn&#39;t need.</p></li><li><p><strong>Latency:</strong> Bigger prompts take longer to transmit and process, and a bolt-on vector database adds network hops and a second system to keep in sync.</p></li><li><p><strong>Quality:</strong> Counterintuitively, <em>more</em> context often produces <em>worse</em> answers. Irrelevant passages bury the signal, and models are prone to &quot;lost in the middle&quot; effects, where key facts in a long context get ignored.</p></li></ul><p>These aren&#39;t three separate problems. They&#39;re one problem — retrieval precision — viewed from three angles. Fix retrieval, and all three improve together. That&#39;s the opportunity, and it&#39;s what turns basic keyword lookup into true <em>agentic AI search</em>: a system that reasons about what to retrieve, retrieves precisely, and acts on it.</p><h2>2. The pipeline at a glance</h2><p>Here&#39;s the shape of a cost-efficient agentic AI search pipeline where the operational data, the vector index, the metadata, and even the embedding and reranking calls all live in one platform:</p><p>The key architectural idea: consolidation. Because MongoDB stores your application data, the vector embeddings, and the metadata together — and Voyage AI&#39;s industry-leading embedding and reranking models are available natively on Atlas via the <a href="https://www.mongodb.com/company/blog/product-release-announcements/introducing-the-embedding-and-reranking-api-on-mongodb-atlas">Embedding and Reranking API</a> — you avoid the data-sync pipelines, extra network round-trips, and glue code that come with bolting a separate vector database onto your primary store.</p><p>Let&#39;s walk the pipeline stage by stage and look at where the tokens (and milliseconds, and dollars) actually go.</p><h2>3. Stage 1 — Embeddings that cost less to store and query</h2><p>Retrieval quality starts with the embedding model, but <em>cost</em> at scale starts with how those vectors are stored. Two Voyage AI + MongoDB capabilities matter here.</p><p><strong>Flexible dimensionality.</strong> Voyage AI text embedding models support a range of output dimensions (from 256 up to 2048), so you can trade a little accuracy for a lot of index footprint when your workload needs it. See the <a href="https://www.mongodb.com/docs/voyageai/models/">Voyage models overview</a> for the current lineup.</p><p><strong>Automatic quantization.</strong> MongoDB Vector Search can automatically quantize float embeddings to compact int8 (scalar) or binary representations directly in the index — you just declare it, and both your stored vectors and incoming query vectors are quantized at query time with no change to your query code. Per the <a href="https://www.mongodb.com/docs/atlas/atlas-vector-search/vector-quantization/">Vector Quantization docs</a>, scalar quantization reduces RAM usage by roughly 3.75x and binary by roughly 24x. Less RAM per vector means more vectors per node, lower cost, and faster search.</p><p><em>(Automatic quantization requires MongoDB 8.0 or later.)</em> For a deep dive on the accuracy/performance trade-offs of each quantization type, see <a href="https://www.mongodb.com/company/blog/technical/scaling-vector-search-mongodb-atlas-quantization-voyage-ai-embeddings">Scaling Vector Search With MongoDB Atlas Quantization &amp; Voyage AI Embeddings</a>.</p><h2>4. Stage 2 — Faster, more precise candidate retrieval</h2><p>Semantic (vector) search is great at meaning but can miss exact keywords, product codes, or names. Lexical (full-text) search nails those but misses paraphrases. Running them separately and merging results in your app is slow and awkward.</p><p>MongoDB does this in a <strong>single query</strong> with the <em>$rankFusion</em> aggregation stage, which implements Reciprocal Rank Fusion (RRF) natively — combining a <em>$vectorSearch</em> pipeline and a full-text <em>$search</em> pipeline server-side:</p><p>Two token-and-latency wins here. First, one round-trip instead of two systems and a client-side merge. Second — and this is easy to overlook — you can attach <strong>metadata filters</strong> (tenant, date range, document type) so you never even retrieve, embed-compare, or pay to process data that couldn&#39;t be relevant. For more on hybrid search, see <a href="https://www.mongodb.com/company/blog/technical/harness-power-atlas-search-vector-search-with-rankfusion">Harness the Power of Atlas Search and Vector Search with $rankFusion</a>.</p><p>At this stage, we deliberately retrieve <em>broadly</em> — a generous candidate set optimized for recall. We&#39;ll tighten it in the next stage, cheaply.</p><h2>5. Stage 3 — Reranking to shrink the context window</h2><p>This is where the token savings become dramatic.</p><p>A reranker takes the broad candidate set from Stage 2 and reorders it by true relevance to the query using a more powerful cross-encoder model, then you keep only the top few. Voyage AI rerankers are available natively on Atlas through the same Embedding and Reranking API, so this is one call, not another vendor integration.</p><p>The pattern is <strong>retrieve broad, rerank sharp, send small</strong>:</p><p>Because the reranker runs against candidates you&#39;ve already narrowed with quantized vector search and metadata filters, it&#39;s operating on a small set — so it&#39;s fast — and its output lets you cut the LLM&#39;s input context by a large factor. Fewer input tokens, lower latency, and typically a <em>better</em> answer because the model isn&#39;t wading through noise. For the retrieval-quality rationale behind this approach, see <a href="https://www.mongodb.com/company/blog/engineering/rethinking-information-retrieval-mongodb-with-voyage-ai">Rethinking Information Retrieval in MongoDB with Voyage AI</a>.</p><p><strong>Note:</strong> Voyage AI&#39;s current recommended reranker is <a href="https://www.mongodb.com/docs/voyageai/models/rerankers/">rerank-2.5</a> (32K token context), with <em>rerank-2.5-lite</em> available for latency-sensitive workloads.</p><h2>6. Stage 4 — The agentic loop</h2><p>This is what makes the search <em>agentic</em> rather than a single retrieve-then-answer pass. An <strong>agent</strong> decides <em>whether</em> it needs to retrieve, issues one or more retrieval tool calls, evaluates what it got back, and only then generates, sometimes looping to refine the query. Search becomes an action the agent takes and reasons over, not a fixed preprocessing step.</p><p><strong>Figure 2. </strong>The agentic AI search loop on MongoDB Atlas for efficient, iterative retrieval.</p><p>This loop is exactly where a consolidated data platform pays off. Every iteration of the loop is a round-trip; when your operational data, vectors, metadata, embeddings, and reranking all live in Atlas, each iteration is fewer network hops and less glue code than coordinating a separate vector store, a separate embedding service, and a separate reranking service. Fewer, sharper retrievals per loop also mean fewer tokens burned per agent step — and agent steps compound.</p><h2>7. Putting it together: an illustrative token-cost example</h2><p>The numbers below are <strong>illustrative arithmetic</strong>, not a benchmark — plug in your own chunk sizes, model, and pricing.</p><p>Say each retrieved chunk is ~500 tokens, and you make 100,000 agentic search calls a month:</p><p>That&#39;s an <strong>80% reduction in retrieved-context input tokens</strong> in this illustration — before counting the latency win from smaller prompts and the quality win from removing noise. The reranking call itself has a cost, but it operates on a small candidate set and is typically a small fraction of what you save on the LLM&#39;s input tokens. The exact ratio depends on your models and pricing; the <em>direction</em> is reliable.</p><h2>8. When to reach for what</h2><h2>9. Wrap-up</h2><p>Token cost, latency, and answer quality in an agentic AI search system are not three problems — they&#39;re one problem, retrieval precision, wearing three hats. By treating the pipeline as a cost-optimization system rather than a pile of features, you can attack all three at once:</p><ul><li><p><strong>Embed and quantize</strong> so vectors cost less to store and search.</p></li><li><p><strong>Hybrid retrieve</strong> in one query, with metadata filters so you never pay to process irrelevant data.</p></li><li><p><strong>Rerank and send small</strong> so the LLM gets a tight, high-signal context — the single biggest token-cost lever.</p></li><li><p><strong>Loop agentically</strong> over a consolidated platform so each step has fewer hops and less glue.</p></li></ul><p>The cheapest token, and the one least likely to mislead your model, is the one you never send.</p>]]></description>
      <pubDate>Mon, 31 Aug 2026 12:08:40 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/technical/cheapest-token-you-never-send-agentic-ai-search-on-mongodb-voyage-ai</link>
      <guid>https://www.mongodb.com/company/blog/technical/cheapest-token-you-never-send-agentic-ai-search-on-mongodb-voyage-ai</guid>
    </item><item>
      <title>Beyond the Cloud: Building an Offline-First Mobile Wallet with MongoDB Atlas and ObjectBox</title>
      <description><![CDATA[<p>The global transition toward a digital-first economy has a critical blind spot: the assumption of continuous, high-speed internet. From subterranean transit systems to rural geographies with spotty coverage, network dependency leaves users stranded and halts commerce.</p><p>Yet for mobile banking apps to work, they assume a network exists and is accessible. If you lose signal on a subway, in a rural area, or on a flaky connection, most wallet apps simply stop working. Balances won&#39;t load, payments can&#39;t be reviewed, and support chat goes silent. Unlike death and taxes, connectivity is not guaranteed. </p><p>For financial services, that&#39;s a real gap. Money doesn&#39;t stop being useful just because the phone loses bars. A new wallet solution that combines <a href="https://www.mongodb.com/products/platform/atlas-database">MongoDB Atlas</a> with an on-device ObjectBox shows that connectivity can be treated as an enhancement rather than a requirement that keeps working,even when the device briefly stops talking to the network.</p><h2>What the wallet solution can offer</h2><p>This solution is a full personal-wallet experience built on MongoDB Atlas: Users can sign in with SSO, check balances and transaction history, send and request money, manage contacts, receive payment notifications, and chat with an AI assistant that answers questions about spending and drafts payments for confirmation.</p><p>Rather than treating network connectivity as a strict requirement, the solution treats it as an enhancement. MongoDB Atlas serves as the core foundation of the application, allowing the experience to remain operational during brief periods of disconnection, with local data access and seamless synchronization when connectivity returns. </p><p><strong>Figure 1.</strong> High-level architecture of the solution.</p><h2>Why offline-first is hard for a mobile wallet</h2><p>Payments aren&#39;t like a to-do list; you can&#39;t just let a write happen locally and figure out consistency later. A wallet has to answer three hard questions while offline:</p><ol><li><p>Where does <em>the data</em> live if the network is gone?</p></li><li><p> What happens to money movements made while offline, once you&#39;re back online—do they get lost, duplicated, or replayed twice?</p></li><li><p>How does an AI assistant answer questions about my spending if the device suddenly has no internet connection?</p></li></ol><p>The answer to all three starts with one idea: Don&#39;t fake offline support by caching a few screens. Give the device a real, queryable database that mirrors MongoDB Atlas.</p><h2>Wallet solution architecture: PSP, MongoDB Atlas, and Objectbox working as one system</h2><p>The architecture of this offline-first wallet demo brings together three core technologies: an external payment platform (PSP), MongoDB Atlas, and ObjectBox. Each plays a distinct role in the system: </p><ul><li><p>The PSP executes real transactions in a BIAN-compliant way and protects sensitive payment data. </p></li><li><p>MongoDB Atlas provides the cloud data foundation and source of truth for the application’s enrichment layer. </p></li><li><p>ObjectBox powers the on-device operational store, so the wallet remains responsive and usable even when connectivity is limited.</p></li></ul><p>Together, these three components form a mirror architecture. This design works well for three reasons:</p><ul><li><p>MongoDB Atlas acts as a replicated database that powers the chatbot when online, leveraging MongoDB’s full performance to deliver accurate, optimized responses.</p></li><li><p>ObjectBox is a full local database running on the device, with the exact same schema as MongoDB Atlas. That means all the data—every screen, the balance, the transaction list, and the contacts—looks and works exactly the same whether it came from the phone (offline) or from the cloud (online).</p></li><li><p>The ObjectBox Sync Server bridges these two components continuously in the background. The syncing device writes up to MongoDB Atlas and streams cloud changes back down via its native MongoDB connector.</p></li></ul><p>Because ObjectBox and MongoDB Atlas remain in sync, the data stays up to date no matter which platform answers a question. That&#39;s what lets the AI assistant respond with high accuracy without merging collections or transforming data to piece together the full context of a user&#39;s wallet. MongoDB&#39;s document model is built to support smart queries like that out of the box.</p><h2>Where MongoDB Atlas actually shines</h2><p>There are two key ways in which MongoDB really works to make this offline model successful. First, it ensures atomic writes with the document model. </p><p>Each transfer&#39;s core data and its enrichment, the note, its embedding, and the sync status live in a single MongoDB document instead of being split across collections that need to be kept in lockstep. That single-document write is atomic. You&#39;ll never see a transfer marked settled with a stale note or embedding, or the reverse. It also keeps reads simple: the AI assistant pulls one document per transfer instead of joining several. </p><p>Next, MongoDB allows for hybrid search to work online and vector search to perform on the device. For example, when sending money, users can attach a short note to the transaction, like “dinner with Luis,” or “rent split.” Finding a note later isn&#39;t always a matter of exact keywords. You might remember “that dinner with Luis last month,” without recalling how you phrased it, or you might type the exact word you used. </p><p>Instead of choosing between keyword search and semantic search, the solution combines both. Every note is embedded with a local embedding model, and when the user is online, MongoDB Atlas runs a hybrid search. This is a single <em>$rankFusion</em> stage that blends a semantic match against the note&#39;s embedding with a lexical, full-text match against its exact words, weighted equally. </p><p>When a connection is lost, however, ObjectBox falls back to its on-device HNSW vector search alone, since the device has no lexical index to fall back on. Either way, the user and the AI assistant never have to know which one to run.</p><h2>The edge engine: Why ObjectBox?</h2><p>Traditional mobile apps are often entirely dependent on the cloud, causing them to stall or crash the moment they lose a connection. To eliminate this connectivity gap, the solution is integrated with ObjectBox to ensure full functionality stays available in offline mode. Through that, it offers four guarantees:</p><ul><li><strong>Personal data guardrails by design</strong>. ObjectBox runs natively on the device, holding a local copy of the user&#39;s balance, contacts, chat history, and transaction log, all keyed by design to avoid raw personally identifiable information (PII). Contacts, for example, are matched by a blind index rather than a stored email address, so what lives on the phone is enrichment data, not identity data.</li><li><strong>Always-on functionality</strong>. This solution is designed to keep working without a network, which means the device can read and write its own data at any time, with no round-trip to the cloud required. Therefore, it feels fast and keeps functioning flawlessly in airplane mode, not just sort of working with a spinner.</li><li><strong>A safeguard against overspending offline</strong>. Before any send, online or offline, the wallet checks the requested amount against the last-synced balance and blocks the send if funds don’t exist. It&#39;s a simple check: Don&#39;t let the device authorize money it can&#39;t yet confirm the user has.</li><li><strong>Automatic, conflict-aware sync</strong>. Once the user regains a signal, the ObjectBox Sync Server automatically picks up where it left off. Queued sends, new contacts, and chat messages all stream up to MongoDB Atlas without any action from the user. No refresh button, no manual retry, just a quiet catch-up. </li></ul><h2>Integration with the payment provider ensures consistent compliance</h2><p>The demo solution doesn&#39;t move money or own identity. Balances, transfers, and registered users remain in the external, BIAN-compliant payment platform (PSP). The application connects only as an OAuth merchant client and never holds a copy of the ledger.</p><p>This boundary applies online and offline: The solution does not expose sensitive financial data. MongoDB Atlas and on-device ObjectBox store only non-financial enrichment data, notes, aliases, embeddings, and sync metadata, linked to PSP reference IDs rather than balances or card data.</p><p>Contact lookups also preserve privacy. Instead of storing raw email addresses, the demo uses MongoDB Queryable Encryption to protect lookup data and query it without exposing plaintext addresses.</p><p>All of these security and compliance features are seamless from the user&#39;s perspective. The solution remains focused on making everyday payments and requests easier, even when the user is offline.</p><h2>What security best practices are implemented?</h2><p>The system enforces end-to-end security measures across authentication, session management, and data storage:</p><ul><li><p><strong>OAuth 2.0 with PKCE (S256)</strong>: The solution uses the PSP&#39;s hosted login and never sees or stores passwords. PKCE prevents intercepted authorization codes from being reused.</p></li><li><p><strong>Short-lived encrypted sessions</strong>: The app keeps only an HTTP-only cookie encrypted with AES-256-GCM, avoiding a long-lived server-side session store.</p></li><li><p><strong>Passwordless re-entry</strong>: A non-extractable WebCrypto key is generated on-device; only its public key is registered with the PSP. OpenID CIBA enables re-authentication without passwords or OTPs.</p></li><li><p><strong>Scoped access</strong>: The app receives only the read/write access required for beneficiaries, transfers, accounts, and transactions.</p></li><li><p><strong>Encrypted enrichment data</strong>: MongoDB Atlas and ObjectBox contain no financial data, and lookup values are protected with MongoDB Queryable Encryption rather than stored in plaintext.</p></li></ul>]]></description>
      <pubDate>Thu, 27 Aug 2026 14:00:01 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/beyond-cloud-building-an-offline-first-mobile-wallet-atlas-objectbox</link>
      <guid>https://www.mongodb.com/company/blog/innovation/beyond-cloud-building-an-offline-first-mobile-wallet-atlas-objectbox</guid>
    </item><item>
      <title>MongoDB Atlas Joins Google Cloud Foundation Fabric (FAST): Secure Private Data Infrastructure in Minutes</title>
      <description><![CDATA[<p>Transitioning from on-premises infrastructure to the cloud can be challenging. Many organizations lack a clear understanding of cloud fundamentals, and establishing a foundational environment is often complex and time-consuming. For every enterprise in particular, security is a critical priority and must be robustly implemented from the outset. Additionally, for new teams building applications, the initial setup presents significant difficulties, as they may not have clear guidance on the precise steps required to create a secure and reliable cloud environment.</p><p>This is where alignment with the Google Cloud architecture framework becomes vital. Without a structured approach, organizations risk &quot;technical debt&quot; in their IAM hierarchy and network topology that is difficult to unwind later. These fundamental challenges are resolved by <a href="https://github.com/GoogleCloudPlatform/cloud-foundation-fabric/tree/master"><strong>Google Cloud Foundation Fabric</strong></a>, which offers an <a href="https://github.com/GoogleCloudPlatform/cloud-foundation-fabric/blob/master/fast"><strong>organization-wide landing zone toolkit</strong></a> designed specifically for this purpose. This toolkit is a reference implementation that dramatically accelerates the often time-consuming process of establishing a production-ready Google Cloud organization. It provides a comprehensive, pre-configured landing zone that includes the typical foundational elements required by enterprise customers, allowing them to bootstrap their cloud foundation quickly and securely. Crucially, Cloud Foundation Fabric follows a &quot;GitOps&quot; methodology, meaning your entire cloud foundation—from folders to firewall rules—is version-controlled, auditable, and immutable. By bridging infrastructure automation with enterprise-grade data services, this integration ensures that your landing zone isn&#39;t just a secure network shell, but a fully production-ready application environment. It drastically reduces the time required to stand up a compliant, fully functional enterprise platform from weeks to minutes, allowing internal development teams to get to work immediately. </p><p><strong>Figure 1.</strong> MongoDB as a art of the Google Cloud Foundation Fabric.</p><h2>New: A MongoDB Atlas module for FAST</h2><p>A powerful new s<a href="https://github.com/GoogleCloudPlatform/cloud-foundation-fabric/tree/master">olution</a> is now available within our Terraform Examples and Modules for Google Cloud repository: the dedicated module for <a href="https://cloud.google.com/mongodb">MongoDB Atlas</a>.</p><p>The core mission of the FAST framework is now powerfully supported by the addition of the MongoDB Atlas module, offering a significant advantage for users by providing a robust Solution that addresses critical cloud adoption needs. This module enables Seamless Data Infrastructure Deployment by incorporating MongoDB Atlas directly into the FAST framework, allowing customers to provision their critical data infrastructure with the toolkit&#39;s signature speed and adherence to enterprise best practices. </p><h2>Security by design with Private Service Connect (PSC)</h2><p>Crucially, it ensures Security by Design through the use of Private Service Connect (PSC). For GCP Solution Architects, the shift from VPC Peering to PSC is a significant architectural upgrade. Unlike peering, PSC consumes no IP address space in your VPC (avoiding CIDR conflict issues), respects project boundaries by design, and eliminates the complexity of transitive routing rules. It creates a unidirectional, consumer-producer relationship that strictly controls data egress. This guarantees that Google Cloud resources connect to the MongoDB Atlas deployment privately and securely, making it an integral and easily provisionable element of the foundational build-out. Furthermore, by routing traffic strictly over Google’s private global fiber network, PSC bypasses the public internet entirely. This setup integrates seamlessly with Google Cloud KMS for Customer-Managed Encryption Keys (CMEK) and Client-Side Field Level Encryption (CSFLE), providing uncompromising data privacy and sovereignty. By coupling this with Google Cloud Service Directory, application teams benefit from native, zone-aware routing and managed endpoint rotation, eliminating complex internal DNS forwarding.</p><p>This Expanded Foundation broadens our existing comprehensive suite of modules—covering foundational, networking, compute, and data components—making it simpler than ever to provision secure, high-performance NoSQL databases as a fundamental part of a Google Cloud organization&#39;s initial structure.</p><p>In essence, the addition of the MongoDB Atlas module to FAST ensures that foundational build-out, cloud security, and critical data service provisioning can all be achieved with maximum efficiency and confidence, solving the initial adoption and setup challenges for all users.</p><h2>Connecting to Google Cloud&#39;s data and AI ecosystem</h2><p>Once your secure foundation and MongoDB Atlas cluster are established, they serve as the ultimate launching pad for Google Cloud’s premier data and AI ecosystem </p><ul><li><p>Real-Time Analytics (Datastream &amp; BigQuery): Seamlessly pipe operational data from Atlas into BigQuery using the Datastream source connector for MongoDB. This enables real-time Operational Analytics and Change Data Capture (CDC) utilizing BigQuery’s native JSON functions—without complex, manual ETL pipelines.</p></li><li><p>Generative AI &amp; Agentic Memory: Power your GenAI workloads by using Atlas Vector Search integrated with Vertex AI. MongoDB Atlas serves as the foundational, long-term memory layer for autonomous agents built on the Vertex AI Agent Development Kit (ADK), transforming operational data into context-aware, production-grade actions.</p></li><li><p>Firebase Developer Agility: For mobile and web developers, the Firebase Extension for MongoDB Atlas allows one-click synchronization and immediate vector search deployment, offloading backend complexity.</p></li></ul><p>This ensures that your foundational build-out is directly aligned with your long-term modernization and AI strategy. </p><h2>What the module automates</h2><p>We&#39;ve made the setup process incredibly straightforward. This simple configuration allows you to:</p><ol><li><p>Create and set up a managed <a href="https://cloud.google.com/mongodb"><strong>MongoDB Atlas cluster</strong></a>.</p></li><li><p>Connect that cluster directly to your local Google Cloud Virtual Private Cloud (VPC) network using <strong>Private Endpoints</strong> (which leverage <a href="https://docs.cloud.google.com/vpc/docs/private-service-connect">Private Service Connect</a>).</p></li><li><p>Automatically register these endpoints with Google Cloud Service Directory, ensuring that your applications can resolve and reach the database using internal DNS names without complex forwarding rules.</p></li></ol><h2>Preparing your Google Cloud project</h2><p>Before you hit &#39;deploy,&#39; you need to ensure your Google Cloud Project is ready. The included <em>project.yaml</em> file acts as your checklist: </p><ul><li><p><strong>API Activation:</strong> Check the list of APIs under the services section and make sure they are enabled in your project.</p></li><li><p><strong>Permissions (IAM):</strong> The permissions listed under iam must be granted to the user or service account running the Terraform code. Specifically, servicedirectory.admin is required to allow the Terraform provider to register the PSC endpoint for DNS resolution.</p></li></ul><p>All the major adjustments are handled through two main variables: <em>atlas_config</em> and <em>vpc_config</em>. Here are the important things to keep in mind:</p><ul><li><p><strong>VPC Flexibility:</strong> The <em>vpc_config</em> can point to a <strong>Shared VPC Host network</strong> (as shown in the examples) or a standard network located within your project. Using a Shared VPC is the recommended pattern for enterprise landing zones, as it centralizes network administration while delegating application management to the service projects. This pattern is supercharged by Google Cloud&#39;s unique Global VPC capability. Unlike other cloud providers, where virtual networks are regionally bound, a GCP Global VPC spans multiple regions natively. This means a single, centralized network can connect your global application microservices to multi-region MongoDB Atlas deployments with dramatically simplified network topologies, lower latency, and reduced egress costs. </p></li><li><p><strong>PSC CIDR Block:</strong> If you use the default (recommended) port-mapping architecture for MongoDB Atlas Private Service Connect, only a single IP address is needed for the PSC endpoint in your VPC. You no longer need to allocate a large block; specify a /32 CIDR for just one address. (Legacy, non-port-mapped endpoints require larger blocks, but are deprecated and will be disabled after April 30, 2027.) Always avoid overlapping any service ranges.</p></li><li><p><strong>Private Service Connect (PSC):</strong></p></li><ul><li><p><strong>Endpoint Registration:</strong> Atlas PSC endpoints are registered with Google Cloud Service Directory. Make sure you assign the `servicedirectory.admin` IAM role to the Terraform runner service account so your endpoint DNS is configured correctly.</p></li><li><p><strong>Connectivity and DN</strong>S: Applications should always connect to the database using the Service Directory internal DNS name to benefit from managed endpoint rotation and zone-aware routing. Avoid manual DNS mappings or forwarding rules.</p></li><li><p><strong>PSC Limitations:</strong> Standard Google serverless services (Cloud Run, Cloud Functions, App Engine) require a Serverless VPC Access connector to reach Atlas over PSC. GKE clusters are supported if their nodes are on the target subnetwork. Double-check your region matches between the PSC endpoint subnet and the Atlas cluster region to ensure the lowest latency.</p></li></ul><li><p><strong>Region Matching:</strong> This is critical! The MongoDB Atlas region you select <strong>must match</strong> the region of your Google Cloud subnetwork to minimize latency and avoid cross-region data transfer costs.</p></li></ul><p>Be patient! Bringing up a new MongoDB Atlas cluster and all the associated private network connectivity from scratch usually takes about <strong>20 to 30 minutes</strong>.</p><h2>Your fast track to production-ready data</h2><p>The Organization Toolkit (Fabric FAST) addresses the core challenges of cloud adoption—complex setup and mandatory security—by providing a pre-configured foundation. The new MongoDB Atlas module enhances this solution by making the secure, private provisioning of high-performance NoSQL data infrastructure effortless. This powerful combination allows users to achieve foundational build-out and critical data service deployment with maximum efficiency, enabling faster time-to-value and assured security.</p><p>On a side note, if you are deploying this inside a FAST-enabled organization, the files can be lightly edited to match your configuration and then used directly in the <a href="https://github.com/GoogleCloudPlatform/cloud-foundation-fabric/tree/master/fast/stages/2-project-factory">project factory</a>. This integration enables you to leverage MongoDB-backed projects as standardized &quot;products&quot; to your internal development teams, maintaining governance while empowering developers.</p><h3>References</h3><ul><li><p><a href="https://github.com/GoogleCloudPlatform/cloud-foundation-fabric/blob/master/fast/README.md">Cloud Foundation Fabric FAST documentation</a></p></li><li><p><a href="https://www.mongodb.com/docs/atlas/security-private-endpoint/">MongoDB Atlas private endpoint documentation</a></p></li><li><p><a href="https://www.mongodb.com/docs/atlas/architecture/current/landing-zone/">MongoDB Atlas landing-zone guidance</a></p></li></ul>]]></description>
      <pubDate>Wed, 26 Aug 2026 14:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/technical/mongodb-atlas-joins-google-cloud-foundation-fabric-fast-secure-private-data-infrastructure-minutes</link>
      <guid>https://www.mongodb.com/company/blog/technical/mongodb-atlas-joins-google-cloud-foundation-fabric-fast-secure-private-data-infrastructure-minutes</guid>
    </item><item>
      <title>Agent Observability: Monitoring Decisions, Not Requests</title>
      <description><![CDATA[<p>Observability is the practice of making a system’s internal behavior legible from the outside—capturing enough signal that an engineer can reconstruct what happened and why. For a web service, that signal is the request: a status code, a latency number, a stack trace when something throws. For an agent, the unit of behavior is a decision: the choice it makes between one call and the next. The agent reads context, chooses an action, calls a tool or a model, observes the result, and chooses again. </p><p>Agent observability is the practice of capturing that sequence of decisions and making it legible. This is Part 6 of a series on designing an agentic platform, and it covers what that requires: what to instrument, which metrics actually matter, and why the operations layer around agents is still being built rather than adopted.</p><h2>Why monitoring, observability, and evaluation are three different jobs</h2><p>Three jobs often get collapsed into one. Monitoring tracks whether the system is healthy. Observability reconstructs what the agent did and why. Evaluation judges whether what it did was any good. MongoDB’s developer blog has already covered the first for databases, in a three-part series[1] on query performance, latency, and resource utilization across a cluster; this post is about the second, and Part 7 of this series will take up the third.</p><p>Agent observability is a different problem from database monitoring. A database is a deterministic system where failure is explicit: a query is slow, a connection pool is exhausted, an index is missing. An agent is a non-deterministic system where every individual step can succeed, and the run as a whole can still fail.</p><p>An agent rewrites a function, runs the test suite, sees a failure, attempts a fix, and loops. Each iteration is a valid model call that returns within normal latency. Traditional application monitoring reports every span as successful, while the agent burns tokens in a loop that never converges—the failure class that Augment Code’s agent-observability guide[2] uses to justify fine-grained tracing, where a plan-and-execute agent retrieves the right answer and the replanner rejects it and re-plans, indefinitely. The same shape appears in other forms: a tool invoked with a parameter the model hallucinated, a retrieval that returned plausible but irrelevant context, a multi-agent handoff that dropped half its state. In each case the request-level log records that the run happened and how long it took. It does not record why the agent chose the path it did.</p><p>The reasonable assumption is that an existing MLOps or APM stack will extend to agents. It captures most of what a deterministic system needs, and it rests on an abstraction that has held for years: a model maps inputs to outputs, and observability means watching that mapping. The abstraction holds when the model is the system. It breaks when the system is an agent, because the behavior that needs explaining lives in the decisions between calls, not in any single call’s inputs and outputs. The rest of this post is about what the agent case needs that the request case does not.</p><p>This series is about engineering the agent harness and its runtime, and it treats several of the harness’s layers as places a failure can originate: state and persistence in <a href="https://www.mongodb.com/company/blog/technical/state-persistence-the-problem-of-agent-reliability">Part 2</a>, orchestration, and memory.</p><p>Agents do not fail at the observability layer. They fail in memory, orchestration, state, or tool use, and the root cause is genuinely distributed across those layers rather than concentrated in one. Production breakage becomes visible somewhere in the harness, rarely in the model call itself. Observability is the layer that attributes a failure to the correct components.</p><h2>What agent observability captures: traces, reasoning paths, tools, and memory</h2><p>The primary artifact in agent observability is the trace. A trace represents the full lifecycle of an agent task as a parent-child tree of spans: the top-level agent invocation, each model call beneath it, each tool execution, each memory read or write. Where a software engineer reads source code to understand a program’s behavior, an agent engineer reads the trace[2] to understand a run’s behavior. The source code is fixed; what the agent actually did emerges at runtime, and the trace is the only place it is recorded.</p><p>The instrumentation standard for these traces is converging on OpenTelemetry. The OpenTelemetry GenAI semantic conventions[3] define the span types an agent system emits—create_agent, invoke_agent, execute_tool, and invoke_workflow for systems that group several agent invocations—alongside the LLM client spans that carry model name, token usage, and latency. As of mid-2026, these conventions are still in Development status and have changed in nearly every release; version 1.37 reworked how multi-turn chat history is recorded[4]. </p><p>Datadog added native support at v1.37[5], Honeycomb, New Relic, and Grafana consume the spans, and frameworks including LangChain, CrewAI, and AutoGen emit them. Vendor and framework support is broad; team adoption is not. Enterprises remain split between the conventions and bespoke instrumentation. The practical argument for the conventions is integration: a framework that emits them drops into a platform like Datadog or Langfuse with far less work than one that does not.</p><p>A useful span carries more than a name and a duration. It carries additional attributes that let a team ask questions across many traces at once: which tool fails most often, which model call consumes the most tokens, and where latency accumulates. Without them, a team is left reading runs one at a time.</p><p>Capturing spans is the operational layer of observability: where time went, which calls failed, and how many tokens each step consumed. The agent case needs a second layer on top of it. A reasoning trace is the sequence of implicit steps an agent takes to reach a decision—the action it chose, the tool it selected, the context that was in its window when it chose. Researchers have begun calling this cognitive observability[6] —a label still settling, though the underlying distinction is not—to separate it from the operational telemetry that can tell you a step failed but not why the agent’s reasoning led there. An operational signal localizes a failure to a step. The reasoning trace is what explains it. A reasoning trace captured as telemetry is run-bounded execution context (state, as this series defines it), not cross-session memory. Observability records it; it does not turn it into memory.</p><p>In a multi-agent system, the trace has to span the full coordination chain, not just one agent’s output. When a supervisor delegates to a researcher and a writer, a failure can surface in the writer while the cause sits in what the researcher passed along. A trace scoped to a single agent shows the symptom; a trace that follows the handoffs shows where the chain broke. </p><p>Much of what looks like a reasoning failure originates upstream, in retrieval. When an agent chooses the wrong action, the cause is often that the memory read feeding that step returned the wrong fragment, stale context, or nothing usable. This series has argued that some orchestration failures are memory failures in disguise; the reverse holds too, and a retrieval problem can present as a reasoning problem or a tool problem. Telling them apart is exactly what the trace is for. Memory access has to show up in the trace next to the model and tool spans—the query, what came back, and how relevant it was—so a failure can be attributed to the retrieval that caused it rather than guessed at. Memory-access logging belongs in the trace, not in a separate system that a team has to correlate by hand.</p><p>Agents that act through a browser add a layer that text spans cannot capture: what the agent saw. For a web or computer-use agent, the screenshot and the session recording are the perception record. Cloudflare built this into Browser Run[7] after hearing repeatedly that when an automation failed, teams had no idea why. The perception record is also the artifact that automated evaluation handles the worst. Agents that render tables, diagrams, or full interfaces produce output whose correctness an LLM-as-judge cannot reliably assess from the trace alone. </p><p><strong>Figure 1. </strong>The same agent run seen two ways. </p><p>As a request, every call returns 200 OK, and the run that failed is indistinguishable from the run that worked. As a decision path, every span still returns ok—the trace localizes the failure to the memory-read step, but only once something outside the telemetry has defined it as a failure.</p><h2>What to measure: Three metrics, three alerts, one audit trail</h2><h3>Why the operations layer is yours to build</h3><p>One-half of agent observability is largely solved: capturing the decision path. LangChain’s LangSmith[8] instruments the decision-making layer directly, letting a team localize a failure to the step where a retrieval returned irrelevant documents or a model hallucinated a tool parameter, and attribute cost down to a single sub-task, sometimes finding that one sub-task consumes most of a trace’s tokens. Practitioners shipping coding agents have converged on operational patterns like tail-based sampling[2] (retaining every trace that contains an error, every trace that exceeds a cost threshold, and a small random sample of the rest) because full-fidelity capture is affordable in development and breaks storage budgets in production. </p><p>The gap teams hit is not capture but operations, and it begins with a definition problem. Teams adding agentic features to an existing application are used to the failure modes of conventional software: a crash, a stack trace, a non-zero exit code. Agents fail differently. Incorrect information given to a customer, a safety check bypassed. Neither announces itself in telemetry, and finding either one across a corpus of traces is closer to searching a haystack than to reading a stack trace. The consequence is that a trace can look healthy while the run is broken. A clean sequence of tool calls with no errors is fully compatible with a wrong outcome, because the agent retrieved the wrong context or took a plausible but incorrect path. Instrumentation is rarely where teams fall short; converting traces into something actionable is. The pattern across enterprise agent teams is that instrumentation arrives before the team has decided what counts as a failure, what to alert on, or what a security reviewer will need to see. The signal is captured; the operations practice around it is not yet written.</p><p>Trusting a trace enough to page someone off it takes more than a single instrumentation pass. It takes reliable instrumentation, a stable trace schema, agreed success metrics, and enough manual validation to confirm that the traces match reality. It also takes exercising the detector against positive and negative cases, so that it fires on the situations that are genuinely problems and stays quiet on the ones that are not. How many cycles that takes depends on how much the use case can tolerate being wrong.</p><p>A related problem shows up in how teams use the signal once they have it. Hamel Husain, who has consulted on more than thirty production AI implementations, describes teams building dashboards full of generic scores[9]—helpfulness, toxicity, correctness—and celebrating improvements that do not correlate with real outcomes. Capturing the trace is necessary; measuring the wrong thing on top of it still leaves the team blind.</p><p>The discipline has a name and no standard. AgentOps has been formally defined by IBM[10] and Microsoft[11], but as IBM acknowledges, there is no universally agreed-upon means of conducting it. The closest precedent, DORA[12], expanded its 2025 report to six metrics and seven team archetypes, yet every metric still measures how AI tools affect human developers rather than how agent systems themselves perform. There is, as of this writing, no DORA-for-agents.</p><h3>Three metrics, three alerts, and the audit trail</h3><p>That practice comes down to three things: what to measure, what to alert on, and what to prove to a reviewer. Each rests on the same precondition: a platform that makes the decision path observable by default. It emits OpenTelemetry-compliant spans, so a team’s traces stay portable across backends and the team is not locked into one vendor’s tracing tool. It treats memory reads and tool calls as first-class nodes in the trace, so a reasoning failure can be traced back to the retrieval that caused it. And it produces an audit trail from the first deployment rather than the tenth. An audit trail retrofitted under review pressure is a harder artifact to produce, and a less trusted one, than a trail that was emitted from the first run.</p><p>Three metrics matter from the start. Decision quality measures whether the action the agent chose advanced the task. Memory-retrieval relevance measures whether a retrieval returned context that the agent could actually use. Fully-loaded cost per task measures the cost of a completed task in total: infrastructure, tokens, and human oversight together. The third has no real precedent in DevOps dashboards—every autonomous action carries a direct, variable cost, and a stack that cannot see it cannot tell whether a change made tasks cheaper or just moved the cost somewhere else. It is also the metric teams most often skip. Decision quality tends to get discussed qualitatively rather than instrumented, because it is harder to operationalize than spend, and in production it is usually computed several ways at once: downstream outcome analysis to catch regressions, an LLM-as-judge pass to score semantics at volume, and human review for the cases where the judgment is contested. Where those three signals disagree is where the definition of “good” starts doing real work.</p><p>These three metrics sit inside a broader frame, the closest thing the discipline has to a map. AgentOps borrows two clusters from DORA and adds one it never needed (Figure 2). Delivery covers getting agents to production: lead time from concept to deployment, and the share of agents that make it out of pilot. Operations covers keeping them running: mean time to detect and recover from a failure, and the percentage of agent decisions with a traceable reasoning chain, which is a direct readout of whether the trace instrumentation is in place. Economics is the third cluster: the variable cost of autonomous action. Measuring all three at once is mostly a question of whether the tooling composes—fully-loaded cost per task in particular pulls infrastructure, token, and oversight numbers from systems that often do not talk to each other.</p><p><strong>Figure 2.</strong> The three AgentOps metric clusters. </p><p>None of this requires a new platform to start. A team can instrument one agent end-to-end with the OpenTelemetry GenAI conventions, beginning with the model-call instrumentation that auto-captures token usage and adding agent-level and tool spans from there. Set tail-based sampling[2] so every error trace and every high-cost trace is retained. Then stand up three alerts. The first is task-completion failure rate: the share of runs that end without the user’s task being done. It comes before latency, cost, and quality alerts because it is the earliest signal that the agent is breaking in a way a user feels, and non-convergence, a run that exceeds its step or cost budget, is one of the ways it breaks. The second is a drop in retrieval relevance, which usually precedes a drop in decision quality. The third is cost-per-task regression.</p><p>The last check is the reviewer’s test. Pick an agent action from last week and try to reconstruct, from the trace alone, why the agent took it. If the reconstruction is possible, the audit trail is real. If it is not, that is the gap to close before a compliance team finds it. Most teams get partway. The trace will show which tools were called and what came back, which is enough to reconstruct the sequence of actions. What it does not yet produce is the account a reviewer is asking for: what the agent was trying to do, whether the action was within policy, and which alternatives it weighed and set aside. That account has to be assembled from the trace, and today it is mostly assembled by hand.</p><p>The audit trail carries a compliance cost of its own. A reasoning trace records whatever sat in the agent’s context window, which, for most applications, includes user data, and a telemetry pipeline that ships raw traces to a tracing backend ships that data with them. Redaction belongs in the pipeline rather than in the backend’s retention policy. <a href="https://www.mongodb.com/company/blog/technical/three-questions-agent-security-has-to-answer">Part 3</a> covers where that governance boundary sits; the requirement observability adds is that a trace has to survive redaction and remain reconstructable.</p><h2>Where observability ends, and evaluation begins</h2><p>Instrumented well, a trace shows every step an agent took: the context it read, the action it chose, the tool it called, the cost it incurred. It does not show whether the decision was a good one. Judging the decision means defining what “good” looks like for an agent and testing against it, which is a separate problem from capturing the path. Part 7 takes it up, with a framework for evaluating agent memory and a public leaderboard that puts the definitions to the test.</p><p>This week, instrument one agent run end-to-end with the <a href="https://github.com/open-telemetry/semantic-conventions-genai">OpenTelemetry GenAI conventions</a> and set the three alerts: task-completion failure rate, retrieval-relevance drop, and cost-per-task regression.</p><h2>Frequently asked questions</h2><p><strong>What is the difference between agent observability and monitoring?</strong> Monitoring and observability answer different questions. Monitoring tracks whether a system is healthy—whether it is up and within its latency and error budgets. Observability reconstructs what the system did and why. For an agent, the behavior that needs explaining is a sequence of decisions rather than a single request, so agent observability captures the decision path: the context the agent read, the action it chose, the tool it called, and the memory it accessed. A run can pass every health check and still reach the wrong outcome, which is the gap monitoring alone cannot close.</p><p><strong>How is agent observability different from evaluation? </strong>Observability shows what an agent did; evaluation judges whether what it did was any good. A trace can capture every step of a run completely and still say nothing about whether the decision was correct. Judging that means defining what “good” looks like and testing against it, a separate discipline. In this series, capturing the decision path is the subject of this post; evaluating agent memory against a defined standard comes next.</p><p><strong>Can an existing APM or MLOps stack handle agent observability? </strong>Partly, but not where it matters most. An APM or MLOps stack captures what a deterministic system needs and rests on the assumption that a model maps inputs to outputs. That assumption holds when the model is the system, and breaks when the system is an agent, because the behavior that needs explaining lives in the decisions between calls, not in any single call’s inputs and outputs. Agents need decision-level observability: reasoning traces, tool calls, and memory reads recorded as one connected path, which request-level monitoring does not provide.</p><p><strong>What should you measure for an agent in production? </strong>Three metrics matter from the start: decision quality (did the chosen action advance the task), memory-retrieval relevance (did a retrieval return context the agent could actually use), and fully-loaded cost per task (what a completed task cost in infrastructure, tokens, and human oversight together). The third has no real precedent in traditional dashboards, because every autonomous action carries a direct, variable cost. Pair the metrics with three alerts: task-completion failure rate, a drop in retrieval relevance, and cost-per-task regression.</p><p><strong>What is AgentOps? </strong>AgentOps is the emerging practice of operating agents in production with the same rigor applied to other production infrastructure. It borrows two clusters from DORA—Delivery and Operations—and adds a third that software delivery never needed: Economics, the variable cost of autonomous action. The term has been defined by several vendors, but as of this writing there is no universally agreed standard for how to conduct it, so teams adopt the instrumentation and build the operations practice themselves.</p><p><strong>Is a reasoning trace the same as agent memory? </strong>No. A reasoning trace captured as telemetry is run-bounded execution context: state, in the sense this series uses the term. It is not cross-session memory. Observability records the trace; it does not promote it into memory. Memory is durable, cross-session knowledge deliberately written for future runs, and it carries different governance: retention, access control, and deletion. Conflating the two is a common architectural mistake, which is why the series keeps state and memory on separate definitions.</p><h2>References</h2><p><em>Numbered in order of first appearance; superscript markers in the body point here. </em></p><p><strong>1. </strong>MongoDB. “Database Observability” (three-part series), MongoDB Developer Blog, 2025. <a href="https://www.mongodb.com/company/blog/innovation/mongodb-database-observability-integrating-with-monitoring-tools">https://www.mongodb.com/company/blog/innovation/mongodb-database-observability-integrating-with-monitoring-tools</a></p><p><strong>2. </strong>Augment Code. “Agent Observability for AI Coding” (guide). <a href="https://www.augmentcode.com/guides/agent-observability-for-ai-coding">https://www.augmentcode.com/guides/agent-observability-for-ai-coding</a></p><p><strong>3. </strong>OpenTelemetry. “Semantic conventions for generative-AI agent spans.” <a href="https://github.com/open-telemetry/semantic-conventions-genai/blob/main/docs/gen-ai/gen-ai-agent-spans.md">https://github.com/open-telemetry/semantic-conventions-genai/blob/main/docs/gen-ai/gen-ai-agent-spans.md</a></p><p><strong>4. </strong>Greptime. “OpenTelemetry GenAI Semantic Conventions,” May 9, 2026. <a href="https://greptime.com/blogs/2026-05-09-opentelemetry-genai-semantic-conventions">https://greptime.com/blogs/2026-05-09-opentelemetry-genai-semantic-conventions</a></p><p><strong>5. </strong>Datadog. “Monitor LLM applications with the OpenTelemetry semantic conventions.” <a href="https://www.datadoghq.com/blog/llm-otel-semantic-convention/">https://www.datadoghq.com/blog/llm-otel-semantic-convention/</a></p><p><strong>6. </strong>Watson et al. “Cognitive observability for foundation-model-based agents,” arXiv:2411.03455. <a href="https://arxiv.org/pdf/2411.03455">https://arxiv.org/pdf/2411.03455</a></p><p><strong>7. </strong>Cloudflare. “Browser Run for AI agents.” <a href="https://blog.cloudflare.com/browser-run-for-ai-agents/">https://blog.cloudflare.com/browser-run-for-ai-agents/</a></p><p><strong>8. </strong>LangChain. “Agent Observability” (LangSmith). <a href="https://www.langchain.com/resources/agent-observability">https://www.langchain.com/resources/agent-observability</a></p><p><strong>9. </strong>Hamel Husain. “A Field Guide to Rapidly Improving AI Products.” <a href="https://hamel.dev/blog/posts/field-guide/index.html">https://hamel.dev/blog/posts/field-guide/index.html</a></p><p><strong>10. </strong>IBM. “What is AgentOps?” <a href="https://www.ibm.com/think/topics/agentops">https://www.ibm.com/think/topics/agentops</a></p><p><strong>11. </strong>Microsoft. “Introducing built-in AgentOps tools in Azure AI Foundry Agent Service.” <a href="https://techcommunity.microsoft.com/blog/azure-ai-foundry-blog/introducing-built-in-agentops-tools-in-azure-ai-foundry-agent-service/4414389">https://techcommunity.microsoft.com/blog/azure-ai-foundry-blog/introducing-built-in-agentops-tools-in-azure-ai-foundry-agent-service/4414389</a></p><p><strong>12. </strong>DORA. “2025 research questions,” Google Cloud. <a href="https://dora.dev/research/2025/questions/">https://dora.dev/research/2025/questions/</a></p><h2>Series: Designing an Agentic Platform</h2><ul><li><p><a href="https://www.mongodb.com/company/blog/technical/designing-an-agentic-platform-infrastructure-that-makes-agents-work">Pt 0 — Series Intro: The Infrastructure That Makes Agents Work</a></p></li><li><p><a href="https://www.mongodb.com/company/blog/technical/agent-harness-why-llm-is-smallest-part-of-your-agent-system">Pt 1 — The Agent Harness</a></p></li><li><p><a href="https://www.mongodb.com/company/blog/technical/state-persistence-the-problem-of-agent-reliability">Pt 2 — State &amp; Persistence</a></p></li><li><p><a href="https://www.mongodb.com/company/blog/technical/three-questions-agent-security-has-to-answer">Pt 3 — Security &amp; Governance</a></p></li><li><p>Pt 4 — <a href="https://www.mongodb.com/company/blog/technical/agent-orchestration-tool-use-machinery-underneath">Orchestration &amp; Tool Use</a></p></li><li><p>Pt 5 — <a href="https://www.mongodb.com/company/blog/technical/agent-memory-inside-harness">Memory Inside the Harness</a></p></li><li><p><strong>Pt 6 — Agent Observability </strong><em>(this post)</em></p></li><li><p>Capstone — The Agent Platform Buyer’s Checklist</p></li></ul><h2>About the authors</h2><p><strong>Mikiko Bazeley, Staff Developer Advocate, MongoDB. </strong>Mikiko writes about agentic AI systems, agent memory and context engineering, and the POC-to-production gap.</p><p><strong>Ashish Kumar, Technical Fellow, MongoDB. </strong>Ashish joined MongoDB over two years ago through the acquisition of Grainite, a database startup he co-founded. Before that, he spent many years at Google, most recently responsible for Google’s native database suite — Bigtable, Spanner, Datastore, and Firestore — across Google’s own products and Google Cloud. His passion is large-scale distributed systems, and at MongoDB he focuses on architectural improvements across the product stack.</p><p><strong>Max Marcon, Director of Product Management, MongoDB. </strong>Max leads product for agentic AI initiatives at MongoDB. His mission is to ensure customers are successful with running agents at enterprise scale.</p><p><strong>Charlie Xu, Senior Product Manager, AI and Emerging Products, MongoDB</strong>. Charlie focuses on products that help developers and enterprises build agents. His work spans the strategy, product experience, and architecture needed to move agents from prototype to production.</p><p><strong>Ahmed Sulaiman, </strong><strong>Staff Engineer, AI and Emerging Products</strong><strong>, MongoDB. </strong>Ahmed focuses on the architecture and engineering required to move agentic AI systems from prototype to production, with an emphasis on scale, reliability, and real-world deployment.</p><p><strong>Nandini Kapa, Software Engineer, MongoDB. </strong>Nandini focuses on the engineering and operational work required to run agentic systems reliably in production, with an emphasis on platform reliability, deployment health, and decision quality.</p>]]></description>
      <pubDate>Tue, 25 Aug 2026 14:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/technical/agent-observability-monitoring-decisions-not-requests</link>
      <guid>https://www.mongodb.com/company/blog/technical/agent-observability-monitoring-decisions-not-requests</guid>
    </item><item>
      <title>How Indian Organizations in Regulated Industries Are Scaling with MongoDB</title>
      <description><![CDATA[<p>Scaling while ensuring regulatory compliance is a major challenge that many Indian organizations today face, particularly when operating in industries like financial services, retail, education, and aviation. </p><p>Too often, companies are held back by their rigid, legacy data infrastructures, which can leave them unable to meet increased customer demand and expand. For organizations operating in highly regulated, critical industries, scale isn’t the only issue—many companies find themselves stuck in the innovation/compliance conundrum: how to innovate at scale and speed without adding complexity, and without jeopardizing regulatory compliance, security, or reliability? </p><p>By modernizing legacy infrastructure and moving to <a href="https://www.mongodb.com/resources/basics/flexible-data-model">MongoDB’s flexible document model</a>, Indian organizations are demonstrating how scale and compliance can be achieved, all while removing complexity and allowing for resources to be spent where they matter most. </p><p>Here are great examples from a number of customers who presented at MongoDB.local Bengaluru event: </p><p>First is <strong>Physics Wallah (PW)</strong>, which has built one of India’s leading edtech platforms on MongoDB. Today, PW serves over 7 million students, and their app has been downloaded over 10 million times. </p><p>The latest offering from Physics Wallah is a unified, compliant, multi-tenant payment platform—PW Payments—that is powered by <a href="https://www.mongodb.com/products/platform/atlas-database">MongoDB Atlas</a>. To build a scalable and compliant fintech architecture rapidly, PW established two primary design principles: configuration over code (No-Code/Low-Code) and strict tenant isolation. </p><p>MongoDB Atlas’s capabilities, including <a href="https://www.mongodb.com/products/capabilities/transactions">ACID transactions</a>, allowed PW to wrap all financial flows in strict ACID transactions across multiple collections. With <a href="https://www.mongodb.com/resources/products/capabilities/change-streams">MongoDB Change Streams</a>, it’s easy to keep track of every configuration edit, payment state modification, and system event to generate an immutable audit trail for regulatory bodies (i.e., RBI). Finally, <a href="https://www.mongodb.com/products/platform/atlas-search">MongoDB Search</a> provides native full-text search capabilities across hundreds of business models, users, and rule configurations, eliminating the need for a separate data lake search infrastructure.</p><p>The ability to scale can directly impact whether an organization can succeed, particularly in industries such as E-commerce. <strong>Flipkart</strong>,<strong> </strong>one of India’s leading e-commerce giants, is a great example: <strong> </strong>with <a href="https://www.mongodb.com/products/platform/atlas-database">MongoDB Atlas</a>, they were able to <a href="https://youtu.be/ZlYPhKjIAkk?si=Nl58CZ3kaZWmXsz2&amp;t=617">make great scale happen</a> by supporting high-throughput write operations, real-time payment aggregation, and seamless horizontal sharding during mega sales events like <em>The Big Billion Days</em>. Furthermore, <a href="https://www.mongodb.com/resources/products/capabilities/change-streams">MongoDB Change Streams</a> and aggregation pipelines allow the team to maintain strict data integrity throughout real-time data updates and analysis. </p><p>Another SaaS leader using MongoDB Atlas is <strong>IBS Software. </strong>For IBS Software, scale hasn’t been the only challenge to overcome—the company provides mission-critical technology to the global travel and logistics industries, and requires an infrastructure that can reliably support thousands of enterprise customers and millions of transactional data assets. </p><p>With MongoDB’s flexible document model and sharding capabilities, IBS Software scaled three mission-critical platforms at once: its hospitality platform iStay; its cruise platform iTravel Cruise; and Loyalty Offer Management, its loyalty and retailing system. With MongoDB, IBS Software is able to process billions of records and millions of searches per day on its hospitality platform, with API responses of less than 100ms. iTravel Cruise is now able to process selling price writes of 100,000 TPS within an average latency of 5 milliseconds, and the company can provide extreme reliability to its customers with uptime guarantees of 99.99% on the cloud. </p><p>Finally, some companies operating in heavily regulated industries need even greater control. <a href="https://www.mongodb.com/products/self-managed/enterprise-advanced">MongoDB Enterprise Advanced (EA)</a> is the most flexible way to run MongoDB on-premises with powerful tools for automation, operations, and security in a self-managed environment. </p><p>For example, MongoDB EA is used by companies like <strong>Kore.ai, </strong>which provides an enterprise conversational AI platform that serves regulated industries (e.g., banking, healthcare, retail) that demand high availability, strict security, and low-latency interaction.<a href="https://youtu.be/pN0b8UQ_dy4?si=gtUlHZFtYK_cz8Ou&amp;t=994"> As Kore.ai shared during their presentation at MongoDB .local,</a> MongoDB EA’s reliability enables the company to maintain 24/7 operational continuity and high availability across complex enterprise deployments. </p><p>Another example is <strong>PineLabs, </strong>a leading merchant commerce platform with operations across Asia that uses both <a href="https://www.mongodb.com/products/platform/atlas-database">MongoDB Atlas</a> and <a href="https://www.mongodb.com/products/self-managed/enterprise-advanced">MongoDB Enterprise Advanced</a> to handle extreme scaling, high-throughput transaction processing, and rapid data growth across its fintech ecosystem. Using MongoDB ensures mission-critical uptime across payment processing pipelines, particularly during massive traffic surges and peak sales periods. </p><p>These Indian organizations are proving that with MongoDB, scale, speed, and regulatory compliance don’t have to be mutually exclusive. As AI continues to reshape how digital services are built and delivered at scale—and as regulatory compliance requirements keep growing—there’s no question that organizations that don’t modernize will be left behind. But those who take advantage of the flexibility of the document model to build a powerful intelligent data platform will have the infrastructure they need to thrive in the AI era. </p>]]></description>
      <pubDate>Tue, 25 Aug 2026 00:30:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/how-indian-organizations-regulated-industries-are-scaling</link>
      <guid>https://www.mongodb.com/company/blog/innovation/how-indian-organizations-regulated-industries-are-scaling</guid>
    </item><item>
      <title>10 Years of MongoDB Atlas: Built for What’s Next</title>
      <description><![CDATA[<p>Nearly a decade ago, I joined MongoDB as a Senior Product Manager to help build the company’s new cloud product, MongoDB Atlas. Our customers had been telling us they wanted to bring MongoDB’s familiar developer experience to the cloud, with the reliability and confidence teams needed to run in production. Atlas was our answer.</p>
<p>Today, we’re celebrating 10 years of MongoDB Atlas, the generational data platform for AI applications, and the customers who pushed us to build it.</p>
<p>Atlas was shaped in close conversation with those customers and scaled alongside them every step of the way. Today, more than 250,000 builders get started on Atlas every month. Atlas serves more than three trillion queries a day (a roughly threefold increase just since 2023!), and represents 75% of MongoDB’s revenue. Those numbers reflect something more important than growth: the trust builders and customers have placed in us to scale their businesses.</p>
<p>That trust was earned by listening closely. Every major capability and architectural investment in Atlas was rooted in what customers asked for: the flexibility and speed of MongoDB’s document model, delivered in a platform that removed operational overhead and could scale with their applications. Over time, Atlas expanded beyond a managed database into a broader data platform, because builders kept asking for more flexibility, more simplicity, and more room to build.</p>
<p>That matters even more in the AI era. AI applications create new demands, but the underlying requirement is familiar: builders need a platform that can support operational data, search, and retrieval while scaling through constant change—without forcing them to stitch together a mess of disconnected systems. We spent ten years becoming the flexible, durable data platform that builders trust. Those are the same qualities AI applications need most, and that’s why builders are now using Atlas to build trustworthy AI applications with highly accurate retrieval, real-time context, and the scale to run in production.</p>
<p>Atlas 10 Year Anniversary Blog - Image 1
media</p>
<p>Managed cloud databases become the default</p>
<p>When Atlas launched in 2016, organizations were moving away from traditional data center build-outs and toward cloud-based delivery, a market Gartner forecasted would reach $204 billion (and is now approaching $1 trillion).</p>
<p>Developers loved MongoDB as a flexible, intuitive foundation for building applications, but they also wanted to take advantage of the cloud. Atlas’s first promise was simple: bring MongoDB’s familiar developer experience to the cloud, with the reliability and confidence teams needed to run in production.</p>
<p>Atlas 10 Year Anniversary Blog - Quote 1
aside</p>
<p>To deliver that confidence to developer teams, we built Atlas with security, resilience, and performance at its core—from encryption and access controls to backups and high availability. The result was a service that teams could run in production with confidence, freeing developers to do their very best work without the headaches associated with database administration.</p>
<p>By 2018, 81% of enterprises were operating in multi-cloud environments, and an IDG study found that more than half indicated they were thinking about cloud as a portfolio strategy. As customer architectures became more distributed, teams needed the flexibility to choose the cloud environment that fit their applications, teams, and compliance needs.</p>
<p>To support them, we extended our original promise of simplicity into multi-cloud flexibility, with availability across all three major cloud providers. And in 2020, we introduced Atlas Multi-Cloud Clusters, making Atlas the first and only cloud database to let customers run applications simultaneously across AWS, Azure, and Google Cloud regions—a unique achievement that gave organizations that require ultra-high availability one consistent data foundation across all the major clouds.</p>
<p>Today, customers can run across over 125 AWS, Google Cloud, and Microsoft Azure cloud regions, making Atlas the most widely available managed data platform in the world.</p>
<p>Atlas 10 Year Anniversary Blog - Quote 2
aside</p>
<p>Enterprises' scale, and consolidation becomes a customer priority</p>
<p>As cloud adoption accelerated, customers wanted more than a hosted database. The cloud had become a long-term investment, and developers needed global reach, resilience, and a platform that could handle more workloads, securely, without requiring them to keep adding infrastructure around it. Because developers already trusted us on the fundamentals, Atlas could expand into the kinds of workloads enterprises could not afford to get wrong.</p>
<p>For workloads like payments, inventory, and order processing, strong transactional consistency is a requirement. The addition of multi-document ACID transactions in 2018 brought that transactional consistency to MongoDB and marked an important step in MongoDB’s evolution, enabling MongoDB to serve the kinds of high-stakes transactional workloads that enterprises had historically reserved for relational databases. Now, customers could use MongoDB with greater confidence for a wider set of systems where accuracy, resilience, and trust could not be compromised.</p>
<p>MongoDB extended its trustworthy database foundation with the launch of MongoDB Queryable Encryption, an industry-first encryption capability that allows customers to query encrypted data while keeping sensitive information protected when it is at rest, in transit, and in use—an important step for securing regulated and highly sensitive workloads.</p>
<p>At the same time, Atlas continued to evolve to help customers operate at a larger scale. In 2020, we introduced Atlas Search and Online Archive, adding rich application search and giving customers a simpler, lower-cost way to store older data without losing easy access to it. In 2021, Native Time Series Collections and Live Resharding followed, helping customers manage time-stamped data more efficiently and scale architectures without downtime.</p>
<p>These updates made Atlas easier for builders to work with as deployments became bigger, more distributed, and more complex, all while minimizing the number of disparate systems that development teams had to stitch together and maintain.</p>
<p>Atlas 10 Year Anniversary Blog - Quote 3
aside</p>
<p>Trustworthy AI becomes the new frontier</p>
<p>Then, the launch of ChatGPT in late 2022—and with it the rise of generative AI—created a massive new challenge for builders.</p>
<p>Enterprise adoption moved faster than standards and controls, leaving teams to figure out how to connect the necessary data components to run semantic search and retrieval-augmented generation (RAG) workloads together without creating a brittle mess of data pipelines, sync jobs, and specialized infrastructure that compromised security and performance.</p>
<p>To help teams bring these critical AI building blocks together on one secure platform, Atlas evolved again. With the public release of Atlas Vector Search in 2023, MongoDB was one of the first databases to launch vector search as a native capability, which enabled developers to keep vectors close to operational data and run semantic retrieval directly in the database without having to manage a separate vector store. Search Nodes gave teams a way to scale search and vector workloads independently from the operational database, while Atlas Stream Processing gave builders a way to process real-time streaming data without adding separate infrastructure.</p>
<p>The business demand for this architecture has been staggering: over 726,000 vector indexes and 55,000 vector applications have been created since we introduced Atlas Vector Search, and we’ve seen a 92% increase in customers showing production-level vector search usage over the past 12 months.</p>
<p>And with the company’s acquisition of Voyage AI in 2025, MongoDB sharpened its focus on retrieval quality—bringing advanced embedding and reranking models into Atlas. The integration of Voyage AI was about rethinking the data architecture to help customers reduce hallucinations, improve relevance, and make AI useful in the real-world environments where accuracy and trust matter most.</p>
<p>10 Year Anniversary Blog - Quote 4
aside</p>
<p>This immediately paid huge dividends for customers building highly accurate semantic search and RAG applications. But we knew that as the market moved towards autonomous AI, trustworthy retrieval and access to real-time context would matter even more.</p>
<p>Agents and the future of the data layer</p>
<p>Today, we’re firmly in AI’s agentic era. Builders want to deploy agents that can reason over business context with autonomy. But agent memory requires fast accuracy at scale so that the right information is recalled at precisely the right time. And this is where they run into a challenge. They're excited about agents, but they can't put an agent in front of their customers if the results are inconsistent, irrelevant, or flat-out wrong.</p>
<p>That puts increasing focus on the data layer of the tech stack. Agents are only as good as the context they can retrieve, rank, and retain. If the underlying data is stale, incomplete, or poorly retrieved, the output will be wrong—regardless of how strong the model is. In practice, production agents depend less on model choice alone than on retrieval quality and the ability to ground responses in live operational data.</p>
<p>With search, vector search, embeddings, and rerankers natively integrated into the Atlas platform, businesses are closing the gap between data and retrieval to produce fast, accurate results for agents at scale. And with foundational capabilities to ensure exceptional security, resilience, and performance, builders are freed up to do what they do best, instead of spending their days bogged down managing data infrastructure.</p>
<p>Atlas 10 Year Anniversary Blog - Quote 5
aside</p>
<p>Over the past decade, our goal has been to reduce operational burden for customers without compromising on the technical bar. As the industry moves toward agents, that aim still applies.</p>
<p>We’re ten years in, and Atlas has grown into the data platform that runs intelligent, mission-critical applications for nearly 70,000 customers across every industry. The world runs on Atlas! Our customers pushed us to build everything that matters in the platform, so they could do more, faster. The same holds true today: the agentic AI era is raising the bar for innovation, and we're raising it with them. The ambition our customers bring to what they're building next is what drives us forward—and we're ready for it.</p>
<p>Here's to the next 10 years.</p>
]]></description>
      <pubDate>Thu, 25 Jun 2026 17:28:40 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/news/10-years-mongodb-atlas-built-for-whats-next</link>
      <guid>https://www.mongodb.com/company/blog/news/10-years-mongodb-atlas-built-for-whats-next</guid>
    </item><item>
      <title>Build Trust in Agentic AI: From POC to Production</title>
      <description><![CDATA[<p>The enterprise adoption of artificial intelligence has reached an inflection point. Organizations are rapidly moving into the era of agentic AI, autonomous systems capable of executing complex reasoning and making operational decisions independently. Yet as executives attempt to transition agents from sandbox environments into mission-critical production channels, they inevitably collide with an AI trust gap.</p>
<p>Unlike traditional applications, agentic solutions interpret intent and take autonomous action on behalf of your business. Traditional IT tools are not designed to manage dynamic solutions. To scale securely, organizations must deploy a proactive control plane that evaluates an agent's logic and employs strict governance.</p>
<p>In this article, we outline a four-step approach for building safety and optimization into agentic solutions. The approach outlines a broad framework that can be tailored to an organization’s specific needs.</p>
<p>The 4-step framework for agentic trust</p>
<p>To close the AI trust gap, enterprises need to consider reliability, predictability, accountability, and optimization. To achieve this, we’ve outlined four steps with their critical capabilities.</p>
<p>Figure 1. The Agentic Trust Framework: Four steps from reliability to optimized outcomes.</p>
<p>Build Trust in Agentic Systems Blog - Image 1
media</p>
<p>Customer refund example</p>
<p>To anchor this framework, let us follow a common high-stakes workflow, a customer refund. On the surface, resolving a customer refund is a straightforward business process:</p>
<p>Understand the request</p>
<p>Verify eligibility</p>
<p>Decide &amp; execute</p>
<p>While a human handles this seamlessly, an autonomous agent introduces compounding factors of risk. Specifically, there are risks related to interpretation and logic, as well as financial risk:</p>
<p>How do we ensure the agent doesn't hallucinate on policy?</p>
<p>How do we verify that the agent isn't guessing on complex, nested eligibility criteria?</p>
<p>What controls prevent an agent from executing an irreversible $5,000 refund?</p>
<p>Step 1: The foundation layer</p>
<p>The first step of the framework grounds agents in business reality. An agent is only as dependable as the factual data it consumes. By utilizing retrieval-augmented generation (RAG) and operational data, we supply the model with real-time, factual data, such as refund terms. Grounding agents with business data dramatically reduces hallucinations.</p>
<p>The data foundation and agent memory transform agents into dynamically adaptive systems. Short-term memory maintains context across immediate actions. Meanwhile, long-term memory uses episodic recall of past interactions and procedural memory to permanently embed expert (SME) corrections. This feedback loop ensures the system retrieves updated guardrails to avoid repeating mistakes.</p>
<p>The second critical aspect of the foundation is observability. Modern observability requires detailed tracing to record every reasoning step, tool invocation, and token expenditure, providing a clear audit trail for every action the agent takes and the associated costs. For leaders, this deep logging acts as a &quot;black box recorder&quot; that provides the definitive audit trails necessary for strict regulatory compliance, immediate root-cause analysis of execution failures, and precise cost-to-serve metrics.</p>
<p>With the rapidly changing AI landscape, teams need to focus on building robust agentic solutions and not stitching together infrastructure, the “sync tax.” By unifying vector, operational, and time series under one solution, MongoDB eliminates this tax. JSON is the default language for AI and the native language for MongoDB. Teams recognize a significant performance boost by having agent memory, execution traces, vectors, and operational data on the same platform.</p>
<p>Figure 2. The AI application data layer, before and after consolidation.</p>
<p>Build Trust in Agentic AI Blog - Image 2
media</p>
<p>Step 2: The verification layer</p>
<p>Step two shifts from core data to active agent inspection with two operational dials:</p>
<p>Figure 3. Verification Metrics: Agent Confidence Score and Business Risk Score</p>
<p>Build Trust in Agentic AI Blog - Image 1
media</p>
<p>Dial 1: Agent Confidence Score (ACS)</p>
<p>ACS measures the technical probability of agent correctness. By normalizing this metric to a value between 0.0 and 1.0, the architecture can seamlessly combine disparate technical checks into a single, standardized mathematical formula for governance.</p>
<p>Often referred to as “Eval Engineering,” calculating this confidence frequently uses an approach known as “LLM-as-a-Judge.” While traditional large models are expensive to run at scale, small language models (SLMs), like Galileo’s Luna models, are becoming the gold standard for their speed, accuracy, and cost-efficiency. SLMs can score semantic groundedness and faithfulness in milliseconds. However, for exceptionally high-risk situations where maximum latency and token costs are acceptable, large frontier models remain the best solution.</p>
<p>Dial 2: Business Risk Score (BRS)</p>
<p>BRS measures the business (financial, compliance, and security) consequences of an agentic action. Similar to the ACS, this metric is normalized to a value between 0.0 and 1.0 to plug into the final governance formula.</p>
<p>While standard AI guardrails focus narrowly on simple constraints, the BRS evaluates the broader organizational liability of the task itself. BRS should use deterministic means, such as regular code or risk registries, to determine the risk score. Risk should be treated as a business concern and not a technical concern, except in the case of a system failure, like a failing API call.</p>
<p>Step 3: The governance layer</p>
<p>The governance layer is where verification transforms into action via the Agent Decision Score (ADS). ADS is a simple mathematical formula that provides an auditable and predictable metric:</p>
<p>ADS = ACS x (1 - BRS)</p>
<p>By multiplying technical certainty (ACS) against the inverse of real-world liability (BRS), the system establishes a metric that dictates the agent's operational autonomy. To illustrate, we’ll use a traffic light protocol:</p>
<p>Build Trust in Agentic AI Blog - Table
table</p>
<p>Let us apply this logic directly to our customer refund story:</p>
<p>Understand the reason: The agent analyzes the customer's chat. Confidence is high (0.90), and risk is low (0.2). ADS = 0.72 (green). The agent proceeds autonomously.</p>
<p>Verify eligibility: The agent checks the return policy against a complex order history. It is unsure of a specific discount code. Confidence drops (0.70), while risk remains low (0.4). ADS = 0.42 (yellow). The agent pauses and sends a summary to the team’s messaging platform for a review (thumbs up/down) from a human expert.</p>
<p>Execute transaction: The refund amount is $500. Because this exceeds a defined policy threshold, the business risk is set to high (0.85). Even with high confidence (0.95), the ADS drops to 0.14 (red). The task is automatically routed to a supervisor’s management backlog for formal takeover.</p>
<p>SME feedback:</p>
<p>When governance triggers a yellow or red light, the workflow pauses. The system instantly packages the entire execution history into a comprehensive audit trace. The system then routes this package into a standard IT service queue for a subject matter expert (SME) to review.</p>
<p>When the SME corrects the agent's proposed path, the resolution serves two critical purposes. First, it securely resolves the immediate customer issue. Second, the system writes this exact correction back into its long-term procedural memory. This continuous feedback loop ensures that every SME review permanently updates the operational guardrails, preventing the agent from making the same logical error in the future.</p>
<p>Simplified Trace:</p>
<p>Build Trust in Agentic AI Blog - Code Block
code_panel</p>
<p>Step 4: The outcomes layer</p>
<p>For an enterprise digital workforce to be sustainable, thousands of individual runtime traces must be continuously aggregated into macro-level business observability dashboards. Organizations will have different needs, but executive visibility must prioritize strategic value and systemic risk.</p>
<p>Designed specifically for the CFO and business unit directors, this lens tracks clear corporate returns. It monitors top-line financial metrics such as Total ROI and Cumulative Savings. Most importantly, it verifies that the architecture is scaling efficiently by tracking AI Unit Economics. By showing that the average cost-per-task has been optimized down to $1.85 compared to the legacy manual human execution baseline of $3.05, the dashboard proves a clear $1.20 unit-economic savings per execution.</p>
<p>However, true agentic observability goes beyond passive charts. Specialized analytical agents continuously interpret this aggregated telemetry to provide active recommendations. For example, if the data reveals that guardrail violations have spiked to 38 percent or that refund workflows are stuck in a high-risk red zone, an analytical agent proactively flags the risk. It can then alert leadership and recommend targeted actions, such as mitigating escalations by adjusting governance thresholds or updating the RAG knowledge base to improve autonomous decision confidence for order processing. This continuous analysis transforms raw operational metrics into autonomous business intelligence.</p>
<p>Figure 4. Agentic AI value and risk dashboard.</p>
<p>Build Trust in Agentic AI Blog - Image 4
media</p>
<p>Moving beyond the sandbox</p>
<p>Trust is an engineering discipline, not an abstract ideal. As enterprises deploy autonomous agents, successful organizations will treat AI as a formally governed IT service.</p>
<p>This requires anchoring your agents in a unified AI data platform like MongoDB to manage memory, operational data, and agent traces. When you pair this robust data foundation with strong verification, governance, and agent optimization, you can confidently bridge the trust gap. This approach unlocks safe, predictable, and profitable AI autonomy at true enterprise scale.</p>
<p>Figure 5. Agentic trust infographic.</p>
]]></description>
      <pubDate>Tue, 23 Jun 2026 15:27:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/build-trust-in-agentic-ai-from-poc-to-production</link>
      <guid>https://www.mongodb.com/company/blog/innovation/build-trust-in-agentic-ai-from-poc-to-production</guid>
    </item><item>
      <title>Production-Ready Agents Need A Production-Ready Data Platform</title>
      <description><![CDATA[<p>There’s a common theme to the conversations I’ve been having with AI teams lately: change. Constant, head-spinning change. Teams across industries are evaluating and re-evaluating model providers, agent frameworks, and harnesses on a continuous basis.</p>
<p>At MongoDB, we believe that your choice of technology partner—specifically, your data platform—should simplify how you build with AI. It should deliver performance at scale, enable you to build and run anywhere, and it should allow you to choose your own providers and frameworks. This is exactly what MongoDB offers, and it’s why more than 67,000 customers rely on us for their most important applications.</p>
<p>The organizations seeing the most AI success are the ones whose technology stacks are set up for the current pace of change. For example, DevRev’s AgentOS platform is powered by MongoDB Atlas. AgentOS handles billions of requests each month, for everything from AI-assisted insights and analytics to internal communications and development. Relying on MongoDB Atlas has helped DevRev get innovations to market faster, and enables the company to scale seamlessly as it grows.</p>
<p>MongoDB is ideal for agentic AI in two key ways.</p>
<p>First, an agent is only as smart as its context—which requires blending short-term memory, long-term knowledge, and enterprise data. Because this information is highly dynamic and unstructured, JSON is the ideal format. It provides the schema flexibility inherently needed by the data and allows attaching metadata like IDs and confidence scores. MongoDB stores JSON natively and provides the scale and consistency required to run thousands of concurrent agents.</p>
<p>Second, it’s designed for how agents work. As memory accumulates, agents must pinpoint the precise context needed for a request. MongoDB solves this by providing state-of-the-art information retrieval capabilities (search, vector search, hybrid search, embeddings) directly where the operational data already lives, eliminating the need to constantly sync data across separate systems. Customers get high-precision semantic retrieval without the operational headache of managing multiple fragmented products.</p>
<p>A good example of how MongoDB powers agents is ElevenLabs. The company relies on MongoDB Atlas to power the long-term memory and knowledge base for its autonomous agents. By leveraging Atlas Search and Vector Search, ElevenLabs enables their agents to retain complex context and deliver highly personalized interactions in real-time.</p>
<p>Adobe, meanwhile, chose MongoDB as the long-term memory and reasoning layer for Journey Agent, its composite multimodal AI agent that unifies Adobe's marketing suite and orchestrates end-to-end customer journeys. Adobe leverages MongoDB Atlas Search and Atlas Vector Search together to power the sub-100 millisecond hybrid search the agent needs to act in real time.</p>
<p>Defining an open standard for agent memory</p>
<p>Last month, MongoDB partner LangChain announced the launch of Context Hub in LangSmith, a place to store, version, and collaborate on the files that define how agents behave, like AGENT.md and agent skills.</p>
<p>But context engineering goes beyond that. Agents also rely on memory: short-term context captured in states, sessions, and interaction history, and long-term memory that persists across sessions.</p>
<p>Figure 1. Agent memory with MongoDB.</p>
<p>Production-Ready Agents blog image 1
media</p>
<p>Today, there is no broadly adopted open standard for defining and managing portable agent memory across agent frameworks. Now, MongoDB—alongside LangChain and ecosystem partners—is working on an open reference architecture and contributing toward greater interoperability in this space.</p>
<p>This work will help define what has been missing from the AI ecosystem: shared interfaces, metadata conventions, versioning patterns, and retrieval semantics for the data that differentiate agentic experiences and shape agent behavior.</p>
<p>The aim is to enable organizations to switch model providers or try a new framework on a Tuesday—and not lose Wednesday rewriting memory plumbing. Ultimately, we want to make agent memory and context easier (and faster) to manage.</p>
<p>For customer-facing agents to make real-time decisions, such as responding to a support request or making a policy change, they need contextual information instantly. Not info from a data warehouse that might be 30 minutes old. The context layer needs to be real-time, a required capability we’ve been delivering for tens of thousands of customers going on almost two decades.</p>
<p>MongoDB’s performant, flexible platform = agentic success</p>
<p>The next generation of agents will increasingly be long-horizon systems, running for hours or more. As they take on more complex tasks, context will become even more critical, and agent memory will be central to making them effective.</p>
<p>This will create a demand for diverse, high-performance memory systems, and MongoDB is positioned to provide the flexibility and scalability agents require. With the recent release MongoDB 8.3, our core database has evolved to better support the speed and demands of AI workloads. MongoDB also delivers the retrieval accuracy necessary for agent outputs to be trusted (a non-negotiable for customer-facing applications) while optimizing tokens and cost in production.</p>
<p>Every AI team is currently making a bet about what the future of the agentic stack will look like. The ones betting on a flexible, production-ready data platform like MongoDB—that enables teams to innovate now while ensuring structure and resilience for the future—will be able to pivot quickly. The ones betting on rigid schema designs, or on a smattering of specific models and frameworks, might end up redoing their plumbing instead of shipping products.</p>
<p>Figure 2. Advantages of MongoDB's flexible schema for AI workloads.</p>
<p>Production Ready Agents Blog - Image 2
media</p>
<p>MongoDB is built for AI: JSON is the lingua franca of AI. The information agents need is highly dynamic and can be structured, semi-structured, and unstructured. MongoDB provides the schema flexibility inherently needed by the data and allows attaching metadata for richer, more precise context. Dynamic, adaptive schemas that evolve in place as fast as thought without breaking what runs on top. The MongoDB document model isn’t adapted for AI; it’s the natural shape of AI data.</p>
<p>MongoDB offers one data platform: Every data requirement for production AI is natively integrated. Search, vector search, embeddings, hybrid retrieval, time series, and streaming run on the same OLTP foundation 67,000+ customers trust with mission-critical applications—with one API, one security model, one operational footprint.</p>
]]></description>
      <pubDate>Thu, 11 Jun 2026 19:46:11 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/production-ready-agents-need-production-ready-data-platform</link>
      <guid>https://www.mongodb.com/company/blog/innovation/production-ready-agents-need-production-ready-data-platform</guid>
    </item><item>
      <title>Agentic Supplier Management with MongoDB Atlas, Voyage AI, and Multi-Modal Search</title>
      <description><![CDATA[<p>Retail supply chains are not a back-office logistics function; they are a high-stakes, board-level concern. Imagine learning suddenly that shipment rerouting surcharges have doubled due to new regional escalations; the impact on competitive differentiation and consumer trust is immediate. As a result, a long-standing focus on linear efficiency and lean inventory is being disrupted by a mandate for resilience and AI-driven responsiveness. To survive, retailers must move beyond the rigidity of legacy systems and embrace an AI-ready data platform that can pivot as fast as headlines change.</p>
<p>Indeed, a 2026 study by KPMG reported that businesses are establishing new performance metrics, centered around post-disruption recovery time, supplier diversification, sourcing agility, revenue growth from improved experiences, cost savings, and employee engagement.</p>
<p>Now, retailers are modernizing their supplier management capabilities. An effective supplier management application that boosts visibility, builds resilience, and delivers material business benefits must be underpinned by unified supplier data and AI copilots. To unlock these next-generation capabilities, retail leaders use MongoDB as a unified data foundation, enabling the high-velocity intelligence and material results required in today’s volatile landscape.</p>
<p>However, the business agility of many organizations remains restricted by their enterprise resource planning (ERP) systems, which were designed for an era when stability was assumed, laborious data access was the norm, and delays due to batch processing were acceptable. These legacy foundations have become an operational bottleneck and a strategic threat that prevents real-time responsiveness to external shocks.</p>
<p>The speed of supply chain decision-making is hard-capped by the difficulty of getting fast, accurate answers from supplier information buried in legacy systems, PDFs, spreadsheets, and email chains. These systems fail because they are not able to force incompatible data profiles into a one-size-fits-all table structure. Any multi-modal data, such as images and PDFs, is not queryable. By the time a supplier manager has gathered the data required to make a decision, hours, if not days, have passed.</p>
<p>Benefits of supplier management modernization</p>
<p>The opportunity for retailers that move decisively to modernize is measured in both profitability and market share. IDC predicts that 70% of large retailers will invest in data modernization to unlock better insights and resilience by 2027.</p>
<p>To achieve true resilience, retailers must decouple supplier management from the ERP core and deliver a high-impact capability for the business. MongoDB facilitates low-latency data access, geospatial data, and multi-modal AI-assisted discovery that can deliver a world-class supplier management capability. By creating a dedicated application with MongoDB as its consolidated operational data layer, retailers gain the flexibility to handle modern complexities without the legacy overhead.</p>
<p>Imagine a geopolitical escalation has triggered a 50% tariff on aluminium imports from South Korea from midnight tonight. The external event propagates its way into your modernized system, triggering a real-time identification of your impacted suppliers. The business assesses this impact and decides whether to seek alternatives. Instead of typing in a specific supplier attribute, they describe the need: &quot;Alternative dairy partner in a tariff-neutral zone.&quot; The system scans thousands of supplier profiles and digitized contracts stored as high-dimensional vectors. Within seconds, it identifies a mid-sized supplier that hasn't been used in two years. The business delves deeper into the supplier details and decides they are a suitable alternative. The risk has been mitigated; the disruption avoided. Breaking free from the pitfalls inherent within legacy systems has ensured the business remains operationally agile in the face of external change.</p>
<p>Figure1. An Agentic Supplier Management solution, with multi-modal search, powered by MongoDB.</p>
<p>Agentic Supplier Management Blog - Image 1
media</p>
<p>Operational flexibility for supplier attributes</p>
<p>Suppliers are complex entities with varied and evolving attributes. A textile supplier in Vietnam will have very specific data requirements when compared with a packaging partner in Poland. New requirements will emerge over time, like the need to track a custom &quot;Tariff Exposure Rating&quot; or &quot;Sustainability Score&quot; for 500 suppliers in a specific region. Business users will expect a modern application to add those fields instantly to the relevant supplier profiles without taking the system offline or rewriting the schema.</p>
<p>MongoDB’s flexible data model allows different supplier data attributes to be stored inside a single collection of suppliers. This polymorphic capability allows data to evolve at the same pace as global trade policy, without impacting core operations.</p>
<p>Sourcing agility with semantic discovery</p>
<p>When a primary supplier is sidelined by a localized lockdown or a shipping bottleneck, the clock starts ticking. Traditionally, finding an alternative meant a manual, frantic search through spreadsheets. In a modern system, business users will expect semantic search capabilities, low-latency experiences, and intelligent, AI-powered assistance.</p>
<p>MongoDB provides multi-modal intelligence with Voyage AI, a specialized retrieval layer for AI applications that provides API-based embedding models and re-rankers. It enables unstructured data like documents and images to be defined as high-dimensional vectors, all stored right beside standard operational data in the same MongoDB platform.</p>
<p>When a supplier in a disrupted region fails, MongoDB Vector Search can instantly identify alternative suppliers across your global network who have the most similar attributes. Think product attributes, lead times, and sustainability credentials. Because semantic search is based on mathematical &quot;closeness&quot; rather than exact keyword matches, it can surface a high-potential partner in a different region that your team might have otherwise overlooked. This transforms searching from a reactive, manual scramble into a proactive, intelligent capability</p>
<p>Real-time, low-latency visibility</p>
<p>In 2026, visibility is no longer a luxury; it is the heartbeat of operational survival. Most retailers are paralyzed by disconnected systems that trap critical data points in isolated silos, leaving decision-makers to act on data that is difficult to access or out-of-date. In a disruption scenario, this disconnect is fatal. Unifying supply chain data into a single, coherent layer is the only way to ensure that customer promises are grounded in current reality.</p>
<p>Through MongoDB Change Streams, the data platform acts as a high-speed nervous system, propagating updates from legacy cores to a modernized supplier application with near-zero latency. Because MongoDB does not require a rigid, pre-defined structure for every incoming piece of data, you can instantly ingest a flow of data directly into your supplier profiles.</p>
<p>This immediacy fundamentally changes the dynamic of an impending crisis: instead of managing the aftermath of an external issue over an extended period, the business can address the impact in minutes. Decision-making shifts from reactive guesswork to high-confidence execution, allowing businesses to reroute shipments or trigger alternative sourcing before the disruption reaches the bottom line.</p>
<p>The foundation of resilience</p>
<p>By leveraging MongoDB’s AI-ready data platform to modernize supplier management, retailers will achieve business outcomes that were previously impossible. When supply chain disruption inevitably occurs, the business can be empowered with AI-driven impact assessment, semantic discovery of alternative supplier options, and multi-modal data access, combining to mitigate risk and maintain consumer confidence.</p>
<p>Figure 2. An AI-driven Supplier Management workflow with MongoDB.</p>
<p>Agentic Supplier Management Blog - Image 2
media</p>
<p>Market data from Congruence shows that 72% of leading retailers are investing in AI-integrated platforms, including supply chain. While the 2026 macroenvironment generates supply chain issues that result in manual struggles and customer frustration, competitors will use MongoDB to treat their supplier management agility as a dynamic engine for resilience and value.</p>
<p>Our recommendation is simple: start your migration to a flexible, AI-ready data platform now, or prepare to be outmaneuvered by competitors that are already moving on.</p>
<p>Agentic Supplier Management Blog - Aside
aside</p>
<p>References</p>
<p>KPMG (2026), Key trends impacting supply chains in 2026</p>
<p>IDC (2025), ​IDC FutureScape: Worldwide Retail 2026 Predictions</p>
<p>Congruence Market Insights (2025), Next-Gen Retail Technology Market Report: Growth Drivers, Market Dynamics &amp; Future Potential (2026–2033)</p>
]]></description>
      <pubDate>Wed, 03 Jun 2026 19:51:09 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/agentic-supplier-management-with-atlas-voyage-ai-multi-modal-search</link>
      <guid>https://www.mongodb.com/company/blog/innovation/agentic-supplier-management-with-atlas-voyage-ai-multi-modal-search</guid>
    </item><item>
      <title>Fighting Tool Sprawl: The Case for AI Tool Registries</title>
      <description><![CDATA[<p>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.</p>
<p>Every enterprise needs its own shared tool registry, one that reflects its specific regulatory environment, security posture, and operational conventions. To be clear, this is not an argument for a public package manager, something like npm, PyPI, or Maven. The infrastructure each enterprise needs is internal; scoped to its own teams, its own data, its own policies, its own domain. Trying to expand the scope beyond the confines of individual organizations would be premature standardization in a fast-moving, nascent space.</p>
<p>A shared enterprise tool registry is not an optimization or a nice-to-have. It is foundational infrastructure as agent deployments scale beyond early experiments. The case for it rests on two pillars: reducing coordination cost and enabling risk management, both for the humans building with agents and for the agents themselves.</p>
<p>AI agents depend on tools that retrieve data, write records, trigger workflows, and call external APIs. According to McKinsey, in most large organizations, these tools are built by individual teams in an ad hoc fashion: undocumented, ungoverned, and invisible to the rest of the organization. This pattern is familiar to most engineering leaders, and the fragmentation it creates compounds with every new agent deployment. Teams rebuild what already exists elsewhere, security reviews miss tools that were never registered, and when something breaks, no one has a complete picture of what is running or why.</p>
<p>A coordination failure at infrastructure scale</p>
<p>The software industry solved an analogous problem decades ago with package managers. Centralized registries gave teams a way to discover, depend on, and govern shared code. The learning was clear: preventing duplication and inconsistency is an infrastructure problem, not a discipline problem.</p>
<p>The agent era presents the same problem in a new domain. When Kong launched its enterprise MCP Registry in February 2026, they explicitly called out the problems of manual MCP configuration, hardcoded and managed tool isolation across teams, fragmented integrations, and limited organization visibility.</p>
<p>Fragmented tool development is not a consequence of poor engineering practice. Rather, it is the predictable outcome of asking teams to solve an infrastructure problem at the application layer.</p>
<p>The visibility problem</p>
<p>Gravitee's The State of AI Agent Security 2026 survey quantifies what happens when agent tooling is invisible to the people responsible for securing it. The survey found that only 14.4% of teams with agents beyond the planning phase have full security approval, and 88% of organizations had an agent-related security incident this year. Bad practices like shared API keys are endemic, with only 22% of organizations treating agents as independent identities. This governance gap transforms agents from productivity boosters into high-velocity liabilities capable of executing unauthorized actions or leaking sensitive data before a human can even intervene.</p>
<p>The story is clear: adoption is outpacing governance, and in a race for speed, old lessons are having to be retaught. The majority of deployed agents (and the MCP servers powering them!) are operating without any security sign-off. This is not primarily a resourcing failure, and it is not something a registry alone solves. Security teams cannot review what they cannot discover, and without a registry, discovery is manual, incomplete, and stale. A registry does not make tools inherently secure; rather, it makes security work possible by ensuring tools exist not as transitory, ad hoc shims, but rather as inventoried artifacts that audits and policy can attach to.</p>
<p>It is worth revisiting public package managers here. These registries have not been able to eliminate a number of security problems, issues such as typosquatting, malicious packages, and dependency confusion, showing clearly that centralization alone is not a security solution. But they also show the converse: a registry is a precondition for security. Numerous community responses to breaches in these ecosystems demonstrate the power centralization provides. Centralization does not guarantee security, but decentralization forfeits the means to coordinate it.</p>
<p>Governance requires shared context</p>
<p>The default posture in most agent deployments is permissive: tools are available unless explicitly blocked. AgilityFeat's analysis of enterprise AI guardrails identifies the structural risk this creates, since an architecture not built on deny-by-default increases risk and creates upkeep costs.</p>
<p>Allow-by-default, replicated across dozens of independent agent deployments, produces an attack surface that scales with adoption. Inverting this requires a coordination point, a shared, organization-wide context. The registry itself isn’t a governance layer, but it is what makes governance possible. When every tool an agent can use is registered with ownership, version, and review status, the governance layer has something concrete to enforce against. Without that context, policy has to be reimplemented by every consuming team, and consistency becomes impossible.</p>
<p>Frontegg's framework for AI agent governance describes what that policy layer looks like operationally: agent actions mapped to explicit, granular guardrails that define the operational boundaries for what any agent can attempt or execute. These guardrails live outside the registry, but they depend on it. A guardrail that references a tool the security team has never heard of cannot be written in the first place.</p>
<p>What a production-grade tool catalog requires</p>
<p>A mature enterprise tool registry has two core functions, discovery and versioning, and serves as the foundation for two others: certification metadata and access control. Think of it as an Internal Developer Portal (IDP) built for the agent era, solving the same coordination problem that IDPs solved for service teams, but one layer up.</p>
<p>Discovery allows any team building an agent to search for existing tools before writing new ones. With ownership metadata, version history, and usage metrics centralized, duplication is reduced not through mandate but through reduced friction. A well-designed catalog goes further than a flat list: tools should be grouped hierarchically by functional domain so that both humans and agents can find relevant capabilities quickly.</p>
<p>Versioning closes a gap that neither discovery nor access controls address: when agent behavior changes, why did it change? A tool registry that tracks versions gives enterprises the visibility to answer that question. Was it the model? A tool prompt update? An underlying API change? Without proper versioning, finding the answer goes from a simple diff comparison to a time-consuming, manual investigation.</p>
<p>Certification status (things like security approval, API contract validation, PII handling checks) is metadata that the registry surfaces, not a boundary that the registry itself enforces. The actual review work happens through the security organization’s existing tooling. The registry’s contribution is making the result of that review visible at the moment a team is deciding whether to adopt a tool, ensuring the review actually informs the decision it was meant to inform.</p>
<p>Access control works the same way. A policy layer enforces authorization scoped to agent identity, team, environment, and action type, reading from the registry to know what tools exist and who owns them. The registry’s centralization lets access control be applied consistently, rather than forcing each team to come up with something bespoke.</p>
<p>None of this is achievable when each team maintains its own isolated tooling stack. Platform teams already understand why IDPs exist. The value of the paradigm in the agent context is no different.</p>
<p>The compounding cost of inaction</p>
<p>The cost of inaction is direct, not merely operational and security-related. Without a searchable, well-organized catalog of tools, teams continually reinvent the wheel, since it is easier to generate a tool than to find one that already exists. Duplication means redundancy and technical debt. A registry, by making tools discoverable and reusable, converts that redundant spend into capacity for actual work.</p>
<p>For platform engineering teams, the trajectory is clear. Agent adoption is increasing, tool duplication is increasing with it, and the shims that worked at small scale will not hold as the number of agents and tools grows. The security exposure documented in the Gravitee survey will widen, not narrow, without structural intervention.</p>
<p>The organizations that build centralized tool infrastructure now will be able to onboard new agents quickly, govern them consistently, and audit them when something goes wrong. Those that defer will rediscover, the hard way, what platform teams learned a decade ago: coordination problems do not resolve themselves at the application layer. They compound there.</p>
]]></description>
      <pubDate>Mon, 11 May 2026 14:35:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/technical/fighting-tool-sprawl-case-for-ai-tool-registries</link>
      <guid>https://www.mongodb.com/company/blog/technical/fighting-tool-sprawl-case-for-ai-tool-registries</guid>
    </item><item>
      <title>AI Is Changing What Customers Need From a Database. MongoDB 8.3 Is Built for It</title>
      <description><![CDATA[<p>Today, we announced at .local London that MongoDB 8.3 is built for the speed AI demands—and our customers can't afford to wait.</p>
<p>The data layer has to move at AI speed</p>
<p>The old contract between databases and the applications on top of them was simple: databases improve slowly, and architectures evolve around them. AI has changed that contract.</p>
<p>The workloads our customers are shipping today—agents retrieving at sub-100ms, retry storms hitting in milliseconds, multi-region deployments that can't trade compliance for latency—were edge cases 18 months ago. Now they're the baseline.</p>
<p>MongoDB 8.3, generally available today, is our fourth significant release in 19 months. These releases compound. Customers running on 8.0 have seen 36% faster reads and 59% higher throughput for updates. 8.3 adds another 35% to write throughput, 45% to reads, and 15% to ACID transactions over 8.0 — without changing a line of application code.</p>
<p>Enterprises like Adobe, running the most demanding AI in production, have made the requirements clear: sub-100ms retrieval, sub-second context updates, zero downtime. That's what MongoDB Atlas is built for.</p>
<p>That's the commitment: when the data platform keeps pace, our customers can focus on shipping.</p>
<p>MongoDB.local London Core Blog 2026 - Image 1
media</p>
<p>Run anywhere. Stay secure.</p>
<p>Where you run your agents isn't just an infrastructure decision anymore. Now, it's a critical compliance and security decision as well. While most platforms force a trade-off between global reach and necessary control, with 130 regions across AWS, Google Cloud, and Microsoft Azure, Atlas doesn’t force you to compromise. Atlas even enables clusters spanning multiple providers simultaneously.</p>
<p>Avalara and Iron Mountain both took the cloud-agnostic path, modernizing on Atlas so they could meet their customers wherever they ran. The deployment shape changes. The data layer underneath doesn't.</p>
<p>What's shifted in the last year is the pressure on both ends. Customers want retrieval and embedding capabilities closer to their users, in more places, on more clouds. They also want more authority over the residency of their data. Those two demands used to be in tension. They don't have to be.</p>
<p>Cross-region connectivity for AWS PrivateLink, generally available today, is the clearest example. Traffic between Atlas clusters in different AWS regions stays on the AWS private backbone, with no public internet exposure. Security and compliance teams get the guarantees they need. Engineering teams design around fewer edge cases. Nobody has to make a trade-off.</p>
<p>Built to keep pace</p>
<p>Every capability in this post addresses friction that technical leaders have been engineering around for years. They solve different problems, but share one objective: to eliminate the infrastructure trade-offs that slow down production of AI.</p>
<p>The AI workloads our customers will run 18 months from now will look different from those today. That's not a risk. That's the point. Four significant releases in 19 months isn't a marketing number. It's a signal about how seriously we take the current pace of change, and our commitment to staying ahead of it for our 65,200+ customers.</p>
<p>Getting agents to retrieve the right information, accurately and at speed, is where embeddings and memory come in. Pablo Stern covers that in his blog, The Bottleneck in Enterprise AI Isn't the Model. It's the Data.</p>
]]></description>
      <pubDate>Thu, 07 May 2026 14:33:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/product-release-announcements/ai-changing-what-customers-need-from-database-mongodb-8-3-built-for-it</link>
      <guid>https://www.mongodb.com/company/blog/product-release-announcements/ai-changing-what-customers-need-from-database-mongodb-8-3-built-for-it</guid>
    </item><item>
      <title>New Research Reveals Overcoming Legacy Tech Issues Key to AI Success</title>
      <description><![CDATA[<p>This guest post comes from IDC’s Dr. William Lee, Senior Research Director, Service Provider and Core Infrastructure Research. MongoDB commissioned IDC to explore the connection between legacy infrastructure, data challenges, and AI across Asia Pacific, and today we’re happy to share that work. For more, see the full MongoDB-sponsored IDC InfoBrief, Modernizing Legacy: Winning in the Age of AI, Doc #AP242555-IB, April 2026.</p>
<p>AI ambition is everywhere across Asia/Pacific. But ambition alone does not determine success. Organizations are discovering that AI outcomes are directly tied to the quality, accessibility, and modernity of their underlying technology stack and associated data technology foundations.</p>
<p>Organizations that have managed to stay abreast of technical and data management changes across the application and infrastructure stacks, by embedding modernization into their organizational DNA, are experiencing 3x more digital revenue growth than those that are bound up in technical and data debt.</p>
<p>To better understand this connection, IDC surveyed 1,400 organizations across eight Asia/Pacific markets. The findings reveal that modernization is no longer a side initiative. It is the core of a sustainable AI strategy.</p>
<p>The AI readiness divide: Leaders versus mainstream</p>
<p>IDC’s latest Asia/Pacific Modernization Survey, sponsored by MongoDB, identifies two distinct groups:</p>
<p>The Mainstream Cohort: organizations still burdened by technical debt, siloed data, and skills gaps</p>
<p>The Leaders Cohort: organizations that have embedded modernization into their strategy and experience the business results to match</p>
<p>This divide is not theoretical. It is measurable in business performance. Organizations in the Leaders Cohort generate nearly three times more digital revenue than their peers.</p>
<p>The difference is not simply higher AI spending. Leaders modernize core infrastructure, align executive support with transformation goals, and invest in skills development alongside technology. They treat AI readiness as an enterprise capability—not a standalone initiative.</p>
<p>APAC IDC Blog Image 1
media</p>
<p>The rigidity trap: Technical debt and AI failure risk</p>
<p>A significant portion of Asia/Pacific organizations remain constrained by legacy architectures. According to IDC’s research, 43% report that their existing architecture is a major obstacle, making it difficult to build new applications without extensive modernization.</p>
<p>This rigidity creates what IDC refers to as data debt—siloed, redundant, outdated, and poor-quality data that undermines AI performance and increases operational cost, and is in addition to the growing levels of technical debt that are being accumulated by organizations due to the slow modernization of older applications.</p>
<p>When AI systems are trained on fragmented or inconsistent data:</p>
<p>Outcomes become unreliable</p>
<p>Bias risks increase</p>
<p>Operational costs rise</p>
<p>Business trust erodes</p>
<p>IDC predicts that CIOs who fail to launch data debt remediation initiatives will face 50% higher AI failure rates and rising costs by 2027.</p>
<p>Yet one-third of all enterprises continue to rely on legacy relational databases.</p>
<p>Many such databases have been implemented in support of a wide array of business applications where business leaders expect they can use AI. Yet the legacy RDBMS-type databases are not capable of delivering on the dynamic, rapidly evolving, high-volume real-time demands that AI requires.</p>
<p>Organizations that are unable to move to AI-ready application stacks are being left behind by those that have already made the switch.</p>
<p>The gap between AI investment and infrastructure readiness is widening.</p>
<p>APAC IDC Blog Image 2
media</p>
<p>Legacy drag: The real business impact</p>
<p>The consequences of technical debt are already visible.</p>
<p>95% of organizations report project delays</p>
<p>90% have experienced failed modernization initiatives</p>
<p>89% acknowledge technical debt as a major modernization obstacle</p>
<p>In addition, organizations cite weak security integration, limited engagement with the business users, and outdated workflows as compounding challenges.</p>
<p>Modernization failures are rarely just technical. They are organizational and structural.</p>
<p>What sets leaders apart</p>
<p>The Leaders Cohort does not operate in a constraint-free environment. Instead, they respond differently.</p>
<p>IDC defines Leaders as organizations—across both digital-native and traditional industries—that have broken free from legacy rigidity and embedded modernization into ongoing operations. Their distinguishing characteristics include:</p>
<p>Continuous, multi-pronged approaches to addressing legacy systems</p>
<p>Alignment between executive leadership, funding, and AI outcomes</p>
<p>Investment in modernization as a long-term capability, not a one-off project</p>
<p>Strong focus on AI and modern application development skills</p>
<p>The result is not just better IT performance. Leaders grow digital revenue faster and are positioned to extract value from AI initiatives earlier and more consistently than their peers.</p>
<p>Cloud-centric data management: A strategic enabler</p>
<p>Modern data platforms are central to this shift.</p>
<p>In IDC’s research, 38% of Asia/Pacific organizations identify cloud-centric data management platforms as their top modernization investment priority for 2026. The motivation is clear: support hybrid architectures and AI workloads without introducing additional complexity.</p>
<p>While AI enablement is a universal requirement, Leaders distinguish themselves by prioritizing:</p>
<p>Security and compliance</p>
<p>Flexibility across structured and unstructured data</p>
<p>Scalable architectures aligned to modern AI toolchains</p>
<p>This capability is increasingly critical. Much of today’s AI-relevant data—including content, sensor outputs, and customer interactions—resides in unstructured formats that traditional architectures struggle to integrate effectively.</p>
<p>Handling both structured and unstructured data seamlessly has become a competitive differentiator.</p>
<p>Modernization as a continuous strategy</p>
<p>IDC’s perspective is clear: modernization is no longer a technology refresh cycle. It is a strategic operating model.</p>
<p>Successful organizations approach modernization across three dimensions:</p>
<p>People</p>
<p>Leaders invest deliberately in AI and modern application development skills. They recognize resistance to change as a strategic risk and actively manage it.</p>
<p>Process</p>
<p>They adopt cloud-native approaches rather than repeating short-term “lift-and-shift” migrations that simply relocate technical debt. They use structured prioritization frameworks to embed modernization into business-as-usual operations.</p>
<p>Technology</p>
<p>They modernize to data platforms that support scalability, diverse data types, rapid feature development, and alignment with contemporary AI ecosystems.</p>
<p>The ROI equation: Risk of action versus risk of inaction</p>
<p>Modernization is often perceived as expensive and risky. However, IDC’s analysis suggests that the risk of inaction is frequently underestimated, and this study affirms that those who invest effectively, and continuously, into their application modernization program are experiencing both better ROI and higher digital revenues!</p>
<p>Organizations that modernize report:</p>
<p>Significant reductions in reporting time</p>
<p>Double-digit productivity improvements</p>
<p>Meaningful cost savings</p>
<p>Hundreds of thousands of dollars in quantified cost reductions</p>
<p>While full application rewrites and database modernization demand greater upfront investment than lift-and-shift migrations, they can deliver up to three times the long-term benefit.</p>
<p>For CIOs and business leaders, the decision should not be framed as modernization cost versus status quo stability. It is modernization investment versus escalating AI failure risk.</p>
<p>The Path forward: Legacy systems are not permanent</p>
<p>Overcoming legacy is often perceived to be as significant a risk as taking on new technologies. IDC notes that many CIOs across the region focus on risk avoidance as a priority. In contrast, business leaders are seeking innovative solutions that drive new business opportunities, and so CIOs must balance their risk aversion concerns with the business demands. IDC’s research shows that legacy migrations that are under-funded pose significantly higher risk, and deliver lower returns, than those that are sufficiently funded from the outset.</p>
<p>Organizations that proactively address technical debt, modernize systems, and align leadership and funding around AI-enabled outcomes will increasingly separate themselves from the pack.</p>
<p>Those that delay will face structural disadvantages:</p>
<p>Growing technical debt</p>
<p>Escalating modernization costs</p>
<p>Underperforming AI systems</p>
<p>Slower digital revenue growth</p>
<p>IDC’s research shows that the next wave of AI advantage in Asia/Pacific will not be determined solely by model sophistication. It will be determined by architectural foundations.</p>
<p>Ultimately, without modernization, there can be no sustainable AI strategy.</p>
]]></description>
      <pubDate>Tue, 14 Apr 2026 17:01:07 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/new-research-reveals-overcoming-legacy-tech-issues-key-ai-success</link>
      <guid>https://www.mongodb.com/company/blog/innovation/new-research-reveals-overcoming-legacy-tech-issues-key-ai-success</guid>
    </item><item>
      <title>MongoDB Predictive Auto-Scaling: An Experiment</title>
      <description><![CDATA[<p>You can often predict a load spike before it arrives. Maybe it happens at the same time every day, or there’s always a spike at midnight on a Friday when you run a certain batch job. Or maybe it’s not cyclical, but load is rising steadily, and it’s a reasonable guess that it will keep rising for a while. MongoDB Atlas’s reactive auto-scaler handles these spikes, but scaling to the right size takes several minutes. What if MongoDB Atlas could use these temporal patterns—cycles and trends—to scale up a replica set before it’s overloaded?</p>
<p>In 2023, we prototyped predictive auto-scaling. We wanted to see if it was possible to predict rises and falls in load on MongoDB Atlas replica sets. We researched which machine learning models made the best predictions, and estimated how much a predictive auto-scaler could improve performance and save our customers money. 
MongoDB has now rolled out predictive auto-scaling. The production version of the algorithm is quite different from the prototype, and so far, it only scales replica sets up before a predicted load spike; we rely on the existing reactive algorithm to scale them down afterward. Now that predictive auto-scaling is in production, we want to look back at the research project that started it.</p>
<h2>MongoDB Atlas</h2>
<p>MongoDB is free and source-available, you can download it and deploy a database yourself, and lots of people do. But many customers use our cloud service, MongoDB Atlas. Atlas customers decide how many MongoDB servers to deploy in Atlas, what cloud providers and regions to deploy them in, and what size of server: how many CPUs, how much RAM, and so on. Each server in a replica set must use the same tier. (With exceptions.) We charge customers according to their choices, including how many servers, what size, and how many hours they're running. Of course, we compensate our cloud providers (including AWS, Microsoft Azure, and Google Cloud) according to the number and size of servers. We sell MongoDB server sizes as a set of &quot;tiers&quot;—named M10, M20, and so on—which map to specific instance sizes in each cloud provider.</p>
<p>If we could anticipate each customer's needs and perfectly scale their servers up and down, according to their changing demands, that would save our customers money and reduce our carbon emissions.</p>
<h2>Predictive Auto-Scaling Image 1</h2>
<p>media
Back in 2023, MongoDB Atlas’s autoscaling was only reactive. The reactive auto-scaling algorithm scales up after a few minutes of overload, or a few hours of underload. It only scales between adjacent tiers; for example, if an M60 replica set is underloaded, Atlas will scale it down to M50, but not directly to any tier smaller than that. If the customer's demand changes dramatically, it takes several scaling operations to reach the optimum server size. This means servers can be overloaded or underloaded for a while. An underloaded server costs the customer more than necessary. An overloaded server is bad for performance, and if it's really slammed, it could interfere with the scaling operation itself.</p>
<p>The reactive algorithm wants to keep replica sets the perfect size. But it doesn’t react instantly to every change, because it also wants to avoid scaling too frequently. Besides, no matter how quickly the algorithm reacts, the scaling operation itself takes a few minutes to change the replica set’s server sizes. To radically improve auto-scaling, we needed an algorithm that could see the future.</p>
<p>Predictive auto-scaling</p>
<p>We envisioned an algorithm that would forecast each replica set's resource needs. We could scale a replica set up just before it's overloaded, and scale it down as soon as it's underloaded. We would scale it directly to the right server size, skipping intermediate tiers. We'd always use the cheapest size that could meet demand.</p>
<p>Figure 1. An imaginary perfect auto-scaling algorithm.</p>
<p>Predictive Auto-Scaling Image 3
media</p>
<p>Predictive scaling experiment</p>
<p>We hypothesized that there existed some forecasting algorithm that could predict customers’ workload changes, with enough accuracy and foresight to outperform the reactive auto-scaler. We experimented with a variety of algorithms to test whether this was worth building for MongoDB Atlas.</p>
<p>The experiment was possible because Atlas keeps servers' past performance metrics. For a random selection of 10,000 replica sets, we split the history into a training period and a testing period, as usual with machine learning, and trained models to forecast the replica sets' demand and CPU utilization. (CPU is the simplest and most important metric; eventually, we could forecast RAM, disk I/O, and so on.)</p>
<p>Once we'd prototyped this predictive scaler, we estimated how it would've performed during the testing period, compared to the reactive scaler that was running at that time. The prototype had three components:</p>
<p>Forecaster: tries to predict each replica set's future workload</p>
<p>Estimator: estimates CPU% for any workload, any instance size</p>
<p>Planner: chooses the cheapest instance that satisfies forecasted demand</p>
<p>Figure 2. Components of the predictive auto-scaling experiment.</p>
<p>Predictive auto-scaling image 4
media</p>
<p>For each replica set, its history is an input to the Short-Term and Long-Term Forecasters. (We'll explain why we have two Forecasters soon.) The Forecasters must be retrained every few minutes, as new samples arrive.We sampled 25 million points in time from random replica sets in MongoDB Atlas. Each of these samples includes a count of operations per second, an instance size, and the CPU utilization at that moment. We used this to train the Estimator, which can predict the CPU utilization for any amount of customer demand and any instance size. This is a hard problem, since we can't see our customers' queries or their data, but we did our best. The Estimator must be retrained rarely, when there's new hardware available, or a more efficient version of the MongoDB software. (Eventually we plan to train an Estimator for each MongoDB version.)</p>
<p>The Forecasters and Estimator cooperate to predict each replica set's future CPU on any instance size available. For example, they might predict that 20 minutes in the future, some replica set will use 90% CPU if it's on M40 servers, and 60% CPU if it's on more powerful M50 servers.</p>
<p>Predictive scaling: Planner</p>
<p>Let's look at the Planner in more detail. Here's a forecasted workload; it's forecasted to rise and then fall.</p>
<p>Figure 3. Adjusting server size just in time.</p>
<p>Predictive Auto-scaling Image 5
media</p>
<p>Predictive scaling: Long-term forecaster</p>
<p>Our goal is to forecast a customer's CPU utilization, but we can't just train a model based on recent fluctuations of CPU, because that would create a circular dependency: if we predict a CPU spike and scale accordingly, we eliminate the spike, invalidating the forecast. Instead we forecast metrics unaffected by scaling, which we call &quot;customer-driven metrics&quot;—e.g., queries per second, number of client connections, and the scanned-objects rate. We assume these are independent of instance size or scaling actions. (Sometimes this is false; a saturated server exerts backpressure on the customer's queries. But customer-driven metrics are normally exogenous.)</p>
<p>Figure 4. Predicting seasonal variations in demand.</p>
<p>Predictive Auto-Scaling Image 6
media</p>
<p>Our forecasting model, MSTL (multi-seasonal trend decomposition using LOESS), extracts components from the time series for each customer-driven metric for an individual replica set. It separates long-term trends (e.g., this replica set's query load is steadily growing) and &quot;seasonal&quot; components (daily and weekly) while isolating residuals. We handle these residuals with a simple autoregressive model from the ARIMA family.</p>
<p>Figure 5. MSTL (multi-seasonal trend decomposition using LOESS).</p>
<p>Predictive Auto-Scaling Image 7
media</p>
<p>By combining these components, we forecast each metric separately, creating a &quot;Long-Term Forecaster&quot; for each. Despite the name, the Long-Term Forecaster doesn't project far into the future; it's trained on several weeks of data to capture patterns, then predicts a few hours ahead.</p>
<p>Figure 6. How often is demand seasonal?</p>
<p>Predictive Auto-Scaling Image 8
media</p>
<p>Most MongoDB Atlas replica sets have daily seasonality. About 25% have weekly seasonality. Generally, if a replica set has weekly seasonality, it also has daily seasonality. Hourly seasonality is rare, and anyway, it isn't helpful for planning a scaling operation that takes a quarter-hour. Replica sets with sufficient daily/weekly seasonality are predictable by the Long-Term Forecaster.</p>
<p>In the chart below, the long-term forecaster learns from the previous two weeks of data (left of the vertical dotted red line) and accurately predicts the next few hours (prediction in green on the far right).</p>
<p>Figure 7. Example “long-term” forecast.</p>
<p>Predictive Auto-Scaling Image 9
media</p>
<p>But only some replica sets have seasonality! For non-seasonal replica sets, the Long-Term Forecaster's prediction of customer-driven metrics is unusable.</p>
<p>Predictive auto-scaling image 10
media</p>
<p>So we added a &quot;self-censoring&quot; mechanism to our prototype: the Long-Term Forecaster scores its own confidence based on its recent accuracy, and only trusts its prediction if its recent error has been small.</p>
<p>Predictive scaling: Short-term forecaster</p>
<p>What can we do when the Long-Term Forecaster isn't trustworthy? We didn't want to fall back to purely-reactive scaling; we can still do better than that.</p>
<p>So we prototyped a &quot;Short-Term Forecaster&quot;; this model uses only the last hour or two of data and does trend interpolation. We compared this to a naïve baseline Forecaster, which assumes the future will look like the last observation, and found that trend interpolation beats the baseline 68% of the time (29% reduction in error).</p>
<p>Figure 8. Approximation of local trends for near-future forecast.</p>
<p>Predictive Auto-Scaling Image 11</p>
<p>Predictive scaling: estimator</p>
<p>The Forecasters predict customer demand, but we still need to know whether CPU utilization will be within the target range (50-75%). That's the Estimator's job. The Estimator takes the forecasted demand and an instance size (defined by CPU and memory), and outputs the projected CPU.</p>
<p>Using a regression model based on boosted decision trees trained on millions of samples, we've achieved fairly accurate results. For around 45% of replica sets, our error rate is under 7%, allowing us to make precise scaling decisions. For another 42%, the model is somewhat less accurate but useful in extreme cases. We exclude the remaining 13% of replica sets with higher error rates from predictive scaling.</p>
<p>Figure 9. Example of input and output of Estimator.</p>
<p>Predictive Auto-Scaling Image 12</p>
<p>Predictive scaling: Putting it all together</p>
<p>With both forecasts and CPU estimates, the Planner can choose the cheapest instance size that we guess can handle the next 15 minutes of customer demand without exceeding 75% CPU. Our experiment showed that this predictive scaler, compared to the reactive scaler in use during the test period, would've stayed closer to the CPU target and reduced over- and under-utilization. For the average replica set it saved 9 cents an hour. That could translate to millions of dollars a year if the predictive scaler were enabled for all MongoDB Atlas users.</p>
<p>Predictive Auto-Scaling Image 14
media</p>
<p>Predictive auto-scaling in production</p>
<p>Our experiment showed that predictive auto-scaling could work in MongoDB Atlas, and we learned important facts: only some replica sets are predictable, and short-term trends are often better signals than daily and weekly cycles.</p>
<p>In the two years since, MongoDB has used these results to develop a production-grade predictive auto-scaler. The algorithms are different, and the code is new—the experiment is more of a godparent to the product, rather than its parent. In November 2025, we began rolling it out in MongoDB Atlas. All customers who enabled auto-scaling (about a third) will soon have both predictive and reactive auto-scaling. This first version is conservative, it only uses predictions to scale replica sets up. If load declines, the reactive auto-scaler will scale the replica set back down after a few hours.</p>
<p>We’re proud that MongoDB’s research and data science teams have contributed an Atlas feature that will help tens of thousands of customers, and we’re excited to see how the predictive auto-scaler evolves.</p>
]]></description>
      <pubDate>Tue, 07 Apr 2026 17:03:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/engineering/mongodb-predictive-auto-scaling-an-experiment</link>
      <guid>https://www.mongodb.com/company/blog/engineering/mongodb-predictive-auto-scaling-an-experiment</guid>
    </item><item>
      <title>Introducing MongoDB Agent Skills and Plugins for Coding Agents</title>
      <description><![CDATA[<p>Software engineering is evolving into agentic engineering. According to the Stack Overflow Developer Survey 2025, 84% of respondents use or plan to use AI tools in their development, up from 76% the previous year. At this rate, the tooling needs to keep pace.</p>
<p>Last year, we introduced the MongoDB MCP Server to give agents the connectivity they need to interact with MongoDB, helping them generate context-aware code. But connectivity was only the start. Agents are generalists by design, and they don't inherently know the best practices and design patterns that real-world production systems demand.</p>
<p>Today, we're addressing this by introducing official MongoDB Agent Skills: structured instructions, best practices, and resources that agents can discover and apply to generate more reliable code across the full development lifecycle, from schema design and performance optimization to implementing advanced capabilities like AI retrieval.</p>
<p>To bring this directly into the tools you use, we're also launching plugins for Claude Code, Cursor, Gemini CLI, and VS Code, combining the MongoDB MCP Server and Agent Skills in a single, ready-to-use package.</p>
<p>Turning coding agents into MongoDB experts
Coding agents are great at producing working code, but they still make common mistakes in production systems, often defaulting to relational thinking that doesn't translate well to MongoDB, such as:</p>
<p>Over-normalizing schemas, ignoring MongoDB's document-oriented strengths.</p>
<p>Underusing compound indexes, causing performance bottlenecks at scale.</p>
<p>Misusing indexes and search indexes, overlooking the consistency trade-off for high-performance full-text search.</p>
<p>Because these pitfalls mirror common human errors, they are naturally reflected in agent outputs. MongoDB Agent Skills address this by providing expert guidance to agents, like schema design heuristics, indexing strategies, query patterns, and operational safeguards, enabling agents to ship more reliable, more consistent code faster.</p>
<p>Agent Skills were introduced by Anthropic as an open standard and have since been adopted by the leading AI development tools, including Claude Code, Cursor, Codex, and more.</p>
<p>This initial release covers the full application development lifecycle on MongoDB, from connection management and schema design to guidance on implementing advanced capabilities. We will continue to update and expand our skills library based on user needs.</p>
<p>Figure 1. MongoDB Agent Skills.</p>
<p>Scaling agentic engineering with MongoDB
As organizations embrace agentic software engineering, existing processes and workflows must be reimagined. The MongoDB MCP Server and MongoDB Agent Skills are built for this shift and work best together, giving builders and agents the tools to move fast without sacrificing guardrails or control.</p>
<p>The MongoDB MCP Server serves as the connectivity layer for your MongoDB deployments. It manages authentication and defines exactly what agents can access and do. Combined with MongoDB’s native authorization, it ensures agents operate with only the permissions they need, while giving teams governance through configurable controls like disabling specific tools.</p>
<p>Agent Skills ensure agents follow best practices from the start, reducing architectural risk, accelerating implementation, and raising the baseline quality of every agent-generated code.</p>
<p>While some skills can be used independently, others work in conjunction with the MongoDB MCP Server for workflows that require it. To simplify setup, the MCP Server and skills are now packaged together as plugins and extensions for Claude Code, Cursor, Gemini CLI, and VS Code, bringing these capabilities directly into your preferred tools.</p>
<p>Figure 2. MongoDB for Claude plugin in action.</p>
<p>We also encourage you to build your own skills as your agentic workflows mature. Whether enforcing internal naming conventions, custom data modeling patterns, or team-specific workflows, skills give you a practical way to codify institutional knowledge and ensure every agent and every developer works from the same playbook.</p>
<p>How to get started
Whether you’re using Claude Code, Cursor, Gemini CLI, or other AI development tools, you can install the MongoDB MCP Server and Agent Skills in seconds.</p>
<p>For example, in Claude Code, install the plugin that bundles both:</p>
<p>Code Snippet
/plugin marketplace add mongodb/agent-skills
/plugin install mongodb@mongodb-plugins</p>
<p>For Cursor, Gemini CLI, and VS Code extensions, refer to their respective documentation.</p>
<p>You can also install the skills for most coding agents using the Vercel Skills CLI (requires Node.js):</p>
<p>Code Snippet
npx skills add mongodb/agent-skills</p>
<p>If you prefer, you can manually clone the GitHub repository and copy the skills into the appropriate folder for your agent.</p>
<p>Similarly, to install the MongoDB MCP Server, use the following command:</p>
<p>Code Snippet
npx mongodb-mcp-server@latest setup</p>
<p>Agentic engineering is changing how teams work, and it is changing fast. Agents need the context and guidance to meet the standards of real-world production applications. With the official MongoDB Agent Skills and plugins, builders can move faster with confidence, and organizations can adopt coding agents knowing that MongoDB best practices are embedded directly into every workflow.</p>
<p>Next Steps
Ship faster, more reliable apps on MongoDB with Agent Skills. Install for Claude Code, Cursor, Gemini CLI and VS Code!</p>
]]></description>
      <pubDate>Tue, 31 Mar 2026 13:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/product-release-announcements/introducing-mongodb-agent-skills</link>
      <guid>https://www.mongodb.com/company/blog/product-release-announcements/introducing-mongodb-agent-skills</guid>
    </item><item>
      <title>Enhance Your In-IDE Data Browsing Experience With MongoDB</title>
      <description><![CDATA[<p>MongoDB is excited to announce the general availability of our enhanced data browsing experience in the MongoDB for Visual Studio (VS) Code extension. This new experience offers a unified workspace for developers to visually browse, query, and edit their data natively, streamlining workflows so they can manage their database right where they write their code.</p>
<p>Evolving the developer workflow
The modern developer’s workflow is incredibly fast-paced. With developers juggling an average of 14 different tools daily, the cognitive load of constantly jumping between applications can easily disrupt focus. When your application needs to evolve, working with your data shouldn’t force a break in your flow state.</p>
<p>As the MongoDB for VS Code extension has grown to nearly 3 million downloads, we’ve seen firsthand how developers are pushing the boundaries of what an in-IDE (integrated development environment) database tool can do. While developers love accessing their data directly in the editor, we wanted to transform this experience to be even more visual, actionable, and seamless. Instead of switching to external terminals for quick tasks or taking the time to translate familiar MongoDB Shell commands into Extended JSON (EJSON), we are bringing a full-fledged, intuitive data management suite right to your VS Code sidebar.</p>
<p>Exploring what’s new in the MongoDB for VS Code extension
Here are the key improvements that transform the extension into a complete workflow solution:</p>
<ol>
<li>Paginated tree view and prescriptive titles
Understanding complex data models at a glance is crucial for rapid development. We are transforming the document browsing experience by automatically detecting human-readable fields (like names or emails) to create prescriptive document titles, rather than just displaying standard _id hashes. Furthermore, you can now use a structured, paginated tree view to instantly browse collection data from the “Documents” tab, as well as interactively explore playground results when you run a script. This means you get the full context of your collections visually and instantly.</li>
</ol>
<p>Figure 1. Paginated tree view and prescriptive titles</p>
<ol start="2">
<li>Powerful action menus and header controls
Navigating your data should be inherently actionable. To give you full management capabilities without the need for you to write manual queries, we’ve added a new action header directly inside the tree view. This header equips you with buttons to instantly insert documents, refresh (to rerun the current query or playground script), sort ascending/descending by _id, paginate through results, and even bulk delete to empty a collection.</li>
</ol>
<p>Additionally, managing individual records is easier than ever. Simply hover over any document within the tree view to reveal a contextual action menu that allows you to instantly delete, copy, clone, and edit the document natively.</p>
<p>Figure 2. Native action menus</p>
<ol start="3">
<li>Native editing and shell syntax default
We wanted to make interacting with your database as natural as possible.</li>
</ol>
<p>To remove the friction of translating your commands, we’ve added a setting that defaults to standard Shell syntax over EJSON for all insert, clone, edit, and clipboard functionalities. This guarantees that any document you copy or any quick fix you make in the extension is instantly compatible with your application code.</p>
<p>Figure 3. Clone action.</p>
<p>Stop context switching and start building
Your database tools should adapt to your workflow, not disrupt it. By bringing native data editing, intelligent tree views, and standard Shell syntax directly into your sidebar, we’re bridging the gap between writing code and managing data. You no longer have to sacrifice your flow state just to make a quick database fix, verify a playground result, or translate verbose EJSON formats. This overhaul is another step in our commitment to making this MongoDB extension your ultimate command center—empowering you to spend less time wrestling with external tools and more time actually building your application.</p>
]]></description>
      <pubDate>Tue, 17 Mar 2026 17:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/technical/enhance-your-in-ide-data-browsing-experience-with-mongodb</link>
      <guid>https://www.mongodb.com/company/blog/technical/enhance-your-in-ide-data-browsing-experience-with-mongodb</guid>
    </item><item>
      <title>Observability and OpenTelemetry: Introducing MongoDB Atlas Log Integration</title>
      <description><![CDATA[<p>In high-stakes enterprise environments, outages do not wait for business hours, and neither do IT/Network Operators.</p>
<p>A latency spike hits the dashboard, and metrics signal that the database is under pressure. The cause? Indeterminate. Meanwhile, the business impact is immediate: orders fail to process, customers can’t access accounts, transactions stall, and critical records become temporarily unavailable. Every minute of uncertainty translates into lost revenue, frustrated users, and escalating pressure.</p>
<p>Teams often fall back on a familiar—yet time-consuming—ritual: logging into their data platform, exporting large log files, extracting compressed archives, and manually searching through thousands of lines of entries to identify the issue. What should be a quick diagnosis becomes a manual context-switching investigation. By the time the problematic query, configuration issue, or audit event is identified, users have already experienced the disruption—and the business has absorbed the cost.</p>
<p>MongoDB believes the database should be the heartbeat of a digital business. So we’re introducing a new log integration that brings MongoDB Atlas system and audit logs directly into external observability and storage platforms. This enhancement helps bridge the gap between metrics and meaning when it matters most.</p>
<p>Flexible log delivery for modern observability workflows
Now database operators, DevOps pros, and IT Operations teams alike can send MongoDB system and audit logs—including mongod, mongos, and audit logs—directly to the tools they already rely on: Datadog, Splunk, Google Cloud Storage, Azure Blob Storage, or Amazon S3.</p>
<p>Beyond native integrations, MongoDB supports sending logs via OpenTelemetry (OTel), the open-source standard for collecting and transmitting telemetry data. This enables customers to export MongoDB logs to any observability or logging backend that supports OTel. By using a vendor-neutral, standards-based protocol, MongoDB fits seamlessly into modern observability architectures. This eliminates lock-in and preserves flexibility as tooling strategies evolve.</p>
<p>Enabling real-time clarity
Modern enterprises generate rich system logs essential for debugging and compliance. However, when these logs are siloed, operational inefficiencies grow. Manual log access introduces friction, delays resolution, and creates a visibility gap between metrics and logs.</p>
<p>MongoDB’s new log integration transforms that experience with:</p>
<p>Accelerated troubleshooting: Send logs in near real-time to observability platforms like Datadog, Splunk, or OpenTelemetry-compatible backends, enabling teams to quickly identify issues and reduce manual operational steps that slow incident resolution.</p>
<p>Unified telemetry: Correlate MongoDB logs with application traces and infrastructure metrics in existing observability platforms, helping teams quickly understand how database behavior impacts overall system performance.</p>
<p>Simplified compliance: Automatically route audit logs to secure long-term storage such as Amazon S3, helping organizations meet regulatory and audit requirements without manual log management.</p>
<p>Figure 1. Atlas Log Integration configuration options for delivering MongoDB logs to observability and storage platforms.</p>
<p>image</p>
<p>Real-world use cases
How does this look in practice for modern application, operations, and engineering teams? Here are a few examples.</p>
<p>table</p>
<p>The criticality of observability
As applications scale, the database becomes the most critical layer of an organization’s technology stack. Missing or siloed visibility leads to costly downtime and fragmented decision-making.</p>
<p>This log integration is available for dedicated M10+ clusters. An external sink can be configured in minutes:</p>
<p>Navigate to the Project Integrations page in the MongoDB Atlas UI.</p>
<p>Select the intended destination: Datadog, Splunk, Google Cloud, Microsoft Azure, Amazon S3, or any OTel log endpoint.</p>
<p>Enter the required credentials and select the desired logs to send: mongod, mongos, or audit.</p>
<p>Note: Atlas Search logs are also currently available via private preview.</p>
<p>Figure 2. MongoDB Atlas logs integrated into an OpenTelemetry observability pipeline.</p>
<p>image</p>
<p>One observability strategy, built to scale
For teams that need fast, MongoDB-centric visibility, MongoDB Atlas continues to offer powerful native tools like Query Insights and the Query Profiler. These capabilities are designed to surface what is happening inside a user’s clusters with minimal friction.</p>
<p>However, as organizations scale, database insights can not live in isolation. MongoDB Atlas’s log integration extends observability systematically to the data plane. This enables MongoDB logs to flow into the observability platforms teams already use across engineering, security, IT operations, and compliance. With native integrations and an OpenTelemetry-compatible endpoint, teams can route logs wherever they are needed. This enables rapid troubleshooting, stronger auditability, and confident scaling without blind spots.</p>
]]></description>
      <pubDate>Thu, 12 Mar 2026 14:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/product-release-announcements/introducing-mongodb-atlas-log-integration</link>
      <guid>https://www.mongodb.com/company/blog/product-release-announcements/introducing-mongodb-atlas-log-integration</guid>
    </item><item>
      <title>Inside MongoDB Dublin: The Heart of Our International Growth</title>
      <description><![CDATA[<p>Nestled between the Irish Sea and the Wicklow Mountains, MongoDB’s Dublin office brings together people from around the world. It’s a place where you can build a meaningful career, contribute to leading global products, and feel part of a close-knit community. Located in Ballsbridge just south of Dublin city center, the office is a short walk from the Lansdowne DART station and is well-served by multiple bus routes, making it easy to plug into everything the city has to offer.</p>
<p>Image of a wall in the MongoDB Dublin office that is painted with Dublin relevant illustrations and text that says &quot;Build together&quot; and &quot;Make it matter&quot;
As MongoDB’s international headquarters, Dublin is a key hub where over 300 employees from more than 40 nationalities own critical parts of the company’s products and support customers running mission-critical systems across the globe. Established in 2012, MongoDB Dublin has long played a pivotal role in helping the company achieve its mission of empowering innovators to create, transform, and disrupt industries by unleashing the power of software and data.</p>
<p>In this spotlight, you’ll hear from people across MongoDB’s Product &amp; Technology, Sales, and Technical Services teams about what it’s like to build your career—and your life—in Dublin with MongoDB.</p>
<p>Image of CEO, CJ Desai, speaking in front of a group of employees in the Dublin office.
CEO CJ Desai holds an “Ask Me Anything” session in a recent visit to Dublin.
Life at MongoDB Dublin
The MongoDB Dublin office represents both the company’s global energy and the warmth of Irish culture. Ciara, workplace manager for the office, notes:</p>
<p>There’s always something happening here, from fun in-office activities and lively trivia nights to vibrant town halls that bring people together. We run regular volunteer days that give everyone the chance to give back, along with coffee mornings, team socials, and plenty more that keep the atmosphere welcoming and connected.</p>
<p>There’s a real sense that MongoDB Dublin captures true Irish charm and character, friendly, open, and full of personality. That mix creates a workplace that feels both globally diverse and locally grounded. You get the best of both worlds: international perspectives combined with that uniquely Irish sense of humour and hospitality.</p>
<p>MongoDB Dublin isn’t just a workplace—it’s a team that wins and grows together!</p>
<p>Here’s what stands out about life and work here:</p>
<p>Wellness comes first: From private health, dental, and vision care, to Gympass discounts and Headspace subscriptions, we support your physical and mental well-being.</p>
<p>Family and flexibility: Eligible employees enjoy 20 weeks of paid parental leave, fertility and family planning support through Carrot, and Cleo resources for parenting. Our flexible work model means you never have to choose between career and family.</p>
<p>Financial security: We offer life insurance, income protection, and the chance to grow wealth through our employee stock purchase plan.</p>
<p>Time for you: Every employee enjoys 27 days of annual leave, plus extra wellness initiatives like MongoDB Bloom (our internal wellness program), midday meditation sessions, and fun in-office perks.</p>
<p>Growth and development: You’ll have access to dedicated learning programs, technical training and leadership development to upskill in programming, leadership, communication, and more.</p>
<p>Inclusion and community: With over 40 nationalities represented in our Dublin office, our teams reflect the global customers and communities we serve. From active Employee Resource Groups (ERGs) like MDBWomen, Queer Collective, and Config to a warm, collaborative office culture, MongoDB Dublin is a place where you’ll feel supported—whether you’re relocating to Ireland or continuing to grow your career here.</p>
<p>2 separate images of colleagues from MongoDB smiling together during volunteer opportunities.
Local volunteer opportunities, team outings, and other events to bring colleagues together
Hear from the Dublin team
Donal, product &amp; technology leader for EMEA, describes how MongoDB’s platform and culture drew him in:</p>
<p>Joining MongoDB felt like the right move at the right time. MongoDB is an amazing platform, with capabilities ranging from deploy anywhere, support for unstructured and semi-structured data, native vector search for embeddings, and flexible workload handling. The problems we’re tackling around data, scale, and flexibility are real, hard problems and they matter to how modern applications are built.</p>
<p>What’s really impressed me since joining is the engineering culture. People are curious, thoughtful, and open to learning, bringing strong ownership and intellectual honesty to their work. Building out our engineering teams in Ireland is exciting because we’re creating groups that will own critical parts of the product, not just contributing at the edges.</p>
<p>It’s a great moment to join MongoDB in Ireland. The company is growing, the Dublin office is becoming a core engineering hub, and engineers here have the chance to make a real impact. If you’re looking for challenging work, smart teammates, and the opportunity to help shape what we’re building, this is a really exciting place to be.</p>
<p>2 separate images of multiple employees of MongoDB attending events in the Dublin office.
You’ll find the office frequently buzzing with events.
For Max, an engineer working on query optimization, joining MongoDB Dublin has been both a professional challenge and a personal milestone:</p>
<p>MongoDB was the first database I ever used when learning how to build backend applications, so getting the opportunity to intern here and now work here full-time feels like a real full-circle moment. Today, I work on query optimization, a core part of the database engine focused on making queries as fast as possible. It brings a lot of interesting theoretical computer science problems. We get to dive into research papers and actually implement those ideas in practice, which means I’m learning something new every day.</p>
<p>The Dublin team is incredibly international, with talented engineers from all over the world. I genuinely feel lucky to work alongside people with such deep experience building databases. Especially at the start of my career, being surrounded by colleagues I look up to makes a huge difference. We’re often tackling hard problems that haven’t been solved before in the context of document databases, so having that level of expertise around you is invaluable.</p>
<p>It’s been almost a year since I moved to Dublin, and it’s flown by. Relocating to a new country is always a bit daunting, but Ireland is such a welcoming place that it already feels like a second home. Dublin doesn’t always get the credit it deserves, but being so close to both the sea and mountains is something I really value. What more could you ask for?</p>
<p>An image of 3 employees working and taking meeting calls from within small private phone booths.
Need a space for focus time? Grab a phone booth!
On the sales side, Dublin is at the crossroads of cloud, AI, and data-driven innovation, making it an exciting place to build a long-term career in tech sales.</p>
<p>Account executive Stephane shares how MongoDB’s culture and the Dublin market shape the experience:</p>
<p>Selling at MongoDB stands out because of the sales culture and investment in people. You’re constantly challenged to adapt, stay flexible (much like the document model), and raise the bar, both individually and as a team. There’s a strong entrepreneurial mindset here. If you’re curious, proactive, and eager to learn, you’re given real ownership and the support to run with your ideas, rather than being tied to a one-size-fits-all script. It’s why Think Big, Go Far genuinely shows up in how we work.</p>
<p>Dublin sits at the centre of cloud, AI, and data-driven innovation, making it a great place to build a long-term career. Here, you’re not just selling software - you’re helping customers modernise mission-critical systems and move from experimentation to real production impact. I joined MongoDB because I believed in the impact of cloud and digital transformation, and that opportunity has only grown. Now, with AI driving the next wave of innovation, MongoDB is well-positioned to play a meaningful role, and it’s exciting to be part of that journey.</p>
<p>What really sums up sales at MongoDB is the opportunity to grow. There’s a clear path forward, whether that’s moving from sales development representative to account executive, stepping into leadership, or exploring new roles across the business. If you’re motivated, open to learning, and serious about building a long-term sales career, MongoDB gives you the environment and support to do it.</p>
<p>The image on the left shows employees taking a break by playing foosball and billiards together. The image on the right shows employees gathered at a table with open laptops and a larger screen with a presentation.
Silvia, an account development representative, recalls how the culture came through even before she joined—and how it’s shown up since:</p>
<p>From the very first interviews, I was struck by how clearly MongoDB’s values came through. Every conversation felt supportive and intentional. What stood out most was the genuine investment in me as a candidate, making sure I had what I needed to succeed before I’d even contributed anything back.</p>
<p>Once you join, that support only grows. It’s a high-performance environment and the work is challenging, but you’re never doing it alone. Learning is constant, collaboration is open, and from week one, you feel like an active part of the team, without rigid hierarchies holding you back.</p>
<p>Walking into the Dublin office for the first time, I immediately felt the sense of community. In my first month, I met both our CIO and CEO in person. Hearing them speak about the company’s ambition made it clear this is something bigger, and that the work we do here truly matters.</p>
<p>An image of two employees smiling with #LifeAtMongoDB photo props.
The annual summer party is always good craic.
The technical services team in Dublin plays a critical role in helping customers succeed on MongoDB. For Fernanda, a manager on the team, that journey has been about impact, community, and the confidence to grow her career in a new country:</p>
<p>I joined MongoDB in 2018, when the Cloud support team had just four people across all of EMEA. From the start, there was a strong culture of ‘we’re here to help each other, you can count on me.’ It made us much more than colleagues, and I had never experienced such a supportive environment before.</p>
<p>What’s kept me here is that this culture never faded as we scaled. Even on cold, rainy Dublin mornings, there’s real warmth in the office, smart conversations, and a real sense that you’re not facing challenges alone. That combination of impact, continuous learning, and a true ‘team first’ mindset is what’s made me stay and grow my career here.</p>
<p>Today, Dublin is larger, more diverse, and deeply connected to global initiatives, but the essence remains the same. You feel welcomed, people are approachable, and there’s a real Build Together mindset across teams.</p>
<p>Ready to build your career in Dublin?
Whether you’re building core database features or partnering with customers on their most strategic initiatives, at MongoDB Dublin, you’ll be surrounded by people who want to see you succeed and by teams that are shaping the future of software.</p>
]]></description>
      <pubDate>Fri, 27 Feb 2026 16:30:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/culture/inside-mongodb-dublin-the-heart-of-our-international-growth</link>
      <guid>https://www.mongodb.com/company/blog/culture/inside-mongodb-dublin-the-heart-of-our-international-growth</guid>
    </item><item>
      <title>Towards Model-based Verification of a Key-Value Storage Engine</title>
      <description><![CDATA[<p>In our previous post, we talked about our process of specifying MongoDB’s distributed transactions protocol and how it enabled novel analysis of its performance characteristics. In this follow-up, we talk about how the modularity of our specification also enabled us to check that the underlying storage engine implementation actually conforms to the abstract behavior defined in our formal specification. That is, we are able to formalize the interface boundary between the sharded transaction protocol and WiredTiger, the underlying key-value storage engine, and develop an automated way to generate tests for checking conformance between the semantics of the underlying storage engine layer and this abstract model.</p>
<p>As mentioned in the previous post, a deeper exploration of the concepts covered in this post is covered in our recently published VLDB ’25 paper, Design and Modular Verification of Distributed Transactions in MongoDB.</p>
<p>Modular, Model-Based Verification
As discussed in Part 1, we had developed a TLA+ specification of MongoDB’s distributed transactions protocol in a compositional manner, describing the high level protocol behavior while also formalizing the boundary between the distributed aspect of the transactions protocol and the underlying single-node WiredTiger storage engine component. As mentioned, the distributed transactions protocol can be viewed as running atop the lower level storage layer.</p>
<p>When considering the correctness guarantees of the distributed transactions protocol, a subtle aspect is its interaction with the concurrency control mechanisms at each layer of the system. In particular, its interaction with the WiredTiger storage engine API, which has various timestamp-based operations implemented to adequately support the correct operation of the distributed transactions protocol.</p>
<p>Our formal model of the distributed transactions protocol was useful for checking its guarantees, but we also wanted to formalize the contract between this distributed protocol and the underlying storage engine, to check that this interface boundary, as defined in our abstract specification, was matched by the implementation. Leveraging the clean interface boundary in our specification, we developed a tool for automatically checking conformance between the WiredTiger implementation and this abstract storage specification (Storage) we defined. Our storage layer specification itself serves as a useful and precise definition of a subset of the WiredTiger storage engine semantics, but we can also use it for automatically generating test cases to check conformance of WiredTiger semantics to our spec.</p>
<p>Figure 1. Compositional specification of distributed transactions in TLA+ and storage engine component.</p>
<p>Path-based test case generation
To do this, we make use of a modified version of the TLC model checker to first generate the storage component specification’s complete graph of reachable states for finite parameters. We then compute a set of path coverings in this graph, where each path is then converted to an individual test case as a sequence of underlying storage engine API calls. This model-based verification technique allows us to automatically generate tens of thousands of individual test cases for WiredTiger which each check that the implementation matches the behavior defined in our abstract specification, which is also the contract relied on by the high level, distributed transactions protocol.</p>
<p>Figure 2. Model-based test case generation workflow.</p>
<p>For a small, complete finite model (2 keys and 2 transactions), we are able to check conformance with WiredTiger with a generated suite of 87,143 tests, which are generated and executed against the storage engine in around ~40 minutes.</p>
<p>Figure 3. Test case generation statistics for the storage layer model.</p>
<p>Our current storage layer specification can be found in Github, and a link to an interactive, explorable version of it can also be found in Github. In the future, we hope to explore modeling of a more extensive subset of the WiredTiger API and explore alternate state space exploration strategies for generating tests, e.g., randomized path sampling, or other strategies that only require approximate coverage of the state space model. This approach bears similarity to other testing efforts we had explored in the past.</p>
<p>Conclusion
Modeling our distribution transactions protocol enabled verification of protocol correctness, and our use of modularity and compositional verification was instrumental in letting us reason about these high-level correctness properties while also being able to automatically check that our abstract storage interface correctly matches the semantics of the implementation. Similar approaches have been explored recently for model-based verification of distributed systems, as well as other approaches for testing systems using path-based test case generation techniques. In the future, we also remain optimistic about the role that LLMs can play in this type of verification workflow. For example, once such a testing harness for checking conformance is developed, having LLMs autonomously develop a model of the underlying system behavior allows for precise characterization of behavior, along with automated test suite generation capabilities.</p>
<p>You can find more details about this work in our recently published VLDB ‘25 paper, and in the associated Github repo that contains our specifications and code, as well as links to in-browser, explorable versions of our specifications.</p>
]]></description>
      <pubDate>Fri, 27 Feb 2026 15:30:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/engineering/towards-model-based-verification-key-value-storage-engine</link>
      <guid>https://www.mongodb.com/company/blog/engineering/towards-model-based-verification-key-value-storage-engine</guid>
    </item><item>
      <title>Innovating with MongoDB | Customer Successes, February 2026</title>
      <description><![CDATA[<p>Who says that winter is when things slow down? MongoDB has had a busy start to the year, with a steady stream of announcements and product features—all against the backdrop of an industry moving at warp speed. It's been a lot, and it's been a blast!</p>
<p>For example, the energy at January’s MongoDB.local San Francisco—where we announced capabilities to help teams ship production AI faster—was infectious. MongoDB isn’t just starting a new chapter in AI; we’re rewriting the book in real time.</p>
<p>The next generation of AI companies isn't just looking for a temporary place to store data; they’re looking to build on a generational modern data platform. Indeed, the most innovative founders are moving away from rigid, legacy systems and embracing a single, fluid foundation that can grow with them.</p>
<p>At MongoDB.local SF, our message was clear: Choose your data platform strategically in order to ship faster. From our new Voyage 4 models to the general availability of our Intelligent Assistant, we are obsessed with anticipating what developers need next. This assistant is particularly impactful because it embeds MongoDB-specific expertise directly into Compass and MongoDB Atlas, allowing developers to troubleshoot performance without the &quot;context-switching&quot; that traditionally slows them down.</p>
<p>In this issue, I’m thrilled to spotlight four startups who are building the future on the right foundation. You’ll see how Modelence and Thesys are using our flexible document model to eliminate 'operational drag,' allowing them to iterate on AI-native workflows in real time. And then there’s Heidi and Emergent Labs, who both are proving that when you simplify your codebase with a unified platform, you can turn a plan into shipped code at record speeds.</p>
<p>I’ve highlighted their journeys below so you can see exactly how these leaders are setting a new pace and changing their trajectory with MongoDB.</p>
<p>Modelence
Modelence aims to modernize backend infrastructure for the era of AI-assisted development. Traditional relational databases and manual systems create significant operational drag, as their rigid schemas and heavy migrations cannot keep pace with agent-native workflows. These legacy systems struggle with the high-velocity requirements of intelligent coding agents, which must iterate on data structures in real time without causing system downtime.</p>
<p>To build a stable foundation for automation, Modelence integrated MongoDB Atlas as its core data layer. The platform utilizes the flexible document model to align with how intelligent systems think, allowing specifications and runtime events to coexist. This &quot;fit&quot; enables per-tenant isolation and managed credentials, ensuring automated changes remain safe and traceable without the tangle of relational joins.</p>
<p>Standardizing on MongoDB Atlas helped Modelence raise $3 million dollars in its Seed round. The company now moves from planning to running features in minutes, achieving faster iteration loops and fewer regressions.</p>
<p>Thesys
Thesys aims to empower developers by making generative user interfaces—adaptive, real-time components—accessible to everyone. Previously, developers faced the friction of static chat bubbles and hardcoded dashboards that failed to visually represent complex AI outputs. These traditional interfaces forced teams to rebuild UI layers for every use case, which kills user engagement.</p>
<p>To solve these orchestration challenges, Thesys integrated MongoDB Atlas as the operational backbone for its C1 API middleware. The platform utilizes the document model to manage complex entities within a single, high-performance data layer. By removing the friction of mapping unstructured LLM outputs to rigid schemas, engineering teams can now ship updates weekly.</p>
<p>Through the MongoDB for Startups program, Thesys successfully accelerated its go-to-market timeline. By offloading operational management to MongoDB Atlas, Thesys now maintains the agility to evolve its data layer alongside emerging AI trends, ensuring its intelligent interfaces remain high-performing as they scale globally.</p>
<p>Emergent Labs
Emergent Labs sought to democratize software development through “vibe coding,” a platform where AI agents build applications from natural language prompts. The company’s initial use of PostgreSQL caused significant friction, as AI agents frequently failed during schema migrations when non-technical users iteratively changed their application requirements.</p>
<p>By switching to MongoDB Atlas, Emergent Labs provided its agents with a flexible, document-based architecture that matches the JSON data they naturally produce. This eliminated the PostgreSQL migration loops, allowing agents to modify data structures on the fly and deploy isolated, production-ready databases in minutes.</p>
<p>The transition has powered the creation of nearly 2 million applications across 180 countries in just four months. With MongoDB Atlas, the platform now supports complex builds of up to 300,000 lines of code, doubling deployment rates and allowing non-technical entrepreneurs to launch sophisticated tools without traditional engineering resources.</p>
<p>Heidi
Heidi aims to reclaim clinician time by automating administrative tasks. Previously, clinicians spent 40% of their shifts on paperwork, reducing time for patient care. To manage this at scale, Heidi initially used Amazon DocumentDB, but faced critical limitations including mandatory downtime for scaling, high latency, and a lack of native search functionalities essential for complex AI workloads.</p>
<p>To eliminate these bottlenecks, Heidi migrated to MongoDB Atlas for its flexible schema and built-in AI capabilities. Integrating MongoDB Vector Search enables Heidi to perform RAG without &quot;bolt-on&quot; databases, streamlining vector and semantic search under a single API. This technical fit enables developers to unify diverse medical data while meeting stringent healthcare security and regulatory requirements.</p>
<p>Since migrating, Heidi has supported 81 million consultations, returning 18 million hours to the frontline. By offloading management to MongoDB Atlas, Heidi ensures its platform remains high-performing while empowering practitioners to focus on their primary mission: providing compassionate patient care.</p>
<p>Video Spotlight
Before you go, watch TinyFish Co-founder and CEO, Sudheesh Nair, explain how “nano agents” are transforming web-based research.</p>
<p>Learn how TinyFish extracts actionable intelligence from unstructured internet data using MongoDB and Voyage AI.</p>
]]></description>
      <pubDate>Wed, 25 Feb 2026 16:45:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/innovating-with-mongodb-customer-successes-february-2026</link>
      <guid>https://www.mongodb.com/company/blog/innovation/innovating-with-mongodb-customer-successes-february-2026</guid>
    </item><item>
      <title>Building a Movie Recommendation Engine with Hugging Face and Voyage AI</title>
      <description><![CDATA[<p>This guest blog post is from Arek Borucki, Machine Learning Platform &amp; Data Engineer for Hugging Face - a collaboration platform for the machine learning community. The Hugging Face Hub works as a central place where anyone can share, explore, discover, and experiment with open-source ML. HF empowers the next generation of machine learning engineers, scientists, and end users to learn, collaborate and share their work to build an open and ethical AI future together. With the fast-growing community, some of the most used open-source ML libraries and tools, and a talented science team exploring the edge of tech, Hugging Face is at the heart of the AI revolution.</p>
<p>Traditional movie search relies on filtering by genre, actor, or title. But what if you could search by how you feel? Imagine typing:</p>
<p>&quot;something uplifting after a rough day at work&quot;</p>
<p>&quot;a movie that will make me cry&quot;</p>
<p>&quot;I need adrenaline, can't sleep anyway&quot;</p>
<p>&quot;something to watch with grandma who hates violence&quot;</p>
<p>This is mood-based semantic search: matching your emotional state to movie plot descriptions using AI embeddings.</p>
<p>In this tutorial, you will build a mood-based movie recommendation engine using three powerful technologies: voyage-4-nano (a state-of-the-art open-source embedding model), Hugging Face (for model and dataset hosting), and MongoDB Atlas Vector Search (for storing and querying embeddings at scale).</p>
<p>Why mood-based search?
Genre tags are coarse. A &quot;drama&quot; can be heartwarming or devastating. A &quot;comedy&quot; can be light escapism or dark satire. Traditional filters cannot capture these nuances.</p>
<p>Semantic search solves this by understanding meaning. When you search for &quot;feel-good movie for a rainy Sunday&quot;, the system doesn't look for those exact words. It understands the intent and matches it against plot descriptions that evoke similar feelings.</p>
<p>Architecture overview
The system combines three components from the Hugging Face ecosystem with MongoDB:</p>
<p>voyage-4-nano (Hugging Face Hub): Converts text to embeddings (up to 2048 dimensions, we use 1024)</p>
<p>MongoDB/embedded_movies(Hugging Face Datasets): 1500+ movies with plot summaries, genres, cast</p>
<p>MongoDB Atlas Vector Search: Stores embeddings and performs similarity search</p>
<p>Understanding voyage-4-nano
voyage-4-nano is the smallest model in Voyage AI's latest embedding series, released with open-weights under the Apache 2.0 license. Voyage AI was acquired by MongoDB, and the Voyage 4 series models are now available through MongoDB Atlas. All models in the series (voyage-4-large, voyage-4, voyage-4-lite, and voyage-4-nano) produce compatible embeddings in a shared embedding space, allowing you to mix and match models within a single use case.</p>
<p>Although voyage-4-nano natively supports embeddings up to 2048 dimensions, we deliberately truncate them to 1024 dimensions using its Matryoshka embedding property. In practice, this provides a strong balance between semantic quality, storage efficiency, and vector search latency, while preserving stable ranking behavior.</p>
<p>Sentence Transformers
This tutorial uses Sentence Transformers, a Python library built on top of Hugging Face Transformers. It is specifically designed for working with embedding models and provides a simple API for generating text embeddings.</p>
<p>Why Sentence Transformers instead of raw Transformers? When working with embedding models, you need to handle tokenization, pooling, normalization, and prompt formatting. Sentence Transformers does all of this automatically in a single method call. The code is cleaner, there are fewer potential errors, and you get built-in features like batch processing with progress bars.</p>
<p>Under the hood, Sentence Transformers still uses Hugging Face Transformers to load and run the model.</p>
<p>Configure the development environment
Let's get started!</p>
<p>Create the Project Structure
Code Snippet
1
mkdir mood-movie-search
2
cd mood-movie-search
3
mkdir src
4
touch requirements.txt .env</p>
<p>Install dependencies
Create the requirements.txt file:</p>
<p>Code Snippet
1
cat &lt;<EOF > requirements.txt
2
fastapi&gt;=0.109.0
3
uvicorn&gt;=0.27.0
4
pymongo&gt;=4.6.1
5
sentence-transformers&gt;=3.0.0
6
python-dotenv&gt;=1.0.0
7
datasets&gt;=2.16.0
8
torch
9
EOF</p>
<p>Create a Python virtual environment and install dependencies:</p>
<p>to be continued...</p>
]]></description>
      <pubDate>Tue, 17 Feb 2026 15:30:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/technical/building-a-movie-recommendation-engine-with-hugging-face-and-voyage-ai</link>
      <guid>https://www.mongodb.com/company/blog/technical/building-a-movie-recommendation-engine-with-hugging-face-and-voyage-ai</guid>
    </item><item>
      <title>Edge AI Made Easy: MongoDB and ObjectBox Data Synchronization</title>
      <description><![CDATA[<p>AI is currently undergoing a shift, from massive centralized models to distributed, real-world deployments. While the cloud remains the foundation for large-scale AI training and analytics, AI’s next evolution lies at the edge—where data is created, where decisions require instant action, and where connectivity cannot be guaranteed.</p>
<p>At MongoDB, we are committed to helping organizations build intelligent applications that span cloud and edge environments seamlessly. That’s why we are excited to highlight our work with ObjectBox, a lightweight, high-performance on-device database and sync solution purpose-built for edge AI and offline-first applications.</p>
<p>Together, MongoDB and ObjectBox are making it easier for developers to build hybrid architectures that deliver fast, private, and resilient AI experiences across devices and environments.</p>
<p>Figure 1. Example cloud-edge AI setup.</p>
<p>Example cloud-edge AI setup.
ObjectBox: A purpose-built database for the edge
Founded by Markus Junginger and Dr. Vivien Dollinger, ObjectBox was designed specifically to support edge computing and offline-first use cases. At its core, ObjectBox’s design prioritizes efficiency (including speed, privacy, battery use, and memory consumption) and ease of development.</p>
<p>This strong foundation makes ObjectBox particularly well-suited for next-generation applications that need to run reliably in edge environments—whether on a factory floor, in a retail store, or through a remote healthcare device. ObjectBox empowers developers to build responsive, privacy-conscious applications that work even when connectivity is limited or unavailable.</p>
<p>The platform includes the following features:</p>
<p>A fast, local vector database that stores data directly on devices, supporting on-device AI and local vector search.</p>
<p>Built-in data sync, which keeps data consistent across devices even when offline, and now integrates directly with MongoDB.</p>
<p>Multi-language support, including support for C++, Swift, Flutter, Python, Go, Java, and Kotlin, makes ObjectBox accessible to developers across ecosystems.</p>
<p>These features make ObjectBox an ideal solution for building intelligent applications that run reliably at the edge. This includes a wide range of devices—from smartphones and industrial sensors to automotive ECUs and point-of-sale (POS) devices.</p>
<p>Edge to cloud data sync: The MongoDB Atlas native connector
ObjectBox's new MongoDB Sync Connector combines local-first edge processing with centralized cloud intelligence (i.e., hybrid AI).</p>
<p>This is increasingly important as organizations seek to process data closer to where it is generated—at the edge—while still benefiting from the power and scalability of the cloud. Managing this dual environment efficiently is key to unlocking performance, resilience, and real-time insights.</p>
<p>Developers can now use ObjectBox for real-time, low-latency operations on edge devices while syncing relevant data to MongoDB Atlas, enabling organizations to achieve:</p>
<p>Long-term storage</p>
<p>Centralized dashboards and analytics</p>
<p>AI model retraining</p>
<p>Cloud-based coordination and automation</p>
<p>This hybrid architecture aligns with how modern applications are being built—distributing intelligence where it makes the most sense.</p>
<p>Figure 2. Central Sync for ObjectBox and MongoDB Atlas.</p>
<p>Central Sync for ObjectBox and MongoDB Atlas.
Figure 3. Edge setup for ObjectBox and MongoDB Atlas.</p>
<p>Edge setup for ObjectBox and MongoDB Atlas
Bringing AI to the edge isn’t just about performance. It is also about privacy, sustainability, and user experience. By processing data locally:</p>
<p>Privacy is enhanced—sensitive information stays on the device.</p>
<p>Latency is reduced—actions can be taken instantly.</p>
<p>Bandwidth usage drops—lowering costs and improving efficiency.</p>
<p>Battery and CPU use are optimized—extending the life of edge devices.</p>
<p>This aligns with MongoDB’s commitment to empowering developers to build intelligent, resilient, and user-centric applications—wherever they need.</p>
<p>Real-world use cases
Industrial IoT
Industrial IoT (IIoT) is a prime example of where edge and cloud must work together. On a modern factory floor, everything from low-frequency brownfield devices to high-frequency greenfield machines generates vast amounts of data.</p>
<p>Data generated include vibration levels, temperature readings, pressure changes, and machine runtimes. In short, the sort of data that often needs to be processed locally to monitor systems in real time and to trigger alerts when anomalies or threshold breaches occur.</p>
<p>With ObjectBox running on device, this critical operational data can be captured, analyzed, and used onsite and within AI applications immediately, even with limited or no connectivity. ObjectBox is designed for efficient, high-throughput I/O, enabling real-time processing of high-frequency data streams even on resource-constrained edge devices.</p>
<p>It supports a broad range of data types—from objects and time series data, to tree structures (e.g., UMATI) and vector embeddings—with a lightweight database (typically only a few MB in size). This makes it well-suited for production deployments that need to integrate modern AI and edge workloads with legacy systems and heterogeneous hardware, typical for the manufacturing industry.</p>
<p>The ObjectBox Sync Server can run on almost any device, enabling fast, reliable, and secure offline data synchronization across the shop floor. Paired with the MongoDB Sync Connector, the most relevant insights can then be synced to the cloud, where they can be aggregated, enriched with AI models, and stored for long-term analysis (like anomaly detection or RUL models).</p>
<p>This hybrid architecture enables advanced use cases such as predictive maintenance, where historical records, live equipment data, and machine learning models are combined to forecast potential failures before they happen. (For more details, explore our Predictive Maintenance solutions library.)</p>
<p>With this architecture, the system provides:</p>
<p>Real-time responsiveness on the shop floor</p>
<p>Centralized analytics and cross-site dashboards at cloud scale</p>
<p>Support for predictive maintenance workflows in offline or intermittently connected environments</p>
<p>Unified data access across heterogeneous data sources, from individual sensors to full production lines</p>
<p>By combining low-latency edge processing with centralized intelligence, developers and operators gain visibility into how equipment is performing from the health of a single machine, to trends across an entire fleet or factory network—without compromising performance or reliability.</p>
<p>Figure 4. Industrial IoT.</p>
<p>Industrial IoT.
Point-of-sale systems
Point-of-sale (POS) systems—such as those used in restaurants—are another strong fit for edge AI and hybrid architectures. During peak dining hours, cashiers and servers need instant, reliable access to menus, order histories, and payment processing—even if their internet connection is unstable or drops.</p>
<p>With ObjectBox’s offline-first, on-device database, restaurants can process real-time transactions, track inventory, and personalize customer experiences with local AI directly at the POS terminal. This helps store owners avoid service disruptions or lost sales.</p>
<p>With MongoDB Sync Connector, relevant data (like sales trends, customer preferences, and stock levels) syncs to MongoDB Atlas. This enables restaurant managers to run centralized dashboards, perform demand forecasting, and train AI models that optimize staffing, menu design, and supply chain planning.</p>
<p>In summary, this hybrid POS architecture of local-first responsiveness and cloud-powered insights ensures:</p>
<p>Seamless customer experiences without downtime</p>
<p>Accurate, up-to-date data whenever needed</p>
<p>Scalable, resilient operations across multiple restaurant locations</p>
<p>Figure 5. Point-of-sale systems.</p>
<p>Point-of-sale systems.
What’s next
With the release of ObjectBox 5.0 and its new MongoDB Connector, ObjectBox has taken a major step toward simplifying user‑specific data sync at the edge. Together, MongoDB and ObjectBox offer a modern foundation for building intelligent, distributed applications that run reliably from device to cloud. This partnership makes it easier than ever to pair low‑latency edge data processing with the flexibility, security, and global reach of MongoDB Atlas.</p>
]]></description>
      <pubDate>Tue, 03 Feb 2026 15:30:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/edge-ai-made-easy-mongodb-and-objectbox-data-synchronization</link>
      <guid>https://www.mongodb.com/company/blog/innovation/edge-ai-made-easy-mongodb-and-objectbox-data-synchronization</guid>
    </item><item>
      <title>MongoDB.local San Francisco 2026: Ship Production AI, Faster</title>
      <description><![CDATA[<p>Today at MongoDB.local San Francisco, we announced capabilities that collapse the distance between AI prototype and production.</p>
<p>Building AI applications means solving real problems: keeping conversational context clean and queryable, retrieving the right information from thousands of past interactions, connecting AI agents to your data without custom plumbing. These aren't theoretical challenges, they're the friction points that slow teams down every day.</p>
<p>The AI era demands more from your data platform. MongoDB gives you everything you need to build quickly.</p>
<p>Voyage AI: the best gets better
Embedding models can make or break AI search experiences. We're proud that voyage-3-large has been the world's top-performing embedding model on Hugging Face's RTEB benchmark since its inception.</p>
<p>But we didn’t rest on our laurels. There’s a new model at the top of the charts.</p>
<p>Today, we're pleased to announce that the Voyage 4 model family is now generally available. The best just got better. The voyage-4 series models operate in a shared embedding space, allowing for cross-model compatibility and unprecedented flexibility to optimize for accuracy, speed, or cost. This release also includes voyage-4-nano, our first open-weight model available on HuggingFace, perfect for local development.</p>
<p>Additionally, we're launching the new voyage-multimodal-3.5 model, which has been specifically trained to support video content alongside text and images. For developers building multimodal AI applications, this represents a significant leap forward in handling diverse content types within a single retrieval system. Best of all, upgrading is remarkably straightforward—you can simply change the model parameter to &quot;voyage-multimodal-3.5&quot; in your API call, instantly unlocking video capabilities without needing to refactor your existing codebase or change your application architecture.</p>
<p>Finally, we’re announcing the public preview of the Embedding and Reranking API on MongoDB Atlas, providing API support for Voyage AI models. While enabling standalone usage of the models with any technology stack, the API benefits from the robust security and scalability standards of MongoDB. By bringing critical components into a single control plane and interface, it eliminates the need to manage separate vendors and significantly reduces operational overhead.</p>
<p>Automated Embedding, convenience built into MongoDB Community
Persistence matters. An AI with amnesia isn’t helpful; users need systems to remember context from minutes, hours, and weeks ago. Every interaction is a goldmine of preferences, patterns, and behavior that should make the next interaction smarter.</p>
<p>But storing conversation history in a database isn't enough. Simple storage solves nothing if you can't retrieve the right information at the right time. The real challenge is intelligent retrieval: finding relevant context across thousands of past interactions, filtered by metadata and user attributes, without your system buckling under production load. This is where vector search becomes critical—enabling semantic search that captures meaning, not just keywords, while operating on your real-time operational data. And this is where MongoDB's approach eliminates a major pain point: the need to sync data between separate systems for vectors and application data.</p>
<p>Until now, generating and storing these vectors required overhead—development time, infrastructure management, and cognitive load. No longer.</p>
<p>We're introducing Automated Embedding for MongoDB Community Edition in public preview. MongoDB Community Edition now handles the complexity of managing embedding models automatically, giving developers high-accuracy semantic search in the database while maintaining flexibility to use any LLM provider or orchestration framework. Automated Embedding offers one-click automatic embedding directly inside MongoDB, which eliminates the need to sync data and manage external models. It’s an easy way to get high quality embedding natively.</p>
<p>Best-in-class retrieval shouldn't require infrastructure work—Automated Embedding in MongoDB Vector Search delivers on that promise. Automated Embedding in MongoDB Vector Search is available now in Community Edition, with Atlas access coming soon.</p>
<p>Precise text filtering for advanced search use cases
Today, we announced the launch of Lexical Prefilters for Vector Search. This addresses a long-standing request from developers building semantic search interfaces who need advanced text filtering alongside vector operations.</p>
<p>The new syntax enables powerful text filtering capabilities—fuzzy matching, phrase search, wildcards, and geospatial filtering—as prefilters for vector search. This leverages full text analysis capabilities while maintaining the semantic power of vector search. We've introduced a new vector data type in $search index definitions and a vectorSearch operator within the $search aggregation stage to make this work seamlessly.</p>
<p>This replaces the knnBeta operator with a cleaner, more powerful approach. For teams already using lexical and vector search together, this provides a simplified migration path with significantly expanded capabilities.</p>
<p>Intelligent assistance wherever you work
MongoDB’s intelligent assistant is generally available in MongoDB Compass. The assistant provides in-app guidance for debugging connection errors, optimizing query performance, and learning best practices, all without leaving your development environment. You can even query your database using natural language through read-only database tools that require your approval before execution, allowing for deeper contextual awareness of your data.</p>
<p>The assistant was built to address real friction: developers switching between multiple tools and documentation tabs, waiting for support responses, or getting generic advice from general-purpose AI chatbots that don't understand MongoDB-specific contexts. Now, tailored guidance is available instantly, right where you're working.</p>
<p>The modernized Atlas Data Explorer interface brings the Compass experience directly into the Atlas web UI, addressing a critical gap for teams with security policies that restrict desktop application usage. Users can now perform sophisticated query development, optimization, bulk operations, and complex aggregations—all with AI assistance—across all MongoDB Atlas clusters in a unified web interface.</p>
<p>Whether you're troubleshooting a connection issue, optimizing a slow query, or learning how to structure an aggregation pipeline, the intelligent assistant delivers MongoDB-specific expertise without context switching. Try the intelligent assistant in the modernized Atlas Data Explorer now.</p>
<p>The engine behind MongoDB Search and Vector Search is now available under SSPL
Finally, mongot, the engine powering MongoDB Search and Vector Search, is now publicly available under SSPL. While still in preview, after years of development and investment, we're making the source code of this core technology available to the community, expanding our unified search architecture beyond Atlas to every MongoDB deployment.</p>
<p>mongot runs separately from mongod, MongoDB's core database process, and is the foundation that makes powerful search native to MongoDB. Releasing mongot under SSPL means full transparency for security audits and debugging complex edge cases. Developers can dive into mongot's architecture, understand how search and vector operations work under the hood, and help shape the future of search at MongoDB.</p>
<p>A modern data platform that evolves with your needs
These announcements reflect our commitment to anticipating what developers need as AI development matures. Vector search, time series, stream processing, queryable encryption, Atlas itself—we've consistently delivered on emerging requirements. &quot;If you're building an early-stage company that is going to scale very rapidly, you need a database solution that isn't going to break under the load of a huge volume of users,&quot; said Eno Reyes, Co-founder and CTO of Factory. &quot;You need a fast-moving team with a reliable solution, and there really is one option in this space—and it's MongoDB.&quot;</p>
<p>Rabi Shanker Guha, CEO of Thesys, put it this way: “MongoDB helps us move fast in an ever-changing world. The best database is the one you don’t have to think about—it just works exactly where and how you need it. That’s MongoDB for us.”</p>
<p>Ship faster, scale confidently
Each capability we announced today addresses real friction in the AI development workflow and in the developer experience. We're not asking developers to choose between structured data and vectors, between performance and flexibility, or between rapid iteration and production readiness.</p>
<p>The promise is straightforward: ship faster, scale confidently, and focus on what makes your AI application unique—not on managing database infrastructure. In an ecosystem crowded with point solutions and retrofitted legacy systems, MongoDB is a modern data platform built for the long haul.</p>
]]></description>
      <pubDate>Thu, 15 Jan 2026 20:15:39 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/events/mongodb-local-san-francisco-2026-ship-production-ai-faster</link>
      <guid>https://www.mongodb.com/company/blog/events/mongodb-local-san-francisco-2026-ship-production-ai-faster</guid>
    </item><item>
      <title>Vision RAG: Enabling Search on Any Documents</title>
      <description><![CDATA[<p>Information comes in many shapes and forms. While retrieval-augmented generation (RAG) primarily focuses on plain text, it overlooks vast amounts of data along the way. Most enterprise knowledge resides in complex documents, slides, graphics, and other multimodal sources. Yet, extracting useful information from these formats using optical character recognition (OCR) or other parsing techniques is often low-fidelity, brittle, and expensive.</p>
<p>Vision RAG makes complex documents—including their figures and tables—searchable by using multimodal embeddings, eliminating the need for complex and costly text extraction. This guide explores how Voyage AI’s latest model powers this capability and provides a step-by-step implementation walkthrough.</p>
<p>Vision RAG: Building upon text RAG
Vision RAG is an evolution of traditional RAG built on the same two components: retrieval and generation.</p>
<p>In traditional RAG, unstructured text data is indexed for semantic search. At query time, the system retrieves relevant documents or chunks and appends them to the user’s prompt so the large language model (LLM) can produce more grounded, context-aware answers.</p>
<p>Figure 1. Text RAG with Voyage AI and MongoDB.</p>
<p>Text RAG with Voyage AI and MongoDB
Enterprise data, however, is rarely just clean plain text. Critical information often lives in PDFs, slides, diagrams, dashboards, and other visual formats. Today, this is typically handled by parsing tools and OCR services. Those approaches create several problems:</p>
<p>Significant engineering effort to handle many file types, layouts, and edge cases</p>
<p>Accuracy issues across different OCR or parsing setups</p>
<p>High costs when scaled across large document collections</p>
<p>Next-generation multimodal embedding models provide a simpler and more cost-effective alternative. They can ingest not only text but also images or screenshots of complex document layouts, and generate vector representations that capture the meaning and structure of that content.</p>
<p>Vision RAG uses these multimodal embeddings to index entire documents, slides, and images directly, even when they contain interleaved text and images. This enables them to be searchable via vector search without requiring heavy parsing or OCR. At query time, the system retrieves the most relevant visual assets and feeds them, along with the text prompt, into a vision-capable LLM to inform its answer.</p>
<p>Figure 2. Vision RAG with Voyage AI and MongoDB.</p>
<p>Vision RAG with Voyage AI and MongoDB
As a result, vision RAG enables LLM-based systems with native access to rich, multimodal enterprise data, while reducing engineering complexity and avoiding the performance and cost pitfalls associated with traditional text-focused preprocessing pipelines.</p>
<p>Voyage AI’s latest multimodal embedding model
The multimodal embedding model is where the magic happens. Historically, building such a system was challenging due to the modality gap. Early multimodal embedding models, such as contrastive language-image pretraining (CLIP)-based models, processed text and images using separate encoders. Because the outputs were generated independently, results were often biased toward one modality, making retrieval across mixed content unreliable. These models also struggled to handle interleaved text and images, a critical limitation for vision RAG in real-world environments.</p>
<p>Voyage-multimodal-3 adopts an architecture similar to modern vision-capable LLMs. It uses a single encoder for both text and visual inputs, closing the modality gap and producing unified representations. This ensures that textual and visual features are treated consistently and accurately within the same vector space.</p>
<p>Figure 3. CLIP-based architecture vs. voyage-multimodal-3’s architecture.</p>
<p>CLIP-based architecture vs. voyage-multimodal-3’s architecture
This architectural shift enables true multimodal retrieval, making vision RAG a viable and efficient solution. For more details, refer to the voyage-multimodal-3 blog announcement.</p>
<p>Implementation of vision RAG
Let’s take a simple example and showcase how to implement vision RAG. Traditional text-based RAG often struggles with complex documents, such as slide decks, financial reports, or technical papers, where critical information is often locked inside charts, diagrams, and figures.</p>
<p>By using Voyage AI’s multimodal embedding models alongside Anthropic’s vision-capable LLMs, we can bridge this gap. We will treat images (or screenshots of document pages) as first-class citizens, retrieving them directly based on their visual and semantic content and passing them to a vision-capable LLM for reasoning.</p>
<p>To demonstrate this, we will build a pipeline that extracts insights from the charts and figures of the GitHub Octoverse 2025 survey, which simulates the type of information typically found in enterprise data.</p>
<p>The Jupyter Notebook for this tutorial is available on GitHub in our GenAI Showcase repository. To follow along, run the notebook in Google Colab (or similar), and refer to this tutorial for explanations of key code blocks.</p>
<p>Step 1: Install necessary libraries
First, we need to set up our Python environment. We will install the voyageai client for generating embeddings and the anthropic client for our generative model.</p>
<p>....</p>
]]></description>
      <pubDate>Mon, 12 Jan 2026 16:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/technical/vision-rag-enabling-search-on-any-documents</link>
      <guid>https://www.mongodb.com/company/blog/technical/vision-rag-enabling-search-on-any-documents</guid>
    </item><item>
      <title>That’s a Wrap: MongoDB’s 2025 in Review &amp; 2026 Predictions</title>
      <description><![CDATA[<p>It’s nearly the end of the year—again! That means it’s time for an end-of-year blog post that expresses disbelief at the passage of time. Which, as the saying goes, flies when you’re having fun. And definitely when you’re as busy as MongoDB was in 2025.</p>
<p>It was a big year for the company—and more importantly, for the tens of thousands of customers and millions of developers who rely on MongoDB’s modern data platform for their most mission-critical workloads. At MongoDB, everything we do starts with our obsession with customers and their needs, and if there’s a theme to MongoDB’s 2025, it was (and will continue to be) enabling customer innovation and helping them succeed in the AI era.</p>
<p>So here are a few highlights of how MongoDB acted on behalf of customers in 2025. From the acquisition of Voyage AI to customer success across industries, a lot happened in 2025. Let’s go!*</p>
<p>*Read to the end for 2026 thoughts.</p>
<p>2025: The (MongoDB) year that was
Voyage AI, modernization, and search
In February, MongoDB announced the acquisition of Voyage AI, a pioneer in embedding and reranking models, to enhance the accuracy of AI applications. Integrating Voyage AI's advanced retrieval technology with MongoDB’s modern, AI-ready data platform addresses a critical challenge: LLM model hallucinations caused by a lack of context. By improving retrieval accuracy for specialized domains like finance and law, the integration enables businesses to deploy AI for mission-critical use cases.</p>
<p>To learn more, see the MongoDB Voyage AI page.</p>
<p>Then, in September, we launched MongoDB AMP, an AI-powered Application Modernization Platform. AMP is designed to accelerate the transformation of legacy applications through a combination of AI-powered tooling, a proven delivery framework, and expert guidance (tools, techniques, and talent) to help enterprises reduce technical debt and modernize 2-3 times faster.</p>
<p>Want more? Sure you do! Check out this short video.</p>
<p>MongoDB also announced the addition of search and vector search capabilities to MongoDB Community Edition and MongoDB Enterprise Server. This allows developers to build and test AI-native applications, including those using retrieval-augmented generation (RAG), in local or on-premises environments. Previously exclusive to MongoDB Atlas, these features enable secure, hybrid deployments where sensitive data can remain on-premises while still leveraging advanced search tools.</p>
<p>Here’s a (slightly less short) video about search and vector search on Enterprise Server.</p>
<p>Growing and scaling with MongoDB
As noted, everything we do at MongoDB starts with our obsession with customers. 2025 was another banner year for customer success and innovation—we were inspired by what organizations of every shape and size, across industries and geographies, built with MongoDB in 2025. Here are just two of the many stories our customers shared in 2025; much more can be found in my colleague Katie Palmer’s blog series, Innovating with MongoDB.</p>
<p>Factory
By combining the Atlas modern data platform with Voyage AI’s high-performance embeddings, the AI-native startup Factory—which uses AI agents called Droids to accelerate software development lifecycles for organizations—consolidated its fragmented tech stack. This enabled superior code retrieval, simplified operations, and provided the scalability needed to process billions of tokens daily.</p>
<p>McKesson
McKesson, a global pharmaceutical distributor, replaced its monolithic legacy infrastructure with MongoDB Atlas to meet strict drug tracing mandates. By adopting our modern cloud data platform, McKesson scaled its operations 300x, managing tracking data for 1.2 billion containers annually without latency, and ensuring compliance and patient safety while reducing developer complexity.</p>
<p>For more, check out the video of McKesson at MongoDB.local NYC from September.</p>
<p>From niche NoSQL to enterprise powerhouse
As senior MongoDB engineer and Technical Fellow Ashish Kumar put it earlier this year, “through a sustained and deliberate engineering effort,” MongoDB has gone from a (seemingly) niche NoSQL solution to a trusted enterprise standard, and now delivers “the high availability, tunable consistency, ACID transactions, and robust security that enterprises demand.”</p>
<p>A new era of leadership
The face of MongoDB has also changed—our CFO, Mike Berry, joined the company in April, and Dev Ittycheria stepped down as CEO in November, after more than 11 years leading the company (including its 2017 IPO). In a LinkedIn post about his role, new MongoDB CEO CJ Desai noted that the company is “at the forefront of a new data revolution, unlocking the next wave of productivity and intelligence.”</p>
<p>“Having spent my career building and scaling technology platforms, I’ve always been drawn to companies defined by clarity of vision, relentless organic innovation, and a customer-first culture. MongoDB exemplifies all three,” said Desai.</p>
<p>We couldn’t agree more. Onward!</p>
<p>Reading the 2026 tea leaves
So what might 2026 bring (for MongoDB and tech at large)? Here are a handful of our leaders’ predictions:</p>
<p>“As much as people want to talk about Artificial General Intelligence (AGI), we’re still in the phase where most AI use cases automate redundant tasks but benefit from human-in-the-loop checks. Organizations that use AI to complete work that historically is a drain on human resources—but then uses people to carefully verify what AI builds, apply governance frameworks, and maintain accountability across the data lifecycle—will be more successful.”
—Pete Johnson, Field CTO, AI, MongoDB</p>
<p>“After years of inflated expectations and unsustainable spending, the AI industry is trapped in a bubble where companies reflexively attempt to deploy LLMs at every problem, driving up costs with minimal to no return. Businesses that break free from this spending cycle are the ones that understand the need to ground LLM responses in factual data and learn from prior mistakes. We believe the best way to do this will be with highly accurate embedding models and rerankers for reliable data retrieval.”
—Frank Liu, Staff Product Manager, MongoDB</p>
<p>&quot;In 2026, cloud independence will evolve from strategic preference to existential imperative across enterprises of every scale. The outages and disruptions of recent years have exposed a fundamental truth: in an always-on digital economy—where commerce, mobility, governance, and even public safety depend on uninterrupted access to cloud services—single-provider reliance is no longer a calculated risk, but a systemic vulnerability.</p>
<p>Compounding this is the inexorable rise of data sovereignty. Regulatory regimes worldwide now demand precise jurisdictional control over data residency, rendering rigid cloud commitments incompatible with compliance at global scale.</p>
<p>The defining competitive advantage will belong to organizations that transcend fragile prevention theater and engineer true infrastructural resilience: architectures inherently portable, data frictionlessly mobile, and operations autonomously sustained across heterogeneous clouds through AI-orchestrated redundancy.</p>
<p>In short, the winners will not merely mitigate downtime—they will design systems that render the concept obsolete.&quot;
—Ben Cefalo, SVP, Head of Core Products, MongoDB</p>
<p>Happy holidays and happy New Year, everyone!</p>
]]></description>
      <pubDate>Mon, 22 Dec 2025 17:34:58 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/mongodb-2025-in-review-2026-predictions</link>
      <guid>https://www.mongodb.com/company/blog/mongodb-2025-in-review-2026-predictions</guid>
    </item><item>
      <title>Token-count-based Batching: Faster, Cheaper Embedding Inference for Queries</title>
      <description><![CDATA[<p>Embedding model inference often struggles with efficiency when serving large volumes of short requests—a common pattern in search, retrieval, and recommendation systems. At Voyage AI by MongoDB, we call these short requests queries, and other requests are called documents. Queries typically must be served with very low latency (typically 100–300 ms).</p>
<p>Queries are typically short, and their token-length distribution is highly skewed. As a result, query inference tends to be memory-bound rather than compute-bound. Query traffic is pretty spiky, so autoscaling is too slow. In sum, serving many short requests sequentially is highly inefficient.</p>
<p>In this blog post, we explore how batching can be used to serve queries more efficiently. We first discuss padding removal in modern inference engines, a key technique that enables effective batching. We then present practical strategies for forming batches and selecting an appropriate batch size. Finally, we walk through the implementation details and share the resulting performance improvements: a 50% reduction in GPU inference latency—despite using 3X fewer GPUs.</p>
<p>Padding removal makes effective batching possible
Given the patterns of query traffic, one straightforward idea is: can we batch them to improve inference efficiency? Padding removal, supported in inference engines like vLLM and SGLang, makes efficient batching possible.</p>
<p>Most inference engines accept requests in the form (B, S), where B is the sequence number in the batch, and S is the maximum sequence length. Sequences should be padded to the max sequence length so that tensors line up. But that convenience comes at a cost: padding tokens do no useful work but still consume compute and memory bandwidth, so latency scales with B × S instead of the actual token count. With serving large volumes of short requests, this wastes a large share of compute and can inflate tail latency.Padding removal and variable-length processing fix this by concatenating all active sequences into one long &quot;super sequence&quot; of length T = Σtoken_count_i, where token_count_i is the token count in sequence i. Inference engines like vLLM and SGLang can process this combined sequence. Attention masks and position indices ensure that each sequence only attends to its own tokens. As a result, inference time now tracks T rather than B × S, aligning GPU work with what matters.</p>
<p>Proposal: token-count-based batching
In Voyage AI, we proposed and built token-count-based batching, batching queries (short requests) by total token count in the batch (Σtoken_count_i), rather than by total request count or arbitrary time windows.</p>
<p>Time-window batching is inefficient when serving many short requests. Time-window batching swings between under- and over-filled batches depending on traffic. A short window keeps latency low but produces small, under-filled batches; a long window improves utilization but adds queueing delay. Traffic is bursty, so a single window size oscillates between under- and over-filling. Time-window batching introduces variability in resource utilization, causing the system to shift between memory-bound and compute-bound operations. Request-count batching has similar problems.</p>
<p>Diagram illustrating the difference between request-number-based batching and token-count-based batching.
Figure 1. Request-number-based batching VS token-count-based batching.
Token-count batching aligns the batch size (total token count in the batch) with the actual compute required. When many queries arrive close together, we group them by token counts so the GPU processes a larger combined workload in a single forward pass. Based on our experiment, token-count-based batching amortizes fixed costs, reduces per-request latency and cost, and increases throughput and model flops utilization (MFU).</p>
<p>What is the optimal batch size?
Our inference-latency-vs-token-count profiling of query inference shows a clear pattern: latency is approximately flat up to a threshold (saturation point) and then becomes approximately linear. For small requests, fixed per-request overheads (like GPU scheduling, memory movement, pooling and normalization, etc.) dominate, and latency stays nearly constant; beyond that point, latency scales with token count. The threshold (saturation point) depends on factors like the model architecture, inference engines, and GPU. For our voyage-3 model running on A100, the threshold is about 600 tokens.</p>
<p>Line graph showing that GPU inference latency for the Voyage-3 model on A100 is approximately flat for batches up to about 600 tokens (the saturation point), and then increases linearly with the total token count.
Figure 2. Inference latency vs token count for Voyage-3 on A100.
Based on the data of inference latency vs token count, we can analyze FLOPs Utilization (MFU) vs. token count and throughput vs. token count, which are shown in the following graph. We observe that Model FLOPs Utilization (MFU) and throughput scale approximately linearly with token count until reaching a saturation point. Most of our queries inferences are in the memory-bound zone, far away from the saturation point.</p>
<p>Approximated diagram showing Model FLOPs Utilization (MFU) and throughput scaling linearly with token count up to a saturation point, and inference latency remaining flat until the saturation point, after which it also scales linearly. This illustrates how batching can shift inference from memory-bound to compute-bound.
Figure 3. Approximated diagram of MFU/throughput/inference latency vs token count.
Batching short requests can move the inference from memory-bound to compute-bound. If we choose the saturation point in Figure 3 as the batch size (total token count in the batch), the latency and throughput/MFU can be balanced and optimized.</p>
<p>Queue design: enabling token-count-based batching
Token-count–based batching needs a data system that does more than simple FIFO delivery. The system has to attach an estimated token_count to each request, peek across pending requests, and then atomically claim a subset whose total tokens fit the optimal batch size (Σtoken_count_i ≤ optimal_batch_size). Without these primitives, we either underfill the GPU—wasting fixed overheads—or overfill it and spike tail latency.</p>
<p>General-purpose brokers like RabbitMQ and Kafka are excellent at durability, fan-out, and delivery, but their batching knobs are message count/bytes, not tokens. RabbitMQ’s prefetch is request-count-based, and messages are pushed to consumers, so there’s no efficient way to peek and batch requests by Σtoken_count_i. Kafka batches by bytes/messages within a partition; token count varies with text and tokenizer, so there is no efficient way to batch requests by Σtoken_count_i.</p>
<p>So there are two practical paths to make token-count-based batching work. One is to place a lightweight aggregator in front of Kafka/RabbitMQ that consumes batches by token counts and then dispatches batches to model servers. The other is to use a store that naturally supports fast peek + conditional batching—for example, Redis with Lua script. In our implementation, we use Redis because it lets us atomically “pop up to the optimal batch size” and set per-item TTLs within a single lua script call. Whatever we choose, the essential requirement is the same: the queue must let our system see multiple pending items, batch by Σtoken_count_i, and claim them atomically to keep utilization stable and latency predictable.</p>
<p>Our system enqueues each embedding query request into a Redis list as:</p>
<p>Code Snippet
1
&lt;token_count&gt;::<timestamp>::<query></p>
<p>Model servers call lua script atomically to fetch a batch of requests until the optimal batch size is reached. The probability of Redis losing data is very low. In the rare case that it does happen, users may receive 503 Service Unavailable errors and can simply retry. When QPS is low, batches are only partially filled and GPU utilization remains low, but latency still improves.</p>
<p>Diagram illustrating the token-count-based batching implementation, where incoming embedding query requests are enqueued into a Redis list and model servers atomically fetch a batch of requests up to the optimal total token count using a Lua script.
Figure 4. Batching implementation.
Results
We ran a production experiment on the Voyage-3-Large model serving, comparing our new pipeline (query batching + vLLM) against our old pipeline (no batching + Hugging Face Inference). We saw a 50% reduction in GPU inference latency—despite using 3X fewer GPUs.</p>
<p>We gradually onboarded 7+ models to the above query batching solution, and saw the following results (note that these results are based on our specific implementations of the “new” and “old” pipelines, and are not necessarily generalizable):</p>
<p>vLLM reduces GPU inference time by up to ~20 ms for most of our models.</p>
<p>GPU utilization and MFU increase, reflecting reduced padding, better amortization of per-batch overhead, and inference moving closer to the compute-bound regime.</p>
<p>Throughput improves by up to 8× via token-count–based batching.</p>
<p>Some model servers see P90 end-to-end latency drop by 60+ ms as queuing time is reduced under resource contention.</p>
<p>P90 end-to-end latency is more stable during traffic spikes, even with fewer GPUs.</p>
<p>In summary, combining padding removals with token-count-based batching improves throughput and reduces latency, while improving resource utilization and lowering operational costs during short query embedding inference.</p>
]]></description>
      <pubDate>Thu, 18 Dec 2025 15:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/engineering/token-count-based-batching-faster-cheaper-embedding-inference-for-queries</link>
      <guid>https://www.mongodb.com/company/blog/engineering/token-count-based-batching-faster-cheaper-embedding-inference-for-queries</guid>
    </item><item>
      <title>MongoDB Announces Leadership Transition</title>
      <description><![CDATA[<p>Dev Ittycheria, President and Chief Executive Officer, shared the following message with MongoDB employees this morning.</p>
<p>This is the hardest email I have ever had to write to all of you. If you have not seen the announcement, I have decided to retire as CEO. Effective November 10, 2025, Chirantan “CJ” Desai will become the new CEO of MongoDB.</p>
<p>This was not an easy decision for me. The process to get to this point has been deeply emotional, as I care profoundly about MongoDB and the people who have made the company what it is today.</p>
<p>This news may come as a surprise, and for some, perhaps even a shock. That’s natural. Leadership transitions can evoke a range of reactions. I want to share why this is happening, and why it’s the right thing for MongoDB.</p>
<p>Every personnel change, including the most senior leadership changes, involves two key decisions: first, recognizing that it is the right time for change, and second, selecting the best person to replace the person leaving. This email is intended to explain both decisions.</p>
<p>Earlier this year, as part of our regular succession planning process, the Board and I discussed my long-term commitment. They asked if I would continue as CEO for another five years. After many conversations with my family and the Board, I realized I could not make that commitment. Some CEOs see their title as their identity. I do not. My core responsibility is to serve in the company's best interests. The company is primed for a new leader. One with a fresh perspective, grounded in experience and skills needed to guide MongoDB through its next evolution as a company, what we call MongoDB 3.0.</p>
<p>Consequently, I informed the Board that I would commit to two more years to help find a successor. That began the search process for a suitable successor. To our surprise and delight, what we thought would easily take 12 to 24 months happened much faster than anyone expected. After engaging with multiple qualified candidates, we found the right successor in CJ.</p>
<p>CJ is uniquely qualified for this role. CJ brings the rare growth-at-scale experience that will help continue to build MongoDB into an iconic technology company. At ServiceNow, he was the only executive to work directly with three of its highly regarded public company CEOs and played a pivotal role in organically scaling the company from just over $1 billion to more than $10 billion in revenue. Only a handful of independent software companies have ever reached that milestone. CJ helped transform ServiceNow from a product company to a platform company, scaled engineering, drove go-to-market excellence, and engaged deeply with investors. More recently, as President of Product and Engineering at Cloudflare, he helped fuel strong growth and stock performance.</p>
<p>CJ also possesses the personal qualities needed to succeed as CEO. He is humble, eager to learn, and wants to draw on the perspectives of the people at MongoDB and other stakeholders to inform his thinking. This blend of experience, judgment, and character gives me full confidence that he is well-equipped to lead MongoDB through its next phase of growth.</p>
<p>I often think of MongoDB’s journey as a long and extraordinary expedition. For the past eleven years, I have had the privilege of serving as its guide, helping chart the course, rally the team, and climb together through both calm and challenging terrain. Along the way, we have reached remarkable summits and proven what is possible through relentless innovation, persistence, and teamwork. Now it is time for a new guide to lead the next stage of the ascent and take MongoDB to even greater heights. CJ is the right leader to take MongoDB to the next summit.</p>
<p>MongoDB is on a strong footing, with a clear strategy, an exceptional leadership team, a product platform that is more relevant than ever, and a business that is executing well. The rise of AI and the explosion of data-intensive applications play directly to MongoDB’s strengths. Our technology sits at the center of how modern applications are built and how organizations will harness data to power intelligent, adaptive systems. I am confident MongoDB is perfectly positioned to capture this next wave of innovation.</p>
<p>As for me, I am not running away from MongoDB or leaving to join another company as CEO. I will remain on the Board and work closely with CJ to ensure a seamless transition. Over the years, this role has demanded an enormous amount of focus and energy; as a result, there are many things I’ve missed doing along the way. I’m looking forward to being more present for those moments — from simple time with my family to experiences and travel we’ve long put off. I plan to hold on to my MongoDB stock, as I firmly believe in the people and the opportunity, knowing that MongoDB’s best days are ahead of it.</p>
<p>Yes, change can be unsettling. I’m sure you will have many questions about this change, such as why now, why CJ is the best person to lead the company, and what this means for you. We will hold an all-hands meeting tomorrow at 10:30AM ET to discuss this transition, introduce CJ and take your questions.</p>
<p>That being said, I want to emphasize that the right change at the right time is how great companies get stronger. Just as a championship team refreshes its roster to stay competitive, MongoDB is bringing in new leadership, including other recent C-suite leaders who came before CJ, to drive our next phase of growth. This is not an ending; it’s the founding of a new moment.</p>
<p>I am incredibly proud of what we have built together and genuinely excited about what lies ahead with CJ leading us forward. I also want to thank each of you for making this journey so meaningful. Words cannot fully capture my gratitude for your passion, creativity, and belief in building something truly special.</p>
<p>I have often said that I want MongoDB to be an inflection point in people’s careers, a place where they can grow, take risks, and do the best work of their lives. I can say without hesitation that it has been exactly that for me. The skills I have developed, the experiences I have gained, and the relationships I have formed here have shaped me more than any other chapter in my professional life. I will carry them with me always, and will continue to cheer for and support MongoDB every step of the way.</p>
<p>--Dev</p>
]]></description>
      <pubDate>Mon, 03 Nov 2025 18:55:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/news/mongodb-announces-leadership-transition</link>
      <guid>https://www.mongodb.com/company/blog/news/mongodb-announces-leadership-transition</guid>
    </item><item>
      <title>Cars24 Improves Search For 300 Million Users With MongoDB Atlas</title>
      <description><![CDATA[<p>The Indian multinational online car marketplace Cars24 serves 300 million users globally.  The company offers services that span sales, insurance, maintenance, financing, and more, reshaping the entire car ownership journey.</p>
<p>Speaking at <a href="https://www.youtube.com/watch?v=zlR3wXzoa74&list=PL4RCxklHWZ9tfGnzDp49-tswA8hqsA70M&index=12" target="_blank">MongoDB .local Bengaluru in July 2025</a>, Pradeep Sharma, Head of Technology at Cars24, shared how MongoDB has been a key driver of Car24’s digital transformation journey. Specifically, he highlighted two recent use cases that show how <a href="https://www.mongodb.com/products/platform">MongoDB Atlas</a> has helped Cars24 scale, improve its search capabilities, and reduce its architectural complexity.</p>
<iframe width="800" height="425" src="https://www.youtube.com/embed/zlR3wXzoa74?si=sgjrzqbrS3wXHkHI" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
<h2>Matching the growing scale with simplified and expanded search</h2>
<p>Cars24 has operations in multiple countries, and a diverse customer base. Over the years, the company has used customer data, behavior analytics, and operational workflows to build, evolving from being a platform for buying and selling cars, to an end-to-end ecosystem, supported by a hub of interconnected systems.</p>
<p>At the start of its journey, Cars24 relied on legacy databases for managing and searching data, such as Postgres. Their relational database set-up would store information, synchronize the data to a separate “bolt-on” search engine (such as Elasticsearch), manually indexing it, and then querying the index.</p>
<p>While initially effective for a small application ecosystem, these processes became bottlenecked as the organization’s services grew. Multiple engineering teams piped data into a single search index, which often resulted in synchronization challenges and overwhelming administrative overhead.</p>
<p>Cars24 faced three core limitations with this setup:</p>
<ul>
<li>
<p><b>Lower developer productivity:</b> Exponential effort was spent maintaining pipelines and synchronizing procedures. Developers had little bandwidth for building business features or innovation.</p>
</li>
<li>
<p><b>Architectural complexity:</b> Ensuring data sync consistency required multiple pipelines and race logic. This led to inefficiencies in real-time dashboard updates for agents.</p>
</li>
<li>
<p><b>Operational overhead:</b> Maintaining separate systems for database and search—alongside provisioning, patching, scaling, and monitoring—strained resources.</p>
</li>
</ul>
<p>Seeking an integrated approach, Cars24 embraced MongoDB Atlas, hosted on <a href="https://www.mongodb.com/resources/products/platform/mongodb-on-google-cloud">Google Cloud</a>. MongoDB Atlas would serve as a single, consistent, modern database and embedded search solution, powered by Apache Lucene.</p>
<p><a href="https://www.mongodb.com/products/platform/atlas-search">MongoDB Atlas Search</a> also enabled Cars24 to run queries directly in the database. This eliminated the need to synchronise data between systems while delivering real-time results.</p>
<p>This unified approach allowed the company’s developers to transition from managing complex synchronization mechanisms to building applications. Furthermore, the reduced administrative overhead enabled Cars24 to consolidate the team’s efforts, and to streamline query execution across the ecosystem.</p>
<p>Thanks to MongoDB Atlas and MongoDB Atlas Search, Cars24 was able to:</p>
<ul>
<li>
<p><b>Avoid &quot;synchronization tax”:</b> Switching to MongoDB Atlas eliminated the need for data synchronization and the additional tooling this mandated. Real-time searches can be performed from a single interface and workflow.</p>
</li>
<li>
<p><b>Deliver new search features faster:</b> By using a single, unified API across database and search operations, new features can be delivered rapidly.</p>
</li>
<li>
<p><b>Work with a fully managed platform:</b> With MongoDB Atlas, Cars24’s engineers can focus more on application development and building products, rather than thinking about managing indexes, syncing, and more.</p>
</li>
</ul>
<p>Following this successful migration, Cars24 decided to also use MongoDB Atlas to replace one of its legacy databases, ArangoDB. The switch to MongoDB Atlas eliminated major roadblocks for other critical search capabilities.</p>
<h2>From ArangoDB to MongoDB: Streamlined operations and 50% cost savings</h2>
<p>As Cars24 scaled new services globally, it encountered limitations with its geospatial search solution, which was based on ArangoDB. This included performance bottlenecks, weak transactions as it was difficult to guarantee consistent data operations, and a limited ecosystem which meant that  scaling developer onboarding and troubleshooting became increasingly onerous.<br>
Moving to MongoDB Atlas enabled Cars24 to transition its geospatial services, consolidating its data storage and search capabilities under a single, versatile platform.</p>
<p>“We now have a highly available architecture, and an amazing team at MongoDB that has our back,” said Sharma.</p>
<p>MongoDB offered a proven architecture for high availability, scalability, and real-world production readiness:</p>
<ul>
<li>
<p><b>Enhanced scalability:</b> MongoDB’s ability to scale massive workloads supports Cars24’s growing global presence.</p>
</li>
<li>
<p><b>Reliable transactions:</b> MongoDB provides robust multi-document ACID transactions across shards, meeting mission-critical needs.</p>
</li>
<li>
<p><b>Streamlined operations:</b> MongoDB offers a single platform that is not limited to a database only. By consolidating its geospatial search workload under MongoDB, Cars24 has reduced maintenance and operational overhead.</p>
</li>
</ul>
<p>Not only did Cars24 cut costs in half by moving to MongoDB, but the widespread market adoption of MongoDB Atlas also means that Cars24 can continue to rapidly onboard developers familiar with MongoDB, a recruiting priority for Cars24’s growing development team.</p>
<p>“To give you an idea, one of our business units had a developer team of less than 10 about a year ago. Now they are a triple-digit team,” said Sharma. “If we are going to keep introducing new developers, for a product coming up or scaling up, it becomes very important to focus on the community skills and support provided by our technology partner.”</p>
<p>“Now that we have moved from ArangoDB to MongoDB Atlas, our developers are the happiest,” he added.</p>
<p>Cars24 is now looking to consolidate even more of its application and data workflows under MongoDB Atlas. With the growing number of developers joining Cars24’s engineering teams, plans are to utilize MongoDB Atlas further to enhance productivity, scalability, and data-driven insights.</p>
<div class="callout">
<p><b>Visit the <a href="https://www.mongodb.com/resources/product/platform/atlas-learning-hub">MongoDB Atlas Learning Hub</a> to learn more about Atlas.</b></p>
<p><b>To learn more about MongoDB Atlas Search, visit our <a href="https://www.mongodb.com/products/platform/atlas-search">product page</a>.</b></p>
</div>	]]></description>
      <pubDate>Sun, 12 Oct 2025 23:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/cars24-improves-search-for-300-million-users-with-atlas</link>
      <guid>https://www.mongodb.com/company/blog/innovation/cars24-improves-search-for-300-million-users-with-atlas</guid>
    </item><item>
      <title>The Cost of Not Knowing MongoDB, Part 3: appV6R0 to appV6R4</title>
      <description><![CDATA[<p>Welcome to the third and final part of the series &quot;The Cost of Not Knowing MongoDB.&quot; Building upon the foundational optimizations explored in Part 1 and Part 2, this article delves into advanced MongoDB design patterns that can dramatically transform application performance.</p>
<p>In Part 1, we improved application performance by concatenating fields, changing data types, and shortening field names. In Part 2, we implemented the <b><a href="https://www.mongodb.com/docs/manual/data-modeling/design-patterns/group-data/bucket-pattern/">Bucket Pattern</a></b> and <b><a href="https://www.mongodb.com/company/blog/building-with-patterns-the-computed-pattern">Computed Pattern</a></b> and optimized the aggregation pipeline to achieve even better performance.</p>
<p>In this final article, we address the <b>issues and improvements</b> identified in <b>appV5R4</b>. Specifically, we focus on reducing the document size in our application to alleviate the disk throughput bottleneck on the MongoDB server. This reduction will be accomplished by adopting a <b>dynamic schema</b> and modifying the storage compression algorithm.</p>
<p>All the application versions and revisions from this article were developed by a senior MongoDB developer, as they are built on all the previous versions and utilize the Dynamic Schema pattern, which isn't very common to see.</p>
<h2>Application version 6 revision 0 (appV6R0): A dynamic monthly bucket document</h2>
<p>As mentioned in the Issues and Improvements of appV5R4 from the previous article, the primary limitation of our MongoDB server is its disk throughput. To address this, we need to reduce the size of the documents being stored.</p>
<p>Consider the following document from appV5R3, which has provided the best performance so far:</p>
<pre><code tabindex="0">const document = {&NewLine;  _id: Buffer.from(&quot;...01202202&quot;),&NewLine;  items: [&NewLine;    { date: new Date(&quot;2022-06-05&quot;), a: 10, n: 3 },&NewLine;    { date: new Date(&quot;2022-06-16&quot;), p: 1, r: 1 },&NewLine;    { date: new Date(&quot;2022-06-27&quot;), a: 5, r: 1 },&NewLine;    { date: new Date(&quot;2022-06-29&quot;), p: 1 },&NewLine;  ],&NewLine;};&NewLine;</code></pre>
<p>The items array in this document contains only four elements, but on average, it will have around 10 elements, and in the worst-case scenario, it could have up to 90 elements. These elements are the primary contributors to the document size, so they should be the focus of our optimization efforts.</p>
<p>One commonality among the elements is the presence of the date field, with its value including the year and month, for the previous document. By rethinking how this field and its value could be stored, we can reduce storage requirements.</p>
<p>An unconventional solution we could use is:</p>
<ul>
<li>
<p>Changing the items field type from an array to a document.</p>
</li>
<li>
<p>Using the date value as the field name in the items document.</p>
</li>
<li>
<p>Storing the status totals as the value for each date field.</p>
</li>
</ul>
<p>Here is the previous document represented using the new schema idea:</p>
<pre><code tabindex="0">const document = {&NewLine;  _id: Buffer.from(&quot;...01202202&quot;),&NewLine;  items: {&NewLine;    20220605: { a: 10, n: 3 },&NewLine;    20220616: { p: 1, r: 1 },&NewLine;    20220627: { a: 5, r: 1 },&NewLine;    20220629: { p: 1 },&NewLine;  },&NewLine;};&NewLine;</code></pre>
<p>While this schema may not significantly reduce the document size compared to appV5R3, we can further optimize it by leveraging the fact that the year is already embedded in the _id field. This eliminates the need to repeat the year in the field names of the items document.</p>
<p>With this approach, the items document adopts a Dynamic Schema, where field names encode information and are not predefined.</p>
<p>To demonstrate various implementation possibilities, we will revisit all the bucketing criteria used in the appV5RX implementations, starting with appV5R0.</p>
<p>For appV6R0, which builds upon appV5R0 but uses a dynamic schema, data is bucketed by year and month. The field names in the items document represent only the day of the date, as the year and month are already stored in the _id field.</p>
<p>A detailed explanation of the bucketing logic and functions used to implement the current application can be found in the appV5R0 introduction.</p>
<p>The following document stores data for January 2022 (2022-01-XX), applying the newly presented idea:</p>
<pre><code tabindex="0">const document = {&NewLine;  _id: Buffer.from(&quot;...01202201&quot;),&NewLine;  items: {&NewLine;    &quot;05&quot;: { a: 10, n: 3 },&NewLine;    16: { p: 1, r: 1 },&NewLine;    27: { a: 5, r: 1 },&NewLine;    29: { p: 1 },&NewLine;  },&NewLine;};&NewLine;</code></pre>
<h3>Schema</h3>
<p>The application implementation presented above would have the following TypeScript document schema denominated SchemaV6R0:</p>
<pre><code tabindex="0">export type SchemaV6R0 = {&NewLine;  _id: Buffer;&NewLine;  items: Record&lt;&NewLine;    string,&NewLine;    {&NewLine;      a?: number;&NewLine;      n?: number;&NewLine;      p?: number;&NewLine;      r?: number;&NewLine;    }&NewLine;  &gt;;&NewLine;};&NewLine;</code></pre>
<h3>Bulk upsert</h3>
<p>Based on the specification presented, we have the following updateOne operation for each event generated by this application version:</p>
<pre><code tabindex="0">const DD = getDD(event.date); // Extract the `day` from the `event.date`&NewLine;&NewLine;const operation = {&NewLine;  updateOne: {&NewLine;    filter: { _id: buildId(event.key, event.date) }, // key + year + month&NewLine;    update: {&NewLine;      $inc: {&NewLine;        [`items.${DD}.a`]: event.approved,&NewLine;        [`items.${DD}.n`]: event.noFunds,&NewLine;        [`items.${DD}.p`]: event.pending,&NewLine;        [`items.${DD}.r`]: event.rejected,&NewLine;      },&NewLine;    },&NewLine;    upsert: true,&NewLine;  },&NewLine;};&NewLine;</code></pre>
<p><b>filter:</b></p>
<ul>
<li>
<p>Target the document where the _id field matches the concatenated value of key, year, and month.</p>
</li>
<li>
<p>The buildId function converts the key+year+month into a binary format.</p>
</li>
</ul>
<p><b>update:</b></p>
<ul>
<li>
<p>Uses the <a href="https://www.mongodb.com/docs/manual/reference/operator/update/inc/">$inc</a> operator to increment the fields corresponding to the same DD as the event by the status values provided.</p>
</li>
<li>
<p>If a field does not exist in the items document and the event provides a value for it, $inc treats the non-existent field as having a value of 0 and performs the operation.</p>
</li>
<li>
<p>If a field exists in the items document but the event does not provide a value for it (i.e., undefined), $inc treats it as 0 and performs the operation.</p>
</li>
</ul>
<p><b>upsert:</b></p>
<ul>
<li><font size="4">Ensures a new document is created if no matching document exists.</font></li>
</ul>
<h3>Get reports</h3>
<p>To fulfill the Get Reports operation, five aggregation pipelines are required, one for each date interval. Each pipeline follows the same structure, differing only in the filtering criteria in the $match stage:</p>
<pre><code tabindex="0">const pipeline = [&NewLine;  { $match: docsFromKeyBetweenDate },&NewLine;  { $addFields: buildTotalsField },&NewLine;  { $group: groupSumTotals },&NewLine;  { $project: { _id: 0 } },&NewLine;];&NewLine;</code></pre>
<p>The complete code for this aggregation pipeline is quite complicated. Because of that, we will have just a pseudocode for it here.</p>
<p>1: <code tabindex="0">{ $match: docsFromKeyBetweenDate }</code></p>
<ul>
<li><font size="4">Range-filters documents by _id to retrieve only buckets within the report date range. It has the same logic as appV5R0.</font></li>
</ul>
<p>2: <code tabindex="0">{ $addFields: buildTotalsField }</code></p>
<ul>
<li>
<p>The logic is similar to the one used in the Get Reports of appV5R3.</p>
</li>
<li>
<p>The <a href="https://www.mongodb.com/docs/manual/reference/operator/aggregation/objectToArray/">$objectToArray</a> operator is used to convert the items document into an array, enabling a $reduce operation.</p>
</li>
<li>
<p>Filtering the items fields within the report's range involves extracting the year and month from the _id field and the day from the field names in the items document.</p>
</li>
<li>
<p>The following JavaScript code is logic equivalent to the real aggregation pipeline code.</p>
</li>
</ul>
<pre><code tabindex="0">// Equivalent JavaScript logic:&NewLine;const [MM] = _id.slice(-2).toString(); // Get month from _id&NewLine;const [YYYY] = _id.slice(-6, -2).toString(); // Get year from _id&NewLine;const items_array = Object.entries(items); // Convert the object to an array of [key, value]&NewLine;&NewLine;const totals = items_array.reduce(&NewLine;  (accumulator, [DD, status]) =&gt; {&NewLine;    let statusDate = new Date(`${YYYY}-${MM}-${DD}`);&NewLine;&NewLine;    if (statusDate &gt;= reportStartDate &amp;&amp; statusDate &lt; reportEndDate) {&NewLine;      accumulator.a += status.a || 0;&NewLine;      accumulator.n += status.n || 0;&NewLine;      accumulator.p += status.p || 0;&NewLine;      accumulator.r += status.r || 0;&NewLine;    }&NewLine;&NewLine;    return accumulator;&NewLine;  },&NewLine;  { a: 0, n: 0, p: 0, r: 0 }&NewLine;);&NewLine;</code></pre>
<p>3: <code tabindex="0">{ $group: groupCountTotals }</code></p>
<ul>
<li><font size="4">Group the totals of each document in the pipeline into final status totals using $sum operations.</font></li>
</ul>
<p>4: <code tabindex="0">{ $project: { _id: 0 } }</code></p>
<ul>
<li><font size="4">Format the resulting document to have the reports format.</font></li>
</ul>
<h3>Indexes</h3>
<p>No additional indexes are required, maintaining the single _id index approach established in the appV4 implementation.</p>
<h3>Initial scenario statistics</h3>
<h4>Collection statistics</h4>
<p>To evaluate the performance of appV6R0, we inserted 500 million event documents into the collection using the schema and Bulk Upsert function described earlier. For comparison, the tables below also include statistics from previous comparable application versions:</p>
<html>
<head>
     <style>
    table,
    th,
    td {
        border: 1px solid black;
        border-collapse: collapse;
    }
    th,
    td {
        padding: 5px;
    }
    </style>
</head>
<body>
    <table style="width:100%">
        <tr>
            <th>Collection</th>
            <th>Documents</th>
					<th>Data Size</th>
					<th>Document Size</th>
					<th>Storage Size</th>
					<th>Indexes</th>
					<th>Index Size</th>
        </tr>
        <tr>
					<td>appV5R0</td>
					<td>95,350,431</td>
					<td>19.19GB</td>
					<td>217B</td>
					<td>5.06GB</td>
					<td>1</td>
					<td>2.95GB</td>
        </tr>
			<tr>
				<td>appV5R3</td>
				<td>33,429,492</td>
				<td>11.96GB</td>
				<td>385B</td>
				<td>3.24GB</td>
				<td>1</td>
				<td>1.11GB</td>
			</tr>
			<tr>
				<td>appV6R0</td>
				<td>95,350,319</td>
				<td>11.1GB</td>
				<td>125B</td>
				<td>3.33GB</td>
				<td>1</td>
				<td>3.13GB</td>
    </table>
</body>
</html>
<h4>Event statistics</h4>
<p>To evaluate the storage efficiency per event, the Event Statistics are calculated by dividing the total data size and index size by the 500 million events.</p>
<html>
<head>
     <style>
    table,
    th,
    td {
        border: 1px solid black;
        border-collapse: collapse;
    }
    th,
    td {
        padding: 5px;
    }
    </style>
</head>
<body>
    <table style="width:100%">
        <tr>
            <th>Collection</th>
            <th>Data Size/Events</th>
					<th>Index Size/Events</th>
					<th>Total Size/Events</th>
        </tr>
        <tr>
					<td>appV5R0</td>
					<td>41.2B</td>
					<td>6.3B</td>
					<td>47.5B</td>
        </tr>
			<tr>
				<td>appV5R3</td>
				<td>25.7B</td>
				<td>2.4B</td>
				<td>28.1B</td>
			</tr>
			<tr>
				<td>appV6R0</td>
				<td>23.8B</td>
				<td>6.7B</td>
				<td>30.5B</td>
			</tr>
    </table>
</body>
</html>
<p>It is challenging to make a direct comparison between appV6R0 and appV5R0 from a storage perspective. The appV5R0 implementation is the simplest bucketing possible, where event documents were merely appended to the items array without bucketing by day, as is done in appV6R0.</p>
<p>However, we can attempt a comparison between appV6R0 and appV5R3, the best solution so far. In appV6R0, data is bucketed by month, whereas in appV5R3, it is bucketed by quarter. Assuming document size scales linearly with the bucketing criteria (though this is not entirely accurate), the appV6R0 document would be approximately 3 * 125 = 375 bytes, which is 9.4% smaller than appV5R3.</p>
<p>Another indicator of improvement is the Data Size/Events metric in the Event Statistics table. For appV6R0, each event uses an average of 23.8 bytes, compared to 27.7 bytes for appV5R3, representing a 14.1% reduction in size.</p>
<h3>Load test results</h3>
<p>Executing the load test for appV6R0 and plotting it alongside the results for appV5R0 and Desired rates, we have the following results for Get Reports and Bulk Upsert.</p>
<h4>Get Reports rates</h4>
<p>The two versions exhibit very similar rate performance, with appV6R0 showing slight superiority in the second and third quarters, while appV5R0 is superior in the first and fourth quarters.</p>
<center><caption><b>Figure 1.</b> Graph showing the rates of appV5R0 and appV6R0 when executing the load test for Get Reports functionality. Both have similar performance, but without reaching the desired rates.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-10-08 at 11.49.49 AM-vzb1w73m29.png" alt="Graph showing the rates of appV5R0 and appV6R0 when executing the load test for Get Reports functionality. Both have similar performance, but without reaching the desired rates." title=" " style="width: 800px"/>
</div>
<figcaption class="fl-center"> </figcaption>
</figure>
<h4>Get Reports latency</h4>
<p>The two versions exhibit very similar latency performance, with appV6R0 showing slight advantages in the second and third quarters, while appV5R0 is superior in the first and fourth quarters.</p>
<center><caption><b>Figure 2.</b> Graph showing the latency of appV5R0 and appV6R0 when executing the load test for Get Reports functionality. appV5R0 has lower latency than appV6R0.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-10-08 at 11.52.08 AM-tcgwfvap9f.png" alt="Graph showing the latency of appV5R0 and appV6R0 when executing the load test for Get Reports functionality. appV5R0 has lower latency than appV6R0. " title=" " style="width: 800px"/>
</div>
<figcaption class="fl-center"> </figcaption>
</figure>
<h4>Bulk Upsert rates</h4>
<p>Both versions have similar rate values, but it can be seen that appV6R0 has a small edge compared to appV5R0.</p>
<center><caption><b>Figure 3.</b> Graph showing the rates of appV5R0 and appV6R0 when executing the load test for Bulk Upsert functionality. appV6R0 has better rates than appV5R0, but without reaching the desired rates.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-10-08 at 12.09.53 PM-rsx3uaz6xn.png" alt="Graph showing the rates of appV5R0 and appV6R0 when executing the load test for Bulk Upsert functionality. appV6R0 has better rates than appV5R0, but without reaching the desired rates. " title=" " style="width: 800px"/>
</div>
<figcaption class="fl-center"> </figcaption>
</figure>
<h4>Bulk Upsert latency</h4>
<p>Although both versions have similar latency values for the first quarter of the test, for the final three-quarters, appV6R0 has a clear advantage over appV5R0.</p>
<center><caption><b>Figure 4.</b> Graph showing the latency of appV5R0 and appV6R0 when executing the load test for Bulk Upsert functionality. appV6R0 has lower latency than appV5R0.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-10-08 at 12.11.15 PM-gnmg26z6bk.png" alt="Graph showing the latency of appV5R0 and appV6R0 when executing the load test for Bulk Upsert functionality. appV6R0 has lower latency than appV5R0" title=" " style="width: 800px"/>
</div>
<figcaption class="fl-center"> </figcaption>
</figure>
<h4>Performance summary</h4>
<p>Despite the significant reduction in document and storage size achieved by appV6R0, the performance improvement was not as substantial as expected. This suggests that the bottleneck in the application when bucketing data by month may not be related to disk throughput.</p>
<p>Examining the collection stats table reveals that the index size for both versions is close to 3GB. This is near the 4GB of available memory on the machine running the database and exceeds the <a href="https://www.mongodb.com/docs/manual/core/wiredtiger/#memory-use">1.5GB allocated by WiredTiger for cache</a>. Therefore, it is likely that the limiting factor in this case is memory/cache rather than document size, which explains the lack of a significant performance improvement.</p>
<h3>Issues and improvements</h3>
<p>To address the limitations observed in appV6R0, we propose adopting the same line of improvements applied from appV5R0 to appV5R1. Specifically, we will bucket the events by quarter in appV6R1. This approach not only follows the established pattern of enhancements but also aligns with the need to optimize performance further.</p>
<p>As highlighted in the Load Test Results, the current bottleneck lies in the size of the index relative to the available cache/memory. By increasing the bucketing interval from month to quarter, we can reduce the number of documents by approximately a factor of three. This reduction will, in turn, decrease the number of index entries by the same factor, leading to a smaller index size.</p>
<h2>Application version 6 revision 1 (appV6R1): A dynamic quarter bucket document</h2>
<p>As discussed in the previous Issues and Improvements section, the primary bottleneck in appV6R0 was the index size nearing the memory capacity of the machine running MongoDB. To mitigate this issue, we propose increasing the bucketing interval from a month to a quarter for appV6R1, following the approach used in appV5R1.</p>
<p>This adjustment aims to reduce the number of documents and index entries by approximately a factor of three, thereby decreasing the overall index size. By adopting a quarter-based bucketing strategy, we align with the established pattern of enhancements applied in appV5R1 versions while addressing the specific memory/cache constraints identified in appV6R0.</p>
<p>The implementation of appV6R1 retains most of the code from appV6R0, with the following key differences:</p>
<ul>
<li>
<p>The _id field will now be composed of key+year+quarter.</p>
</li>
<li>
<p>The field names in the items document will encode both month and day, as this information is necessary for filtering date ranges in the Get Reports operation.</p>
</li>
</ul>
<p>The following example demonstrates how data for June 2022 (2022-06-XX), within the second quarter (Q2), is stored using the new schema:</p>
<pre><code tabindex="0">const document = {&NewLine;  _id: Buffer.from(&quot;...01202202&quot;),&NewLine;  items: {&NewLine;    &quot;0605&quot;: { a: 10, n: 3 },&NewLine;    &quot;0616&quot;: { p: 1, r: 1 },&NewLine;    &quot;0627&quot;: { a: 5, r: 1 },&NewLine;    &quot;0629&quot;: { p: 1 },&NewLine;  },&NewLine;};&NewLine;</code></pre>
<h3>Schema</h3>
<p>The application implementation presented above would have the following TypeScript document schema denominated SchemaV6R0:</p>
<pre><code tabindex="0">export type SchemaV6R0 = {&NewLine;  _id: Buffer;&NewLine;  items: Record&lt;&NewLine;    string,&NewLine;    {&NewLine;      a?: number;&NewLine;      n?: number;&NewLine;      p?: number;&NewLine;      r?: number;&NewLine;    }&NewLine;  &gt;;&NewLine;};&NewLine;</code></pre>
<h3>Bulk upsert</h3>
<p>Based on the specification presented, we have the following updateOne operation for each event generated by this application version:</p>
<pre><code tabindex="0">const MMDD = getMMDD(event.date); // Extract the month (MM) and day(DD) from the `event.date`&NewLine;&NewLine;const operation = {&NewLine;  updateOne: {&NewLine;    filter: { _id: buildId(event.key, event.date) }, // key + year + quarter&NewLine;    update: {&NewLine;      $inc: {&NewLine;        [`items.${MMDD}.a`]: event.approved,&NewLine;        [`items.${MMDD}.n`]: event.noFunds,&NewLine;        [`items.${MMDD}.p`]: event.pending,&NewLine;        [`items.${MMDD}.r`]: event.rejected,&NewLine;      },&NewLine;    },&NewLine;    upsert: true,&NewLine;  },&NewLine;};&NewLine;</code></pre>
<p>This updateOne operation has a similar logic to the one in appV6R0, with the only differences being the filter and update criteria.</p>
<p><b>filter:</b></p>
<ul>
<li>
<p>Target the document where the _id field matches the concatenated value of key, year, and quarter.</p>
</li>
<li>
<p>The buildId function converts the key+year+quarter into a binary format.</p>
</li>
</ul>
<p><b>update:</b></p>
<ul>
<li><font size="4">Uses the $inc operator to increment the fields corresponding to the same MMDD as the event by the status values provided.</font></li>
</ul>
<h3>Get reports</h3>
<p>To fulfill the Get Reports operation, five aggregation pipelines are required, one for each date interval. Each pipeline follows the same structure, differing only in the filtering criteria in the $match stage:</p>
<pre><code tabindex="0">const pipeline = [&NewLine;  { $match: docsFromKeyBetweenDate },&NewLine;  { $addFields: buildTotalsField },&NewLine;  { $group: groupSumTotals },&NewLine;  { $project: { _id: 0 } },&NewLine;];&NewLine;</code></pre>
<p>This aggregation operation has a similar logic to the one in appV6R0, with the only differences being the implementation in the $addFields stage.</p>
<p><code tabindex="0">{ $addFields: itemsReduceAccumulator }:</code></p>
<ul>
<li>
<p>A similar implementation to the one in appV6R0</p>
</li>
<li>
<p>The difference relies on extracting the value of year (YYYY) from the _id field and the month and day (MMDD) from the field name.</p>
</li>
<li>
<p>The following JavaScript code is logic equivalent to the real aggregation pipeline code.</p>
</li>
</ul>
<pre><code tabindex="0">const [YYYY] = _id.slice(-6, -2).toString(); // Get year from _id&NewLine;const items_array = Object.entries(items); // Convert the object to an array of [key, value]&NewLine;&NewLine;const totals = items_array.reduce(&NewLine;  (accumulator, [MMDD, status]) =&gt; {&NewLine;    let [MM, DD] = [MMDD.slice(0, 2), MMDD.slice(2, 4)];&NewLine;    let statusDate = new Date(`${YYYY}-${MM}-${DD}`);&NewLine;&NewLine;    if (statusDate &gt;= reportStartDate &amp;&amp; statusDate &lt; reportEndDate) {&NewLine;      accumulator.a += status.a || 0;&NewLine;      accumulator.n += status.n || 0;&NewLine;      accumulator.p += status.p || 0;&NewLine;      accumulator.r += status.r || 0;&NewLine;    }&NewLine;&NewLine;    return accumulator;&NewLine;  },&NewLine;  { a: 0, n: 0, p: 0, r: 0 }&NewLine;);&NewLine;</code></pre>
<h3>Indexes</h3>
<p>No additional indexes are required, maintaining the single _id index approach established in the appV4 implementation.</p>
<h3>Initial scenario statistics</h3>
<h4>Collection statistics</h4>
<p>To evaluate the performance of appV6R1, we inserted 500 million event documents into the collection using the schema and Bulk Upsert function described earlier. For comparison, the tables below also include statistics from previous comparable application versions:</p>
<html>
<head>
     <style>
    table,
    th,
    td {
        border: 1px solid black;
        border-collapse: collapse;
    }
    th,
    td {
        padding: 5px;
    }
    </style>
</head>
<body>
    <table style="width:100%">
        <tr>
            <th>Collection</th>
            <th>Documents</th>
					<th>Data Size</th>
					<th>Document Size</th>
					<th>Storage Size</th>
					<th>Indexes</th>
					<th>Index Size</th>
        </tr>
        <tr>
					<td>appV5R3</td>
					<td>33,429,492</td>
					<td>11.96GB</td>
					<td>385B</td>
					<td>3.24GB</td>
					<td>1</td>
					<td>1.11GB</td>
        </tr>
			<tr>
				<td>appV6R0</td>
				<td>95,350,319</td>
				<td>11.1GB</td>
				<td>125B</td>
				<td>3.33GB</td>
				<td>1</td>
				<td>3.13GB</td>
			</tr>
			<tr>
				<td>appV6R1</td>
				<td>33,429,366</td>
				<td>8.19GB</td>
				<td>264B</td>
				<td>2.34GB</td>
				<td>1</td>
				<td>1.22GB</td>
			</tr>
    </table>
</body>
</html>
<h4>Event statistics</h4>
<p>To evaluate the storage efficiency per event, the Event Statistics are calculated by dividing the total data size and index size by the 500 million events.</p>
<html>
<head>
     <style>
    table,
    th,
    td {
        border: 1px solid black;
        border-collapse: collapse;
    }
    th,
    td {
        padding: 5px;
    }
    </style>
</head>
<body>
    <table style="width:100%">
        <tr>
            <th>Collection</th>
            <th>Data Size/Events</th>
					<th>Index Size/Events</th>
					<th>Total Size/Events</th>
        </tr>
        <tr>
					<td>appV5R3</td>
					<td>25.7B</td>
					<td>2.4B</td>
					<td>28.1B</td>
        </tr>
			<tr>
				<td>appV6R0</td>
				<td>23.8B</td>
				<td>6.7B</td>
				<td>30.5B</td>
			</tr>
			<tr>
				<td>appV6R1</td>
				<td>17.6B</td>
				<td>2.6B</td>
				<td>20.2B</td>
			</tr>
    </table>
</body>
</html>
<p>In the previous Initial Scenario Statistics analysis, we assumed that document size would scale linearly with the bucketing range. However, this assumption proved inaccurate. The average document size in appV6R1 is approximately twice as large as in appV6R0, even though it stores three times more data. Already a win for this new implementation.</p>
<p>Since appV6R1 buckets data by quarter at the document level and by day within the items sub-document, a fair comparison would be with appV5R3, the best-performing version so far. From the tables above, we observe a significant improvement in Document Size and consequently Data Size when transitioning from appV5R3 to appV6R1. Specifically, there was a 31.4% reduction in Document Size. From an index size perspective, there was no change, as both versions bucket events by quarter.</p>
<h3>Load test results</h3>
<p>Executing the load test for appV6R0 and plotting it alongside the results for appV5R0 and Desired rates, we have the following results for Get Reports and Bulk Upsert.</p>
<h4>Get Reports rates</h4>
<p>For the first three-quarters of the test, both versions have similar rate values, but, for the final quarter, appV6R1 has a notable edge over appV5R3.</p>
<center><caption><b>Figure 5.</b> Graph showing the rates of appV5R3 and appV6R1 when executing the load test for Get Reports functionality. appV5R3 has better rates than appV6R1, but without reaching the desired rates.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-10-08 at 12.41.58 PM-uuprlz3n1y.png" alt="Graph showing the rates of appV5R3 and appV6R1 when executing the load test for Get Reports functionality. appV5R3 has better rates than appV6R1, but without reaching the desired rates." title=" " style="width: 800px"/>
</div>
<figcaption class="fl-center"> </figcaption>
</figure>
<h4>Get Reports latency</h4>
<p>The two versions exhibit very similar latency performance, with appV6R0 showing slight advantages in the second and third quarters, while appV5R0 is superior in the first and fourth quarters.</p>
<center><caption><b>Figure 6.</b> Graph showing the latency of appV5R0 and appV6R0 when executing the load test for Get Reports functionality. appV5R0 has lower latency than appV6R0.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-10-08 at 12.44.56 PM-x60k3nk98v.png" alt="Graph showing the latency of appV5R0 and appV6R0 when executing the load test for Get Reports functionality. appV5R0 has lower latency than appV6R0. " title=" " style="width: 800px"/>
</div>
<figcaption class="fl-center"> </figcaption>
</figure>
<h4>Bulk Upsert rates</h4>
<p>Both versions have similar rate values, but it can be seen that appV6R0 has a small edge compared to appV5R0.</p>
<center><caption><b>Figure 7.</b> Graph showing the rates of appV5R0 and appV6R0 when executing the load test for Bulk Upsert functionality. appV6R0 has better rates than appV5R0, but without reaching the desired rates.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-10-08 at 12.47.10 PM-0pl18wvhs1.png" alt="Graph showing the rates of appV5R0 and appV6R0 when executing the load test for Bulk Upsert functionality. appV6R0 has better rates than appV5R0, but without reaching the desired rates. " title=" " style="width: 800px"/>
</div>
<figcaption class="fl-center"> </figcaption>
</figure>
<h4>Bulk Upsert latency</h4>
<p>Although both versions have similar latency values for the first quarter of the test, for the final three-quarters, appV6R0 has a clear advantage over appV5R0.</p>
<center><caption><b>Figure 8.</b> Graph showing the latency of appV5R0 and appV6R0 when executing the load test for Bulk Upsert functionality. appV6R0 has lower latency than appV5R0.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-10-08 at 12.49.40 PM-zg75zchnty.png" alt="Graph showing the latency of appV5R0 and appV6R0 when executing the load test for Bulk Upsert functionality. appV6R0 has lower latency than appV5R0. " title=" " style="width: 800px"/>
</div>
<figcaption class="fl-center"> </figcaption>
</figure>
<h4>Performance summary</h4>
<p>Despite the significant reduction in document and storage size achieved by appV6R0, the performance improvement was not as substantial as expected. This suggests that the bottleneck in the application when bucketing data by month may not be related to disk throughput.</p>
<p>Examining the collection stats table reveals that the index size for both versions is close to 3GB. This is near the 4GB of available memory on the machine running the database and exceeds the <a href="https://www.mongodb.com/docs/manual/core/wiredtiger/#memory-use">1.5GB allocated by WiredTiger for cache</a>. Therefore, it is likely that the limiting factor in this case is memory/cache rather than document size, which explains the lack of a significant performance improvement.</p>
<h3>Issues and improvements</h3>
<p>To address the limitations observed in appV6R0, we propose adopting the same line of improvements applied from appV5R0 to appV5R1. Specifically, we will bucket the events by quarter in appV6R1. This approach not only follows the established pattern of enhancements but also aligns with the need to optimize performance further.</p>
<p>As highlighted in the Load Test Results, the current bottleneck lies in the size of the index relative to the available cache/memory. By increasing the bucketing interval from month to quarter, we can reduce the number of documents by approximately a factor of three. This reduction will, in turn, decrease the number of index entries by the same factor, leading to a smaller index size.</p>
<h2>Application version 6 revision 1 (appV6R1): A dynamic quarter bucket document</h2>
<p>As discussed in the previous Issues and Improvements section, the primary bottleneck in appV6R0 was the index size nearing the memory capacity of the machine running MongoDB. To mitigate this issue, we propose increasing the bucketing interval from a month to a quarter for appV6R1, following the approach used in appV5R1.</p>
<p>This adjustment aims to reduce the number of documents and index entries by approximately a factor of three, thereby decreasing the overall index size. By adopting a quarter-based bucketing strategy, we align with the established pattern of enhancements applied in appV5R1 versions while addressing the specific memory/cache constraints identified in appV6R0.</p>
<p>The implementation of appV6R1 retains most of the code from appV6R0, with the following key differences:</p>
<ul>
<li>
<p>The _id field will now be composed of key+year+quarter.</p>
</li>
<li>
<p>The field names in the items document will encode both month and day, as this information is necessary for filtering date ranges in the Get Reports operation.</p>
</li>
</ul>
<p>The following example demonstrates how data for June 2022 (2022-06-XX), within the second quarter (Q2), is stored using the new schema:</p>
<pre><code tabindex="0">const document = {&NewLine;  _id: Buffer.from(&quot;...01202202&quot;),&NewLine;  items: {&NewLine;    &quot;0605&quot;: { a: 10, n: 3 },&NewLine;    &quot;0616&quot;: { p: 1, r: 1 },&NewLine;    &quot;0627&quot;: { a: 5, r: 1 },&NewLine;    &quot;0629&quot;: { p: 1 },&NewLine;  },&NewLine;};&NewLine;</code></pre>
<h3>Schema</h3>
<p>The application implementation presented above would have the following TypeScript document schema denominated SchemaV6R0:</p>
<pre><code tabindex="0">export type SchemaV6R0 = {&NewLine;  _id: Buffer;&NewLine;  items: Record&lt;&NewLine;    string,&NewLine;    {&NewLine;      a?: number;&NewLine;      n?: number;&NewLine;      p?: number;&NewLine;      r?: number;&NewLine;    }&NewLine;  &gt;;&NewLine;};&NewLine;</code></pre>
<h3>Bulk upsert</h3>
<p>Based on the specification presented, we have the following updateOne operation for each event generated by this application version:</p>
<pre><code tabindex="0">const MMDD = getMMDD(event.date); // Extract the month (MM) and day(DD) from the `event.date`&NewLine;&NewLine;const operation = {&NewLine;  updateOne: {&NewLine;    filter: { _id: buildId(event.key, event.date) }, // key + year + quarter&NewLine;    update: {&NewLine;      $inc: {&NewLine;        [`items.${MMDD}.a`]: event.approved,&NewLine;        [`items.${MMDD}.n`]: event.noFunds,&NewLine;        [`items.${MMDD}.p`]: event.pending,&NewLine;        [`items.${MMDD}.r`]: event.rejected,&NewLine;      },&NewLine;    },&NewLine;    upsert: true,&NewLine;  },&NewLine;};&NewLine;</code></pre>
<p>This updateOne operation has a similar logic to the one in appV6R0, with the only differences being the filter and update criteria.</p>
<p><b>filter:</b></p>
<ul>
<li>
<p>Target the document where the _id field matches the concatenated value of key, year, and quarter.</p>
</li>
<li>
<p>The buildId function converts the key+year+quarter into a binary format.</p>
</li>
</ul>
<p><b>update:</b></p>
<ul>
<li>Uses the $inc operator to increment the fields corresponding to the same MMDD as the event by the status values provided.</li>
</ul>
<h3>Get reports</h3>
<p>To fulfill the Get Reports operation, five aggregation pipelines are required, one for each date interval. Each pipeline follows the same structure, differing only in the filtering criteria in the $match stage:</p>
<pre><code tabindex="0">const pipeline = [&NewLine;  { $match: docsFromKeyBetweenDate },&NewLine;  { $addFields: buildTotalsField },&NewLine;  { $group: groupSumTotals },&NewLine;  { $project: { _id: 0 } },&NewLine;];&NewLine;</code></pre>
<p>This aggregation operation has a similar logic to the one in appV6R0, with the only differences being the implementation in the $addFields stage.</p>
<p><code tabindex="0">{ $addFields: itemsReduceAccumulator }:</code></p>
<ul>
<li>
<p>A similar implementation to the one in appV6R0</p>
</li>
<li>
<p>The difference relies on extracting the value of year (YYYY) from the _id field and the month and day (MMDD) from the field name.</p>
</li>
<li>
<p>The following JavaScript code is logic equivalent to the real aggregation pipeline code.</p>
</li>
</ul>
<pre><code tabindex="0">const [YYYY] = _id.slice(-6, -2).toString(); // Get year from _id&NewLine;const items_array = Object.entries(items); // Convert the object to an array of [key, value]&NewLine;&NewLine;const totals = items_array.reduce(&NewLine;  (accumulator, [MMDD, status]) =&gt; {&NewLine;    let [MM, DD] = [MMDD.slice(0, 2), MMDD.slice(2, 4)];&NewLine;    let statusDate = new Date(`${YYYY}-${MM}-${DD}`);&NewLine;&NewLine;    if (statusDate &gt;= reportStartDate &amp;&amp; statusDate &lt; reportEndDate) {&NewLine;      accumulator.a += status.a || 0;&NewLine;      accumulator.n += status.n || 0;&NewLine;      accumulator.p += status.p || 0;&NewLine;      accumulator.r += status.r || 0;&NewLine;    }&NewLine;&NewLine;    return accumulator;&NewLine;  },&NewLine;  { a: 0, n: 0, p: 0, r: 0 }&NewLine;);&NewLine;</code></pre>
<h3>Indexes</h3>
<p>No additional indexes are required, maintaining the single _id index approach established in the appV4 implementation.</p>
<h3>Initial scenario statistics</h3>
<h4>Collection statistics</h4>
<p>To evaluate the performance of appV6R1, we inserted 500 million event documents into the collection using the schema and Bulk Upsert function described earlier. For comparison, the tables below also include statistics from previous comparable application versions:</p>
<html>
<head>
     <style>
    table,
    th,
    td {
        border: 1px solid black;
        border-collapse: collapse;
    }
    th,
    td {
        padding: 5px;
    }
    </style>
</head>
<body>
    <table style="width:100%">
        <tr>
            <th>Collection</th>
            <th>Documents</th>
					<th>Data Size</th>
					<th>Document Size</th>
					<th>Storage Size</th>
					<th>Indexes</th>
					<th>Index Size</th>
        </tr>
        <tr>
					<td>appV5R3</td>
					<td>33,429,492</td>
					<td>11.96GB</td>
					<td>11.96GB</td>
					<td>3.24GB</td>
					<td>1</td>
					<td>1.11GB</td>
        </tr>
			 <tr>
					<td>appV6R1</td>
					<td>33,429,366</td>
					<td>8.19GB</td>
					<td>264B</td>
					<td>2.34GB</td>
					<td>1</td>
					<td>1.22GB</td>
        </tr>
			<tr>
					<td>appV6R2</td>
					<td>33,429,207</td>
					<td>9.11GB</td>
					<td>293B</td>
					<td>2.8GB</td>
					<td>1</td>
					<td>1.26GB</td>
        </tr>
    </table>
</body>
</html>
<h4>Event statistics</h4>
<p>To evaluate the storage efficiency per event, the Event Statistics are calculated by dividing the total data size and index size by the 500 million events.</p>
<head>
     <style>
    table,
    th,
    td {
        border: 1px solid black;
        border-collapse: collapse;
    }
    th,
    td {
        padding: 5px;
    }
    </style>
</head>
<body>
    <table style="width:100%">
        <tr>
            <th>Collection</th>
            <th>Data Size/Events</th>
					<th>Index Size/Events</th>
					<th>Total Size/Events</th>
			</tr>
			<tr>
				<td>appV5R3</td>
				<td>25.7B</td>
				<td>2.4B</td>
				<td>28.1B</td>
			</tr>
			<tr>
				<td>appV6R1</td>
				<td>17.6B</td>
				<td>2.6B</td>
				<td>20.2B</td>
			</tr>
			<tr>
				<td>appV6R2</td>
				<td>19.6B</td>
				<td>2.7B</td>
				<td>22.3B</td>
			</tr>
	</table>
	</body>
	</html>
<p>As expected, we had an 11.2% increase in the Document Size by adding a totals field in each document of appV6R2. When comparing to appV5R3, we still have a reduction of 23.9% in the Document Size. Let's review the Load Test Results to see if the trade-off between storage and computation cost is worthwhile.</p>
<h3>Load test results</h3>
<p>Executing the load test for appV6R2 and plotting it alongside the results for appV6R1 and Desired rates, we have the following results for Get Reports and Bulk Upsert.</p>
<h4>Get Reports rates</h4>
<p>We can see that appV6R2 has better rates than appV6R1 throughout the test, but it’s still not reaching the top rate of 250 reports per second.</p>
<center><caption><b>Figure 9.</b> Graph showing the rates of appV6R1 and appV6R2 when executing the load test for Get Reports functionality. appV6R2 has better rates than appV6R1, but without reaching the desired rates.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-10-08 at 1.23.52 PM-91zq1baq1t.png" alt="Graph showing the rates of appV6R1 and appV6R2 when executing the load test for Get Reports functionality. appV6R2 has better rates than appV6R1, but without reaching the desired rates." title=" " style="width: 800px"/>
</div>
<figcaption class="fl-center"> </figcaption>
</figure>
<h4>Get Reports latency</h4>
<p>As shown in the rates graph, appV6R2 consistently provides lower latency than appV6R1 throughout the test.</p>
<center><caption><b>Figure 10.</b> Graph showing the latency of appV6R1 and appV6R2 when executing the load test for Get Reports functionality. appV6R2 has lower latency than appV6R1.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-10-08 at 1.25.32 PM-gpfjrmosjv.png" alt="Graph showing the latency of appV6R1 and appV6R2 when executing the load test for Get Reports functionality. appV6R2 has lower latency than appV6R1." title=" " style="width: 800px"/>
</div>
<figcaption class="fl-center"> </figcaption>
</figure>
<h4>Bulk Upsert rates</h4>
<p>Both versions exhibit very similar rate values throughout the test, with appV6R2 performing slightly better than appV6R1 in the final 20 minutes, yet still failing to reach the desired rate.</p>
<center><caption><b>Figure 11.</b> Graph showing the rates of appV6R1 and appV6R2 when executing the load test for Bulk Upsert functionality. appV6R2 has better rates than appV6R1, almost reaching the desired rates.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-10-08 at 1.27.07 PM-gs2myt8s27.png" alt="Graph showing the rates of appV6R1 and appV6R2 when executing the load test for Bulk Upsert functionality. appV6R2 has better rates than appV6R1, almost reaching the desired rates. " title=" " style="width: 800px"/>
</div>
<figcaption class="fl-center"> </figcaption>
</figure>
<h4>Bulk Upsert latency</h4>
<p>Although appV6R2 had better rate values than appV6R1, their latency performance is not conclusive, with appV6R2 being superior in the first and final quarters and appV6R1 in the second and third quarters.</p>
<center><caption><b>Figure 12.</b> Graph showing the latency of appV6R1 and appV6R2 when executing the load test for Bulk Upsert functionality. Both versions have similar latencies.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-10-08 at 1.28.54 PM-im3qzf1xvd.png" alt="Graph showing the latency of appV6R1 and appV6R2 when executing the load test for Bulk Upsert functionality. Both versions have similar latencies." title=" " style="width: 800px"/>
</div>
<figcaption class="fl-center"> </figcaption>
</figure>
<h4>Performance summary</h4>
<p>The two &quot;maybes&quot; from the previous Issues and Improvements made up for their promises, and we got the best performance for appV6R2 when comparing to appV6R1. This is the redemption of the Computed Pattern applied on a document level. This revision is one of my favorites because it shows that the same optimization on very similar applications can lead to different results. In our case, the difference was caused by the application being very bottlenecked by the disk throughput.</p>
<h3>Issues and improvements</h3>
<p>Let's tackle the last improvement on an application level. Those paying close attention to the application versions may have already questioned it. In every Get Reports section, we have &quot;To fulfill the Get Reports operation, five aggregation pipelines are required, one for each date interval.&quot; Do we really need to run five aggregation pipelines to generate the reports document? Isn't there a way to calculate everything in just one operation? The answer is yes, there is.</p>
<p>The reports documents are composed of fields oneYear, threeYears, fiveYears, sevenYears, and tenYears, where each one was generated by its respective aggregation pipeline until now. Generating the reports this way is a waste of processing power because we are doing some part of the calculation multiple times. For example, to calculate the status totals for tenYears, we will also have to calculate the status totals for the other fields, as from a date range perspective, they are all contained in the tenYears date range.</p>
<p>So, for our next application revision, we'll condense the Get Reports five aggregation pipelines into one, avoiding wasting processing power on repeated calculation.</p>
<h2>Application version 6 revision 3 (appV6R3): Getting everything at once</h2>
<p>As discussed in the previous Issues and Improvements section, in this revision, we'll improve the performance of our application by changing the Get Reports functionality to generate the reports document using only one aggregation pipeline instead of five.</p>
<p>The rationale behind this improvement is that when we generate the tenYears totals, we have also calculated the other totals, oneYear, threeYears, fiveYears, and sevenYears. As an example, when we request to Get Reports with the key ...0001 with the date 2022-01-01, the totals will be calculated with the following date range:</p>
<ul>
<li>
<p>oneYear: from 2021-01-01 to 2022-01-01</p>
</li>
<li>
<p>threeYears: from 2020-01-01 to 2022-01-01</p>
</li>
<li>
<p>fiveYears: from 2018-01-01 to 2022-01-01</p>
</li>
<li>
<p>sevenYears: from 2016-01-01 to 2022-01-01</p>
</li>
<li>
<p>tenYear: from 2013-01-01 to 2022-01-01</p>
</li>
</ul>
<p>As we can see from the list above, the date range for tenYears encompasses all the other date ranges.</p>
<p>Although we successfully implemented the Computed Pattern in the previous revision, appV6R2, achieving better results than appV6R1, we will not use it as a base for this revision. There were two reasons for that:</p>
<ol>
<li>
<p>Based on the results of our previous implementation of the Computed Pattern on a document level, from appV5R3 to appV5R4, I didn't expect it to get better results.</p>
</li>
<li>
<p>Implementing Get Reports to retrieve the reports document through a single aggregation pipeline, utilizing pre-computed field totals generated by the Computed Pattern would require significant effort. By the time of the latest versions of this series, I just wanted to finish it.</p>
</li>
</ol>
<p>So, this revision will be built based on the appV6R1.</p>
<h3>Schema</h3>
<p>The application implementation presented above would have the following TypeScript document schema denominated SchemaV6R0:</p>
<pre><code tabindex="0">export type SchemaV6R0 = {&NewLine;  _id: Buffer;&NewLine;  items: Record&lt;&NewLine;    string,&NewLine;    {&NewLine;      a?: number;&NewLine;      n?: number;&NewLine;      p?: number;&NewLine;      r?: number;&NewLine;    }&NewLine;  &gt;;&NewLine;};&NewLine;</code></pre>
<h3>Bulk upsert</h3>
<p>Based on the specifications, the following bulk updateOne operation is used for each event generated by the application:</p>
<pre><code tabindex="0">const YYYYMMDD = getYYYYMMDD(event.date); // Extract the year(YYYY), month(MM), and day(DD) from the `event.date`&NewLine;&NewLine;const operation = {&NewLine;  updateOne: {&NewLine;    filter: { _id: buildId(event.key, event.date) }, // key + year + quarter&NewLine;    update: {&NewLine;      $inc: {&NewLine;        [`items.${YYYYMMDD}.a`]: event.approved,&NewLine;        [`items.${YYYYMMDD}.n`]: event.noFunds,&NewLine;        [`items.${YYYYMMDD}.p`]: event.pending,&NewLine;        [`items.${YYYYMMDD}.r`]: event.rejected,&NewLine;      },&NewLine;    },&NewLine;    upsert: true,&NewLine;  },&NewLine;};&NewLine;</code></pre>
<p>This updateOne has almost exactly the same logic as the one for appV6R1. The difference is that the name of the fields in the items document will be created based on year, month, and day (YYYYMMDD) instead of just month and day (MMDD). This change was made to reduce the complexity of the aggregation pipeline of the Get Reports.</p>
<h3>Get reports</h3>
<p>To fulfill the Get Reports operation, one aggregation pipeline is required:</p>
<pre><code tabindex="0">const pipeline = [&NewLine;  { $match: docsFromKeyBetweenDate },&NewLine;  { $addFields: buildTotalsField },&NewLine;  { $group: groupCountTotals },&NewLine;  { $project: format },&NewLine;];&NewLine;</code></pre>
<p>This aggregation operation has a similar logic to the one in appV6R1, with the only differences being the implementation in the $addFields stage.</p>
<p><code tabindex="0">{ $addFields: buildTotalsField }</code></p>
<ul>
<li>
<p>It follows a similar logic to the previous revision, where we first convert the items document into an array using $objectToArray, and then use the reduce function to iterate over the array, accumulating the status.</p>
</li>
<li>
<p>The difference lies in the initial value and the logic of the reduce function.</p>
</li>
<li>
<p>The initial value in this case is an object/document with one field for each of the report date ranges. These fields for each report date range are also an object/document, with their fields being the possible status set to zero, as this is the initial value.</p>
</li>
<li>
<p>The logic in this case checks the date range of the item and increments the totals accordingly. If the item isInOneYearDateRange(...), it is also in all the other date ranges: three, five, seven, and 10 years. If the item isInThreeYearsDateRange(...), it is also in all the other wide date ranges, five, seven, and 10 years.</p>
</li>
<li>
<p>The following JavaScript code is logic equivalent to the real aggregation pipeline code. Senior developers could make the argument that this implementation could be less verbose or more optimized. However, due to how MongoDB aggregation pipeline operators are specified, this is how it was implemented.</p>
</li>
</ul>
<pre><code tabindex="0">const itemsArray = Object.entries(items); // Convert the object to an array of [key, value]&NewLine;&NewLine;const totals = itemsArray.reduce(&NewLine;  (totals, [YYYYMMDD, status]) =&gt; {&NewLine;  const [YYYY] = YYYYMMDD.slice(0, 4).toString(); // Get year&NewLine;  const [MM] = YYYYMMDD.slice(4, 6).toString(); // Get month&NewLine;  const [DD] = YYYYMMDD.slice(6, 8).toString(); // Get day&NewLine;    let statusDate = new Date(`${YYYY}-${MM}-${DD}`);&NewLine;&NewLine;    if isInOneYearDateRange(statusDate) {&NewLine;      totals.oneYear = incrementTotals(totals.oneYear, status);&NewLine;      totals.threeYears = incrementTotals(totals.threeYears, status);&NewLine;      totals.fiveYears = incrementTotals(totals.fiveYears, status);&NewLine;      totals.sevenYears = incrementTotals(totals.sevenYears, status);&NewLine;      totals.tenYears = incrementTotals(totals.tenYears, status);&NewLine;    } else if isInThreeYearsDateRange(statusDate) {&NewLine;      totals.threeYears = incrementTotals(totals.threeYears, status);&NewLine;      totals.fiveYears = incrementTotals(totals.fiveYears, status);&NewLine;      totals.sevenYears = incrementTotals(totals.sevenYears, status);&NewLine;      totals.tenYears = incrementTotals(totals.tenYears, status);&NewLine;    } else if isInFiveYearsDateRange(statusDate) {&NewLine;      totals.fiveYears = incrementTotals(totals.fiveYears, status);&NewLine;      totals.sevenYears = incrementTotals(totals.sevenYears, status);&NewLine;      totals.tenYears = incrementTotals(totals.tenYears, status);&NewLine;    } else if isInSevenYearsDateRange(statusDate) {&NewLine;      totals.sevenYears = incrementTotals(totals.sevenYears, status);&NewLine;      totals.tenYears = incrementTotals(totals.tenYears, status);&NewLine;    } else if isInTenYearsDateRange(statusDate) {&NewLine;      totals.tenYears = incrementTotals(totals.tenYears, status);&NewLine;    }&NewLine;&NewLine;    return totals;&NewLine;  },&NewLine;  {&NewLine;    oneYear: { a: 0, n: 0, p: 0, r: 0 },&NewLine;    threeYears: { a: 0, n: 0, p: 0, r: 0 },&NewLine;    fiveYears: { a: 0, n: 0, p: 0, r: 0 },&NewLine;    sevenYears: { a: 0, n: 0, p: 0, r: 0 },&NewLine;    tenYears: { a: 0, n: 0, p: 0, r: 0 },&NewLine;  },&NewLine;);&NewLine;</code></pre>
<h3>Indexes</h3>
<p>No additional indexes are required, maintaining the single _id index approach established in the appV4 implementation.</p>
<h3>Initial scenario statistics</h3>
<h4>Collection statistics</h4>
<p>To evaluate the performance of appV6R3, we inserted 500 million event documents into the collection using the schema and Bulk Upsert function described earlier. For comparison, the tables below also include statistics from previous comparable application versions:</p>
<html>
<head>
     <style>
    table,
    th,
    td {
        border: 1px solid black;
        border-collapse: collapse;
    }
    th,
    td {
        padding: 5px;
    }
    </style>
</head>
<body>
    <table style="width:100%">
        <tr>
            <th>Collection</th>
            <th>Documents</th>
					<th>Data Size</th>
					<th>Document Size</th>
					<th>Storage Size</th>
					<th>Indexes</th>
					<th>Index Size</th>
        </tr>
        <tr>
					<td>appV6R1</td>
					<td>33,429,366</td>
					<td>8.19GB</td>
					<td>264B</td>
					<td>2.34GB</td>
					<td>1</td>
					<td>1.22GB</td>
        </tr>
			 <tr>
					<td>appV6R2</td>
					<td>33,429,207</td>
					<td>9.11GB</td>
					<td>293B</td>
					<td>2.8GB</td>
					<td>1</td>
					<td>1.26GB</td>
        </tr>
			<tr>
					<td>appV6R3</td>
					<td>33,429,694</td>
					<td>9.53GB</td>
					<td>307B</td>
					<td>2.56GB</td>
					<td>1</td>
					<td>1.19GB</td>
        </tr>
    </table>
</body>
</html>
<h4>Event statistics</h4>
<p>To evaluate the storage efficiency per event, the Event Statistics are calculated by dividing the total data size and index size by the 500 million events.</p>
<html>
<head>
     <style>
    table,
    th,
    td {
        border: 1px solid black;
        border-collapse: collapse;
    }
    th,
    td {
        padding: 5px;
    }
    </style>
</head>
<body>
    <table style="width:100%">
        <tr>
            <th>Collection</th>
            <th>Data Size/Events</th>
					<th>Index Size/Events</th>
					<th>Total Size/Events</th>
			</tr>
			<tr>
				<td>appV6R1</td>
				<td>17.6B</td>
				<td>2.6B</td>
				<td>20.2B</td>
			</tr>
			<tr>
				<td>appV6R2</td>
				<td>19.6B</td>
				<td>2.7B</td>
				<td>22.3B</td>
			</tr>
			<tr>
				<td>appV6R3</td>
				<td>20.5B</td>
				<td>2.6B</td>
				<td>23.1B</td>
			</tr>
			    </table>
</body>
</html>
<p>Because we are adding the year (YYYY) information in the name of each items document field, we got a 16.3% increase in storage size when compared to appV6R1 and a 4.8% increase in storage size when compared to appV6R2. This increase in storage size may be compensated by the gains in the Get Reports function, as we saw when going from appV6R1 to appV6R2.</p>
<h3>Load test results</h3>
<p>Executing the load test for appV6R3 and plotting it alongside the results for appV6R2, we have the following results for Get Reports and Bulk Upsert.</p>
<h4>Get Reports rate</h4>
<p>We achieved a significant improvement by transitioning from appV6R2 to appV6R3. For the first time, the application successfully reached all the desired rates in a single phase.</p>
<center><caption><b>Figure 13.</b>Graph showing the rates of appV6R2 and appV6R3 when executing the load test for Get Reports functionality. appV6R3 has better rates than appV6R2, but without reaching the desired rates.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-10-08 at 1.49.51 PM-1hzjkoxux9.png" alt="Graph showing the rates of appV6R2 and appV6R3 when executing the load test for Get Reports functionality. appV6R3 has better rates than appV6R2, but without reaching the desired rates." title=" " style="width: 800px"/>
</div>
<figcaption class="fl-center"> </figcaption>
</figure>
<h4>Get Reports latency</h4>
<p>The latency saw significant improvements, with the peak value reduced by 71% in the first phase, 67% in the second phase, 47% in the third phase, and 30% in the fourth phase.</p>
<center><caption><b>Figure 14.</b> Graph showing the latency of appV6R2 and appV6R3 when executing the load test for Get Reports functionality. appV6R3 has lower latency than appV6R2.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-10-08 at 1.51.45 PM-3dsn5d9if4.png" alt="Graph showing the latency of appV6R2 and appV6R3 when executing the load test for Get Reports functionality. appV6R3 has lower latency than appV6R2." title=" " style="width: 800px"/>
</div>
<figcaption class="fl-center"> </figcaption>
</figure>
<h4>Bulk Upsert rate</h4>
<p>As had happened in the previous version, the application was able to reach all the desired rates.</p>
<center><caption><b>Figure 15.</b> Graph showing the rates of appV6R2 and appV6R3 when executing the load test for Bulk Upsert functionality. appV6R3 has better rates than appV6R2, and reaches the desired rates.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-10-08 at 1.55.47 PM-ey7yp55sw1.png" alt="Graph showing the rates of appV6R2 and appV6R3 when executing the load test for Bulk Upsert functionality. appV6R3 has better rates than appV6R2, and reaches the desired rates. " title=" " style="width: 800px"/>
</div>
<figcaption class="fl-center"> </figcaption>
</figure>
<h4>Bulk Upsert latency</h4>
<p>Here, we have one of the most significant gains in this series: The latency has decreased from seconds to milliseconds. We went from a peak of 1.8 seconds to 250ms in the first phase, from 2.3 seconds to 400ms in the second phase, from 2 seconds to 600ms in the third phase, and from 2.2 seconds to 800ms in the fourth phase.</p>
<center><caption><b>Figure 16.</b> Graph showing the latency of appV6R2 and appV6R3 when executing the load test for Bulk Upsert functionality. appV6R3 has lower latency than appV6R2.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-10-08 at 1.58.48 PM-441rmwiewd.png" alt="Graph showing the latency of appV6R2 and appV6R3 when executing the load test for Bulk Upsert functionality. appV6R3 has lower latency than appV6R2. " title=" " style="width: 800px"/>
</div>
<figcaption class="fl-center"> </figcaption>
</figure>
<h3>Issues and improvements</h3>
<p>The main bottleneck in our MongoDB server is still the disk throughput. As mentioned in the previous Issues and Improvements, this was the application-level improvement. How can we further optimize on our current hardware?</p>
<p>If we take a closer look at the <a href="https://www.mongodb.com/docs/manual/core/wiredtiger/#compression">MongoDB documentation</a>, we'll find out that by default, it uses block compression with the snappy compression library for all collections. Before the data is written to disk, it'll be compressed using the snappy library to reduce its size and speed up the writing process.</p>
<p>Would it be possible to use a different and more effective compression library to reduce the size of the data even further and, as a consequence, reduce the load on the server's disk? Yes, and in the following application revision, we will use the zstd compression library instead of the default snappy compression library.</p>
<h2>Application version 6 revision 4 (appV6R4)</h2>
<p>As discussed in the previous Issues and Improvements section, the performance gains of this version will be provided by changing the algorithm of the <a href="https://www.mongodb.com/docs/manual/reference/configuration-options/#mongodb-setting-storage.wiredTiger.collectionConfig.blockCompressor">collection block compressor</a>. By default, MongoDB uses the <a href="https://www.mongodb.com/docs/manual/reference/glossary/#std-term-snappy">snappy</a>, which we will change to zstd to achieve a better compression performance at the expense of more CPU usage.</p>
<p>All the schemas, functions, and code from this version are exactly the same as the appV6R3.</p>
<p>To create a collection that uses the zstd compression algorithm, the following command can be used.</p>
<pre><code tabindex="0">db.createCollection(&quot;&lt;collection-name&gt;&quot;, {&NewLine;  storageEngine: { wiredTiger: { configString: &quot;block_compressor=zstd&quot; } },&NewLine;});&NewLine;</code></pre>
<h3>Schema</h3>
<p>The application implementation presented above would have the following TypeScript document schema denominated SchemaV6R0:</p>
<pre><code tabindex="0">export type SchemaV6R0 = {&NewLine;  _id: Buffer;&NewLine;  items: Record&lt;&NewLine;    string,&NewLine;    {&NewLine;      a?: number;&NewLine;      n?: number;&NewLine;      p?: number;&NewLine;      r?: number;&NewLine;    }&NewLine;  &gt;;&NewLine;};&NewLine;</code></pre>
<h3>Bulk upsert</h3>
<p>Based on the specifications, the following bulk updateOne operation is used for each event generated by the application:</p>
<pre><code tabindex="0">const YYYYMMDD = getYYYYMMDD(event.date); // Extract the year(YYYY), month(MM), and day(DD) from the `event.date`&NewLine;&NewLine;const operation = {&NewLine;  updateOne: {&NewLine;    filter: { _id: buildId(event.key, event.date) }, // key + year + quarter&NewLine;    update: {&NewLine;      $inc: {&NewLine;        [`items.${YYYYMMDD}.a`]: event.approved,&NewLine;        [`items.${YYYYMMDD}.n`]: event.noFunds,&NewLine;        [`items.${YYYYMMDD}.p`]: event.pending,&NewLine;        [`items.${YYYYMMDD}.r`]: event.rejected,&NewLine;      },&NewLine;    },&NewLine;    upsert: true,&NewLine;  },&NewLine;};&NewLine;</code></pre>
<p>This updateOne is exactly the same logic as the one for appV6R3.</p>
<h3>Get reports</h3>
<p>Based on the information​​ presented in the Introduction, we have the following aggregation pipeline to generate the reports document.</p>
<pre><code tabindex="0">const pipeline = [&NewLine;  { $match: docsFromKeyBetweenDate },&NewLine;  { $addFields: buildTotalsField },&NewLine;  { $group: groupCountTotals },&NewLine;  { $project: format },&NewLine;];&NewLine;</code></pre>
<p>This pipeline is exactly the same logic as the one for appV6R3.</p>
<h3>Indexes</h3>
<p>No additional indexes are required, maintaining the single _id index approach established in the appV4 implementation.</p>
<h3>Initial scenario statistics</h3>
<h4>Collection statistics</h4>
<p>To evaluate the performance of appV6R4, we inserted 500 million event documents into the collection using the schema and Bulk Upsert function described earlier. For comparison, the tables below also include statistics from previous comparable application versions:</p>
<html>
<head>
     <style>
    table,
    th,
    td {
        border: 1px solid black;
        border-collapse: collapse;
    }
    th,
    td {
        padding: 5px;
    }
    </style>
</head>
<body>
    <table style="width:100%">
        <tr>
            <th>Collection</th>
            <th>Documents</th>
					<th>Data Size</th>
					<th>Document Size</th>
					<th>Storage Size</th>
					<th>Indexes</th>
					<th>Index size</th>
        </tr>
        <tr>
					<td>appV6R3</td>
					<td>33,429,694</td>
					<td>9.53GB</td>
					<td>307B</td>
					<td>2.56GB</td>
					<td>1</td>
					<td>1.19GB</td>
        </tr>
			  <tr>
					<td>appV6R4</td>
					<td>33,429,372</td>
					<td>9.53GB</td>
					<td>307B</td>
					<td>1.47GB</td>
					<td>1</td>
					<td>1.34GB</td>
        </tr>
    </table>
</body>
</html>
<h4>Event statistics</h4>
<p>To evaluate the storage efficiency per event, the Event Statistics are calculated by dividing the total data size and index size by the 500 million events.</p>
<html>
<head>
     <style>
    table,
    th,
    td {
        border: 1px solid black;
        border-collapse: collapse;
    }
    th,
    td {
        padding: 5px;
    }
    </style>
</head>
<body>
    <table style="width:100%">
        <tr>
            <th>Collection</th>
            <th>Storage Size/Events</th>
					<th>Index Size/Events</th>
					<th>Total Storage Size/Events</th>
        </tr>
        <tr>
					<td>appV6R3</td>
					<td>5.5B</td>
					<td>2.6B</td>
					<td>8.1B</td>
        </tr>
			  <tr>
					<td>appV6R4</td>
					<td>3.2B</td>
					<td>2.8B</td>
					<td>6.0B</td>
        </tr>
    </table>
</body>
</html>
<p>Since the application implementation of appV6R4 is the same as appV5R3, the values for Data Size, Document Size, and Index Size remain the same. The difference lies in Storage Size, which represents the Data Size after compression. Going from snappy to zstd decreased the Storage Size a jaw-dropping 43%. Looking at the Event Statistics, there was a reduction of 26% of the storage required to register each event, going from 8.1 bytes to 6 bytes. These considerable reductions in size will probably translate to better performance on this version, as our main bottleneck is disk throughput.</p>
<h3>Load test results</h3>
<p>Executing the load test for appV6R4 and plotting it alongside the results for appV6R3, we have the following results for Get Reports and Bulk Upsert.</p>
<h4>Get Reports rate</h4>
<p>Although we didn't achieve all the desired rates, we saw a significant improvement from appV6R3 to appV6R4. This revision allowed us to reach the desired rates in the first, second, and third quarters.</p>
<center><caption><b>Figure 17.</b> Graph showing the rates of appV6R3 and appV6R4 when executing the load test for Get Reports functionality. appV6R4 has better rates than appV6R3, but without reaching the desired rates.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-10-08 at 2.14.11 PM-tg3ngcevab.png" alt="Graph showing the rates of appV6R3 and appV6R4 when executing the load test for Get Reports functionality. appV6R4 has better rates than appV6R3, but without reaching the desired rates." title=" " style="width: 800px"/>
</div>
<figcaption class="fl-center"> </figcaption>
</figure>
<h4>Get Reports latency</h4>
<p>The latency also saw significant improvements, with the peak value reduced by 30% in the first phase, 57% in the second phase, 61% in the third phase, and 57% in the fourth phase.</p>
<center><caption><b>Figure 18.</b> Graph showing the latency of appV6R3 and appV6R4 when executing the load test for Get Reports functionality. appV6R4 has lower latency than appV6R3.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-10-08 at 2.16.10 PM-dg30y19axi.png" alt="Graph showing the latency of appV6R3 and appV6R4 when executing the load test for Get Reports functionality. appV6R4 has lower latency than appV6R3." title=" " style="width: 800px"/>
</div>
<figcaption class="fl-center"> </figcaption>
</figure>
<h4>Bulk Upsert rate</h4>
<p>As had happened in the previous version, the application was able to reach all the desired rates.</p>
<center><caption><b>Figure 19.</b> Graph showing the rates of appV6R3 and appV6R4 when executing the load test for Bulk Upsert functionality. Both versions reach the desired rates.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-10-08 at 2.17.35 PM-h4nltf0qv3.png" alt="Graph showing the rates of appV6R3 and appV6R4 when executing the load test for Bulk Upsert functionality. Both versions reach the desired rates." title=" " style="width: 800px"/>
</div>
<figcaption class="fl-center"> </figcaption>
</figure>
<h4>Bulk Upsert latency</h4>
<p>Here, we also achieved considerable improvements, with the peak value being reduced by 48% in the first phase, 39% in the second phase, 43% in the third phase, and 47% in the fourth phase.</p>
<center><caption><b>Figure 20.</b> Graph showing the latency of appV6R3 and appV6R4 when executing the load test for Bulk Upsert functionality. appV6R4 has lower latency than appV6R3.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-10-08 at 2.19.25 PM-bscvof4mm7.png" alt="Graph showing the latency of appV6R3 and appV6R4 when executing the load test for Bulk Upsert functionality. appV6R4 has lower latency than appV6R3. " title=" " style="width: 800px"/>
</div>
<figcaption class="fl-center"> </figcaption>
</figure>
<h3>Issues and improvements</h3>
<p>Although this is the final version of the series, there is still room for improvement. For those willing to try them by themselves, here are the ones that I was able to think of:</p>
<ul>
<li>
<p>Use the Computed Pattern in the appV6R4.</p>
</li>
<li>
<p>Optimize the aggregation pipeline logic for Get Reports in the appV6R4.</p>
</li>
<li>
<p>Change the <a href="https://www.mongodb.com/docs/manual/reference/configuration-options/#mongodb-setting-storage.wiredTiger.engineConfig.zstdCompressionLevel">zstd compression level</a> from its default value of 6 to a higher value.</p>
</li>
</ul>
<h2>Conclusion</h2>
<p>This final part of &quot;The Cost of Not Knowing MongoDB&quot; series has explored the ultimate evolution of MongoDB application optimization, demonstrating how revolutionary design patterns and infrastructure-level improvements can transcend traditional performance boundaries. The journey through appV6R0 to appV6R4 represents the culmination of sophisticated MongoDB development practices, achieving performance levels that seemed impossible with the baseline appV1 implementation.</p>
<h3>Series transformation summary</h3>
<p><b>From foundation to revolution: </b>The complete series showcases a remarkable transformation across three distinct optimization phases.</p>
<ul>
<li>
<p><b>Part 1</b> (appV1-appV4): Document-level optimizations achieving 51% storage reduction through schema refinement, data type optimization, and strategic indexing.</p>
</li>
<li>
<p><b>Part 2</b> (appV5R0-appV5R4): Advanced pattern implementation with the Bucket and Computed Patterns, delivering 89% index size reduction and first-time achievement of target rates.</p>
</li>
<li>
<p><b>Part 3</b> (appV6R0-appV6R4): Revolutionary Dynamic Schema Pattern with infrastructure optimization, culminating in sub-second latencies and comprehensive target rate achievement.</p>
</li>
</ul>
<p><b>Performance evolution:</b> The progression reveals exponential improvements across all metrics.</p>
<ul>
<li>
<p><b>Get Reports latency:</b> From 6.5 seconds (appV1) to 200-800ms (appV6R4)—a 92% improvement.</p>
</li>
<li>
<p><b>Bulk Upsert latency:</b> From 62 seconds (appV1) to 250-800ms (appV6R4)—a 99% improvement.</p>
</li>
<li>
<p><b>Storage efficiency:</b> From 128.1B per event (appV1) to 6.0B per event (appV6R4)—a 95% reduction.</p>
</li>
<li>
<p><b>Target rate achievement:</b> From consistent failures to sustained success across all operational phases.</p>
</li>
</ul>
<h3>Architectural paradigm shifts</h3>
<p><b>The Dynamic Schema Pattern revolution:</b> appV6R0 through appV6R4 introduced the most sophisticated MongoDB design pattern explored in this series. The Dynamic Schema Pattern fundamentally redefined data organization by</p>
<ul>
<li>
<p><b>Eliminating array overhead:</b> Replacing MongoDB arrays with computed object structures to minimize storage and processing costs.</p>
<ul>
<li><b>Single-pipeline optimization:</b> Consolidating five separate aggregation pipelines into one optimized operation, reducing computational overhead by 80%.</li>
</ul>
</li>
<li>
<p><b>Infrastructure-level optimization:</b> Implementing zstd compression, achieving 43% additional storage reduction over default snappy compression.</p>
</li>
</ul>
<p><b>Query optimization breakthroughs:</b> The implementation of intelligent date range calculation within aggregation pipelines eliminated redundant operations while maintaining data accuracy. This approach demonstrates senior-level MongoDB development by leveraging advanced aggregation framework capabilities to achieve both performance and maintainability.</p>
<h3>Critical technical insights</h3>
<p><b>Performance bottleneck evolution:</b> Throughout the series, we observed how optimization focus shifted as bottlenecks were resolved</p>
<ol>
<li>
<p><b>Initial phase:</b> Index size and query inefficiency dominated performance.</p>
</li>
<li>
<p><b>Intermediate phase:</b> Document retrieval count became the limiting factor.</p>
</li>
<li>
<p><b>Advanced phase:</b> Aggregation pipeline complexity constrained throughput.</p>
</li>
<li>
<p><b>Final phase:</b> Disk I/O emerged as the ultimate hardware limitation.</p>
</li>
</ol>
<p><b>Pattern application maturity:</b>
The series demonstrates the progression from junior to senior MongoDB development practices</p>
<ul>
<li>
<p><b>Junior level:</b> Schema design without understanding indexing implications (appV1)</p>
</li>
<li>
<p><b>Intermediate level:</b> Applying individual optimization techniques (appV2-appV4)</p>
</li>
<li>
<p><b>Advanced level:</b> Implementing established MongoDB patterns (appV5RX)</p>
</li>
<li>
<p><b>Senior level:</b> Creating custom patterns and infrastructure optimization (appV6RX)</p>
</li>
</ul>
<h3>Production implementation guidelines</h3>
<p><b>When to apply each pattern:</b> Based on the comprehensive analysis, the following guidelines emerge for production implementations</p>
<ul>
<li>
<p><b>Document-level optimizations:</b> Essential for all MongoDB applications, providing 40-60% improvement with minimal complexity</p>
</li>
<li>
<p><b>Bucket Pattern:</b> Optimal for time-series data with 10:1 or greater read-to-write ratios</p>
</li>
<li>
<p><b>Computed Pattern:</b> Most effective in read-heavy scenarios with predictable aggregation requirements</p>
</li>
<li>
<p><b>Dynamic Schema Pattern:</b> Reserved for high-performance applications where development complexity trade-offs are justified</p>
</li>
</ul>
<p><b>Infrastructure considerations:</b> The zstd compression implementation in appV6R4 demonstrates that infrastructure-level optimizations can provide substantial benefits (40%+ storage reduction) with minimal application changes. However, these optimizations require careful CPU utilization monitoring and may not be suitable for CPU-constrained environments.</p>
<h3>The true cost of not knowing MongoDB</h3>
<p>This series reveals that the &quot;cost&quot; extends far beyond mere performance degradation:</p>
<p><b>Quantifiable impacts:</b></p>
<ul>
<li>
<p><b>Resource utilization:</b> Up to 20x more storage requirements for equivalent functionality</p>
</li>
<li>
<p><b>Infrastructure costs:</b> Potentially 10x higher hardware requirements due to inefficient patterns</p>
</li>
<li>
<p><b>Developer productivity:</b> Months of optimization work that could be avoided with proper initial design</p>
</li>
<li>
<p><b>Scalability limitations:</b> Fundamental architectural constraints that become exponentially expensive to resolve</p>
</li>
</ul>
<p><b>Hidden complexities:</b> More critically, the series demonstrates that MongoDB's apparent simplicity can mask sophisticated optimization requirements. The transition from appV1 to appV6R4 required a deep understanding of</p>
<ul>
<li>
<p>Aggregation framework internals and optimization strategies.</p>
</li>
<li>
<p>Index behavior with different data types and query patterns.</p>
</li>
<li>
<p>Storage engine compression algorithms and trade-offs.</p>
</li>
<li>
<p>Memory management and cache utilization patterns.</p>
</li>
</ul>
<h3>Final recommendations</h3>
<p><b>For development teams:</b></p>
<ol>
<li>
<p><b>Invest in MongoDB education:</b> The performance differences documented in this series justify substantial training investments.</p>
</li>
<li>
<p><b>Establish pattern libraries:</b> Codify successful patterns like those demonstrated to prevent anti-pattern adoption.</p>
</li>
<li>
<p><b>Implement performance testing:</b> Regular load testing reveals optimization opportunities before they become production issues.</p>
</li>
<li>
<p><b>Plan for iteration:</b> Schema evolution is inevitable; design systems that accommodate architectural improvements.</p>
</li>
</ol>
<p><b>For architectural decisions:</b></p>
<ol>
<li>
<p><b>Start with fundamentals:</b> Proper indexing and schema design provide the foundation for all subsequent optimizations.</p>
</li>
<li>
<p><b>Measure before optimizing:</b> Each optimization phase in this series was guided by comprehensive performance measurement.</p>
</li>
<li>
<p><b>Consider total cost of ownership:</b> The development complexity of advanced patterns must be weighed against performance requirements.</p>
</li>
<li>
<p><b>Plan infrastructure scaling:</b> Understanding that hardware limitations will eventually constrain software optimizations.</p>
</li>
</ol>
<h3>Closing reflection</h3>
<p>The journey from appV1 to appV6R4 demonstrates that MongoDB mastery requires understanding not just the database itself, but the intricate relationships between schema design, query patterns, indexing strategies, aggregation frameworks, and infrastructure capabilities. The 99% performance improvements documented in this series are achievable, but they demand dedication to continuous learning and sophisticated engineering practices.</p>
<p>For organizations serious about MongoDB performance, this series provides both a roadmap for optimization and a compelling case for investing in advanced MongoDB expertise. The cost of not knowing MongoDB extends far beyond individual applications—it impacts entire technology strategies and competitive positioning in data-driven markets.</p>
<p>The patterns, techniques, and insights presented throughout this three-part series offer a comprehensive foundation for building high-performance MongoDB applications that can scale efficiently while maintaining operational excellence. Most importantly, they demonstrate that with proper knowledge and application, MongoDB can deliver extraordinary performance that justifies its position as a leading database technology for modern applications.</p>
<div class="callout">
<p><b>Learn more about <a href="https://www.mongodb.com/company/blog/building-with-patterns-a-summary">MongoDB design patterns</a>!</b></p>
</div>	]]></description>
      <pubDate>Thu, 09 Oct 2025 15:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/technical/cost-of-not-knowing-mongodb-part-3-appv6r0-appv6r4</link>
      <guid>https://www.mongodb.com/company/blog/technical/cost-of-not-knowing-mongodb-part-3-appv6r0-appv6r4</guid>
    </item><item>
      <title>Innovating with MongoDB | Customer Successes, October 2025</title>
      <description><![CDATA[<p>It’s officially fall! The start of every new season is a perfect time to consider change and new beginnings. While fall might make you think about pumpkin spice and newly chilly evenings, I’m thinking about the latest round of transformations that MongoDB’s customers are embracing to thrive in an AI-powered world.</p>
<p>In all seriousness, legacy systems and technical debt are huge challenges: the cost of tech debt has been estimated at almost $4 trillion dollars. That’s trillion with a T! Legacy systems can slow down innovation, create bottlenecks, and make it tough to deliver the seamless, real-time experiences customers increasingly expect. But companies are finding that modernizing their applications isn't just about fixing what's broken—modernization enables them to move faster and innovate for end-users.</p>
<p>That’s why I'm incredibly excited to share the recent launch of MongoDB’s <a href="https://www.mongodb.com/solutions/use-cases/modernize">Application Modernization Platform</a> (AMP). This AI-powered program is designed to help enterprises move beyond outdated infrastructures to embrace a flexible, data-driven future. AMP is a comprehensive approach to modernization that combines smart AI tooling with proven methodologies, enabling businesses to transform their applications from the ground up, moving from legacy monoliths to a more flexible, microservices-based architecture.</p>
<p>In this roundup, we're spotlighting customers who understand the strategic importance of modernization. You'll see how Wells Fargo is using MongoDB to power a new credit card platform, how CSX is ensuring business continuity during a critical migration, how Intellect Design is modernizing its wealth management platform, and how Deutsche Telekom is transforming its B2C digital channels. With MongoDB, customers are showing how integral a <a href="https://www.mongodb.com/resources/solutions/use-cases/innovate-and-modernize">modern database</a> is to powering the next generation of applications—and succeeding in the AI era.</p>
<h2>Wells Fargo</h2>
<p><a href="https://www.mongodb.com/solutions/customer-case-studies/wells-fargo?tck=customer_blog_october_25">Wells Fargo</a> sought to modernize its mainframe-dependent credit card platform to provide a faster, more seamless customer experience and handle an exponential increase in transaction data. The company's legacy system was costly to manage and lacked the scalability needed for its &quot;Cards 2.0&quot; initiative.</p>
<p>To solve this, Wells Fargo built an operational data store (ODS) using MongoDB. This new platform allowed them to adopt reusable APIs, streamline integrations, and move from a monolithic architecture to flexible microservices. The ODS now serves 40% of traffic from external vendors, handling more than 7 million transactions with sub-second service.</p>
<p>By leveraging MongoDB, Wells Fargo was able to jumpstart its <a href="https://www.mongodb.com/solutions/use-cases/mainframe-modernization">mainframe modernization</a> and create curated data products to serve real-time, personalized financial services.</p>
<h2>CSX</h2>
<p><a href="https://www.mongodb.com/solutions/customer-case-studies/csx?tck=customer_blog_october_25">CSX</a>, a major U.S. railroad company, sought to modernize its critical operations platform, RTOP, by migrating it to the cloud. The challenge was to maintain the platform's 24/7 availability with minimal disruption to its mission-critical, near real-time operations during the transition.</p>
<p>To solve this, CSX selected <a href="https://www.mongodb.com/products/platform/atlas-cloud-providers/azure">MongoDB Atlas on Azure</a> and partnered with <a href="https://www.mongodb.com/services/consulting">MongoDB Professional Services</a>. Leveraging the <a href="https://www.mongodb.com/products/tools/cluster-to-cluster-sync">Cluster-to-Cluster Sync (mongosync)</a> feature, the team was able to facilitate continuous data synchronization and complete the entire migration in just a few hours.</p>
<p>The move to MongoDB Atlas has equipped CSX with a more scalable and resilient platform. This modernization effort established a blueprint for migrating other critical applications and helped CSX continue its digital transformation journey toward becoming America’s best-run railroad.</p>
<h2>Intellect Design</h2>
<p><a href="https://www.mongodb.com/company/blog/innovation/intellect-design-accelerates-legacy-modernization-by-200-percent-mongodb-gen-ai?tck=customer_blog_october_25">Intellect Design</a>, a global fintech company, sought to modernize its wealth management platform to overcome legacy system bottlenecks and multihour batch processing delays. The company's rigid relational database architecture limited its ability to scale and innovate.</p>
<p>To solve this, the company partnered with MongoDB, using our <a href="https://www.mongodb.com/company/blog/product-release-announcements/amp-ai-driven-approach-modernization">AMP methodology</a> and generative AI tools. This transformation reengineered the platform's core components, resulting in an 85% reduction in onboarding workflow times, allowing clients to access critical portfolio insights faster than ever.</p>
<p>This initiative is the first step in Intellect Design's long-term vision to integrate its entire application suite into a unified, AI-driven service. By leveraging MongoDB Atlas's flexible schema and powerful native tools, the company is now better positioned to deliver smarter analytics and advanced AI capabilities to its customers.</p>
<div class="callout">
<p><b>Watch Intellect AI’s MongoDB.local Bengaluru <a href="https://youtu.be/FESKCQuQZVA?si=-7zndLmpxb__iknV&t=1316" target="_blank">keynote presentation</a> to learn how AMP helped them transform outdated systems into scalable, modern solutions. </b></p>
</div>	
<h2>Deutsche Telekom</h2>
<p><a href="https://www.mongodb.com/solutions/customer-case-studies/dt?tck=customer_blog_october_25">Deutsche Telekom</a>, a leading telecommunications company, sought to modernize its B2C digital channels, which were fragmented by outdated legacy systems. The company needed to create a unified digital experience for its 30 million customers while improving developer productivity.</p>
<p>By leveraging <a href="https://www.mongodb.com/products/platform/atlas-database">MongoDB Atlas</a> as part of its Internal Developer Platform, Deutsche Telekom built a robust data infrastructure to unify customer data and power its new digital services. This approach allowed the company to retire legacy systems and reduce its reliance on physical shops and call centers.</p>
<p>The transition to MongoDB Atlas led to a massive surge in digital engagement, with daily customer interactions rising from under 50,000 to approximately 1.5 million. The company's customer data platform now handles up to 15 times the load of legacy systems, supporting large-scale loyalty programs and transforming the customer experience.</p>
<h2>Video spotlight: Bendigo Bank</h2>
<p>Before you go, watch how Bendigo and Adelaide Bank modernized their core banking technology using MongoDB Atlas and generative AI.</p>
<iframe width="800" height="425" src="https://www.youtube.com/embed/xv9vIftwvXA?si=gfOHY_GX5IIwViDK" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
<center><figcaption class="fl-center">Bendigo and Adelaide Bank reduced the migration time for legacy applications from 80 hours to just five minutes. This innovative approach allowed them to quickly modernize their systems and better serve their 2.5 million customers. </figcaption></center>
<div class="callout">
<p><b>Want to get inspired by your peers and discover all the ways we empower businesses to innovate for the future? Visit <a href="https://www.mongodb.com/solutions/customer-case-studies">MongoDB’s Customer Success Stories hub</a> to see why these customers, and so many more, build modern applications with MongoDB.</b></p>
</div>	]]></description>
      <pubDate>Thu, 02 Oct 2025 18:52:47 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/innovating-customer-successes-october-2025</link>
      <guid>https://www.mongodb.com/company/blog/innovation/innovating-customer-successes-october-2025</guid>
    </item><item>
      <title>The 10 Skills I Was Missing as a MongoDB User</title>
      <description><![CDATA[<p>When I first started using MongoDB, I didn’t have a plan beyond “install it and hope for the best.” I had read about how flexible it was, and it felt like all the developers swore by it, so I figured I’d give it a shot. I spun it up, built my first application, and got a feature working.</p>
<p>But I felt like something was missing.</p>
<p>It felt clunky. My queries were longer than I expected, and performance wasn’t great; I had the sense that I was fighting with the database instead of working with it. After a few projects like that, I began to wonder if maybe MongoDB wasn’t for me.</p>
<p>Looking back now, I can say the problem wasn’t MongoDB, but was somewhere between the keyboard and the chair. It was me. I was carrying over habits from years of working with relational databases, expecting the same rules to apply.</p>
<p>If <a href="https://learn.mongodb.com/skills">MongoDB’s Skill Badges</a> had existed when I started, I think my learning curve would have been a lot shorter. I had to learn many lessons the hard way, but these new badges cover the skills I had to piece together slowly. Instead of pretending I nailed it from day one, here’s the honest version of how I learned MongoDB, what tripped me up along the way, and how these Skill Badges would have helped.</p>
<h2>Learning to model the MongoDB way</h2>
<p>The first thing I got wrong was data modeling. I built my schema like I was still working in SQL– every entity in its own collection, always referencing instead of embedding, and absolutely no data duplication. It felt safe because it was familiar.</p>
<p>Then I hit my first complex query. It required data from various collections, and suddenly, I found myself writing a series of queries and stitching them together in my code. It worked, but it was a messy process.</p>
<p>When I discovered embedding, it felt like I had found a cheat code. I could put related data together in one single document, query it in one shot, and get better performance.</p>
<p>That’s when I made my second mistake. I started embedding everything.</p>
<p>At first, it seemed fine. However, my documents grew huge, updates became slower, and I was duplicating data in ways that created consistency issues. That’s when I learned about patterns like Extended References, and more generally, how to choose between embedding and referencing based on access patterns and update frequency.</p>
<p>Later, I ran into more specialized needs, such as pre-computing data, embedding a subset of a large dataset into a parent, and tackling schema versioning. Back then, I learned those patterns by trial and error. Now, they’re covered in badges like <a href="https://learn.mongodb.com/courses/relational-to-document-model">Relational to Document Model</a>, <a href="https://learn.mongodb.com/courses/schema-design-patterns-and-antipatterns">Schema Design Patterns</a>, and <a href="https://learn.mongodb.com/courses/advanced-schema-patterns-and-antipatterns">Advanced Schema Patterns</a>.</p>
<h2>Fixing what I thought was “just a slow query”</h2>
<p>Even after I got better at modeling, performance issues kept popping up. One collection in particular started slowing down as it grew, and I thought, “I know what to do! I’ll just add some indexes.”</p>
<p>I added them everywhere I thought they might help. Nothing improved.</p>
<p>It turns out indexes only help if they match your query patterns. The order of fields matters, and whether you cover your query shapes will affect performance. Most importantly, just because you can add an index doesn’t mean that you should be adding it in the first place.</p>
<p>The big shift for me was learning to read an <code tabindex="0">explain()</code> plan and see how MongoDB was actually executing my queries. Once I started matching my indexes to my queries, performance went from “ok” to “blazing fast.”</p>
<p>Around the same time, I stopped doing all my data transformation in application code. Before, I’d pull in raw data and loop through it to filter, group, and calculate. It was slow, verbose, and easy to break. Learning the aggregation framework completely changed that. I could handle the filtering and grouping right in the database, which made my code cleaner and the queries faster.</p>
<p>There was a lot of guesswork in how I created my indexes, but the new <a href="https://learn.mongodb.com/courses/fundamentals-of-data-transformation">Indexing Design Fundamentals</a> covers that now. And when it comes to querying and analyzing data, <a href="https://learn.mongodb.com/courses/indexing-design-fundamentals">Fundamentals of Data Transformation</a> is there to help you. Had I had those two skills when I first started, I would’ve saved a lot of time wasted on trial and error.</p>
<h2>Moving from “it works” to “it works reliably”</h2>
<p>Early on, my approach to monitoring was simple: wait for something to break, then figure out why. If a performance went down, I’d poke around in logs. If a server stopped responding, I’d turn it off and on again, and hope for the best.</p>
<p>It was stressful, and it meant I was always reacting instead of preventing problems.</p>
<p>When I learned to use MongoDB’s monitoring tools properly, that changed. I could track latency, replication lag, and memory usage. I set alerts for unusual query patterns. I started seeing small problems before they turned into outages.</p>
<p>Performance troubleshooting became more methodical as well. Instead of guessing, I measured. Breaking down queries, checking index use, and looking at server metrics side by side. The fixes were faster and more precise.</p>
<p>Reliability was the last piece I got serious about. I used to think a working cluster was a reliable cluster. But reliability also means knowing what happens if a node fails, how quickly failover kicks in, and whether your recovery plan actually works in practice.</p>
<p>Those things you can now learn in the <a href="https://learn.mongodb.com/courses/monitoring-tooling">Monitoring Tooling</a>, <a href="https://learn.mongodb.com/courses/performance-tools-and-techniques">Performance Tools</a> and Techniques, and <a href="https://learn.mongodb.com/courses/cluster-reliability">Cluster Reliability</a> skill badges. If you are looking at deploying and maintaining MongoDB clusters, these skills will teach you what you need to know to make your deployment more resilient.</p>
<h2>Getting curious about what’s next</h2>
<p>Once my clusters were stable, I stopped firefighting, and my mindset changed. When you trust your data model, your indexes, your aggregations, and your operations, you get to relax. You can then spend that time on what’s coming next instead of fixing what’s already in production.</p>
<p>For me, that means exploring features I wouldn’t have touched earlier, like <a href="https://learn.mongodb.com/courses/search-fundamentals">Atlas Search</a>, gen AI, and <a href="https://learn.mongodb.com/courses/vector-search-fundamentals">Vector Search</a>. Now that the fundamentals are solid, I can experiment without risking stability and bring in new capabilities when a project actually calls for them.</p>
<h2>What I’d tell my past self</h2>
<p>If I could go back to when I first installed MongoDB, I’d keep it simple:</p>
<ul>
<li>
<p>Focus on data modeling first. A good foundation will save you from most of the problems I ran into.</p>
</li>
<li>
<p>Once you have that, learn indexing and aggregation pipelines. They will make your life much easier when querying.</p>
</li>
<li>
<p>Start monitoring from day one. It will save you a lot of trouble in the long run.</p>
</li>
<li>
<p>Take a moment to educate yourself. You can only learn so much from trial and error. MongoDB offers a myriad of resources and ways to upskill yourself.</p>
</li>
</ul>
<p>Once you have established that base, you can explore more advanced topics and uncover the full potential of MongoDB. Features like Vector Search, full-text search with Atlas Search, or advanced schema design patterns are much easier to adopt when you trust your data model and have confidence in your operational setup.</p>
<div class="callout">
<p><b>MongoDB Skill Badges cover all of these areas and more. They are short, practical, and focused on solving real problems you will face as a developer or DBA, and most of them can be taken over your lunch break. You can browse the full catalog at <a href="http://learn.mongodb.com/skills">learn.mongodb.com/skills</a> and pick the one that matches the challenge you are facing today. Keep going from there, and you might be surprised how much more you can get out of the database once you have the right skills in place.</b></p>
</div>	]]></description>
      <pubDate>Thu, 02 Oct 2025 15:31:41 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/technical/10-skills-was-missing-as-mongodb-user</link>
      <guid>https://www.mongodb.com/company/blog/technical/10-skills-was-missing-as-mongodb-user</guid>
    </item><item>
      <title>Smarter AI Search, Powered by MongoDB Atlas and Pureinsights</title>
      <description><![CDATA[<p>We’re excited to announce that the integration of <a href="https://www.mongodb.com/products/platform/atlas-database">MongoDB Atlas</a> with the <a href="https://cloud.mongodb.com/ecosystem/pureinsights">Pureinsights</a> Discovery Platform is now generally available—bringing to life a reimagined search experience powered by keyword, vector, and gen AI.</p>
<p>What if your search box didn’t just find results, but instead understood intent? That’s exactly what this integration delivers!</p>
<h2>Beyond search: From matching to meaning</h2>
<p>Developers rely on MongoDB’s expansive knowledge ecosystem to find answers fast. But even with a rich library of technical blogs, forum threads, and documentation, traditional keyword search often falls short—especially when queries are nuanced, multilingual, or context-driven.</p>
<p>That’s where the MongoDB-Pureinsights solution shines.
Built on MongoDB Atlas and orchestrated by the Pureinsights Discovery platform, this intelligent search experience starts with the fundamentals: fast, accurate keyword results, powered by <a href="https://www.mongodb.com/products/platform/atlas-search">MongoDB Atlas Search</a>.</p>
<p>But as queries grow more ambiguous—say, “tutorials for AI”—the platform steps up. <a href="https://www.mongodb.com/products/platform/atlas-vector-search">MongoDB Atlas Vector Search</a> with <a href="https://www.mongodb.com/products/platform/ai-search-and-retrieval">Voyage AI</a>, available as an embedding and reranking option (now part of MongoDB), goes beyond literal keywords to interpret intent—helping applications deliver smarter, more relevant results. The outcome: smarter, semantically aware responses that feel intuitive and accurate—because they are.</p>
<p>What’s more, with generative answers enabled, the platform synthesizes information across MongoDB’s ecosystem (blog content, forums, and technical docs) to deliver clear, contextual answers using state-of-the-art language models. But it's not just pointing you to the right page. Instead, the platform is providing the right answer, with citations, ready to use. It’s like embedding a domain-trained AI assistant directly into your search bar.</p>
<p>“As organizations look to move beyond traditional keyword search, they need solutions that combine speed, relevance, and contextual understanding,” said Haim Ribbi, Vice President, Global CSI, VAR &amp; Tech Partner at MongoDB. “MongoDB Atlas provides the foundation for smarter discovery, and this collaboration with Pureinsights shows how easily teams can deliver gen AI-powered search experiences using their existing content.”</p>
<h2>Built for users everywhere</h2>
<p>But intelligence alone doesn’t make it transformational. What sets this experience apart is its adaptability. Whether you’re a developer troubleshooting in Berlin or a product owner building in São Paulo, the platform tailors responses to your preferences.</p>
<p>Prefer concise summaries or deep technical dives? Want to translate answers in real time? Need responses that reflect your role and context? You’re in control. From tone and length to language and specificity, this is a search that truly understands you—literally and figuratively.</p>
<h2>Built on MongoDB. Elevated by Voyage AI. Delivered by Pureinsights.</h2>
<p>At the core of this solution is MongoDB Atlas, which unifies fast, scalable data access to structured content through Atlas Search and Atlas Vector Search. Looking ahead, by integrating with Voyage AI’s industry-leading embedding models, MongoDB Atlas aims to make semantic search and <a href="https://www.mongodb.com/docs/atlas/atlas-vector-search/rag/">retrieval-augmented generation</a> (RAG) applications even more accurate and reliable. While currently in private preview, this enhancement signals a promising future for developers building intelligent, AI-powered experiences.</p>
<p><a href="https://pureinsights.com/search-application-consulting/mongodb-consulting-and-implementation-services/" target="_blank">Pureinsights</a> handles the orchestration layer. Their Discovery Platform ingests and enriches content, blends keyword, vector, and generative search into a seamless UI, and integrates with large language models like GPT-4. The platform supports multilingual capabilities, easy deployment, and enterprise-grade scalability out of the box. While generative answers are powered by integrated <a href="https://www.mongodb.com/resources/basics/artificial-intelligence/large-language-models">large language models</a> (LLMs) and may vary by deployment, the solution is enterprise-ready, cloud-native, and built to scale.</p>
<h2>Bringing intelligent discovery to your own data</h2>
<p><a href="https://www.youtube.com/watch?v=GJD9iQaL0JE&utm_source=mongodb-blog&utm_medium=referral&utm_campaign=genai-discovery-demo" target="_blank">Watch the demo video</a> to see AI-powered search in action across 4,000+ pages of MongoDB content—from community forums and blog posts to technical documentation.</p>
<p>While the demo features MongoDB’s content, the solution is built to adapt. You can bring the same AI-powered experience to your internal knowledge base, customer support portal, or developer hub—no need to build from scratch.</p>
<div class="callout">
<p><b>Visit our <a href="https://cloud.mongodb.com/ecosystem/pureinsights">partner page</a> to learn more about MongoDB and Pureinsights and how we’re helping enterprises build smarter, AI-powered search experiences. <a href="https://pureinsights.com/demo-request/?utm_source=mongodb-blog&utm_medium=referral&utm_campaign=genai-discovery-demo" target="_blank">Apply for a free gen AI demo</a> using your enterprise content.</b></p>
</div>	]]></description>
      <pubDate>Wed, 01 Oct 2025 14:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/smarter-ai-search-powered-by-atlas-pureinsights</link>
      <guid>https://www.mongodb.com/company/blog/innovation/smarter-ai-search-powered-by-atlas-pureinsights</guid>
    </item><item>
      <title>Top Considerations When Choosing a Hybrid Search Solution</title>
      <description><![CDATA[<p>Search has evolved. Today, natural language queries have largely replaced simple keyword searches when addressing our information needs. Instead of typing “Peru travel guide” into a search engine, we now ask a <a href="https://www.mongodb.com/resources/basics/artificial-intelligence/large-language-models">large language model</a> (LLM) “Where should I visit in Peru in December during a 10-day trip? Create a travel guide.”</p>
<p>Is keyword search no longer useful? While the rise of LLMs and vector search may suggest that traditional keyword search is becoming less prevalent, the future of search actually relies on effectively combining both methods. This is where <a href="https://www.mongodb.com/company/blog/product-release-announcements/boost-search-relevance-mongodb-atlas-native-hybrid-search">hybrid search</a> plays a crucial role, blending the precision of traditional text search with the powerful contextual understanding of vector search. Despite advances in vector technology, keyword search still has a lot to contribute and remains essential to meeting current user expectations.</p>
<h2>The rise of hybrid search</h2>
<p>By late 2022 and particularly throughout 2023, as vector search saw a surge in popularity (see image 1 below), it quickly became clear that vector embeddings alone were not enough. Even as embedding models continue to improve at retrieval tasks, full-text search will always remain useful for identifying tokens outside the training corpus of an embedding model. That is why users soon began to combine vector search with lexical search, exploring ways to leverage both precision and context-aware retrieval. This shift was driven in large part by the rise of generative AI use cases like <a href="https://www.mongodb.com/resources/basics/artificial-intelligence/retrieval-augmented-generation">retrieval-augmented generation</a> (RAG), where high-quality retrieval is essential.</p>
<center><caption><b>Figure 1.</b> Number of vector search vendors per year and type. </center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-09-30 at 6.55.58 AM-nkweizza4d.png" alt="Bar graph displaying the number of vector search vendors each year. The number has increased significantly each year since 2019." title=" " style="width: 800px"/>
</div>
<figcaption class="fl-center"> </figcaption>
</figure>
<p>As hybrid search matured beyond basic score combination, the main fusion techniques emerged - reciprocal rank fusion (RRF) and relative score fusion (RSF). They offer ways to combine results that do not rely on directly comparable score scales. RRF focuses on ranking position, rewarding documents that consistently appear near the top across different retrieval methods. RSF, on the other hand, works directly with raw scores from different sources of relevance, using normalization to minimize outliers and align modalities effectively at a more granular level than rank alone can provide. Both approaches quickly gained traction and have become standard techniques in the market.</p>
<h2>How did the market react?</h2>
<p>The industry realized the need to introduce hybrid search capabilities, which brought different challenges for different types of players.</p>
<p>For lexical-first search platforms, the main challenge was to add vector search features and implement the bridging logic with their existing keyword search infrastructure. These vendors understood that the true value of hybrid search emerges when both modalities are independently strong, customizable, and tightly integrated.</p>
<p>On the other hand, vector-first search platforms faced the challenge of adding lexical search. Implementing lexical search through traditional inverted indexes was often too costly due to storage differences, increased query complexity, and architectural overhead. Many adopted sparse vectors, which represent keyword importance in a way similar to traditional term-frequency methods used in lexical search. Sparse vectors were key for vector-first databases in enabling a fast integration of lexical capabilities without overhauling the core architecture.</p>
<p>Hybrid search soon became table stakes and the industry focus shifted toward improving developer efficiency and simplifying integration. This led to a growing trend of vendors building native hybrid search functions directly into their platforms. By offering out-of-the-box support to combine and manage both search types, the delivery of powerful search experiences was accelerated.</p>
<p>As hybrid search became the new baseline, more sophisticated re-ranking approaches emerged. Techniques like cross-encoders, learning-to-rank models, and dynamic scoring profiles began to play a larger role, providing systems with additional alternatives to capture nuanced user intent. These methods complement hybrid search by refining the result order based on deeper semantic understanding.</p>
<h2>What to choose? Lexical-first or vector-first solutions? Top considerations when choosing a hybrid search solution</h2>
<p>When choosing how to implement hybrid search, your existing infrastructure plays a major role in the decision. For users working within a vector-first database, leveraging their lexical capabilities without rethinking the architecture is often enough. However, if the lexical search requirements are advanced, commonly the optimal solution is served with a traditional lexical search solution coupled with vector search, like MongoDB. Traditional lexical  - or lexical-first - search offers greater flexibility and customization for keyword search, and when combined with vectors, provides a more powerful and accurate hybrid search experience.</p>
<center><caption><b>Figure 2.</b> Vector-first vs Lexical-first systems: Hybrid search evaluation.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-09-30 at 7.12.58 AM-xcff4zgcxo.png" alt="Table providing an evaluation of vector-first and lexical-first systems. For the column for control, vector is marked as low and lexical is high. For complexity, vector is low and lexical is medium. For Flexibility, vector is medium and lexical is high. And finally, for keyword capabilities, vector is low and lexical is high." title=" " style="width: 800px"/>
</div>
<figcaption class="fl-center"> </figcaption>
</figure>
<p>Indexing strategy is another factor to consider. When setting up hybrid search, users can either keep keyword and vector data in separate indexes or combine them into one. Separate indexes give more freedom to tweak each search type, scale them differently, and experiment with scoring. The compromise is higher complexity, with two pipelines to manage and the need to normalize scores. On the other hand, a combined index is easier to manage, avoids duplicate pipelines, and can be faster since both searches run in a single pass. However, it limits flexibility to what the search engine supports and ties the scaling of keyword and vector search together. The decision is mainly a trade-off between control and simplicity.</p>
<p>Lexical-first solutions were built around inverted indexes for keyword retrieval, with vector search added later as a separate component. This often results in hybrid setups that use separate indexes. Vector-first platforms were designed for dense vector search from the start, with keyword search added as a supporting feature. These tend to use a single index for both approaches, making them simpler to manage but sometimes offering less mature keyword capabilities.</p>
<p>Lastly, a key aspect to take into account is the implementation style. Solutions with hybrid search functions handle the combination of lexical and vector search natively, removing the need for developers to manually implement it. This reduces development complexity, minimizes potential errors, and ensures that result merging and ranking are optimized by default. Built-in function support streamlines the entire implementation, allowing teams to focus on building features rather than managing infrastructure.</p>
<p>In general, lexical-first systems tend to offer stronger keyword capabilities and more flexibility in tuning each search type, while vector-first systems provide a simpler, more unified hybrid experience. The right choice depends on whether you prioritize control and mature lexical features or streamlined management with lower operational overhead.</p>
<h2>How does MongoDB do it?</h2>
<p>When vector search emerged, MongoDB added vector search indexes to the existing traditional lexical search indexes. With that, MongoDB evolved into a competitive vector database by providing developers with a unified architecture for building modern applications. The result is an enterprise-ready platform that integrates traditional lexical search indexes and vector search indexes into the core database.</p>
<p>MongoDB <a href="https://www.mongodb.com/blog/post/product-release-announcements/boost-search-relevance-mongodb-atlas-native-hybrid-search">recently released native hybrid search functions</a> to <a href="https://www.mongodb.com/products/platform/atlas-database">MongoDB Atlas</a> and as part of a public preview for use with <a href="https://www.mongodb.com/products/self-managed/community-edition">MongoDB Community Edition</a> and <a href="https://www.mongodb.com/try/download/enterprise-advanced">MongoDB Enterprise Server</a> deployments. This feature is part of MongoDB’s integrated ecosystem, where developers get an out-of-the-box hybrid search experience to enhance the accuracy of application search and RAG use cases.</p>
<p>As a result, instead of managing separate systems for different workloads, MongoDB users benefit from a single platform designed to support both operational and AI-driven use cases. As generative AI and modern applications advance, MongoDB gives organizations a flexible, AI-ready foundation that grows with them.</p>
<div class="callout">
<p><b><a href="https://www.mongodb.com/company/blog/product-release-announcements/boost-search-relevance-mongodb-atlas-native-hybrid-search">Read our blog</a> to learn more about MongoDB’s new Hybrid Search function.</b></p>
<p><b>	Visit the <a href="https://www.mongodb.com/resources/use-cases/artificial-intelligence">MongoDB AI Learning Hub</a> to learn more about building AI applications with MongoDB.</b></p>
</div>	]]></description>
      <pubDate>Tue, 30 Sep 2025 15:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/technical/top-considerations-when-choosing-hybrid-search-solution</link>
      <guid>https://www.mongodb.com/company/blog/technical/top-considerations-when-choosing-hybrid-search-solution</guid>
    </item><item>
      <title>Charting a New Course for SaaS Security: Why MongoDB Helped Build the SSCF</title>
      <description><![CDATA[<p>The way companies everywhere work is powered by SaaS. From collaboration tools to critical infrastructure, organizations rely on SaaS applications to drive their business forward. But this widespread adoption has created a significant security blind spot. How can you ensure every one of these applications is configured securely when they all offer different settings, capabilities, and levels of visibility?</p>
<p>This inconsistency creates friction, wastes resources, and ultimately, exposes businesses to unnecessary risk.</p>
<p>At MongoDB, we believe that securing the SaaS ecosystem is a shared responsibility. That's why we were proud to collaborate with the Cloud Security Alliance (CSA) and industry leaders like GuidePoint Security to develop a new standard—the <b>SaaS Security Capability Framework (SSCF)</b>.</p>
<h2>The problem: A gap in cloud security</h2>
<p>For years, the majority of security assessments have focused on the SaaS provider's organizational security, often through frameworks like SOC 2 or ISO 27001. While essential, these frameworks don't always address a critical question: what security capabilities are available to the SaaS customer within the application?</p>
<p>This gap means that security teams face a chaotic landscape. Every new SaaS app brings a different set of configurable controls for logging, identity management, and data access. This makes it nearly impossible to implement and track consistent security policies at scale, leading to a burdensome assessment process for everyone involved.</p>
<h2>The solution: A common framework for SaaS security</h2>
<p>The SSCF was created to solve this problem by establishing a clear, technical set of customer-facing security controls that SaaS vendors should provide. The framework is designed to empower customers by ensuring they have the tools they need to operate applications securely at scale on their side of the Shared Security Responsibility Model (SSRM).</p>
<p>The framework helps with many use cases, but three key audiences stand out:</p>
<ul>
<li>
<p><b>For risk management teams:</b> The SSCF provides a clear baseline to use during vendor assessments, simplifying procurement.</p>
</li>
<li>
<p><b>For SaaS security teams:</b> It offers a checklist for implementing the security features enterprises expect, streamlining the security program.</p>
</li>
<li>
<p><b>For SaaS vendors:</b> The SSCF standardizes assessment responses, reducing the overhead of custom questionnaires and helping vendors meet customer requirements.</p>
</li>
</ul>
<p>The SSCF focuses on six critical domains, aligned with CSA’s Cloud Control Matrix, providing specific and actionable controls for each:</p>
<ol>
<li>
<p><b>Change Control and Configuration Management (CCC):</b> Ensuring you can programmatically query and get documentation on all security configurations.</p>
</li>
<li>
<p><b>Data Security and Privacy Lifecycle Management (DSP):</b> Giving customers control over features like disabling file uploads to prevent malicious code.</p>
</li>
<li>
<p><b>Identity and Access Management (IAM):</b> Providing robust, modern controls for user access, including SSO enforcement, non-human identity (NHI) governance, and a dedicated read-only security auditor role.</p>
</li>
<li>
<p><b>Interoperability and Portability (IPY):</b> Giving administrators control over mass data exports and visibility into application integrations.</p>
</li>
<li>
<p><b>Logging and Monitoring (LOG):</b> Defining a clear set of comprehensive requirements for machine-readable logs with mandatory fields for effective threat detection and forensics.</p>
</li>
<li>
<p><b>Security Incident Management (SEF):</b> Requiring a simple, effective way for vendors to notify a designated customer security contact during an incident.</p>
</li>
</ol>
<h2>MongoDB's commitment to a more secure ecosystem</h2>
<p>Our involvement in creating the SSCF stems from our deep commitment to the security of our customers' data and the broader developer community. We believe that robust security shouldn't be an afterthought; it must be built in and easy to consume. The principles outlined in the SSCF—like strong identity controls and comprehensive logging—are philosophies we already built into our own data platform.</p>
<p>Strong security capabilities allow our customers to build and innovate faster and more securely, knowing they have a reliable foundation. And personally, as a co-chair of the CSA SSCF, I’ve seen great excitement and engagement on the part of our working group—which helped me realize how many companies are affected by this lack of consistency.</p>
<p>The SSCF is a vital step toward creating a more trusted, efficient, and secure global SaaS ecosystem. We are thrilled to have been a part of this foundational work and will continue to champion this standard that empowers developers and security teams alike.</p>
<div class="callout">
<p><b>Visit our <a href="https://www.mongodb.com/products/capabilities/security">security page</a> to learn more about how MongoDB helps protect your data. </b></p>
</div>	]]></description>
      <pubDate>Tue, 30 Sep 2025 13:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/news/charting-new-course-saas-security-why-mongodb-helped-build-sscf</link>
      <guid>https://www.mongodb.com/company/blog/news/charting-new-course-saas-security-why-mongodb-helped-build-sscf</guid>
    </item><item>
      <title>Carrying Complexity, Delivering Agility</title>
      <description><![CDATA[<h2>Resilience, intelligence, and simplicity: The pillars of MongoDB’s engineering vision for innovating at scale</h2>
<p>We’re relatively new to MongoDB—<a href="https://www.mongodb.com/company/blog/from-niche-nosql-enterprise-powerhouse-story-mongodbs-evolution">Ashish joined two years ago via the Granite acquisition</a> after a decade-plus building Google’s databases and distributed systems, and Akshat joined in June 2024 after 15 years building databases at AWS. We have a shared obsession with distributed systems. We’d seen how much developers loved MongoDB, which is part of the reason we joined the company—MongoDB is one of the most loved databases in the world. So one of the first things we sought to understand was why.</p>
<p>It turned out to be simpler than we thought: MongoDB’s vision is to get developers to production fast. This means making it easy to start, and easier to keep going—one command spin-up, sane defaults for day one, and zero downtime upgrades and zero downtime expansion to multiple clouds as you scale. That’s what developer agility looks like in practice: the ability to choose the best tools, move quickly, and to trust the system to carry the weight of failure, complexity, and change.</p>
<p>At MongoDB, three principles drive that vision: resilience, intelligence, and simplicity.</p>
<p>Resilience is the ability to keep going when something breaks, intelligence is the ability to adapt to changing conditions, and simplicity is reducing cognitive and operational load so users and operators can move quickly and safely. These are not just technical goals—we treat them as non-negotiable design constraints. So if a change widens blast radius, breaks adaptive performance, or adds operator toil, it doesn’t ship.</p>
<p>In this post, we share the key engineering themes shaping our work and the mechanisms that keep us honest.</p>
<h2>Security as a first principle</h2>
<p><a href="https://www.mongodb.com/products/capabilities/security">Security</a> isn't a wall you build around your data. It's an assumption you design against from the very beginning. The assumption is simple: in a distributed system, you can’t trust the network, you can’t trust the hardware, and you certainly can't trust your neighbors.</p>
<p>This starts with architectural isolation. In most cloud database service offerings, you're sharing walls with strangers. Shared walls hurt performance, they leak failures, and sometimes they leak secrets. We minimize shared walls, and where utilities must be shared, we build firebreaks. Stronger isolation reduces the blast radius of mistakes and attacks.
With a <a href="https://www.mongodb.com/products/platform/atlas-database">MongoDB Atlas</a> dedicated cluster, you get the whole building. Your cluster runs on its own provisioned servers, in its own private network (VPC). Your unencrypted data is never available in a shared VM or process. There are no &quot;noisy neighbors&quot; because you have no neighbors. The attack surface shrinks dramatically, and resource contention disappears. The blast radius of a problem elsewhere stops at your door. In other words, we follow an anti-Vegas principle—what happens outside your cluster will stay outside.</p>
<p>But true security is layered. Once we’ve isolated the environment, we defend it from the inside out. We start by asking the hard questions:</p>
<ul>
	<font size="4">
		<li>Who are you? That's strong authentication, from SCRAM to AWS IAM.</li>
		<li>What can you do? That's fine-grained RBAC, enforcing the principle of least privilege.</li>
		<li>What if someone gets in? That's encryption everywhere—in transit, at rest, and even in use with <a href="https://www.mongodb.com/docs/mongoid/current/security/encryption/">Client-Side Field Level Encryption</a>.</li>
		<li>How do we lock down the roads? That’s network controls like IP access lists and private endpoints.</li>
		<li>And how do we prove it? That's granular auditing for a clear, immutable trail.</li>
	</font>
</ul>	
<p>Every one of these layers reflects defense in depth.</p>
<center><caption><b>Figure 1.</b> Queryable Encryption.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-09-24 at 11.56.40 AM-ev2zptr309.png" alt="This diagram breaks down how queryable encryption works. The query is sent from the authenticated application to the MongoDB Driver. The driver then assesses the customer provisioned encryption key to ensure permissions are correct. The encrypted query ten connects to the MongoDB Database, which pulls the encrypted data. This data is then pulled back through the MongoDB driver and then decrypted before reaching the user. " title=" " style="width: 800px" border="1"/>
</div>
<figcaption class="fl-center"> </figcaption>
</figure>
<p>The history of database security is full of trade-offs between safety and functionality. For decades, the trade-off has been brutal: to run a query, you had to decrypt your data on the server, exposing it to risk. <a href="https://www.mongodb.com/docs/v7.0/core/queryable-encryption/">Queryable Encryption</a>—an industry-first searchable encryption scheme developed by MongoDB Research—breaks this paradigm. It allows your application to run expressive queries, including equality and range checks on data that remains fully encrypted on the server. The decryption keys never leave your client. The server maintains encrypted indexes for the fields you wish to query on, and queries can be done entirely on the encrypted data, maintaining the strongest privacy and security of your sensitive data.</p>
<p>By carrying these defenses in the platform itself, security stops being another burden developers have to design around. They get the <a href="https://www.mongodb.com/products/platform/trust">privacy guarantees</a>, the audit trails, and the <a href="https://www.mongodb.com/products/platform/trust">compliance</a>, without sacrificing functionality or velocity.</p>
<h2>Achieving resilience: Architecture, operations, and proof</h2>
<p>Systems don’t live in a vacuum. They live in messy realities: network partitions, power outages, kernel panics, cloud control plane hiccups, operator mistakes. The measure of resilience is not “will it fail?” but “what happens next?” Resilience is the ability to keep going when the thing you depend on stops working, not because you planned for it to fail, but because you planned for it to recover.</p>
<p>Here’s how we achieve resilience.</p>
<p><b>Architecture:</b> MongoDB Atlas is built on the assumption that something may fail at any time. Every cluster starts life as a replica set, spread across independent availability zones. That’s the default, not an upgrade. The moment a primary becomes unreachable, an election happens. Within seconds, another node takes over, clients reconnect, and in-flight writes retry automatically. Single-zone diversity buys you protection against a data center outage. Adding more regions buys you protection against a full region failure. Adding more cloud providers buys you insulation against provider-wide events. Each step up that ladder buys you more protection against bigger failures. The trade-off is that each step adds more moving parts to manage, and the failure modes evolve: intra-region links are fast; cross-region introduce wide, lossy links; cross-cloud adds different fabrics, load balancers, and failure semantics.</p>
<center><caption><b>Figure 2.</b> Resilience options: Single zone, multi-AZ, multi-region, multi-cloud.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-09-25 at 7.43.20 AM-mbvfuz44wi.png" alt="Diagram showing an example of how multi-region, multi-cloud support would work." title=" " style="width: 800px" border="1"/>
</div>
<figcaption class="fl-center"> </figcaption>
</figure>
<p>Our job is to make any type of failures (node failures, link failures, gray failures) invisible to you. Writes are only committed when a majority of voting members have the entry in the same term. That rule sounds small, but it’s the safety net that prevents a primary stranded on the wrong side of a partition from accepting writes it can’t keep. Heartbeats and UpdatePosition messages carry progress and truth; if a node learns of a higher term, it steps down immediately. When elections happen, the new primary doesn’t open for writers until it has caught up to the latest known state, preserving as many uncommitted writers as possible. Secondaries apply operations as they arrive, even over lossy links.</p>
<p><b>Operating discipline:</b> Resilience isn’t just in the code and architecture, it’s in how you operate it every day. Even the best design will fail without the discipline to detect problems early and recover quickly. You need to embed it in how you operate. Operational excellence is about preventing avoidable failures, detecting the ones you can’t prevent, and recovering quickly when they happen.</p>
<p>And we’ve turned that into a discipline. Every week, the people closest to the work—engineers, on-calls, product managers, and leaders—step out of the day’s firefight to review the system with rigor. We celebrate the small wins that quietly make the system safer. We dig into failures to understand not just what happened, but how to make sure it doesn’t happen again anywhere. The goal isn’t perfection. Instead, it’s building a system where every lesson learned and every fix made raises the floor for everyone. A single automation can remove a whole category of incidents. A well-written postmortem can stop the same mistake from happening across dozens of systems. The return isn’t linear—it compounds.</p>
<center><caption><b>Figure 3.</b> The ops excellence flywheel.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-09-25 at 7.46.34 AM-81rd3em1y9.png" alt="Circular diagram for the ops excellence. The names around the diagram are prevent, detect, recover, learn, and improve. " title=" " style="width: 800px" border="1"/>
</div>
<figcaption class="fl-center"> </figcaption>
</figure>
<p>When resilience works, failure stops being something every developer has to carry in their head. The system absorbs it, recovers, and lets them keep moving.</p>
<p><b>Proof before shipping:</b> Testing tells you that your code works in the cases you’ve thought to test. Formal verification tells you whether it works in all the cases that matter, even the ones you didn’t think to test. MongoDB is among the few cloud databases that apply and publish formal methods on the core database paths. This rigor translates into agility; teams using the database ship products without worrying about node failures, failovers, or clock skew, causing edge cases. Those edge cases in the database have already been explored, proven, and designed against.</p>
<center><caption><b>Figure 4.</b> Formal methods.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-09-25 at 7.49.18 AM-7hkbxraoa7.png" alt=" " title=" " style="width: 800px" border="1"/>
</div>
<figcaption class="fl-center"> </figcaption>
</figure>
<p>When we design a new replication or failover protocol, we don’t just code it, run a few chaos tests, and ship it. We build a mathematical model of the core logic stripped of distracting details like disk format or thread pools and ask a model checker to try every possible interleaving of events. The tool doesn’t skip the “unlikely” cases. It tries them all.</p>
<p>Take <a href="https://arxiv.org/pdf/2102.11960" target="_blank">logless reconfiguration</a>. The idea is simple: MongoDB decouples configuration changes from the data replication log, so membership changes no longer queue behind user writes. But while the idea is simple, the implementation is not. Without care, concurrent configs can fork the cluster, primaries can be elected on stale terms, or new majorities can lose the old majority’s writes. We modeled the protocol in TLA+, explored millions of interleavings, and distilled the solution down to four invariants: terms block stale primaries, monotonic versions prevent forks, majority votes stop minority splits, and the oplog-commit rule ensures durability carries forward.</p>
<p>For <a href="https://www.vldb.org/pvldb/vol18/p5045-schultz.pdf" target="_blank">transactions</a>, we developed a modular formal specification of the multi-shard protocol in TLA+ to verify protocol correctness and snapshot isolation, defined and tested the WiredTiger storage interface with automated model-based techniques, and analyzed permissiveness to assess how well concurrency is maximized within the isolation level.</p>
<p>These models are not giant, perfect representations of the whole system. They’re small, precise abstractions that focus on the essence of correctness. The payoff is simple: the model checker explores more corner cases in minutes than a human tester could in years.</p>
<p>Alongside formal proofs, we use additional tools to test the implementation under deterministic simulation: fuzzing, fault injection, and message reordering against real binaries. Determinism gives us one-click bug replication, CI/CD regression gates, and reliable incident replays—o rare timing bugs become easy fixes.</p>
<h2>Mastering the multi-cloud reality with simple abstractions</h2>
<p>Developer agility isn’t about having a hundred choices on a menu; it's about removing the friction that makes real choice impossible. One such choice that almost never materializes in practice is multi-cloud. We achieve multi-cloud by building a unified data fabric that lets you put your data anywhere you need it, controlled from a single place. A DIY multi-cloud database where you run self-managed MongoDB across AWS, Microsoft Azure, and Google Cloud seems simple on paper. In practice, it involves weeks of networking (VPC/VNet peering, routing, and firewall rules) and brittle scripts. The theoretical agility that you got by going multi-cloud collapses under the weight of operational reality.</p>
<center><caption><b>Figure 5.</b> Multi-cloud replica sets with MongoDB.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-09-25 at 7.52.08 AM-veo3fac5hp.png" alt="Diagram that is a map of the world with different data centers highlighted, showcasing the idea of multi-cloud replica sets." title=" " style="width: 800px" border="1"/>
</div>
<figcaption class="fl-center"> </figcaption>
</figure>
<p>Now contrast this with MongoDB Atlas, where you don’t have to manually orchestrate provisioning across three different cloud APIs. A single replica set can span AWS, Google Cloud, and Azure. Provisioning, networking, and failover are handled for you. Your app connects with a standard mongodb+srv string, and our intelligent drivers ensure that if your AWS primary fails, traffic automatically fails over to a new primary in GCP or Azure without any changes to your code. This transforms an operational nightmare into a simple deployment choice, giving you freedom from vendor lock-in and a robust defense against provider-wide outages.</p>
<p>Agility also means precise data placement for data sovereignty and global latency. Global Clusters and Zone sharding let you describe simple rules so data stays where policy requires and users are served locally, e.g., A rule to map &quot;DE&quot;, &quot;FR&quot;, and &quot;ES&quot; to the EU_Zone can guarantee that all European customer data and order history physically reside within European borders, satisfying strict GDPR requirements out of the box. Because Zone Sharding is built into the core sharding system, you can add or adjust placement without app rewrites. That’s real agility: the platform removes the hard parts, so the choices are real.</p>
<h2>From data to intelligence: Building the next generation of AI-powered applications</h2>
<p>Building intelligent AI-powered features has been a complex and fragmented process. The traditional approach forced developers to maintain separate vector databases for semantic search, creating brittle ETL pipelines to shuttle data back and forth from their primary operational database. This introduced architectural complexity, latency, and a higher total cost of ownership. That’s not agility. That’s friction.</p>
<p>Our approach is to eliminate this friction entirely. We believe the best place to build AI-powered applications is directly on your operational data. This is the vision behind MongoDB Atlas Vector Search. Instead of creating a separate product, we integrated vector search capabilities directly into the MongoDB query engine. This is a profound simplification for developers. You can now perform semantic search—finding results based on meaning and context, not just keywords—using the same <a href="https://www.mongodb.com/products/tools/mongodb-query-api">MongoDB Query API</a> (MQL) and drivers you already know. There are no new systems to learn and no data to synchronize. You can seamlessly combine vector search with traditional filters, aggregations, and updates in a single, expressive query. This dramatically accelerates the development of modern features like RAG (<a href="https://www.mongodb.com/resources/basics/artificial-intelligence/retrieval-augmented-generation">retrieval-augmented generation</a>) for chatbots, sophisticated recommendation engines, and intelligent search experiences. Intelligence isn’t something you bolt on. It’s something you build on.</p>
<p>This is an area where we continue to make multiple enhancements. For example, with the acquisition of <a href="https://www.mongodb.com/products/platform/ai-search-and-retrieval">Voyage AI</a> earlier this year, we are making progress towards integrating Voyage's embedding and reranking models into Atlas to deliver a <a href="https://www.mongodb.com/company/blog/engineering/rethinking-information-retrieval-mongodb-with-voyage-ai">truly native experience</a>. We are also actively applying AI toward our <a href="https://www.mongodb.com/resources/basics/application-modernization">Application Modernization</a> efforts. Consider a relational database application that involves pages of SQL statements representing a view or a query. How do you translate it so it can work effectively with MongoDB’s MQL? LLMs have advanced enough to provide a base version that may be mostly the correct shape, but to get it accurate and performant requires building additional tooling. We are actively working with several customers, not only on the SQL → MQL translation, but also on modernizing their application code using similar techniques.</p>
<h2>What’s next?</h2>
<p>We’ll keep pushing on the same three levers: resilience, intelligence, and simplicity. Keep watching this space. We’ll publish deep dives similar to our <a href="https://www.mongodb.com/company/blog/technical/rapid-prototyping-safe-logless-reconfiguration-protocol-mongodb-tla-plus">TLA+ write-up on logless reconfiguration</a>, covering formal methods and other behind-the-scenes work on hard engineering problems, such as <a href="https://www.mongodb.com/company/blog/mongodb-8-0-improving-performance-avoiding-regressions">MongoDB 8.0 performance improvement challenges</a>. Our vision is to carry the complexity so developers don’t have to—and to give them the agility &amp; freedom to build the next generation of intelligent applications wherever they want.</p>
<div class="callout">
<p><b>For more on how MongoDB went from a “niche” NoSQL database to a powerhouse with the high availability, tunable consistency, ACID transactions, and robust security that enterprises demand, <a href="https://www.mongodb.com/company/blog/from-niche-nosql-enterprise-powerhouse-story-mongodbs-evolution">check out the MongoDB blog</a>.</b></p>
</div>	]]></description>
      <pubDate>Thu, 25 Sep 2025 16:15:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/engineering/carrying-complexity-delivering-agility</link>
      <guid>https://www.mongodb.com/company/blog/engineering/carrying-complexity-delivering-agility</guid>
    </item><item>
      <title>From Niche NoSQL to Enterprise Powerhouse: The Story of MongoDB&#39;s Evolution</title>
      <description><![CDATA[<p>I joined MongoDB two years ago through the acquisition of Grainite, a database startup I co-founded. My journey here is built on a long career in databases, including many years at Google, where I was most recently responsible for the company’s entire suite of native databases—Bigtable, Spanner, Datastore, and Firestore—powering both Google's own products and Google Cloud customers. My passion has always been large-scale distributed systems, and I find that the database space offers the most exciting and complex challenges to solve.</p>
<p>At MongoDB my focus is on architectural improvements across the product stack. I've been impressed with the progression of MongoDB's capabilities and the team's continuous innovation ethos.</p>
<p>In this blog post, I’ll share some of my understanding of MongoDB’s history and how MongoDB became the de facto standard for document databases. I’ll also highlight select innovations we are actively exploring.</p>
<h2>The dawn of NoSQL</h2>
<p>During the &quot;move fast and break things&quot; era of Web 2.0, the digital landscape was exploding. Developers were building dynamic, data-rich applications at an unprecedented pace, and the rigid, tabular structures of legacy relational databases like Oracle and Microsoft SQL Server quickly became a bottleneck. A new approach was needed, one that prioritized developer productivity, flexibility, and massive scale. At the same time, <a href="https://www.mongodb.com/resources/basics/json-and-bson">JSON's</a> popularity as a flexible, cross-language format for communicating between browsers and backends was surging. This collective shift toward flexibility gave rise to <a href="https://www.mongodb.com/resources/basics/databases/nosql-explained">NoSQL databases</a>, and MongoDB, with its native document-based approach, was at the forefront of the movement.</p>
<p>In the early days, there was a perception that MongoDB was great for use cases like social media feeds or product catalogs, but not for enterprise applications where data integrity is non-negotiable—like financial transactions. This view was never perfectly accurate, and it certainly isn't today. So, what created this perception? It came down to two main factors: categorization and maturity.</p>
<p>First, most early NoSQL databases were built on an “eventually consistent” model, prioritizing Availability and Partition Tolerance (AP) under the <a href="https://en.wikipedia.org/wiki/CAP_theorem" target="_blank">CAP theorem</a>. MongoDB was an exception, designed to prioritize Consistency and Partition Tolerance (CP). But, in a market dominated by AP systems, MongoDB was often lumped in with the rest, leading to the imprecise label of having “light consistency.” Second, all new databases take time to mature for mission-critical workloads. Any established system-of-record database today has gone through many versions over many years to earn that trust. After more than 15 years of focused engineering, today MongoDB has the required codebase maturity, features, and proven track record for the most demanding enterprise applications.</p>
<p>The results speak for themselves. As our CEO Dev Ittycheria mentioned during the <a href="https://investors.mongodb.com/financial-information/quarterly-results">Q2 2026 earnings</a> call, over 70% of the Fortune 100—as well as 7 of the 10 largest banks, 14 of the 15 largest healthcare companies, and 9 of the 10 largest manufacturers globally—are MongoDB customers. This widespread adoption by the world's most sophisticated organizations is a testament to a multi-year, deliberate engineering journey that has systematically addressed the core requirements of enterprise-grade systems.</p>
<h2>MongoDB’s engineering journey: Building a foundation of trust</h2>
<p>MongoDB’s evolution from being perceived as a niche database to an enterprise powerhouse wasn't an accident; it was the result of a relentless focus on addressing the core requirements of enterprise-grade systems. Improvements instrumental to this transformation include:</p>
<ul>
	<font size="4">
		<li><b><a href="https://www.mongodb.com/resources/basics/high-availability">High availability</a> with replica sets:</b> The first step was eliminating single points of failure. Replica sets were introduced as self-healing clusters that provide automatic failover, ensuring constant uptime and data redundancy. Later, the introduction of a Raft-style consensus protocol provided even more reliable and faster failover and leader elections, especially in the event of a network partition. This architecture is the foundation for MongoDB’s current multi-region or run-anywhere deployments, and even allows a single replica set to span multiple cloud providers for maximum resilience.</li>
	</font>
</ul>	
<center><caption><b>Figure 1.</b> Horizontal scaling.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-09-24 at 11.52.47 AM-hvu9nl4a7c.png" alt="Diagram showing horizontal scaling. This starts at the top with the application, which connects to the mongos/router. From here, data is then sharded to the config shard, shard b, and shard c. " title=" " style="width: 800px" border="1"/>
</div>
<figcaption class="fl-center"> </figcaption>
</figure>
<ul>
	<font size="4">
		<li><b>Massive scalability with horizontal sharding:</b> Introduced at the same time as replica sets, <a href="https://www.mongodb.com/resources/products/capabilities/sharding">sharding</a> is a native, foundational part of MongoDB. MongoDB built sharding to allow data to be partitioned across multiple servers, enabling virtually limitless horizontal scaling to support massive datasets and high-throughput operations. Advanced features like zone sharding further empower global applications by pinning data to specific geographic locations to reduce latency and comply with data residency laws like GDPR.</li>
		<li><b>Tunable consistency:</b> Recognizing that not all data is created equal, MongoDB empowered developers with tunable read and write concerns. Within a single application, some data—like a 'page view count'—might not have the same consistency requirements as a 'order checkout value'. Instead of using separate, specialized databases for each use case, developers can use MongoDB for both. This moved the platform beyond a one-size-fits-all model, allowing teams to choose the precise level of consistency their application required per operation—from "fire and forget" for speed to fully acknowledged writes across a majority of replicas for guaranteed durability. This flexibility provides the best price/performance tradeoffs for modern applications.</li>
		<li><b>The game-changer, multi-document <a href="https://www.mongodb.com/resources/basics/databases/acid-transactions">ACID transactions</a>:</b> From its inception, MongoDB has always provided atomic operations for single documents. The game-changing moment was the introduction of multi-document ACID transactions in 2018 with MongoDB 4.0, which was arguably the single most important development in its history. This feature, later extended to include sharded clusters, meant that complex operations involving multiple documents—like a financial transfer between two accounts—could be executed with the same atomicity, consistency, isolation, and durability (ACID) guarantees as a traditional relational database. This milestone shattered the biggest barrier to adoption for transactional applications. And the <a href="https://www.mongodb.com/docs/manual/release-notes/8.2/">recently released MongoDB 8.2</a> is the most feature-rich and performant version of MongoDB yet. </li>
	</font>
</ul>
<ul>
	<font size="4">
		<li>Strict security and compliance: To meet the stringent security demands of the enterprise, MongoDB layered in a suite of advanced security controls. Features like Role-Based Access Control (RBAC), detailed auditing, and Field-Level Encryption were just the beginning. The release of Queryable Encryption (<a href="https://www.mongodb.com/company/blog/product-release-announcements/queryable-encryption-expands-search-power">to which we recently introduced support for prefix, suffix, and substring queries</a>) marked a revolutionary breakthrough, allowing non-deterministic encrypted data to be queried without ever decrypting it on the server, ensuring data remains confidential even from the database administrator. To provide independent validation, MongoDB Atlas has achieved a number of internationally recognized security certifications and attestations, including <b>ISO/IEC 27001</b>, <b>SOC 2 Type II</b>, <b>PCI DSS</b>, and <b>HIPAA</b> compliance, demonstrating a commitment to meeting the rigorous standards of the world's most regulated industries.</li>
	</font>
</ul>
<center><caption><b>Figure 2.</b> Queryable Encryption.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-09-24 at 11.56.40 AM-ev2zptr309.png" alt="This diagram breaks down how queryable encryption works. The query is sent from the authenticated application to the MongoDB Driver. The driver then assesses the customer provisioned encryption key to ensure permissions are correct. The encrypted query ten connects to the MongoDB Database, which pulls the encrypted data. This data is then pulled back through the MongoDB driver and then decrypted before reaching the user. " title=" " style="width: 800px" border="1"/>
</div>
<figcaption class="fl-center"> </figcaption>
</figure>
<p>The ultimate proof of enterprise readiness lies in real-world adoption. Today, MongoDB is trusted by leading organizations across the most demanding sectors to run their core business systems.</p>
<p>For example, <a href="https://www.mongodb.com/solutions/customer-case-studies/citizens-bank">Citizens Bank</a>, one of the oldest and largest financial institutions in the United States, moved to modernize its fraud detection capabilities from a slow, batch-oriented legacy system. They built a new, comprehensive fraud management platform on MongoDB Atlas that allows for near real-time monitoring of transactions.</p>
<p>This use case in a highly regulated industry requires high availability, low latency, and strong consistency to analyze transactions in real-time and prevent financial loss—a direct refutation of the old &quot;eventual consistency&quot; criticism.</p>
<p>Another example is that of <a href="https://www.mongodb.com/solutions/customer-case-studies/bosch">Bosch Digital</a>, the software and systems house for the Bosch Group. Bosch Digital uses MongoDB for its IoT platform, Bosch IoT Insights, to manage and analyze massive volumes of data from connected devices—from power tools used in aircraft manufacturing, to sensors in vehicles. IoT data arrives at high speeds, in huge volumes, and in variable structures. This mission-critical use case demonstrates MongoDB's ability to handle the demands of industrial-scale IoT, providing the real-time analytics needed to ensure quality, prevent errors, and drive innovation.</p>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Technical_ACTION_Rocket_Spot-smhepwsxn5.png" alt=" " title=" " style="width: 400px"/>
</div>
</figure>
<p>Then there’s <a href="https://www.mongodb.com/solutions/customer-case-studies/coinbase">Coinbase</a>, which relies on MongoDB to seamlessly handle the volatile and unpredictable cryptocurrency market. Specifically, Coinbase architected a MongoDB Atlas solution that would accelerate scaling for large clusters. The result was that Coinbase end-users gained a more seamless experience. Previously, traffic spikes could impact some parts of the Coinbase app. Now, users don’t even notice changes happening behind the scenes.</p>
<p>These are just a few examples; customers across all verticals, industries, and sizes depend on MongoDB for their most demanding production use cases. A common theme is that real-world data is messy, variable, and doesn't fit neatly into rigid, tabular structures.</p>
<p>The old adage says that if all you have is a hammer, everything looks like a nail. For decades, developers only had the relational &quot;hammer.&quot; With MongoDB, they now have a modern tool that adapts to how developers work and the data they need to manage and process.</p>
<h2>The road ahead: Continuous innovation</h2>
<p>MongoDB is not resting on its laurels. The team is as excited about what the future holds as they were when MongoDB was first launched, and we continue to innovate aggressively to meet—and anticipate—the modern enterprise’s demands. Here are select improvements we are actively exploring.</p>
<p>A critical need we hear from customers is how to support elastic workloads in a price-performant way. To address this, over the past two years we’ve rolled out Search Nodes, which is a unique capability in MongoDB that allows scaling of search and vector workloads independent from the database to improve availability and price performance.</p>
<p>We are now working closely with our most sophisticated customers to explore how to deliver similar capabilities across more of MongoDB. Our vision is to enable customers to </b>scale compute for high-throughput queries without over-provisioning storage</b>, and vice versa. We can do all this while building upon what is already one of the strongest security postures of any cloud database, as we continue to raise the bar for durability, availability, and performance.</p>
<p>Another challenge facing large enterprises is the significant cost and risk associated with modernizing legacy applications. To solve this, we are making a major strategic investment in <b>enterprise application modernization, and recently announced the <a href="https://www.mongodb.com/solutions/use-cases/modernize">MongoDB Application Modernization Platform</a></b>. We have been engaged with several large enterprises in migrating their legacy relational database applications—code, data, and everything in between—over to MongoDB. This is not a traditional, manual migration effort capped by the number of bodies assigned. Instead, we are systematically developing Agentic tooling and AI-based frameworks, techniques, and processes that allow us to smartly migrate legacy applications into modern microservices-based architectures at scale.</p>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Technical_SOFTWARE_AMP_Spot None 2x (1)-qvvvzxf9gi.png" alt=" " title=" " style="width: 400px"/>
</div>
<figcaption class="fl-center"> </figcaption>
</figure>
<p>One of the more exciting findings from a recent effort, working with a large enterprise in the insurance sector, was that optimized queries on MongoDB ran just as fast, and often significantly faster, than on their legacy relational database, even when schemas were translated 1:1 between relational tables and MongoDB collections, and lots of nested queries and joins were involved. Batch jobs implemented as complex stored procedures that took several hours to execute on the relational database could be completed in under five minutes, thanks to the parallelism MongoDB natively enables (for more, see the <a href="https://www.mongodb.com/company/blog/technical/modernizing-core-insurance-systems-breaking-batch-bottleneck">MongoDB Developer Blog</a>).</p>
<p>Based on the incredible performance gains seen in these modernization projects, we're addressing another common need: ensuring fast queries even when data models aren't perfectly optimized. We are actively exploring improvements to our <b>Query Optimizer</b> that will improve lookup and join performance. While the document model will always be the most performant way to model your data, we are ensuring that even when you don't create the ideal denormalized data model, MongoDB will deliver performance that is at par or better than the alternatives.</p>
<p>Finally, developers today are often burdened with stitching together multiple services to build modern, AI-powered applications. To simplify this, the platform is expanding far beyond a traditional database, focused on providing a <b>unified developer experience</b>. This includes a richer ecosystem with integrated capabilities like <a href="https://www.mongodb.com/products/platform/atlas-search">Atlas Search</a> for full-text search, <a href="https://www.mongodb.com/products/platform/atlas-vector-search">Atlas Vector Search</a> for AI-powered semantic search, and native <a href="https://www.mongodb.com/products/platform/atlas-stream-processing">Stream Processing</a> to handle real-time data. We are already working on our first integrations, and continue to explore how embedding generation as a service within MongoDB Atlas, powered by our own Voyage AI models, can further simplify application development.</p>
<h2>From niche to necessity</h2>
<p>MongoDB began its journey as a (seemingly) niche NoSQL database with perceptions and tradeoffs that made it unsuitable for many core business applications. But, through a sustained and deliberate engineering effort, it has delivered the high availability, tunable consistency, ACID transactions, and robust security that enterprises demand. The perceptions of the past no longer match the reality of the present. When 7 of the 10 largest banks are already using MongoDB, isn’t it time to re-evaluate MongoDB for your most critical applications?</p>
<div class="callout">
<p><b>For more on why innovation requires a modern, AI-ready database—and why companies like Nationwide, Wells Fargo, and The Knot Worldwide chose MongoDB over relational databases—<a href="https://www.mongodb.com/resources/solutions/use-cases/innovate-and-modernize">see the MongoDB customer use case site</b>.	</b></p>
</div>	]]></description>
      <pubDate>Thu, 25 Sep 2025 16:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/from-niche-nosql-enterprise-powerhouse-story-mongodbs-evolution</link>
      <guid>https://www.mongodb.com/company/blog/from-niche-nosql-enterprise-powerhouse-story-mongodbs-evolution</guid>
    </item><item>
      <title>Endian Communication Systems and Information Exchange in Bytes</title>
      <description><![CDATA[<p>Imagine two people trying to exchange phone numbers. One starts from the country code and moves to the last digit, while the other begins at the last digit and works backwards. Both are technically right, but unless they agree on the direction, the number will never connect.</p>
<p>Computers face a similar challenge when they talk to each other. Deep inside processors, memory chips, and network packets, data is broken into bytes. But not every system agrees on which byte should come first. Some start with the “big end” of the number, while others begin with the “little end.”</p>
<p>This simple difference, known as endianness, quietly shapes how data is stored in memory, transmitted across networks, and interpreted by devices. Whether it’s an IoT sensor streaming temperature values, a server processing telecom call records, or a 5G base station handling billions of radio samples, the way bytes are ordered can determine whether the data makes perfect sense—or complete nonsense.</p>
<h2>What is endianness?</h2>
<p>An endian system defines the order in which bytes of a multi-byte number are arranged.</p>
<ul>
	<font size="4">
		<li><b>Big-endian:</b> The most significant byte (MSB) comes first, stored at the lowest address.</li>
		<li><b>Little-endian:</b> The least significant byte (LSB) comes first, stored at the lowest address.</li>
	</font>
</ul>
<p>For example, the number 0x12345678 would be arranged as:</p>
<ul>
	<font size="4">
		<li>Big-endian → 12 34 56 78</li>
		<li>Little-endian → 78 56 34 12</li>
	</font>
</ul>
<p>While this looks simple, the implications are huge. If one system sends data in little-endian while another expects big-endian, the values may be misread entirely. To avoid this, networking standards like IP, TCP, and UDP enforce big-endian (network byte order) as the universal convention.</p>
<h2>Industries where endianness shapes communication</h2>
<p>From the cell tower to the car dashboard, from IoT devices in our homes to high-speed trading systems, endianness is the silent agreement that keeps industries speaking the same digital language.  Endianness may sound like a low-level detail, but it silently drives reliable communication across industries.</p>
<p>In telecommunications and 5G, standards mandate big-endian formats so routers, servers, and base stations interpret control messages and packet headers consistently. IoT devices and embedded systems also depend on fixed byte order—sensors streaming temperature, pressure, or GPS data must follow a convention so cloud platforms decode values accurately. The automotive sector is another example: dozens of ECUs from different suppliers must agree on byte order to ensure that speed sensors, braking systems, and infotainment units share correct data. In finance and high-frequency trading, binary protocols demand strict endian rules—any mismatch could distort price feeds or disrupt trades. And in aerospace and defense, radar DSPs, avionics systems, and satellites require exact endian handling to process mission-critical data streams.</p>
<p>Across all these domains, endian consistency acts as an invisible handshake, ensuring that machines with different architectures can still speak the same digital language.</p>
<h2>Use case architecture: From endian to analytics</h2>
<center><caption><b>Figure 1.</b> Architecture Diagram for the flow of data.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-09-25 at 7.20.50 AM-vdebi0cs39.png" alt="This diagram is titled Endian Communication Analyser. The IOT devices connect to the Endian converter, which connects to Apache Kafka. This then flows into MongoDB Atlas, which produces the analytics." title=" " style="width: 800px"/>
</div>
<figcaption class="fl-center"> </figcaption>
</figure>
<p>The diagram above illustrates how low-level endian data from IoT devices can be transformed into high-value insights using a modern data pipeline.</p>
<ol>
	<font size="4">
		<li><b><a href="https://www.mongodb.com/solutions/use-cases/internet-of-things">IoT devices</a> (data sources):</b> Multiple IoT devices (e.g., sensors measuring temperature, vibration, or pressure) generate raw binary data. To remain efficient and consistent, these devices often transmit data in a specific endian format (commonly big-endian). However, not all receiving systems use the same convention, which can lead to misinterpretation if left unhandled.</li>
		<li><b>Endian converter:</b> The first processing step ensures that byte ordering is normalized. The endian converter translates raw payloads into a consistent format that downstream systems can understand. Without this step, a simple reading like 25.10°C could be misread as 52745°C—a critical error for industries like telecom or automotive.</li>
		<li><b><a href="https://www.mongodb.com/products/integrations/kafka-connector">Apache Kafka</a> (data transport layer):</b> Once normalized, the data flows into Apache Kafka, a distributed streaming platform. Kafka ensures reliability, scalability, and low latency, allowing thousands of IoT devices to stream data simultaneously. It acts as a buffer and transport mechanism, ensuring smooth handoff between ingestion and storage.</li>
		<li><b><a href="https://www.mongodb.com/products/platform/atlas-stream-processing">Atlas Stream Processing</a> (real-time processing):</b> Inside the MongoDB ecosystem, the Atlas Stream Processor consumes Kafka topics and enriches the data. Here, additional transformations, filtering, or business logic can be applied—such as tagging sensor IDs, flagging anomalies, or aggregating multiple streams into one coherent dataset.</li>
		<li><b><a href="https://www.mongodb.com/products/platform/atlas-database">MongoDB Atlas</a> (storage layer):</b> Processed records are stored in MongoDB Atlas, which provides a flexible, document-oriented database model. This is especially valuable for IoT, where payloads may vary in structure depending on the device. MongoDB’s time-series collections ensure efficient handling of timestamped sensor readings at scale.</li>
		<li><b><a href="https://www.mongodb.com/products/platform/atlas-charts">Analytics & visualization</a>:</b> Finally, the clean, structured data becomes available for analytics tools like Tableau. Business users and engineers can visualize patterns, track equipment health, or perform predictive maintenance, turning low-level binary signals into actionable business intelligence.</li>
	</font>
</ul>
<p>Endianness may seem like an obscure technicality buried deep inside processors and protocols, but in reality, it is the foundation of digital trust. Without a shared agreement on how bytes are ordered, the vast networks of IoT devices, telecom systems, cars, satellites, and financial platforms would quickly collapse into chaos.</p>
<p>What makes this powerful is not just the correction of byte order, but what happens after. With pipelines that normalize, stream, and store data—like the one combining Endian conversion, Kafka, MongoDB Atlas, and Tableau—raw binary signals are elevated into business-ready insights. A vibration sensor’s byte sequence becomes an early-warning alert for machine failure; a packet header’s alignment ensures 5G base stations stay synchronized; a GPS reading, once correctly interpreted, guides a connected car safely on its route.</p>
<p>In short, endianness is the invisible handshake between machines. When paired with modern data infrastructure, it transforms silent signals into meaningful stories—bridging the gap between the language of bytes and the language of decisions. To learn more, please <a href="https://www.linkedin.com/feed/update/urn:li:activity:7361497416467968000/?originTrackingId=FHpEG867TkmgInQQeGOCpQ%3D%3D" target="_blank">check out the video</a> of the prototype I have created.</p>
<div class="callout">
<p><b>Boost your MongoDB skills by visiting the <a href="https://www.mongodb.com/resources/product/platform/atlas-learning-hub">MongoDB Atlas Learning Hub</a>.</b></p>
</div>	]]></description>
      <pubDate>Thu, 25 Sep 2025 15:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/technical/endian-communication-systems-information-exchange-in-bytes</link>
      <guid>https://www.mongodb.com/company/blog/technical/endian-communication-systems-information-exchange-in-bytes</guid>
    </item><item>
      <title>MongoDB SQL Interface: Now Available for Enterprise Advanced </title>
      <description><![CDATA[<p>Today, we’re excited to announce the general availability of <a href="https://www.mongodb.com/products/platform/atlas-sql-interface">MongoDB SQL Interface</a> for <a href="https://www.mongodb.com/try/download/enterprise-advanced">MongoDB Enterprise Advanced</a>. This builds upon the foundation established by MongoDB Atlas SQL Interface, which began by extending SQL connectivity to self-managed MongoDB deployments. Teams can now query their MongoDB data directly from familiar BI tools like Tableau and Microsoft’s Power BI using standard ODBC and Java Database Connectivity (JDBC) connections, eliminating the need to learn MongoDB Query Language (MQL), build extract, transform, and load (ETL) pipelines, or move data.</p>
<h2>Bridging the SQL-MongoDB gap</h2>
<p>Organizations new to MongoDB often face a data access challenge: While developers benefit from increased flexibility and performance, teams moving from SQL-based tools often struggle to access the data they need. Without direct SQL connectivity, they must either learn MongoDB’s query language or build and maintain custom ETL pipelines to move data out of MongoDB for reporting and analytics. This creates fragmented operational reporting workflows, with users switching between multiple tools and data sources to piece together the insights they need. These approaches often lead to increased maintenance overhead, outdated data, and dependency bottlenecks.</p>
<p>MongoDB SQL Interface now eliminates this friction by providing direct SQL access to MongoDB data through custom connectors and drivers. This works by generating comprehensive JSON schemas of MongoDB collections and translating standard SQL queries into MongoDB operations in real time. Users can connect from popular BI tools like Tableau and Power BI, or through JDBC and ODBC drivers for other SQL-based tools. They can use familiar SQL syntax, including joins, aggregations, and subqueries through MongoSQL, a SQL-92 compatible dialect designed specifically for MongoDB. This speeds up analysis and enables self-service reporting while maintaining database performance.</p>
<h2>Getting started</h2>
<p>MongoDB SQL Interface is now included with Enterprise Advanced licenses and works with MongoDB 6.0 or higher, requiring no changes to your existing MongoDB server configuration. The setup process involves three main steps:</p>
<ol>
	<font size="4">
		<li><b>Download the MongoDB SQL Schema Builder CLI</b> from the <a href="https://www.mongodb.com/try/download/sql-interface">download center</a>.</li>
		<li><b>Use the command line interface (CLI)</b> to analyze your data structure and generate schemas that map your collections’ document structures to SQL-queryable formats.</li>
		<li><b>Connect your BI tools</b> using MongoDB’s custom connectors for Tableau and Power BI, or JDBC and ODBC drivers for other SQL-based tools.</li>
	</font>
</ol>
<p>The Schema Builder CLI examines your existing collections to understand document patterns, nested objects, and array structures. It then creates JSON Schema definitions that preserve the full richness of your document model while making complex nested structures and arrays queryable through familiar SQL syntax. This schema-first approach ensures optimal query performance and maintains data type accuracy across your SQL operations.</p>
<p>Once the MongoDB Schema Builder CLI generates your schemas, it stores them alongside your data. SQL Interface then automatically uses them to validate queries and provide proper type information for results. This creates a seamless bridge between MongoDB’s flexible document model and SQL’s structured query expectations.</p>
<h2>Moving forward from MongoDB BI Connector</h2>
<p>For organizations currently using <a href="https://www.mongodb.com/try/download/bi-connector">MongoDB BI Connector</a>, MongoDB SQL Interface represents a significant improvement to our SQL connectivity solution. The interface addresses several limitations of the MongoDB BI Connector approach, including improved query performance through native MongoDB operations and enhanced schema flexibility that better represents document structures. While support for BI Connector will continue until September 2026, MongoDB SQL Interface offers improved performance, enhanced schema control, and a more intuitive setup process.</p>
<div class="callout">
<p><b>Ready to get started with MongoDB SQL Interface for Enterprise Advanced?</b></p>
<ul>
	<font size="4">
		<li><b><a href="https://dochub.mongodb.org/core/sql-schema-builder">Documentation</a>:</b> Complete the implementation guide with configuration options and best practices.</li>
		<li><b><a href="https://www.mongodb.com/try/download/sql-interface">Download center</a>:</b> Get the MongoDB SQL Schema Builder CLI and drivers for your deployment.</li>
		<li><b><a href="https://translators-connectors-releases.s3.amazonaws.com/mongodb-schema-manager/docs/MongoDB_Schema_Manager-overview.pdf" target="_blank">README</a>:</b> Use this guide for quick reference for installation and usage.</li>
		<li><b><a href="https://youtu.be/AUnIs0hlIsE?si=gtCN2-GRU_qrz2mu" target="_blank">Demo video</a>:</b> See MongoDB SQL Interface in action with a step-by-step walkthrough.</li>
	</font>
</ul>
</div>]]></description>
      <pubDate>Thu, 25 Sep 2025 12:30:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/product-release-announcements/mongodb-sql-interface-now-available-enterprise-advanced</link>
      <guid>https://www.mongodb.com/company/blog/product-release-announcements/mongodb-sql-interface-now-available-enterprise-advanced</guid>
    </item><item>
      <title>MongoDB is a Glassdoor Best-Led Company of 2025</title>
      <description><![CDATA[<p>2025 has been a big year for MongoDB.</p>
<p>With MongoDB 8.2, our most feature-rich and performant release yet, we are raising the bar for what developers can achieve. <a href="https://www.mongodb.com/products/platform/ai-search-and-retrieval">Voyage AI</a>’s embedding models and rerankers are bringing state-of-the-art accuracy and efficiency to building trustworthy, reliable AI applications. And we’ve launched the <a href="https://www.mongodb.com/company/blog/product-release-announcements/amp-ai-driven-approach-modernization">MongoDB Application Modernization Platform</a>, or AMP.</p>
<p>Today, MongoDB serves nearly 60,000 organizations across every industry and vertical, including more than 70% of the Fortune 100 and cutting-edge AI-native startups.</p>
<p>On top of these exciting updates, we’re now pleased to announce that MongoDB is among the winners of the annual Glassdoor list of <a href="https://www.glassdoor.com/Award/Best-Led-Companies-LST_KQ0,18.htm" target="_blank">Best-Led Companies</a> in 2025. This list highlights the top 50 companies with more than 1,000 employees whose leaders have been recognized as some of the best. For us, this is not just an external badge of honor—it’s a reflection of the trust and inspiration that MongoDB employees experience every day.</p>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-09-23 at 9.37.18 AM-4kkzbnntzt.png" alt="Image for Glassdoor award winner" title=" " style="width: 800px"/>
</div>
<figcaption class="fl-center"> </figcaption>
</figure>
<p>What makes this award so meaningful is that it’s driven entirely by employee feedback. Unlike other workplace awards, there is no self-nomination or application process. To determine the winners, Glassdoor evaluates <a href="https://www.glassdoor.com/Reviews/index.htm" target="_blank">company reviews</a> shared by current and former employees over the past year. That means every comment, rating, and personal experience shapes the final outcome.</p>
<p>At MongoDB, leadership isn’t limited to titles—it’s how we work. Guided by our <a href="https://www.mongodb.com/company/values">values and Leadership Commitment</a>, we push ourselves to think big, act with ownership, and build trust every day. This recognition is proof that our approach is more than words on a page—it’s shaping a culture where people are inspired to grow, innovate, and win together. Our leaders are not only setting strategy and steering the business; they are building an environment where people feel empowered to take risks, to challenge the status quo, and to achieve more than they thought possible.</p>
<h2>Hear more from our employees</h2>
<p>“I joined MongoDB as the Executive Assistant to our CEO, <a href="https://www.linkedin.com/in/dittycheria/" target="_blank">Dev Ittycheria</a>. During my time working with Dev, I saw firsthand the transparent nature of our leadership team. Though they are focused on the market opportunity in front of us and ensuring MongoDB is set up for long-term success, it does not come at the expense of our people. It was a privilege to support the CEO and work closely with his leadership team who lead with our company values and focus on our people in everything they do.” - <i>Ava Thompson, Executive Support</i></p>
<p>“In my time here, I've been fortunate to see and drive change at the individual level, but also see leadership acknowledge and push innovation at the top, underlining the value we place on continuously improving the way we do things at all levels.” - <i>Charles Shim, FP&amp;A</i></p>
<p>“Every quarter, I have honest conversations with leaders about whether I achieved the goals I set and why. My leaders here help me map out a career path, suggest opportunities I hadn’t considered, and provide feedback on how to align my personal goals with my professional growth. Because of that, I feel I’m growing in every way.” - <i>Jin SEO, Customer Success</i></p>
<p>“MongoDB is a hybrid company. Like many of our engineers, I work outside the company headquarters in New York City. I appreciate MongoDB’s approach to hybrid working and that the company leadership cares about the well-being of their employees. It seems there are companies that don’t seem to trust their employees to make decisions, such as which days to come into the office, so I’m thankful for the autonomy I receive at MongoDB to work in a way that’s best for me.” - <i>Andrew Whitaker, Engineering</i></p>
<p>At MongoDB, we continuously strive to deliver great results for our customers, live our values in everything we do, and demonstrate our leadership principles every day. Because we're not just building next-generation technology – we’re building the next generation of leaders, too.</p>
<div class="callout">
<p><b>Visit our <a href="https://www.mongodb.com/company/careers">careers site</a> to learn more about how you can transform your career at MongoDB.</b></p>
</div>	]]></description>
      <pubDate>Wed, 24 Sep 2025 12:29:03 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/culture/mongodb-is-glassdoor-best-led-company-2025</link>
      <guid>https://www.mongodb.com/company/blog/culture/mongodb-is-glassdoor-best-led-company-2025</guid>
    </item><item>
      <title>Build AI Agents Worth Keeping: The Canvas Framework</title>
      <description><![CDATA[<h2>Why 95% of enterprise AI agent projects fail</h2>
<p>Development teams across enterprises are stuck in the same cycle: They start with &quot;Let's try LangChain&quot; before figuring out what agent to build. They explore CrewAI without defining the use case. They implement RAG before identifying what knowledge the agent actually needs. Months later, they have an impressive technical demo showcasing multi-agent orchestration and tool calling—but can't articulate ROI or explain how it solves actual business needs.</p>
<p>According to McKinsey's latest research, while nearly eight in 10 companies report using generative AI, <a href="https://www.mckinsey.com/capabilities/quantumblack/our-insights/seizing-the-agentic-ai-advantage" target="_blank">fewer than 10% of use cases deployed ever make it past the pilot stage</a>. MIT researchers studying this challenge identified a &quot;<a href="https://mlq.ai/media/quarterly_decks/v0.1_State_of_AI_in_Business_2025_Report.pdf" target="_blank">gen AI divide</a>&quot;—a gap between organizations successfully deploying AI and those stuck in perpetual pilots. In their sample of 52 organizations, researchers found patterns suggesting failure rates as high as 95% (pg.3). Whether the true failure rate is 50% or 95%, the pattern is clear: Organizations lack clear starting points, initiatives stall after pilot phases, and most custom enterprise tools fail to reach production.</p>
<h2>6 critical failures killing your AI agent projects</h2>
<p>The gap between agentic AI's promise and its reality is stark. Understanding these failure patterns is the first step toward building systems that actually work.</p>
<h3>1. The technology-first trap</h3>
<p>MIT's research found that while 60% of organizations evaluated enterprise AI tools, <a href="https://mlq.ai/media/quarterly_decks/v0.1_State_of_AI_in_Business_2025_Report.pdf" target="_blank">only 5% reached production</a> (pg.6)—a clear sign that businesses struggle to move from exploration to execution. Teams rush to implement frameworks before defining business problems. While most organizations have moved beyond ad hoc approaches (<a href="https://newsroom.ibm.com/2025-06-10-IBM-Study-Businesses-View-AI-Agents-as-Essential,-Not-Just-Experimental" target="_blank">down from 19% to 6%</a>, according to IBM), they've replaced chaos with structured complexity that still misses the mark.</p>
<p>Meanwhile, one in four companies taking a true &quot;AI-first&quot; approach—starting with business problems rather than technical capabilities—report transformative results. The difference has less to do with technical sophistication and more about strategic clarity.</p>
<h3>2. The capability reality gap</h3>
<p>Carnegie Mellon's TheAgentCompany benchmark exposed the uncomfortable truth: <a href="https://www.cs.cmu.edu/news/2025/agent-company#:~:text=TheAgentCompany%20shows%20that%20existing%20AI%20agents%20routinely%20failed%20at%20common%20office%20tasks%2C%20providing%20solace%20to%20people%20fearing%20for%20their%20jobs%20and%20giving%20researchers%20a%20way%20to%20assess%20the%20performance%20of%20evolving%20AI%20models." target="_blank">Even our best AI agents would make terrible employees</a>. The best AI model (Claude 3.5 Sonnet) <a href="https://www.cs.cmu.edu/news/2025/agent-company#:~:text=The%20best%20of%20them%2C%20Claude%203.5%20Sonnet%20from%20Anthropic%2C%20only%20completed%2024%25%20of%20the%20tasks.%20Google%27s%20Gemini%202.0%20Flash%20came%20in%20second%20with%2011.4%25%2C%20and%20OpenAI%27s%20GPT%2D4o%20was%20third%20with%208.6%25." target="_blank">completes only 24% of office tasks</a>, with <a href="https://www.cs.cmu.edu/news/2025/agent-company#:~:text=When%20TheAgentCompany%20gave%20partial%20credit%20for%20tasks%20that%20were%20partially%20completed%2C%20it%20only%20boosted%20Claude%20to%2034.4%25%20and%20Qwen%20to%204.2%25." target="_blank">34.4% success when given partial credit</a>. Agents struggle with basic obstacles, such as pop-up windows, which humans navigate instinctively.</p>
<p>More concerning, when faced with challenges, <a href="https://www.cs.cmu.edu/news/2025/agent-company#:~:text=For%20instance%2C%20when%20the%20agent%20couldn%27t%20find%20a%20particular%20person%20it%20needed%20to%20contact%20in%20the%20company%27s%20chat%20platform%2C%20it%20instead%20renamed%20another%20user%2C%20giving%20it%20the%20name%20of%20the%20person%20it%20was%20seeking." target="_blank">some agents resort to deception</a>, like renaming existing users instead of admitting they can't find the right person. These issues demonstrate fundamental reasoning gaps that make autonomous deployment dangerous in real business environments, rather than just technical limitations.</p>
<h3>3. Leadership vacuum</h3>
<p>The disconnect is glaring: <a href="https://www.mckinsey.com/capabilities/quantumblack/our-insights/seizing-the-agentic-ai-advantage#:~:text=In%20fact%2C,9" target="_blank">Fewer than 30% of companies</a> report CEO sponsorship of the AI agenda despite <a href="https://newsroom.ibm.com/2025-06-10-IBM-Study-Businesses-View-AI-Agents-as-Essential,-Not-Just-Experimental#:~:text=With%2070%25%20of%20surveyed%20executives%20indicating%20that%20agentic%20AI%20is%20important%20to%20their%20organization%27s%20future%2C%20the%20research%20suggests%20that%20many%20organizations%20are%20actively%20encouraging%20experimentation.%C2%A0" target="_blank">70% of executives saying agentic AI is important to their future</a>. This leadership vacuum creates cascading failures—AI initiatives fragment into departmental experiments, lack authority to drive organizational change, and can't break through silos to access necessary resources.</p>
<p>Contrast this with Moderna, <a href="https://www.wsj.com/articles/at-moderna-openais-gpts-are-changing-almost-everything-6ff4c4a5#:~:text=CEO%20St%C3%A9phane%20Bancel%20called%20the%20OpenAI%20partnership%2C%20and%20its%20use%20of%20AI%20in%20general%2C%20key%20to%20helping%20the%20vaccine%20maker%20transform%20every%20business%20process%3A%20%E2%80%9CHow%20do%20we%20use%20it%20at%20scale%20to%20reinvent%20all%20of%20Moderna%E2%80%99s%20business%20processes%2C%20in%20science%2C%20in%20legal%2C%20in%20manufacturing%E2%80%94everywhere.%E2%80%9D%C2%A0" target="_blank">where CEO buy-in</a> drove the <a href="https://openai.com/index/moderna/#:~:text=Moderna%20had%20750%20GPTs%20across%20the%20company" target="_blank">deployment of 750+ AI agents</a> and radical restructuring of HR and IT departments. As with the early waves of Big Data, data science, then machine learning adoption, leadership buy-in is the deciding factor for the survival of generative AI initiatives.</p>
<h3>4. Security and governance barriers</h3>
<p>Organizations are paralyzed by a governance paradox: 92% believe governance is essential, <a href="https://www.sailpoint.com/press-releases/sailpoint-ai-agent-adoption-report#:~:text=According%20to%20the%20report%2C%2082%25%20of%20organizations%20already%20use%20AI%20agents%2C%20but%20only%2044%25%20of%20organizations%20report%20having%20policies%20in%20place%20to%20secure%20them" target="_blank">but only 44% have policies</a> (SailPoint, 2025). The result is predictable—80% experienced AI acting outside intended boundaries, with top concerns including privileged data access (60%), unintended actions (58%), and sharing privileged data (57%). Without clear ethical guidelines, audit trails, and compliance frameworks, even successful pilots can't move to production.</p>
<h3>5. Infrastructure chaos</h3>
<p>The infrastructure gap creates a domino effect of failures. While <a href="https://www.sailpoint.com/press-releases/sailpoint-ai-agent-adoption-report#:~:text=According%20to%20the%20report%2C%2082%25%20of%20organizations%20already%20use%20AI%20agents%2C%20but%20only%2044%25%20of%20organizations%20report%20having%20policies%20in%20place%20to%20secure%20them." target="_blank">82% of organizations</a> already use AI agents, <a href="https://newsroom.ibm.com/2025-06-10-IBM-Study-Businesses-View-AI-Agents-as-Essential,-Not-Just-Experimental#:~:text=Those%20surveyed%20indicate%20that%20concerns%20around%20data%20(49%25)%2C%20trust%20issues%20(46%25)%20and%20skills%20shortages%20(42%25)%20remain%20barriers%20to%20adoption%20for%20their%20organizations.%C2%A0" target="_blank">49% cite data concerns</a> as primary adoption barriers (IBM). Data remains fragmented across systems, making it impossible to provide agents with complete context.</p>
<p>Teams end up managing multiple databases—one for operational data, another for vector data and workloads, a third for conversation memory—each with different APIs and scaling characteristics. This complexity kills momentum before agents can actually prove value.</p>
<h3>6. The ROI mirage</h3>
<p>The optimism-reality gap is staggering. <a href="https://www.mckinsey.com/capabilities/quantumblack/our-insights/seizing-the-agentic-ai-advantage#:~:text=More%20than%2080%20percent%20of%20companies%20still%20report%20no%20material%20contribution%20to%20earnings%20from%20their%20gen%20AI%20initiatives." target="_blank">Nearly 80% of companies report no material earnings impact</a> from gen AI (McKinsey), while <a href="https://www.pagerduty.com/newsroom/agentic-ai-survey-2025/#:~:text=Executives%20anticipate%20agentic%20AI%20will%20have%20faster%20adoption%20and%20higher%20ROI%20than%20generative%20AI%2C%20with%2062%25%20expecting%20returns%20above%20100%25" target="_blank">62% expect 100%+ ROI from deployment</a> (PagerDuty). Companies measure activity (number of agents deployed) rather than outcomes (business value created). Without clear success metrics defined upfront, even successful implementations look like expensive experiments.</p>
<h2>The AI development paradigm shift: from data-first to product-first</h2>
<p>There's been a fundamental shift in how successful teams approach agentic AI development, and it mirrors what <a href="https://www.swyx.io/about" target="_blank">Shawn Wang (Swyx)</a> observed in his influential &quot;<a href="https://www.latent.space/p/ai-engineer#:~:text=Fire%2C%20ready%2C%20aim,data%20to%20finetune." target="_blank">Rise of the AI Engineer</a>&quot; post about the broader generative AI space.</p>
<h3>The old way: data → model → product</h3>
<p>In the traditional paradigm practiced during the early years of machine learning, teams would spend months architecting datasets, labeling training data, and preparing for model pre-training. Only after training custom models from scratch could they finally incorporate these into product features.</p>
<p>The trade-offs were severe: massive upfront investment, long development cycles, high computational costs, and brittle models with narrow capabilities. This sequential process created high barriers to entry—only organizations with substantial ML expertise and resources could deploy AI features.</p>
<center><caption><b>Figure 1.</b> The Data → Model → Product Lifecycle.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-09-23 at 7.35.29 AM-8vy6t7f31z.png" alt="This diagram has the title traditional flow: pre-foundation model era. On the left center of this diagram is a box for data, which takes 1-6 months and is for architect datasets, clean & label, and prepare training. This box connects to a box for model through a line titled heavy investment. The model box takes 7-9 months and is for train from scratch, high compute costs, and narrow capabilities. This box then connects to a box titled product through a line titled single purpose. The product box takes 10+ months and has the descriptors of finally integrate, limited features, and brittle deployment. At the bottom is a box that lists the challenges of this approach, such as 10+ months to first value & signal, massive upfront investment, brittle, single-purpose models, and long cycles, limited value, high infrastructure requirements." title=" " style="width: 800px"/>
</div>
<figcaption class="fl-center"><center>Traditional AI development required months of data preparation and model training before shipping products.</center> </figcaption>
</figure>
<h3>The new way: product → data → model</h3>
<p>The emergence of foundation models changed everything.</p>
<center><caption><b>Figure 2.</b> The Product → Data → Model Lifecycle.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-09-23 at 7.41.38 AM-uzjhlrru4d.png" alt="The title of this diagram is modern flow: foundation model era. This model begins on the left with product which is associated with week 1 and is for defining user need, building an MVP, and fast iteration. This then leads to data via fast experimentation. Data is associated with week 2 and is for identifying needed knowledge, collecting examples, and structuring for retrieval. Data then connects to model via immediate capability. Model occurs over week 3+ and is for selecting providers, optimizing prompts, and testing performance. The box at the bottom lists the benefits of this approach, which includes days to first value & signal, easy model swapping, data requirements drive model choice, and product hypotheses can be tested with near immediate feedback." title=" " style="width: 800px"/>
</div>
<figcaption class="fl-center"><center>Foundation model APIs flipped the traditional cycle, enabling rapid experimentation before data and model optimization.</center> </figcaption>
</figure>
<p>Powerful LLMs became commoditized through providers like OpenAI and Anthropic. Now, teams could:</p>
<ol>
	<font size="4">
		<li>Start with the product vision and customer need.</li>
		<li>Identify what data would enhance it (examples, knowledge bases, RAG content).</li>
		<li>Select the appropriate model that could process that data effectively.</li>
	</font>
</ol>	
<p>This enabled zero-shot and few-shot capabilities via simple API calls. Teams could build MVPs in days, define their data requirements based on actual use cases, then select and swap models based on performance needs. Developers now ship experiments quickly, gather insights to improve data (for RAG and evaluation), then fine-tune only when necessary. This democratized cutting-edge AI to all developers, not just those with specialized ML backgrounds.</p>
<h3>The agentic evolution: product → agent → data → model</h3>
<p>But for agentic systems, there's an even more important insight: Agent design sits between product and data.</p>
<center><caption><b>Figure 3.</b> The Product → Agent → Data → Model Lifecycle.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-09-23 at 7.59.33 AM-yauwdcos5r.png" alt="This diagram is titled agentic flow: foundation model era. This diagram begins on the left with product where you define the problem. This connects to agent via user-first design, and the agent is for design behavior. Agent then goes to data via determines requirements, and data is for enhancing performance. Data connects to model via match to agent needs, and the model step is for select provider. The new considerations of this are that the agent layer orchestrates everything, tools & workflows before model selection, and data enhances, doesn't enable. " title=" " style="width: 800px"/>
</div>
<figcaption class="fl-center"><center>Agent design now sits between product and data, determining downstream requirements for knowledge, tools, and model selection.</center> </figcaption>
</figure>
<p>Now, teams follow this progression:</p>
<ol>
	<font size="4">
		<li><b>Product:</b> Define the user problem and success metrics.</li>
		<li><b>Agent:</b> Design agent capabilities, workflows, and behaviors.</li>
		<li><b>Data:</b> Determine what knowledge, examples, and context the agent needs.</li>
		<li><b>Model:</b> Select external providers and optimize prompts for your data.</li>
	</font>
</ol>
<p>With external model providers, the &quot;model&quot; phase is really about selection and integration rather than deployment. Teams choose which provider's models best handle their data and use case, then build the orchestration layer to manage API calls, handle failures, and optimize costs.</p>
<p>The agent layer shapes everything downstream—determining what data is needed (knowledge bases, examples, feedback loops), what tools are required (search, calculation, code execution), and ultimately, which external models can execute the design effectively.</p>
<p>This evolution means teams can start with a clear user problem, design an agent to solve it, identify necessary data, and then select appropriate models—rather than starting with data and hoping to find a use case. This is why the canvas framework follows this exact flow.</p>
<h2>The canvas framework: A systematic approach to building AI agents</h2>
<p>Rather than jumping straight into technical implementation, successful teams use structured planning frameworks. Think of them as &quot;business model canvases for AI agents&quot;—tools that help teams think through critical decisions in the right order.</p>
<p>Two complementary frameworks directly address the common failure patterns:</p>
<center><caption><b>Figure 4.</b> The Agentic AI Canvas Framework.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-09-23 at 8.07.20 AM-4pc5pxkwhd.png" alt="This diagram is titled agent AI canvas framework: From idea to production. This process goes from business problem, to POC Canvas, to prototype & launch, then to production canvas, and finally production agent. " title=" " style="width: 800px"/>
</div>
<figcaption class="fl-center"><center>A structured five-phase approach moving from business problem definition through POC, prototype, production canvas, and production agent deployment. Please see the “Resources” section at the end for links to the corresponding templates, hosted in the gen AI Showcase.</b></figcaption>
</figure>
<h3>Canvas #1 - The POC canvas for validating your agent idea</h3>
<p>The POC canvas implements the product → agent → data → model flow through eight focused squares designed for rapid validation:</p>
<center><caption><b>Figure 5.</b> The Agent POC Canvas V1.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-09-23 at 8.11.06 AM-0gs75a3btz.png" alt="This table is titled agent POC: Canvas 1. The description at the top of the table says the canvas helps teams systematically work through all aspects of an agentic AI project while avoiding redundancy and ensuring nothing critical is missed." title=" " style="width: 800px"/>
</div>
<figcaption class="fl-center"><center>Eight focused squares implementing the product → agent → data → model flow for rapid validation of AI agent concepts.</center></figcaption>
</figure>
<h4>Phase 1: Product validation—who needs this and why?</h4>
<p>Before building anything, you must validate that a real problem exists and that users actually want an AI agent solution. This phase prevents the common mistake of building impressive technology that nobody needs. If you can't clearly articulate who will use this and why they'll prefer it to current methods, stop here.</p>
<html>
<head>
     <style>
    table,
    th,
    td {
        border: 1px solid black;
        border-collapse: collapse;
    }
    th,
    td {
        padding: 5px;
    }
    </style>
</head>
<body>
    <table style="width:100%">
        <tr>
					<th>Square</th>  
					<th>Purpose</th>
            <th>Key Questions</th>
        </tr>
        <tr>
					<td>Product vision & user problem</td>
					<td>Define the business problem and establish why an agent is the right solution.</td>
					<td>
						<ul>
							<li><b>Core problem:</b> What specific workflow frustrates users today?</li><li><b>Target users:</b> Who experiences this pain and how often?</li>
							<li><b>Success vision:</b> What would success look like for users?</li>
							<li><b>Value hypothesis:</b> Why would users prefer an agent to current solutions?</li>
									</ul>
								</td>
        </tr>
			<tr>
				<td>User validation & interaction</td>
				<td>User Validation & Interaction
Map how users will engage with the agent and identify adoption barriers.</td>
				<td>
					<ul>
						<li><b>User journey:</b> What's the complete interaction from start to finish?</li>
						<li><b>Interface preference:</b> How do users want to interact?</li>
						<li><b>Feedback mechanisms:</b> How will you know it's working?</li>
						<li><b>Adoption barriers:</b> What might prevent users from trying it?</li>
					</ul>
				</td>
			</tr>
    </table>
</body>
</html>
<h4>Phase 2: Agent design—what will it do and how?</h4>
<p>With a validated problem, design the agent's capabilities and behavior to solve that specific need. This phase defines the agent's boundaries, decision-making logic, and interaction style before any technical implementation. The agent design directly determines what data and models you'll need, making this the critical bridge between problem and solution.</p>
<html>
<head>
     <style>
    table,
    th,
    td {
        border: 1px solid black;
        border-collapse: collapse;
    }
    th,
    td {
        padding: 5px;
    }
    </style>
</head>
<body>
    <table style="width:100%">
        <tr>
					<th>Square</th>  
					<th>Purpose</th>
            <th>Key Questions</th>
        </tr>
        <tr>
					<td>Agent capabilities & workflow</td>
					<td>Agent Capabilities & Workflow
Design what the agent must do to solve the identified problem.
</td>
					<td>
						<ul>
							<li><b>Core tasks:</b> What specific actions must the agent perform?</li>
							<li><b>Decision logic:</b> How should complex requests be broken down?</li>
							<li><b>Tool requirements:</b> What capabilities does the agent need?</li>
							<li><b>Autonomy boundaries:</b> What can it decide versus escalate?</li>
						</ul>
								</td>
        </tr>
			<tr>
				<td>Agent interaction & memory</td>
				<td>Agent Interaction & Memory
Establish communication style and context management.</td>
				<td>
					<ul>
						<li><b>Conversation flow:</b> How should the agent guide interactions?</li>
						<li><b>Personality and tone:</b> What style fits the use case?</li>
						<li><b>Memory requirements:</b> What context must persist?</li>
						<li><b>Error handling:</b> How should confusion be managed?</li>
					</ul>
				</td>
			</tr>
    </table>
</body>
</html>
<h4>Phase 3: Data requirements—what knowledge does it need?</h4>
<p>Agents are only as good as their knowledge base, so identify exactly what information the agent needs to complete its tasks. This phase maps existing data sources and gaps before selecting models, ensuring you don't choose technology that can't handle your data reality. Understanding data requirements upfront prevents the costly mistake of selecting models that can't work with your actual information.</p>
<html>
<head>
     <style>
    table,
    th,
    td {
        border: 1px solid black;
        border-collapse: collapse;
    }
    th,
    td {
        padding: 5px;
    }
    </style>
</head>
<body>
    <table style="width:100%">
        <tr>
					<th>Square</th>  
					<th>Purpose</th>
            <th>Key Questions</th>
        </tr>
        <tr>
					<td>Knowledge requirements & sources</td>
					<td>Identify essential information and where to find it.</td>
					<td>
						<ul>
							<li><b>Essential knowledge:</b> What information must the agent have to complete tasks?</li>
							<li><b>Data sources:</b> Where does this knowledge currently exist?</li>
							<li><b>Update frequency:</b> How often does this information change?</li>
							<li><b>Quality requirements:</b> What accuracy level is needed?</li>
						</ul>
								</td>
        </tr>
			<tr>
				<td>Data collection & enhancement strategy</td>
				<td>Plan data gathering and continuous improvement.</td>
				<td>
					<ul>
						<li><b>Collection strategy:</b> How will initial data be gathered?</li>
						<li><b>Enhancement priority:</b> What data has the biggest impact?</li>
						<li><b>Feedback loops:</b> How will interactions improve the data?</li>
						<li><b>Integration method:</b> How will data be ingested and updated?</li>
					</ul>
				</td>
			</tr>
    </table>
</body>
</html>
<h4>Phase 4: External model integration—which provider and how?</h4>
<p>Only after defining data needs should you select external model providers and build the integration layer. This phase tests whether available models can handle your specific data and use case while staying within budget. The focus is on prompt engineering and API orchestration rather than model deployment, reflecting how modern AI agents actually get built.</p>
<html>
<head>
     <style>
    table,
    th,
    td {
        border: 1px solid black;
        border-collapse: collapse;
    }
    th,
    td {
        padding: 5px;
    }
    </style>
</head>
<body>
    <table style="width:100%">
        <tr>
					<th>Square</th>  
					<th>Purpose</th>
            <th>Key Questions</th>
        </tr>
        <tr>
					<td>Provider selection & prompt engineering</td>
					<td>Choose external models and optimize for your use case.</td>
					<td>
						<ul>
							<li><b>Provider evaluation:</b> Which models handle your requirements best?</li>
							<li><b>Prompt strategy:</b> How should you structure requests for optimal results?</li>
							<li><b>Context management:</b> How should you work within token limits?</li>
							<li><b>Cost validation:</b> Is this economically viable at scale?</li>
							</ul>
								</td>
        </tr>
			<tr>
				<td>API integration & validation</td>
				<td>Build orchestration and validate performance.</td>
				<td>
					<ul>
						<li><b>Integration architecture:</b> How do you connect to providers?</li>
						<li><b>Response processing:</b> How do you handle outputs?</li>
						<li><b>Performance testing:</b> Does it meet requirements?</li>
						<li><b>Production readiness:</b> What needs hardening?</li>
					</ul>
				</td>
			</tr>
    </table>
</body>
</html>
<br>
<center><caption><b>Figure 6.</b> The Agent POC Canvas V1 (Detailed).</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-09-23 at 8.35.15 AM-ubzvmbi1nu.png" alt="Table diagram titled Agent POC: Canvas V1 - detailed. The description for the table says the canvas helps teams systematically work through all aspects of an agentic AI project while avoiding redundancy and ensuring nothing critical is missed." title=" " style="width: 800px"/>
</div>
<figcaption class="fl-center"><center>Expanded view with specific guidance for each of the eight squares covering product validation, agent design, data requirements, and external model integration.</center></figcaption>
</figure>
<h3>Unified data architecture: solving the infrastructure chaos</h3>
<p>Remember the infrastructure problem—teams managing three separate databases with different APIs and scaling characteristics? This is where a unified data platform becomes critical.</p>
<p>Agents need three types of data storage:</p>
<ul>
	<font size="4">
	<li><b>Application database:</b> For business data, user profiles, and transaction history</li>
	<li><b>Vector store:</b> For semantic search, knowledge retrieval, and RAG</li>
	<li><b>Memory store:</b> For agent context, conversation history, and learned behaviors</li>
	</font>
</ul>
<p>Instead of juggling multiple systems, teams can use a unified platform like MongoDB Atlas that provides all three capabilities—flexible document storage for application data, native vector search for semantic retrieval, and rich querying for memory management—all in a single platform.</p>
<p>This unified approach means teams can focus on prompt engineering and orchestration rather than model infrastructure, while maintaining the flexibility to evolve their data model as requirements become clearer. The data platform handles the complexity while you optimize how external models interact with your knowledge.</p>
<p>For embeddings and search relevance, specialized models like Voyage AI can provide domain-specific understanding, particularly for technical documentation where general-purpose embeddings fall short. The combination of unified data architecture with specialized embedding models addresses the infrastructure chaos that kills projects.</p>
<p>This unified approach means teams can focus on agent logic rather than database management, while maintaining the flexibility to evolve their data model as requirements become clearer.</p>
<h3>Canvas #2 - The production canvas for scaling your validated AI agent</h3>
<p>When a POC succeeds, the production canvas guides the transition from &quot;it works&quot; to &quot;it works at scale&quot; through 11 squares organized following the same product → agent → data → model flow, with additional operational concerns:</p>
<center><caption><b>Figure 7.</b> The Productionize Agent Canvas V1.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-09-23 at 8.41.31 AM-os2mjfdrcz.png" alt="Table diagram titled productionize agent: Canvas V1. The description is this canvas guides enterprise teams through the complete journey from validated POC to production-ready agentic systems, addressing technical architecture, business requirements, and operational excellence." title=" " style="width: 800px"/>
</div>
<figcaption class="fl-center"><center>Eleven squares guiding the transition from validated POC to production-ready systems, addressing scale, architecture, operations, and governance.</center> </figcaption>
</figure>
<h4>Phase 1: Product and scale planning</h4>
<p>Transform POC learnings into concrete business metrics and scale requirements for production deployment. This phase establishes the economic case for investment and defines what success looks like at scale. Without clear KPIs and growth projections, production systems become expensive experiments rather than business assets.</p>
<html>
<head>
     <style>
    table,
    th,
    td {
        border: 1px solid black;
        border-collapse: collapse;
    }
    th,
    td {
        padding: 5px;
    }
    </style>
</head>
<body>
    <table style="width:100%">
        <tr>
					<th>Square</th>  
					<th>Purpose</th>
            <th>Key Questions</th>
        </tr>
        <tr>
					<td>Business case & scale planning</td>
					<td>Translate POC validation into production metrics.</td>
					<td>
						<ul>
							<li><b>Proven value:<b> What did the POC validate?</li>
								<li><b>Business KPIs:</b> What metrics measure ongoing success?</li>
								<li><b>Scale requirements:</b> How many users and interactions?</li>
								<li><b>Growth strategy:</b> How will usage expand over time?</li>
							</ul>
								</td>
        </tr>
			<tr>
				<td>Production requirements & constraints</td>
				<td>Define performance standards and operational boundaries.</td>
				<td>
					<ul>
						<li><b>Performance standards:</b> Response time, availability, throughput?</li>
						<li><b>Reliability requirements:</b> Recovery time and failover?</li>
						<li><b>Budget constraints:</b> Cost limits and optimization targets?</li>
						<li><b>Security needs:</b> Compliance and data protection requirements?</li>
					</ul>
				</td>
			</tr>
    </table>
</body>
</html>
<h4>Phase 2: Agent architecture</h4>
<p>Design robust systems that handle complex workflows, multiple agents, and inevitable failures without disrupting users. This phase addresses the orchestration and fault tolerance that POCs ignore but production demands. The architecture decisions here determine whether your agent can scale from 10 users to 10,000 without breaking.</p>
<html>
<head>
     <style>
    table,
    th,
    td {
        border: 1px solid black;
        border-collapse: collapse;
    }
    th,
    td {
        padding: 5px;
    }
    </style>
</head>
<body>
    <table style="width:100%">
        <tr>
					<th>Square</th>  
					<th>Purpose</th>
            <th>Key Questions</th>
        </tr>
        <tr>
					<td>Robust agent architecture</td>
					<td>Design for complex workflows and fault tolerance.</td>
					<td>
						<ul>
							<li><b>Workflow orchestration:</b> How do you manage multi-step processes?</li>
							<li><b>Multi-agent coordination:</b> How do specialized agents collaborate?</li>
							<li><b>Fault tolerance:</b> How do you handle failures gracefully?</li>
							<li><b>Update rollouts:</b> How do you update without disruption?</li>
							</ul>
								</td>
        </tr>
			<tr>
				<td>Production memory & context systems</td>
				<td>Implement scalable context management.</td>
				<td>
					<ul>
						<li><b>Memory architecture:</b> Session, long-term, and organizational knowledge?</li>
						<li><b>Context persistence:</b> Storage and retrieval strategies?</li>
						<li><b>Cross-session continuity:</b> How do you maintain user context?</li>
						<li><b>Memory lifecycle management:</b> Retention, archival, and cleanup?</li>
					</ul>
				</td>
			</tr>
    </table>
</body>
</html>
<h4>Phase 3: Data infrastructure</h4>
<p>Build the data foundation that unifies application data, vector storage, and agent memory in a manageable platform. This phase solves the &quot;three database problem&quot; that kills production deployments through complexity. A unified data architecture reduces operational overhead while enabling the sophisticated retrieval and context management that production agents require.</p>
<html>
<head>
     <style>
    table,
    th,
    td {
        border: 1px solid black;
        border-collapse: collapse;
    }
    th,
    td {
        padding: 5px;
    }
    </style>
</head>
<body>
    <table style="width:100%">
        <tr>
					<th>Square</th>  
					<th>Purpose</th>
            <th>Key Questions</th>
        </tr>
        <tr>
					<td>Data architecture & management</td>
					<td>Build a unified platform for all data types.</td>
					<td>
						<ul>
							<li><b>Platform architecture:</b> Application, vector, and memory data?</li>
							<li><b>Data pipelines:</b> Ingestion, processing, and updates?</li>
							<li><b>Quality assurance:</b> Validation and freshness monitoring?</li>
							<li><b>Knowledge governance:</b> Version control and approval workflows?</li>
							</ul>
								</td>
        </tr>
			<tr>
				<td>Knowledge base & pipeline operations</td>
				<td>Maintain and optimize knowledge systems.</td>
				<td>
					<ul>
						<li><b>Update strategy:</b> How does knowledge evolve?</li>
						<li><b>Embedding approach:</b> Which models for which content?</li>
						<li><b>Retrieval optimization:</b> Search relevance and reranking?</li>
						<li><b>Operational monitoring:</b> Pipeline health and costs?</li>
					</ul>
				</td>
			</tr>
    </table>
</body>
</html>
<h4>Phase 4: Model operations</h4>
<p>Implement strategies for managing multiple model providers, fine-tuning, and cost optimization at production scale. This phase covers API management, performance monitoring, and the continuous improvement pipeline for model performance. The focus is on orchestrating external models efficiently rather than deploying your own, including when and how to fine-tune.</p>
<html>
<head>
     <style>
    table,
    th,
    td {
        border: 1px solid black;
        border-collapse: collapse;
    }
    th,
    td {
        padding: 5px;
    }
    </style>
</head>
<body>
    <table style="width:100%">
        <tr>
					<th>Square</th>  
					<th>Purpose</th>
            <th>Key Questions</th>
        </tr>
        <tr>
					<td>Model strategy & optimization</td>
					<td>Manage providers and fine-tuning strategies.</td>
					<td>
						<ul>
							<li><b>Provider selection:</b> Which models for which tasks?</li>
							<li><b>Fine-tuning approach:</b> When and how to customize?</li>
							<li><b>Routing logic:</b> Base versus fine-tuned model decisions?</li>
							<li><b>Cost controls:</b> Caching and intelligent routing?</li>
							</ul>
								</td>
        </tr>
			<tr>
				<td>API management & monitoring</td>
				<td>Handle external APIs and performance tracking.</td>
				<td>
					<ul>
						<li><b>API configuration:</b> Key management and failover?</li>
						<li><b>Performance Tracking:</b> Accuracy, latency, and costs?</li>
						<li><b>Fine-tuning pipeline:</b> Data collection for improvement?</li>
						<li><b>Version control:</b> A/B testing and rollback strategies?</li>
					</ul>
				</td>
			</tr>
    </table>
</body>
</html>
<h4>Phase 5: Hardening and operations</h4>
<p>Add the security, compliance, user experience, and governance layers that transform a working system into an enterprise-grade solution. This phase addresses the non-functional requirements that POCs skip but enterprises demand. Without proper hardening, even the best agents remain stuck in pilot purgatory due to security or compliance concerns.</p>
<html>
<head>
     <style>
    table,
    th,
    td {
        border: 1px solid black;
        border-collapse: collapse;
    }
    th,
    td {
        padding: 5px;
    }
    </style>
</head>
<body>
    <table style="width:100%">
        <tr>
					<th>Square</th>  
					<th>Purpose</th>
            <th>Key Questions</th>
        </tr>
        <tr>
					<td>Security & compliance</td>
					<td>Implement enterprise security and regulatory controls.</td>
					<td>
						<ul>
							<li><b>Security implementation:</b> Authentication, encryption, and access management?</li>
							<li><b>Access control:</b> User and system access management?</li>
							<li><b>Compliance framework:</b> Which regulations apply?</li>
							<li><b>Audit capabilities:</b> Logging and retention requirements?</li>
							</ul>
								</td>
        </tr>
			<tr>
				<td>User experience & adoption</td>
				<td>Drive usage and gather feedback.</td>
				<td>
					<ul>
						<li><b>Workflow integration:</b> How do you fit existing processes?</li>
						<li><b>Adoption strategy:</b> Rollout and engagement plans?</li>
						<li><b>Support systems:</b> Documentation and help channels?</li>
						<li><b>Feedback integration:</b> How does user input drive improvement?</li>
					</ul>
				</td>
			</tr>
			<tr>
				<td>Continuous improvement & governance</td>
				<td>Ensure long-term sustainability.</td>
				<td>
					<ul>
						<li><b>Operational procedures:</b> Maintenance and release cycles?</li>
						<li><b>Quality gates:</b> Testing and deployment standards?</li>
						<li><b>Cost management:</b> Budget monitoring and optimization?</li>
						<li><b>Continuity planning:</b> Documentation and team training?</li>
					</ul>
			</tr>
    </table>
</body>
</html>
<br>
<center><caption><b>Figure 8.</b> The Productionize Agent Canvas V1 (Detailed).</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-09-23 at 9.10.21 AM-hczx63dr6t.png" alt="Table diagram titled productionize agent: Canvas V1 - Detailed. The description is this canvas guides enterprise teams through the complete journey from validated POC to production-ready agentic systems, addressing technical architecture, business requirements, and operational excellence." title=" " style="width: 800px"/>
</div>
<figcaption class="fl-center"><center>Expanded view with specific guidance for each of the eleven squares covering scale planning, architecture, data infrastructure, model operations, and hardening requirements.</center> </figcaption>
</figure>
<h2>Next steps: start building AI agents that deliver ROI</h2>
<p>MIT's research found that <a href="https://mlq.ai/media/quarterly_decks/v0.1_State_of_AI_in_Business_2025_Report.pdf" target="_blank">66% of executives want systems that learn from feedback</a>, while 63% demand context retention (pg.14). The dividing line between AI and human preference is memory, adaptability, and learning capability.</p>
<p>The canvas framework directly addresses the failure patterns plaguing most projects by forcing teams to answer critical questions in the right order—following the product → agent → data → model flow that successful teams have discovered.</p>
<p>For your next agentic AI initiative:</p>
<ul>
	<font size="4">
		<li>Start with the POC canvas to validate concepts quickly.</li>
		<li>Focus on user problems before technical solutions.</li>
		<li>Leverage AI tools to rapidly prototype after completing your canvas.</li>
		<li>Only scale what users actually want with the production canvas.</li>
		<li>Choose a unified data architecture to reduce complexity from day one.</li>
	</font>
</ul>	
<p>Remember: The goal isn't to build the most sophisticated agent possible—it's to build agents that solve real problems for real users in production environments.</p>
<div class="callout">
<p><b>For hands-on guidance on memory management, check out our <a href="https://www.youtube.com/watch?v=n-slj72yx8w" target="_blank">webinar</a> on YouTube, which covers essential concepts and proven techniques for building memory-augmented agents.</b></p>
<p><b>Head over to the <a href="https://www.mongodb.com/resources/use-cases/artificial-intelligence?tck=augmented_ai_agents_blog">MongoDB AI Learning Hub</a> to learn how to build and deploy AI applications with MongoDB.</b></p>
</div>
<h3>Resources</h3>
<ul>
	<font size="4">
		<li><a href="https://github.com/mongodb-developer/GenAI-Showcase/blob/main/resources/agent-canvas/MongoDB-agentic-poc-canvas.pdf" target="_blank">Download POC Canvas Template</a> (PDF)</li>
		<li><a href="https://github.com/mongodb-developer/GenAI-Showcase/blob/main/resources/agent-canvas/MongoDB-agent-productionization-canvas.pdf" target="_blank">Download Production Canvas Template</a> (PDF)</li>
<li><a href="https://github.com/mongodb-developer/GenAI-Showcase/blob/main/resources/agent-canvas/MongoDB-combined-agentic-AI-planning-canvas.xlsx" target="_blank">Download Combined POC + Production Canvas</a> (Excel) - Get both canvases in a single excel file, with example prompts and blank templates.</li>
	</font>
</ul>
<h3>Full reference list</h3>
<ol>
	<font size="4">
		<li><b>McKinsey & Company</b>. (2025). "Seizing the agentic AI advantage." <a href="https://www.mckinsey.com/capabilities/quantumblack/our-insights/seizing-the-agentic-ai-advantage" target="_blank">ttps://www.mckinsey.com/capabilities/quantumblack/our-insights/seizing-the-agentic-ai-advantage</a></li>
		<li><b>MIT NANDA</b>. (2025). "The GenAI Divide: State of AI in Business 2025." <a href="https://mlq.ai/media/quarterly_decks/v0.1_State_of_AI_in_Business_2025_Report.pdf" target="_blank">Report</a></li> 
		<li><b>Gartner</b>. (2025). "Gartner Predicts Over 40% of Agentic AI Projects Will Be Canceled by End of 2027." <a href="https://www.gartner.com/en/newsroom/press-releases/2025-06-25-gartner-predicts-over-40-percent-of-agentic-ai-projects-will-be-canceled-by-end-of-2027" target="_blank">https://www.gartner.com/en/newsroom/press-releases/2025-06-25-gartner-predicts-over-40-percent-of-agentic-ai-projects-will-be-canceled-by-end-of-2027</a></li>
		<li><b>IBM</b>. (2025). "IBM Study: Businesses View AI Agents as Essential, Not Just Experimental." <a href="https://newsroom.ibm.com/2025-06-10-IBM-Study-Businesses-View-AI-Agents-as-Essential,-Not-Just-Experimental" target="_blank">https://newsroom.ibm.com/2025-06-10-IBM-Study-Businesses-View-AI-Agents-as-Essential,-Not-Just-Experimental</a></li>
		<li><b>Carnegie Mellon University</b>. (2025). "TheAgentCompany: Benchmarking LLM Agents." <a href="https://www.cs.cmu.edu/news/2025/agent-company" target="_blank">https://www.cs.cmu.edu/news/2025/agent-company</a></li>
		<li><b>Swyx</b>. (2023). "The Rise of the AI Engineer." Latent Space. <a href="https://www.latent.space/p/ai-engineer" target="_blank">https://www.latent.space/p/ai-engineer</a></li>
		<li><b>SailPoint</b>. (2025). "SailPoint research highlights rapid AI agent adoption, driving urgent need for evolved security." <a href="https://www.sailpoint.com/press-releases/sailpoint-ai-agent-adoption-report" target="_blank">https://www.sailpoint.com/press-releases/sailpoint-ai-agent-adoption-report</a></li>
		<li><b>SS&C Blue Prism</b>. (2025). "Generative AI Statistics 2025." <a href="https://www.blueprism.com/resources/blog/generative-ai-statistics-2025/" target="_blank">https://www.blueprism.com/resources/blog/generative-ai-statistics-2025/</a></li>
		<li><b>PagerDuty</b>. (2025). "State of Digital Operations Report." <a href="https://www.pagerduty.com/newsroom/2025-state-of-digital-operations-study/" target="_blank">https://www.pagerduty.com/newsroom/2025-state-of-digital-operations-study/</a></li>
		<li><b>Wall Street Journal</b>. (2024). "How Moderna Is Using AI to Reinvent Itself." <a href="https://www.wsj.com/articles/at-moderna-openais-gpts-are-changing-almost-everything-6ff4c4a5" target="_blank">https://www.wsj.com/articles/at-moderna-openais-gpts-are-changing-almost-everything-6ff4c4a5</a></li>
	</font>
</ol>	]]></description>
      <pubDate>Tue, 23 Sep 2025 16:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/technical/build-ai-agents-worth-keeping-canvas-framework</link>
      <guid>https://www.mongodb.com/company/blog/technical/build-ai-agents-worth-keeping-canvas-framework</guid>
    </item><item>
      <title>Simplify AI-Driven Data Connectivity With MongoDB and MCP Toolbox</title>
      <description><![CDATA[<p>The wave of generative AI applications is revolutionizing how businesses interact with and derive value from their data. Organizations need solutions that simplify these interactions and ensure compatibility with an expanding ecosystem of databases. Enter <a href="https://github.com/googleapis/genai-toolbox/blob/main/README.md" target="_blank">MCP Toolbox for Databases</a>, an open-source Model Context Protocol (MCP) server that enables seamless integration between gen AI agents and enterprise data sources using a standardized protocol pioneered by Anthropic. With the built-in capability to query multiple data sources simultaneously and unify results, MCP Toolbox eliminates fragmented integration challenges, empowering businesses to unlock the full potential of their data.</p>
<p>With <a href="https://www.mongodb.com/products/platform">MongoDB Atlas</a> now joining the ecosystem of databases supported by MCP Toolbox, enterprises using MongoDB’s industry-leading cloud-native database platform can benefit from streamlined connections to their gen AI systems.</p>
<p>As businesses adopt gen AI to unlock insights and automate workflows, the choice of database is critical to meeting demands for dynamic data structures, scalability, and high-performance applications. MongoDB Atlas, with its fully managed, document-oriented NoSQL design and capabilities for flexible schema modeling, is the ultimate companion to MCP Toolbox for applications requiring unstructured or semistructured data connectivity.</p>
<p>This blog post explores how MongoDB Atlas integrates into MCP Toolbox, its advantages for developers, and the key use cases for enabling AI-driven data solutions in enterprise environments.</p>
<center><caption><b>Figure 1.</b> MongoDB as a source for MCP Toolbox for Databases.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-09-19 at 2.04.49 PM-dg7ezporjy.png" alt="This diagram has the agents for application and the agents for developer assistance both connecting to the MCP toolbox for databases, which then connects to MongoDB Atlas." title=" " style="width: 800px"/>
</div>
<figcaption class="fl-center"> </figcaption>
</figure>
<h2>How it works</h2>
<p>The integration of MongoDB Atlas with MCP Toolbox enables users to perform Create, Read, Update, Delete (CRUD) operations on MongoDB data sources using the standardized MCP. Beyond fundamental data management tasks, this integration also unlocks capabilities from MongoDB’s <a href="https://www.mongodb.com/docs/manual/aggregation/">aggregation framework</a>, enabling users to seamlessly execute complex data transformations, computations, and analyses. This empowers businesses to not only access and modify their data but also uncover valuable insights by harnessing MongoDB’s powerful query functionality within workflows driven by MCP Toolbox. By combining the scalability and flexibility of MongoDB Atlas with MCP Toolbox’s ability to query across multiple data sources, organizations can develop advanced AI-driven applications, enhance operational efficiency, and uncover deeper analytical opportunities.</p>
<p>The use of MongoDB as both a source and a sink within MCP Toolbox is simple and highly versatile, thanks to the flexibility of the configuration file. To configure MongoDB as a data source, you can define it under the sources section, specifying parameters such as its kind (&quot;mongodb&quot;) and the connection’s Uniform Resource Identifier (URI) to establish access to your MongoDB instance.</p>
<pre><code tabindex="0">sources:&NewLine;    my-mongodb:&NewLine;        kind: mongodb&NewLine;        uri: &quot;mongodb+srv://username:password@host.mongodb.net&quot;&NewLine;</code></pre>
<p>In the tools section, various operations—such as retrieving, updating, inserting, or deleting data—can be defined by linking the appropriate source, specifying the target database and dataset, and configuring parameters such as filters, projections, sorting, or payload structures. Additionally, databases can act as sinks for storing data by enabling operations to write new records or modify existing ones, making them ideal for workflows where applications or systems need to interact dynamically with persistent storage. The toolsets section facilitates grouping related tools, making it easy to load and manage specific sets of operations based on different use cases or requirements. Whether used for reading or writing data, the integration of databases via MCP Toolbox provides a streamlined and consistent approach to managing and interacting with diverse data sources. Below is an example of running &quot;find query&quot; on MongoDB Atlas using the MCP Toolbox.</p>
<pre><code tabindex="0">tools:&NewLine;  get_user_profile:&NewLine;    kind: mongodb-find-one&NewLine;    source: my-mongo-source&NewLine;    description: Retrieves a user's profile by their email address.&NewLine;    database: user_data&NewLine;    collection: profiles&NewLine;    filterPayload: |&NewLine;        { &quot;email&quot;: {{json .email}} }&NewLine;    filterParams:&NewLine;      - name: email&NewLine;        type: string&NewLine;        description: The email address of the user to find.&NewLine;    projectPayload: |&NewLine;        { &NewLine;          &quot;password_hash&quot;: 0,&NewLine;          &quot;login_history&quot;: 0&NewLine;        }&NewLine;</code></pre>
<h2>Getting started</h2>
<p>The integration of MongoDB Atlas and MCP Toolbox for Databases marks a significant step forward in simplifying database interactions for enterprises embracing gen AI. By enabling seamless connectivity, advanced data operations, and cross-source queries, this collaboration empowers businesses to build AI-driven applications that maximize the value of their data while enhancing efficiency and scalability.</p>
<div class="callout">
<p><b>Get started today through <a href="https://console.cloud.google.com/marketplace/product/mongodb/mdb-atlas-self-service?project=mdb-gcp-marketplace&utm_source=marketplace&utm_medium=ToolboxBlog&utm_campaign=ToolboxBlog_MDB&utm_term=mongodb" target="_blank">Google Cloud Marketplace</a>.</b></p>
<ol>
	<font size="4">
		<li>Set up <a href="https://github.com/googleapis/genai-toolbox/blob/main/docs/en/getting-started/local_quickstart_js.md" target="_blank">MCP Toolbox for Databases</a> locally. </li>
		<li>Set up <a href="https://github.com/googleapis/genai-toolbox/blob/main/docs/en/resources/sources/mongodb.md" target="_blank">MongoDB Atlas source connector</a>. </li>
		<li>And then set up <a href="https://github.com/googleapis/genai-toolbox/tree/main/docs/en/resources/tools/mongodb" target="_blank">MongoDB Atlas tools</a>.</li>
	</font>
</ol>	]]></description>
      <pubDate>Mon, 22 Sep 2025 14:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/simplify-ai-driven-data-connectivity-mcp-toolbox</link>
      <guid>https://www.mongodb.com/company/blog/innovation/simplify-ai-driven-data-connectivity-mcp-toolbox</guid>
    </item><item>
      <title>MongoDB Community Edition to Atlas: A Migration Masterclass With BharatPE</title>
      <description><![CDATA[<p>Launched in 2018, BharatPE is a fintech pioneer serving millions of Indian retailers and small businesses across more than 450 cities. The company processes over ₹12,000 crore (about US $1.368 billion) in monthly Unified Payments Interface (UPI)-based transactions.</p>
<p>One of BharatPE’s most innovative financial solutions is India’s first interoperable UPI QR code—a scannable 2D barcode that empowers users to make payments using the UPI system in India—and a zero-MDR (Merchant Discount Rate) payment acceptance service, which enables merchants to accept payments through the same system without any charges.</p>
<p>Behind BharatPE’s success is the ability to manage high volumes of data, maintain data security, and scale to accommodate growth and adapt to traffic peaks, all while keeping operational and maintenance burden low. This is all powered by <a href="https://www.mongodb.com/atlas">MongoDB Atlas</a>.</p>
<p>Sumit Malik, Head of Database Operations at BharatPE, <a href="https://www.youtube.com/watch?v=wHOopWPhHxI&list=PL4RCxklHWZ9tYeDD_5f41Q2pt694E2nLg&index=2">presented at MongoDB .local Delhi in July 2025</a>, sharing the company’s transformational journey from managing a <a href="https://www.mongodb.com/products/self-managed/community-edition">self-hosted version of MongoDB</a>.</p>
<iframe width="800" height="425" src="https://www.youtube.com/embed/wHOopWPhHxI?si=d0qDed3JwO1oS9vF" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
<h2>From Community Edition to Atlas: Unlocking more scale and reducing complexity</h2>
<p>BharatPE’s legacy infrastructure relied on a self-hosted version of MongoDB: <a href="https://www.mongodb.com/products/self-managed/community-edition">MongoDB Community Edition</a>. The setup included three sharded clusters, each with three nodes (one primary, two secondary), handling BharatPE’s 45 terabytes of data.</p>
<p>However, self-managing this large deployment created several challenges. Data was spread unevenly across clusters, which caused imbalances and scaling complexities. Maintaining the database also proved costly and time-consuming for the team.</p>
<p>BharatPE was also looking to expand its disaster recovery capabilities to remove business continuity and downtime risks.</p>
<p>Finally, operating in a regulated industry with   high security standards meant that BharatPE needed to create robust end-to-end security and compliance.</p>
<p>“We needed a database platform that could scale seamlessly, secure our data, and minimize operational burden,” said Malik.</p>
<p>After careful consideration and due diligence, it was determined that <a href="https://www.mongodb.com/atlas">MongoDB Atlas</a> delivered the ideal solution against BharatPE's requirements.</p>
<h2>A carefully planned, 5-step migration approach</h2>
<p>MongoDB's professional services team helps customers migrate from the self-managed version of MongoDB to MongoDB Atlas. The work we have done with many of our customers has led us to develop a methodical 5-step migration process. This approach, built around five key phases, was central to avoiding downtime and maintaining business continuity throughout BharaPE’s migration process :</p>
<ol>
	<font size="4">
		<li><b>Design phase: defining scope and strategy</b> - In the initial phase, BharatPE worked with MongoDB to lay the groundwork for the migration by clearly defining its scope, timeline, resources, and dependencies. They analyzed data volume, structure, and compatibility between the source system (self-hosted MongoDB) and the target system (MongoDB Atlas). “We carefully designed a migration strategy that accounted for every possible risk and dependency within our system,” said Malik. </li> 
		<li><b>De-risk phase: assessing and mitigating risks</b> - This phase—a core part and value of MongoDB’s approach—  focused on identifying and addressing potential risks associated with the migration. BharatPE validated application compatibility with MongoDB Atlas and assessed the suitability of its driver versions. Malik shared: “Understanding compatibility challenges early on helped us eliminate surprises during production.” </li>
		<li><b>Test phase: validating systems in lower environments</b> - Before touching the production environment, BharatPE conducted extensive testing in a development environment that closely emulated its real-world setup. “We created a fully mirrored MongoDB Atlas test environment where we integrated our existing systems and validated application sanity and compatibility,” said Malik. Introducing an additional MongoDB server allowed the team to simulate real-world scenarios and ensure readiness.</li>
		<li><b>Migration phase: data transition and security</b> - BharatPE used <a href="https://www.mongodb.com/docs/mongosync/current/reference/mongosync/">MongoDB’s mongosync tool</a> alongside the migration strategy built with the MongoDB team to migrate terabytes of data securely and efficiently. Ensuring data privacy during transit was a top priority, and the team adopted <a href="https://www.mongodb.com/products/capabilities/security/encryption">MongoDB’s robust encryption functionality</a> to protect sensitive financial information and ensure compliance.</li> 
		<li><b>Validation phase: confirming data integrity and optimizing performance</b> - Once the data was moved, BharatPE performed rigorous post-migration checks. Automated scripts were developed to validate the integrity of the migrated data, ensuring it matched the original source without discrepancies. Additionally, monitoring systems and real-time alerting were set up to catch and resolve any issues immediately.</li>
	</font>
</ol>
<p>This meticulous five-step approach, and the close partnership with   from partnering with MongoDB’s team, allowed BharatPE to transition to MongoDB Atlas without impacting its production environment, all while ensuring data security, operational continuity, and reliability.</p>
<h2>MongoDB Atlas boosts performance by 40%</h2>
<p>Since migrating to MongoDB Atlas, BharatPE has realized tangible benefits that have directly impacted its operations and customer experience.</p>
<p>“&lt;With MongoDB Atlas, we effectively reduced operational complexity and improved scalability,” Malik said. Atlas’s auto-scaling capabilities enabled BharatPE to effortlessly handle the volume spikes associated with 500M+ UPI transactions monthly.</p>
<p>Atlas’s reliability has improved availability and minimized downtime, critical to BharatPE’s 24/7 operations. “The system’s auto-failover ensures seamless service continuity, even during node failures,” said Malik. Notably, MongoDB’s SLA-guaranteed 99.995% uptime delivered improved consistency.</p>
<p>Performance enhancements have been equally transformative with a 40% improvement in query response times thanks to built-in query performance analytics. Observability dashboards and real-time alerts have enabled faster issue resolution.</p>
<p>The migration also addressed BharatPE’s security concerns. BharatPE now fully meets fintech security and compliance requirements, enabled by MongoDB’s advanced security features such as data encryption, role-based access control, and VPC peering.</p>
<p>Finally, by eliminating the complexities of self-managed infrastructure, the company has freed resources to focus on business growth and customer experience.</p>
<p>“MongoDB handles audit logs with a single click—we no longer need third-party tools or manual setups,” said Malik. “The migration has future-proofed our infrastructure while reducing costs and improving reliability.”</p>
<p>MongoDB Atlas now underpins the foundations of BharatPE’s operations, and ensures merchants can continue transacting seamlessly while enabling BharatPE to expand its offerings across India’s growing fintech landscape.</p>
<div class="callout">
<p><b>Visit the <a href="https://www.mongodb.com/resources/product/platform/atlas-learning-hub">Atlas Learning Hub</a> to learn more about Atlas and start building your MongoDB skills.</b></p>
<p><b>To learn more about MongoDB Community Edition, visit the <a href="https://www.mongodb.com/products/self-managed/community-edition">product page</a>.</b></p>
</div>	]]></description>
      <pubDate>Sun, 21 Sep 2025 23:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/innovation/mongodb-community-edition-to-atlas-migration-masterclass-bharatpe</link>
      <guid>https://www.mongodb.com/company/blog/innovation/mongodb-community-edition-to-atlas-migration-masterclass-bharatpe</guid>
    </item><item>
      <title>Modernizing Core Insurance Systems: Breaking the Batch Bottleneck </title>
      <description><![CDATA[<p>Modernizing your legacy database to Java + <a href="https://www.mongodb.com/products/platform">MongoDB Atlas</a> doesn’t have to mean sacrificing batch performance. By leveraging bulk operations, intelligent prefetching, and parallel execution, we built an optimization framework that not only bridges the performance gap but, in many cases, surpasses legacy systems.</p>
<p>In workloads where jobs were previously running 25–30x slower before using this framework, it brought execution times back on par and, in some cases, delivered 10–15x better performance. For global insurance platforms, significantly improved batch performance has become an added technical benefit to potentially support newer functionality.</p>
<h2>The modernization dilemma</h2>
<p>For organizations modernizing their core platforms, catering to significant user workload and revenue-generating applications, moving from a legacy RDBMS to a modern application stack with Java + MongoDB unlocks several benefits:</p>
<ul>
	<font size="4">
<li><b>Flexible document model:</b> PL/SQL code tightly couples business logic with the database, making even small changes risky and time-consuming. <a href="https://www.mongodb.com/products/platform">MongoDB Atlas</a>, with its flexible document model and application-driven logic, enables teams to evolve schemas and processes quickly, a huge advantage for industries like insurance, where regulations, products, and customer expectations change rapidly.</li>
<li><b>Scalability and resilience:</b> Legacy RDBMS platforms were never designed for today’s scale of digital engagement. MongoDB’s distributed architecture supports <a href="https://www.mongodb.com/resources/basics/horizontal-vs-vertical-scaling">horizontal scale-out</a>, ensuring that core insurance workloads can handle growing customer bases, high-volume claims, and peak-time spikes without major redesigns.</li>
<li><b>Cloud-native by design:</b> MongoDB is built to thrive in the cloud. Features like global clusters, built-in replication, and high availability with reduced infrastructure complexity, while enabling deployment flexibility across hybrid and multi-cloud environments.</li>
<li><b>Modern developer ecosystem:</b> Decouples database and business logic dependencies, accelerating feature delivery.</li>
<li><b>Unified operational + analytical workloads:</b> Modern insurance platforms demand more than transactional processing; they require real-time insights. MongoDB’s ability to support both operational workloads and <a href="https://www.mongodb.com/resources/basics/real-time-analytics-examples">analytics</a> on live data reduces the gap between claims processing and decision-making.</li>
	</font>
</ul>
<p>However, alongside these advantages, one of the first hurdles they encounter is batch jobs performance, the jobs that are meant to run daily/weekly/monthly, like an ETL process.</p>
<p>PL/SQL thrives on set-based operations within the database engine. But when the same workloads are reimplemented with a separate application layer and MongoDB, they can suddenly become unpredictable, slow, and even time out. In some cases, processes that ran smoothly for years started running 25–30x slower after a like-for-like migration. The majority of the issues can be factored into the following broad categories:</p>
<ul>
	<font size="4">
		<li>High network round-trips between the application and the database.</li>
		<li>Inefficient per-record operations replacing set-based logic.</li>
		<li>Under-utilization of database bulk capabilities.</li>
		<li>Application-layer computation overhead when transforming large datasets.</li>
	</font>
</ul>
<p>For teams migrating complex ETL-like processes, this wasn’t just a technical nuisance—it became a blocker for modernization at scale.</p>
<h2>The breakthrough: A batch job optimization framework</h2>
<p>We designed an extensible, multi-purpose &amp; resilient batch optimization framework purpose-built for high-volume, multi-collection operations in MongoDB. The framework focuses on minimising application-database friction while retaining the flexibility of Java services.</p>
<p>Key principles include:</p>
<ol>
	<font size="4">
		<li><b>Bulk operations at scale:</b> Leveraging MongoDB’s native ```bulkWrite``` (including multi-collection bulk transactions in MongoDB 8) to process thousands of operations in a single round trip.</li>
		<li><b>Intelligent prefetching:</b> Reducing repeated lookups by pre-loading and caching reference data in memory-friendly structures.</li>
		<li><b>Parallel processing:</b> Partitioning workloads across threads or event processors (e.g., Disruptor pattern) for CPU-bound and I/O-bound steps.</li>
		<li><b>Configurable batch sizes:</b> Dynamically tuning batch chunk sizes to balance memory usage, network payload size, and commit frequency.</li>
		<li><b>Pluggable transformation modules:</b> Modularized data transformation logic that can be reused across multiple processes.</li>
	</font>
</ol>
<h2>Technical architecture</h2>
<p>The framework adopts a layered and orchestrated approach to batch job processing, where each component has a distinct responsibility in the end-to-end workflow. The diagram illustrates the flow of a batch execution:</p>
<ol>
	<font size="4">
		<li><b>Trigger (user / cron job):</b> The batch process begins when a user action or a scheduled cron job triggers the Spring Boot controller.</li>
		<li>Spring boot controller:</b> The controller initiates the process by fetching the relevant records from the database. Once retrieved, it splits the records into batches for parallel execution.</li>
		<li><b>Database:</b> Acts as the source of truth for input data and the destination for processed results. It supports both reads (to fetch records) and writes (to persist batch outcomes).</li>
		<li><b>Executor framework:</b> This layer is responsible for parallelizing workloads. It distributes batched records, manages concurrency, and invokes ETL tasks efficiently.</li>
		<li><b>ETL process:</b> The ETL (Extract, Transform, Load) logic is applied to each batch. Data is pre-fetched, transformed according to business rules, and then loaded back into the database.</li>
		<li><b>Completion & write-back:</b> Once ETL operations are complete, the executor framework coordinates database write operations and signals the completion of the batch.</li>
		</font>
</ol>
<center><caption><b>Figure 1.</b> The architecture for the layered approach.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-09-17 at 1.11.35 PM-gvslu7l99i.png" alt="Diagram showing the architecture. Starting with users, the architecture progresses through to the ETL process." title=" " style="width: 800px"/>
</div>
<figcaption class="fl-center"> </figcaption>
</figure>
<h2>From bottleneck to advantage</h2>
<p>The results were striking. Batch jobs that previously timed out are now completed predictably within defined SLAs, and workloads that had initially run 25–30x slower after migration were optimized to perform on par with legacy RDBMSs and in several cases even deliver 10–15x better performance. What was once a bottleneck became a competitive advantage, proving that batch processing on MongoDB can significantly outperform legacy PL/SQL when implemented with the right optimization framework.</p>
<h2>Caveats and tuning tips</h2>
<p>While the framework is adaptable, its performance depends on workload characteristics and infrastructure limits:</p>
<ul>
	<font size="4">
		<li><b>Batch size tuning:</b> Too large can cause memory pressure; too small increases round-trips.</li>
		<li><b>Transaction boundaries:</b> MongoDB transactions have limits (document size, total operations), plan batching accordingly.</li>
		<li><b>Thread pool sizing:</b> Over-parallelization can overload the database or network.</li>
		<li><b>Index strategy:</b> Even with bulk writes, poor indexing can cause slowdowns.</li>
		<li><b>Prefetch scope:</b> Balance memory usage against lookup frequency.</li>
	</font>
</ul>	
<p>In short, it’s not one size fits all. Every workload is different, the data you process, the rules you apply, and the scale you run at all shape how things perform. What we’ve seen though is that with the right tuning, this framework can handle scale reliably and take batch processing from being a pain point to something that actually gives you an edge.</p>
<p>If you’re exploring how to modernize your own workloads, this approach is a solid starting point. You can pick and choose the parts that make sense for your setup, and adapt as you go.</p>
<div class="callout">
<p><b>Ready to modernize your applications? Visit the <a href="https://www.mongodb.com/solutions/use-cases/modernize">modernization page</a> to learn about the MongoDB Application Platform.</b></p>
</div>	]]></description>
      <pubDate>Thu, 18 Sep 2025 15:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/technical/modernizing-core-insurance-systems-breaking-batch-bottleneck</link>
      <guid>https://www.mongodb.com/company/blog/technical/modernizing-core-insurance-systems-breaking-batch-bottleneck</guid>
    </item><item>
      <title>MongoDB.local NYC 2025: Defining the Ideal Database for the AI Era</title>
      <description><![CDATA[<p>Yesterday, we welcomed thousands of developers and executives to MongoDB.local NYC, the latest stop in our global .local series. Over the past year, we’ve connected with tens of thousands of partners and customers in 20 cities worldwide. But it’s especially meaningful to be in New York—where MongoDB was founded and where we are still headquartered.</p>
<div class="callout">
<p><b>This post is also available in: <a href="https://www.mongodb.com/company/blog/events/local-nyc-2025-defining-ideal-database-for-ai-era-de" target="_blank">Deutsch</a>, <a href="https://www.mongodb.com/company/blog/events/local-nyc-2025-defining-ideal-database-for-ai-era-fr" target="_blank">Français</a>, <a href="https://www.mongodb.com/company/blog/events/local-nyc-2025-defining-ideal-database-for-ai-era-es" target="_blank">Español</a>, <a href="https://www.mongodb.com/company/blog/events/local-nyc-2025-defining-ideal-database-for-ai-era-br" target="_blank">Português</a>, <a href="https://www.mongodb.com/company/blog/events/local-nyc-2025-defining-ideal-database-for-ai-era-it" target="_blank">Italiano</a>, <a href="https://www.mongodb.com/company/blog/events/local-nyc-2025-defining-ideal-database-for-ai-era-kr" target="_blank">한국어</a>, <a href="https://www.mongodb.com/company/blog/events/local-nyc-2025-defining-ideal-database-for-ai-era-cn" target="_blank">简体中文</a>.</b></p>
</div>	
<p>During the event, we introduced new capabilities that advance MongoDB’s position as the world’s leading modern database. With MongoDB 8.2, our most feature-rich and performant release yet, we are raising the bar for what developers can achieve. We also shared more about our <a href="https://www.mongodb.com/products/platform/ai-search-and-retrieval">Voyage AI</a> embedding models and rerankers, which bring state-of-the-art accuracy and efficiency to building trustworthy, reliable AI applications. And with <a href="https://www.mongodb.com/company/blog/product-release-announcements/supercharge-self-managed-apps-search-vector-search-capabilities">Search and Vector Search now in public preview for both MongoDB Community Edition and Enterprise Server</a>, we are putting powerful retrieval capabilities directly into customers’ environments—wherever they prefer to run.</p>
<p>I am particularly excited about the launch of the <a href="https://www.mongodb.com/company/blog/product-release-announcements/amp-ai-driven-approach-modernization">MongoDB Application Modernization Platform</a>, or AMP. Enterprises everywhere are grappling with the massive costs of legacy systems that cannot support the demands of AI. AMP is not a simple “lift-and-shift.” It is a repeatable, end-to-end platform that combines AI-powered tooling, proven techniques, and specialized talent to reinvent critical business systems while minimizing cost and risk. Early results are impressive: enterprises moving from old systems to MongoDB are doing so two to three times faster, and tasks like code rewriting are accelerating by an order of magnitude.</p>
<center><caption><b>Figure 1.</b> MongoDB.local NYC keynote.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-09-17 at 4.12.30 PM-000u0klcze.png" alt="Photo of the stage for the .local NYC keynote" title=" " style="width: 800px"/>
</div> 
	<figcaption class="fl-center">Watch the&nbsp; <a href="https://www.youtube.com/live/LE8hUTNd2Go?si=GcdvxVoX1w3DRCcg">full keynote</a> &nbsp;on YouTube. </figcaption>
</figure>
<h2>Becoming the world’s most popular modern database</h2>
<p>When I reflect on MongoDB’s journey, I’m struck by how far we’ve come. When I joined just over a decade ago, we had only a few thousand customers. Today, MongoDB serves nearly 60,000 organizations across every industry and vertical, including more than 70% of the Fortune 100 and cutting-edge AI-native startups.</p>
<p>Yet the reason behind our growth remains the same. Relational databases built in the 1970s were never designed for the scale and complexity of modern applications. They were rigid, hard to scale, and slow to adapt. Our founders, who had lived those limitations first-hand while building DoubleClick, set out to create something better: a database model designed for the realities of the modern world. The document model was born.</p>
<p>Based in JSON, the <a href="https://www.mongodb.com/resources/basics/databases/document-databases">document model</a> is intuitive, flexible, and powerful. It allows developers to represent complex, interdependent, and constantly changing data in a natural way. And, as we enter the era of AI, those same qualities—adaptability, scalability, and security—are more critical than ever. The database a company chooses will be one of the most strategic decisions determining the success of its AI initiatives.</p>
<p>Generative AI applications have already begun delivering productivity gains, writing code, drafting documents, and answering questions. But the real transformation lies ahead with <a href="https://www.mongodb.com/resources/basics/artificial-intelligence/ai-agents">agentic AI</a>—applications that perceive, decide, and act. These intelligent agents don’t just follow workflows; they pursue outcomes, reasoning about the best steps to achieve them. And in that loop, the database is indispensable. It provides the memory that allows agents to perceive context, the facts that allow them to decide intelligently, and the state that will enable them to act coherently.</p>
<p>This is why a company’s data is its most valuable asset. <a href="https://www.mongodb.com/resources/basics/artificial-intelligence/large-language-models">Large language models</a> (LLMs) may generate responses, but it is the database that provides continuity, collaboration, and true intelligence. The future of AI is not only about reasoning—it is about context, memory, and the power of your data.</p>
<h2>The ideal database for transformative AI</h2>
<p>So what does the ideal database for agentic AI look like? It must reflect today’s complexity and tomorrow’s change. It must speak the language of AI, which is increasingly JSON. It must integrate advanced retrieval across raw data, metadata, and embeddings—not just exact matching but meaning and intent. It must bridge private data and LLMs with the highest-quality embeddings and rerankers. And it must deliver the performance, scalability, and security required to power mission-critical applications at a global scale.</p>
<p>This is precisely what MongoDB delivers. We don’t simply check the boxes on this list—we define them.</p>
<h2>We’re only just getting started</h2>
<p>That’s why I am so optimistic about our future. The energy and creativity we see at every MongoDB.local event remind me of the passion that has always fueled this company. As our customers continue to innovate, I know MongoDB is in the perfect position to help them succeed in the AI era.</p>
<p>We can’t wait to see what you build next.</p>
<div class="callout">
<p><b>To see more announcements and for the latest product updates, visit our <a href="http://www.mongodb.com/new">What’s New</a> page. And head to the <a href="https://www.mongodb.com/events/mongodb-local">MongoDB.local hub</a> to see where we’ll be next.</b></p>
</div>	]]></description>
      <pubDate>Thu, 18 Sep 2025 12:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/events/local-nyc-2025-defining-ideal-database-for-ai-era</link>
      <guid>https://www.mongodb.com/company/blog/events/local-nyc-2025-defining-ideal-database-for-ai-era</guid>
    </item><item>
      <title>MongoDB.local NYC 2025: Definiendo la base de datos ideal para la era de la IA</title>
      <description><![CDATA[<p>Ayer, dimos la bienvenida a miles de desarrolladores y ejecutivos a MongoDB.local NYC, la última parada en nuestro recorrido global .local series. Durante el último año, nos hemos conectado con decenas de miles de Emparejar y cliente en 20 ciudades de todo el mundo. Sin embargo, es especialmente significativo estar en Nueva York, donde se fundó MongoDB y donde todavía tenemos nuestra sede.</p>
<p>Durante el evento, presentamos nuevas capacidades que refuerzan la posición de MongoDB como la base de datos moderna líder a nivel mundial. Con MongoDB 8.2, nuestra versión más rica en características y de alto rendimiento hasta el momento, estamos elevando el estándar de lo que los desarrolladores pueden lograr. También compartimos más sobre nuestros modelos de incrustación y reclasificación de <a href="https://www.mongodb.com/products/platform/ai-search-and-retrieval">Voyage IA</a>, que aportan precisión y eficiencia de vanguardia a la creación de aplicaciones de IA confiables y fiables. Y con <a href="https://www.mongodb.com/company/blog/product-release-announcements/supercharge-self-managed-apps-search-vector-search-capabilities">la búsqueda y la búsqueda vectorial ahora en vista previa pública tanto para MongoDB Community Edition como para Enterprise Server</a>, estamos incorporando potentes capacidades de recuperación directamente en los entornos de los clientes, dondequiera que prefieran ejecutar.</p>
<p>Estoy particularmente entusiasmado con el <a href="https://www.mongodb.com/company/blog/product-release-announcements/amp-ai-driven-approach-modernization">lanzamiento de la Plataforma de Modernización de Aplicaciones de MongoDB</a>, o AMP. Las empresas de todo el mundo están lidiando con los costos masivos de los sistemas heredados que no pueden soportar las demandas de la IA. AMP no es un simple “traslado y cambio”. Es una plataforma repetible de extremo a extremo que combina herramientas impulsadas por IA, técnicas probadas y talento especializado para reinventar los sistemas críticos de negocio mientras se minimizan los costos y riesgos. Los primeros resultados son impresionantes: las empresas que pasan de sistemas antiguos a MongoDB lo están haciendo dos o tres veces más rápido, y tareas como la reescritura de código se están acelerando en un orden de magnitud.</p>
<center><caption><b>Figura 1.</b> Ponencia de MongoDB.local NYC.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-09-17 at 4.12.30 PM-000u0klcze.png" alt="Photo of the stage for the .local NYC keynote" title=" " style="width: 800px"/>
</div> 
	<figcaption class="fl-center">Vea la presentación completa en&nbsp;<a href="https://www.youtube.com/live/LE8hUTNd2Go?si=GcdvxVoX1w3DRCcg">YouTube</a>.  </figcaption>
</figure>
<h2>Convertirse en la base de datos moderna más popular del mundo</h2>
<p>Cuando reflexiono sobre el recorrido de MongoDB, me sorprende lo lejos que hemos llegado. Cuando me uní hace poco más de una década, solo teníamos unos pocos miles de clientes. Hoy en día, MongoDB sirve a casi 60,000 Organizaciones en todas las industrias y sectores, incluyendo más del 70% de las Fortune 100 y empresas emergentes nativas de IA de vanguardia.</p>
<p>Sin embargo, la razón detrás de nuestro crecimiento sigue siendo la misma. Las relational database creadas en la década de 1970 nunca fueron diseñadas para escalar y la complejidad de las aplicación modernas. Eran rígidos, difíciles de escalar y lentos para adaptarse. Nuestros fundadores, que experimentaron esas limitaciones de primera mano mientras construían DoubleClick, se propusieron crear algo mejor: un modelo de base de datos diseñado para las realidades del mundo moderno. Había nacido el document model.</p>
<p>Basado en JSON, el <a href="https://www.mongodb.com/resources/basics/databases/document-databases">document model</a> es intuitivo, flexible y potente. Permite a los desarrolladores representar datos complejos, interdependientes y en constante cambio de manera natural. Y, a medida que ingresamos en la era de la IA, esas mismas cualidades—adaptabilidad, escalabilidad y seguridad—son más críticas que nunca. La base de datos que elija una empresa será una de las decisiones más estratégicas que determinarán el éxito de sus iniciativas de IA.</p>
<p>Las aplicaciones de IA generativa ya han comenzado a proporcionar mejoras en la productividad, escribiendo código, redactando documentos y respondiendo preguntas. Pero la verdadera transformación está por delante con la <a href="https://www.mongodb.com/resources/basics/artificial-intelligence/ai-agents">IA agente</a>: aplicaciones que perciben, deciden y actúan. Estos agentes inteligentes no solo siguen los flujos de trabajo; persiguen resultados, razonando sobre los mejores pasos para lograrlos. Y en ese ciclo, la base de datos es indispensable. Proporciona la memoria que permite a los agentes percibir el contexto, los hechos que les permiten decidir de manera inteligente, y el estado que les permitirá actuar de forma coherente.</p>
<p>Por eso, los datos de una empresa son su activo más valioso. <a href="https://www.mongodb.com/resources/basics/artificial-intelligence/large-language-models">Los grandes modelos de lenguaje</a> (LLM) pueden generar respuestas, pero es la base de datos la que proporciona continuidad, colaboración y verdadera inteligencia. El futuro de la IA no solo se trata de razonamiento, sino de contexto, memoria y el poder de sus datos.</p>
<h2>La base de datos ideal para la IA transformativa</h2>
<p>Entonces, ¿cómo debería ser la base de datos ideal para la IA agencial? Debe reflejar la complejidad de hoy y el cambio del mañana. Debe hablar el lenguaje de la IA, que cada vez más es JSON. Debe integrar la recuperación avanzada a través de datos sin procesar, metadatos e incrustaciones, no solo de coincidencia exacta, sino también de significado e intención. Debe conectar los datos privados y los LLM con incrustaciones y rerankeadores de la más alta calidad. Y debe ofrecer el rendimiento, la escalabilidad y la seguridad necesarios para impulsar aplicaciones de misión crítica a escala global.</p>
<p>Esto es precisamente lo que ofrece MongoDB. No nos limitamos a marcar las casillas de esta lista; las definimos.</p>
<h2>Apenas estamos comenzando</h2>
<p>Por eso soy tan optimista sobre nuestro futuro. La energía y la creatividad que vemos en cada evento de MongoDB.local me recuerdan la pasión que siempre ha impulsado a esta empresa. A medida que nuestros clientes continúan innovando, sé que MongoDB está en la posición perfecta para ayudarles a tener éxito en la era de la IA.</p>
<p>¡Estamos ansiosos por ver qué desarrollas a continuación!</p>
<div class="callout">
<p><b>Para ver más anuncios y obtener las últimas actualizaciones de productos, visite <a href="https://www.mongodb.com/products/updates/">nuestra página Novedades</a>. Y diríjase al <a href="https://www.mongodb.com/events/mongodb-local">centro MongoDB.local</a> para ver dónde estaremos siguiente.</b></p>
</div>	]]></description>
      <pubDate>Thu, 18 Sep 2025 12:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/events/local-nyc-2025-defining-ideal-database-for-ai-era-es</link>
      <guid>https://www.mongodb.com/company/blog/events/local-nyc-2025-defining-ideal-database-for-ai-era-es</guid>
    </item><item>
      <title>MongoDB.local NYC 2025：定义 AI 时代的理想数据库</title>
      <description><![CDATA[<p>昨天，我们迎来了数千名开发者和高管参加 MongoDB.local NYC，这是我们全球 .local 系列的最新一站。在过去的一年里，我们与全球 20 个城市的数万名合作伙伴和客户建立了联系。而纽约更是意义重大，因为这里是 MongoDB 的诞生地，也是我们的总部所在地。</p>
<p>活动期间，我们推出了新功能，进一步巩固了 MongoDB 作为全球领先现代数据库的地位。MongoDB 8.2 是我们迄今为止功能最丰富、性能最高的版本，我们提高了开发者的能力标准。我们还分享了更多关于 <a href="https://www.mongodb.com/products/platform/ai-search-and-retrieval">Voyage AI</a> 嵌入模型和重排序器的信息，它们为构建值得信赖、可靠的 AI 应用程序带来了最先进的准确性和效率。目前，<a href="https://www.mongodb.com/company/blog/product-release-announcements/supercharge-self-managed-apps-search-vector-search-capabilities">MongoDB Community Edition 和 Enterprise Server 的搜索和向量搜索功能已进入公开预览阶段</a>，我们将强大的检索功能直接应用到客户环境中，无论他们喜欢在哪里运行。</p>
<p>我对 MongoDB 应用程序现代化平台 (<a href="https://www.mongodb.com/company/blog/product-release-announcements/amp-ai-driven-approach-modernization">AMP</a>) 的推出感到特别兴奋。世界各地的企业都在努力应对旧版系统带来的巨额成本问题，因为这些系统无法支持 AI 的需求。AMP 不是简单的“搬运”，而是可重复的端到端平台，结合 AI 驱动的工具、成熟的技术和专业的人才，重塑关键业务系统，同时最大限度地降低成本和风险。早期成果令人印象深刻：企业从旧系统迁移到 MongoDB 的速度提高了两到三倍，代码重写等任务的速度也提高了一个数量级。</p>
<center><caption>图 1.MongoDB.local NYC 主题演讲。</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-09-17 at 4.12.30 PM-000u0klcze.png" alt="Photo of the stage for the .local NYC keynote" title=" " style="width: 800px"/>
</div> 
	<figcaption class="fl-center"><a href="https://www.youtube.com/live/LE8hUTNd2Go?si=GcdvxVoX1w3DRCcg">在 YouTube 上观看完整的主题演讲。</a></figcaption>
</figure>
<h2>成为全球最受欢迎的现代数据库</h2>
<p>当我回顾 MongoDB 的历程时，我对我们所取得的进步感到震惊。十多年前我加入公司时，我们的客户数量只有几千名。如今， MongoDB 为各行业和垂直领域的近 60,000 个组织提供服务，其中包括超过 70% 的 Fortune 100 强企业和尖端 AI 初创企业。</p>
<p>然而，我们成长背后的原因却始终如一。关系数据库诞生于 20 世纪 70 年代，其设计初衷早已无法匹配现代应用程序的扩展性与复杂性。它们死板，难以扩展，适应速度慢。我们的创始人在构建 DoubleClick 时曾深切体会这些局限，从而立志创造更卓越的解决方案：一种专为现代世界现实而设计的数据库模型。文档模型诞生了。</p>
<p><a href="https://www.mongodb.com/resources/basics/databases/document-databases">文档模型</a>基于 JSON，直观、灵活且功能强大。它允许开发者以自然的方式表示复杂、相互依赖且不断变化的数据。而且，随着我们步入 AI 时代，这些品质——适应性、可扩展性与安全性——其重要性空前凸显。公司选择的数据库将是决定其 AI 计划成功与否的最具战略性的决策之一。</p>
<p>生成式人工智能应用程序已经开始提高工作效率，编写代码、草拟文档和回答问题。但真正的变革在于<a href="https://www.mongodb.com/resources/basics/artificial-intelligence/ai-agents">代理 AI</a>——能够感知、决策和行动的应用程序。这些智能代理不仅仅遵循工作流程；它们还追求结果，推理实现结果的最佳步骤。在此过程中，数据库不可或缺。凭借其提供的记忆，代理得以感知上下文；依据提供的事实，从而做出明智决策；再根据当前状态，最终执行出连贯的行动。</p>
<p>这就是为什么公司的数据是其最宝贵的资产。<a href="https://www.mongodb.com/resources/basics/artificial-intelligence/large-language-models">大型语言模型</a> (LLM) 可能会生成响应，但提供连续性、协作和真正智能的是数据库。AI 的未来不仅与推理有关，还与上下文、记忆和数据的力量有关。</p>
<h2>变革性 AI 的理想数据库</h2>
<p>那么，适合代理 AI 的理想数据库是什么样的？必须反映当今的复杂性和未来变化。必须使用 AI 语言，而这种语言越来越多地使用 JSON。必须集成跨原始数据、元数据和嵌入的高级检索——不仅仅是精确匹配，还包括意义和意图。必须通过最高质量的嵌入和重排序器来桥接私人数据和大型语言模型。而且必须提供在全球范围内支持关键任务应用程序所需的性能、可扩展性和安全性。</p>
<p>这正是 MongoDB 所提供的。我们不仅仅是在列表上打勾，而是定义这些标准。</p>
<h2>我们才刚刚入门。</h2>
<p>这就是为什么我对我们的未来如此乐观。我们在每一次 MongoDB.local 活动中亲眼见证的活力与创造力，让我感受到一种与公司发展驱动力一脉相承的激情。随着客户持续推动创新，我确信 MongoDB 能为他们提供在 AI 时代取得成功所需的关键基石。</p>
<p>未来可期，我们携手见证。</p>
<div class="callout">
<p>如需查看更多公告并获取最新产品动态，请访问我们的“<a href="https://www.mongodb.com/products/updates/">最新动态”页面</a>。前往 <a href="https://www.mongodb.com/events/mongodb-local">MongoDB.local</a> 中心，查看我们的下一个行程。</p>
</div>	]]></description>
      <pubDate>Thu, 18 Sep 2025 12:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/events/local-nyc-2025-defining-ideal-database-for-ai-era-cn</link>
      <guid>https://www.mongodb.com/company/blog/events/local-nyc-2025-defining-ideal-database-for-ai-era-cn</guid>
    </item><item>
      <title>MongoDB.local NYC 2025 : définir la base de données idéale à l&#39;ère de l&#39;IA</title>
      <description><![CDATA[<p>Hier, nous avons accueilli des milliers de développeurs et de cadres à MongoDB.local NYC, la dernière étape de notre tournée mondiale .local. Cette année, nous avons rencontré des dizaines de milliers de partenaires et de clients dans 20 villes à travers le monde. Mais pour nous, être à New York a une saveur particulière, car c'est la ville où MongoDB a été fondée et où nous avons toujours notre siège social.</p>
<p>Lors de cet événement, nous avons présenté de nouvelles fonctionnalités qui renforcent la position de MongoDB en tant que principale base de données moderne au monde. Avec MongoDB 8.2, notre version la plus riche en fonctionnalités et la plus performante à ce jour, nous mettons la barre encore plus haut sur ce que les développeurs peuvent accomplir. Nous avons également partagé plus d'informations sur nos modèles d'intégration et de reclassement <a href="https://www.mongodb.com/products/platform/ai-search-and-retrieval">Voyage AI</a>, qui apportent une précision et une efficacité de pointe à la création d'applications d'IA fiables. Et alors que <a href="https://www.mongodb.com/company/blog/product-release-announcements/supercharge-self-managed-apps-search-vector-search-capabilities">Search et Vector Search sont désormais disponibles au public pour MongoDB Community Edition et Enterprise Server</a>, nous mettons de puissantes capacités de récupération directement dans les environnements des clients, quels qu'ils soient.</p>
<p>Je suis particulièrement ravi du lancement de la <a href="https://www.mongodb.com/company/blog/product-release-announcements/amp-ai-driven-approach-modernization">plateforme de modernisation des applications de MongoDB</a>, ou AMP. Partout, les entreprises sont confrontées aux coûts considérables des systèmes hérités qui ne peuvent pas supporter les exigences de l'IA. L’AMP n’est pas un simple « lift-and-shift ». Il s'agit d'une plateforme reproductible et de bout en bout qui combine des outils alimentés par l'IA, des techniques éprouvées et des talents spécialisés pour réinventer les systèmes d'entreprise critiques tout en minimisant les coûts et les risques. Les premiers résultats sont impressionnants : les entreprises qui migrent d’anciens systèmes vers MongoDB le font deux à trois fois plus vite, et des tâches comme la réécriture de code gagnent en rapidité.</p>
<center><caption><b>Figure 1.</b> Conférence keynote de MongoDB.local NYC.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-09-17 at 4.12.30 PM-000u0klcze.png" alt="Photo of the stage for the .local NYC keynote" title=" " style="width: 800px"/>
</div> 
	<figcaption class="fl-center">Regardez l'intégralité de la&nbsp;<a href="https://www.youtube.com/live/LE8hUTNd2Go?si=GcdvxVoX1w3DRCcg">keynote</a>&nbsp;sur YouTube.</a> 
	</figcaption>
</figure>
<h2>Devenir la base de données moderne la plus populaire au monde</h2>
<p>Lorsque je repense au parcours de MongoDB, je suis frappé par tout le chemin parcouru. Lorsque j'ai rejoint l'entreprise il y a un peu plus de dix ans, nous n'avions que quelques milliers de clients. Aujourd'hui, MongoDB est utilisé par près de 60 000 organisations tous secteurs confondus, dont plus de 70 % des entreprises du Fortune 100 et des startups de pointe natives de l'IA.</p>
<p>Pourtant, la raison de notre croissance reste la même. Les relational database créées dans les années 1970 n’ont jamais été conçues pour l'envergure et la complexité des applications modernes. Elles étaient rigides, difficiles à répartir et lentes à s’adapter. Nos fondateurs, qui avaient connu ces limitations lors de la création de DoubleClick, se sont mis en tête de créer quelque chose de mieux : un modèle de base de données conçu pour les réalités du monde moderne. Le document model est né.</p>
<p>Basé sur JSON, le <a href="https://www.mongodb.com/resources/basics/databases/document-databases">document model</a> est intuitif, flexible et puissant. Il permet aux développeurs de représenter de manière naturelle des données complexes, interdépendantes et en constante évolution. Et, alors que nous entrons dans l'ère de l'IA, ces mêmes qualités — adaptabilité, évolutivité et sécurité — sont plus essentielles que jamais. La base de données choisie par une entreprise sera l'une des décisions les plus stratégiques pouvant déterminer la réussite de ses initiatives en matière d'IA.</p>
<p>Les applications d'IA générative ont déjà commencé à générer des gains de productivité, en écrivant du code, en rédigeant des documents et en répondant aux questions. Mais la véritable transformation se trouve dans <a href="https://www.mongodb.com/resources/basics/artificial-intelligence/ai-agents">l'IA agentique</a> — des applications qui perçoivent, décident et agissent. Ces agents intelligents ne suivent pas seulement les flux de travail ; ils recherchent des résultats et réfléchissent aux meilleures étapes pour les atteindre. Et dans cette boucle, la base de données est indispensable. Elle fournit la mémoire qui permet aux agents de percevoir le contexte, les faits qui leur permettent de décider intelligemment et l'état qui leur permettra d'agir de manière cohérente.</p>
<p>C'est pourquoi les données d'une entreprise sont l'actif le plus précieux qu'elle ait. Les <a href="https://www.mongodb.com/resources/basics/artificial-intelligence/large-language-models">Large Language Models</a> (grands modèles de langage) peuvent générer des réponses, mais c'est la base de données qui assure la continuité, la collaboration et la véritable intelligence. L'avenir de l'IA ne se limite pas au raisonnement, il concerne également le contexte, la mémoire et la puissance de vos données.</p>
<h2>La base de données idéale pour une IA transformatrice</h2>
<p>À quoi ressemble donc la base de données idéale pour l'IA agentique ? Elle doit refléter la complexité d'aujourd'hui et les changements de demain. Elle doit parler la langue de l’IA, qui est de plus en plus JSON. Elle doit intégrer une récupération avancée des données brutes, des métadonnées et des intégrations, non seulement les correspondances exactes, mais aussi la signification et l'intention. Elle doit faire le lien entre les données privées et les LLM avec des intégrations et des reclassements de la plus haute qualité. Et elle doit offrir les performances, l’évolutivité et la sécurité nécessaires pour alimenter les applications critiques à l’échelle mondiale.</p>
<p>C'est précisément ce que propose MongoDB. Nous ne nous contentons pas de cocher les cases de cette liste — nous les créons.</p>
<h2>Et ce n'est que le début</h2>
<p>C’est pourquoi l'avenir me rend très optimiste. L’énergie et la créativité que nous voyons à chaque événement MongoDB.local me rappellent la passion qui a toujours alimenté cette entreprise. Alors que nos clients continuent d’innover, je sais que MongoDB est idéalement placée pour les aider à réussir à l’ère de l’IA.</p>
<p>Nous avons hâte de voir vos créations !</p>
<div class="callout">
<p><b>Pour voir d’autres annonces et consulter les dernières mises à jour de produits, accédez à notre page « <a href="https://www.mongodb.com/products/updates/">Nouveautés</a> ». Et rendez-vous sur le hub <a href="https://www.mongodb.com/events/mongodb-local">MongoDB.local</a> pour voir où nous serons prochainement.</b></p>
</div>	]]></description>
      <pubDate>Thu, 18 Sep 2025 12:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/events/local-nyc-2025-defining-ideal-database-for-ai-era-fr</link>
      <guid>https://www.mongodb.com/company/blog/events/local-nyc-2025-defining-ideal-database-for-ai-era-fr</guid>
    </item><item>
      <title>MongoDB.local NYC 2025: Definindo o Banco de Dados Ideal para a Era da IA</title>
      <description><![CDATA[<p>Ontem, demos as boas-vindas a milhares de desenvolvedores e executivos no MongoDB.local NYC, a mais recente parada do nosso .local séries. Ao longo do último ano, conectamos-nos com dezenas de milhares de parceiros e clientes em 20 cidades ao redor do mundo. Mas é especialmente significativo estar em Nova York, onde o MongoDB foi fundado e onde ainda temos nossa sede.</p>
<p>Durante o evento, apresentamos novas capacidades que reforçam a posição do MongoDB como o principal banco de dados moderno do mundo. Com o MongoDB 8.2, nossa versão mais rica em recursos e de melhor desempenho até agora, estamos elevando o padrão do que os desenvolvedores podem alcançar. Também compartilhamos mais sobre nossos modelos de incorporação e reclassificação da <a href="https://www.mongodb.com/products/platform/ai-search-and-retrieval">Voyage AI</a>, que trazem precisão e eficiência de última geração para a criação de aplicativos de IA confiáveis e seguros. E com a <a href="https://www.mongodb.com/company/blog/product-release-announcements/supercharge-self-managed-apps-search-vector-search-capabilities">pesquisa e a pesquisa vetorial agora em visualização pública para o MongoDB Community Edition e o Enterprise Server</a>, estamos colocando poderosas funcionalidades de recuperação diretamente nos ambientes dos clientes—onde quer que eles prefiram executar.</p>
<p>Estou particularmente entusiasmado com o lançamento da <a href="https://www.mongodb.com/company/blog/product-release-announcements/amp-ai-driven-approach-modernization">Plataforma de Modernização de Aplicativos MongoDB</a>, ou AMP. Empresas em todo o mundo estão lidando com os custos massivos dos sistemas legados que não conseguem dar suporte às demandas da IA. AMP não é um simples &quot;lift-and-shift&quot;. É uma plataforma repetível e de ponta a ponta que combina ferramentas impulsionadas por IA, técnicas comprovadas e talento especializado para reinventar sistemas críticos de negócios, minimizando custos e riscos. Os primeiros resultados são impressionantes: as empresas que estão migrando de sistemas antigos para o MongoDB estão fazendo isso de duas a três vezes mais rápido, e tarefas como a reescrita de código estão acelerando em uma ordem de magnitude.</p>
<center><caption><b>Figura 1.</b> Palestra principal do MongoDB.local NYC.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-09-17 at 4.12.30 PM-000u0klcze.png" alt="Photo of the stage for the .local NYC keynote" title=" " style="width: 800px"/>
</div> 
	<figcaption class="fl-center">Assista à palestra completa no&nbsp;<a href="https://www.youtube.com/live/LE8hUTNd2Go?si=GcdvxVoX1w3DRCcg">YouTube</a>. </figcaption>
</figure>
<h2>Tornar-se o banco de dados moderno mais popular do mundo.</h2>
<p>Ao refletir sobre a jornada do MongoDB, fico impressionado com o quanto avançamos. Quando entrei há pouco mais de uma década, tínhamos apenas alguns milhares de clientes. Hoje, o MongoDB serve a quase 60.000 organizações em todos os setores e verticais, incluindo mais de 70% das empresas da Fortune 100 e inicializações nativas de IA de ponta.</p>
<p>No entanto, a razão por trás do nosso crescimento permanece a mesma. Os relational database criados na década de 1970 nunca foram projetados para dimensionar a escala e complexidade dos aplicativo modernos. Eles eram rígidos, difíceis de dimensionar e lentos para se adaptar. Nossos fundadores, que vivenciaram essas limitações em primeira mão ao construir a DoubleClick, decidiram criar algo melhor: um modelo de banco de dados projetado para as realidades do mundo moderno. O modelo de documento foi criado.</p>
<p>Baseado em JSON, o <a href="https://www.mongodb.com/resources/basics/databases/document-databases">modelo de documento</a> é intuitivo, flexível e poderoso. Ele permite que os desenvolvedores representem dados complexos, interdependentes e em constante mudança de maneira natural. E, ao entrarmos na era da IA, essas mesmas qualidades — adaptabilidade, escalabilidade e segurança — são mais críticas do que nunca. O banco de dados que uma empresa escolhe será uma das decisões mais estratégicas que determinarão o sucesso de suas iniciativas de IA.</p>
<p>Os aplicativos de IA generativa já começaram a oferecer ganhos de produtividade, escrever código, elaborar documentos e responder a perguntas. Mas a verdadeira transformação está por vir com a <a href="https://www.mongodb.com/resources/basics/artificial-intelligence/ai-agents">IA agêntica</a> — aplicativos que percebem, decidem e agem. Esses agentes inteligentes não apenas seguem fluxos de trabalho; eles buscam resultados, raciocinando sobre as melhores etapas para alcançá-los. E nesse loop, o banco de dados é indispensável. Ela fornece a memória que permite aos agentes perceberem o contexto, os fatos que lhes permitem decidir de forma inteligente e o estado que lhes permitirá agir de forma coerente.</p>
<p>É por isso que os dados de uma empresa são seu ativo mais valioso. LLM (<a href="https://www.mongodb.com/resources/basics/artificial-intelligence/large-language-models">LLMs</a>) podem gerar respostas, mas é o banco de dados que fornece continuidade, colaboração e verdadeira inteligência. O futuro da IA não é apenas sobre raciocínio—é sobre contexto, memória e o poder dos seus dados.</p>
<h2>O banco de dados ideal para IA transformativa</h2>
<p>Então, como é o banco de dados ideal para IA agentic? Deve refletir a complexidade de hoje e as mudanças de amanhã. Deve falar a linguagem da IA, que é cada vez mais JSON. Ele deve integrar a recuperação avançada de dados brutos, metadados e embeddings — não apenas a correspondência exata, mas também o significado e a intenção. Ele deve conectar dados privados e LLM com incorporações e reclassificadores da mais alta qualidade. E deve fornecer o desempenho, a escalabilidade e a segurança necessários para suportar aplicativos de missão crítica em um dimensionamento global.</p>
<p>Isso é precisamente o que o MongoDB entrega. Nós não apenas marcamos as caixas desta lista — nós as definimos.</p>
<h2>Estamos apenas dando os primeiros passos</h2>
<p>É por isso que estou tão otimista quanto ao nosso futuro. A energia e a criatividade que vemos em todos os eventos do MongoDB.local me lembram da paixão que sempre impulsionou esta empresa. À medida que nossos clientes continuam a inovar, sei que o MongoDB está na posição ideal para ajudá-los a prosperar na era da IA.</p>
<p>Mal podemos esperar para ver suas próximas criações.</p>
<div class="callout">
<p><b>Para ver mais anúncios e as atualizações mais recentes do produto, visite nossa página <a href="https://www.mongodb.com/products/updates/">Novidades</a>. E vá para o <a href="https://www.mongodb.com/events/mongodb-local">hub MongoDB.local</a> para ver onde estaremos em seguida.</b></p>
</div>	]]></description>
      <pubDate>Thu, 18 Sep 2025 12:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/events/local-nyc-2025-defining-ideal-database-for-ai-era-br</link>
      <guid>https://www.mongodb.com/company/blog/events/local-nyc-2025-defining-ideal-database-for-ai-era-br</guid>
    </item><item>
      <title>MongoDB.local NYC 2025: AI 시대를 위한 이상적인 데이터베이스 정의</title>
      <description><![CDATA[<p>어제, 글로벌 .local 시리즈의 최신 목적지인 MongoDB.local NYC에서 수천 명의 개발자와 경영진을 맞이했습니다. 지난 1년 동안 저희는 전 세계 20개 도시의 수만 명의 제휴하다와 고객과 소통했습니다. 하지만 MongoDB 본사가 설립되었고 지금도 본사가 있는 뉴욕에서 개최하게 되어 더욱 뜻깊습니다.</p>
<p>이번 이벤트에서는 세계 최고의 최신 데이터베이스로서 MongoDB의 입지를 더욱 강화하는 새로운 역량을 소개했습니다. MongoDB 8.2는 역대 가장 기능이 풍부하고 성능이 뛰어난 릴리스로, 개발자가 달성할 수 있는 목표의 기준을 한층 더 높이고 있습니다. 또한 신뢰할 수 있고 안정적인 AI 애플리케이션 구축에 최첨단 정확성과 효율성을 제공하는 <a href="https://www.mongodb.com/products/platform/ai-search-and-retrieval">Voyage AI</a> 임베딩 모델과 리랭커에 대한 자세한 내용도 공유했습니다. 또한 검색 및 벡터 검색이 이제 <a href="https://www.mongodb.com/company/blog/product-release-announcements/supercharge-self-managed-apps-search-vector-search-capabilities">MongoDB Community Edition과 Enterprise Server에 대한 공개 프리뷰로 제공됨에 따라 고객이 원하는 운영 환경 어디에서나 강력한 검색 역량을 직접 활용할 수 있게 되었습니다</a>.</p>
<p>저는 특히 MongoDB 애플리케이션 현대화 플랫폼(<a href="https://www.mongodb.com/company/blog/product-release-announcements/amp-ai-driven-approach-modernization">AMP</a>)의 출시에 대해 매우 기대하고 있습니다. 모든 엔터프라이즈는 AI 의 요구 사항을 지원할 수 없는 레거시 시스템의 막대한 비용으로 인해 어려움을 겪고 있습니다. AMP는 단순한 &quot;리프트 앤 시프트&quot;가 아닙니다. AI 기반 도구, 검증된 기술, 전문 인력을 결합하여 비용과 위험을 최소화하면서 중요한 비즈니스 시스템을 재창조하는 반복 가능한 엔드투엔드 플랫폼입니다. 초기 결과는 인상적입니다. 구형 시스템에서 MongoDB로 전환하는 엔터프라이즈는 2~3배 더 빠르게 전환하고 있으며 코드 재작성 같은 작업의 속도가 엄청나게 빨라지고 있습니다.</p>
<center><caption>그림 1. MongoDB.local NYC 기조연설.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-09-17 at 4.12.30 PM-000u0klcze.png" alt="Photo of the stage for the .local NYC keynote" title=" " style="width: 800px"/>
</div> 
	<figcaption class="fl-center"><a href="https://www.youtube.com/live/LE8hUTNd2Go?si=GcdvxVoX1w3DRCcg">YouTube</a>에서 기조연설 전문을 시청하세요.</figcaption>
</figure>
<h2>세계에서 가장 인기 있는 현대 데이터베이스가 되다</h2>
<p>MongoDB의 여정을 되돌아보면 저희가 얼마나 멀리 왔는지 놀라움을 금할 수 없습니다. 제가 10여 년 전에 입사했을 때는 고객이 수천 명에 불과했습니다. 오늘날 MongoDB는 Fortune 100대 기업 중 70% 이상과 최첨단 AI 네이티브 스타트업을 포함해 모든 산업과 업종에 걸쳐 거의 60,000개 조직에 서비스를 제공하고 있습니다.</p>
<p>하지만 성장의 원동력은 여전히 변함이 없습니다. 1970년대에 구축된 관계형 데이터베이스는 현대 애플리케이션의 규모와 복잡성에 맞게 설계되지 않았습니다. 경직되어 있고 확장하기 어려우며 적응 속도가 느렸습니다. DoubleClick을 구축하면서 이러한 한계를 직접 경험한 창립자들은 현대 세계의 현실에 맞춰 설계한 더욱 개선된 데이터베이스 모델을 설정했습니다. 바로 문서 모델이 탄생한 것입니다.</p>
<p>JSON을 기반으로 하는 문서 모델은 직관적이고 유연하며 강력합니다. 이를 통해 개발자는 복잡하고 상호 의존적이며 끊임없이 변화하는 데이터를 자연스럽게 표현할 수 있습니다. 그리고 AI 시대에 접어들면서 이러한 적응성, 확장성, 보안과 같은 자질은 그 어느 때보다 중요해졌습니다. 기업이 선택하는 데이터베이스는 AI 이니셔티브의 성공을 결정하는 가장 전략적인 결정 중 하나가 될 것입니다.</p>
<p>생성형 인공지능 애플리케이션은 이미 생산성 향상, 코드 작성, 문서 초안 작성, 질문에 대한 답변 등을 제공하기 시작했습니다. 하지만 진정한 변화는 인지하고, 결정하고, 행동하는 <a href="https://www.mongodb.com/resources/basics/artificial-intelligence/ai-agents">에이전트 AI</a> 애플리케이션에 있습니다. 이러한 지능형 에이전트는 단순히 워크플로를 따르는 것이 아니라 결과를 추구하고 이를 달성하기 위한 최선의 단계를 추론합니다. 이 과정에서 데이터베이스는 필수 불가결한 요소입니다. 에이전트가 컨텍스트를 인식할 수 있는 메모리, 지능적으로 판단할 수 있는 사실, 일관성 있게 행동할 수 있는 상태를 제공합니다.</p>
<p>그렇기 때문에 기업의 데이터는 가장 소중한 자산입니다. 거대 언어 모델(<a href="https://www.mongodb.com/resources/basics/artificial-intelligence/large-language-models">LLM</a>)은 응답을 생성할 수 있지만, 연속성, 협업 및 진정한 인텔리전스를 제공하는 것은 데이터베이스입니다. AI의 미래는 단순히 추론에 관한 것이 아닙니다. 그것은 컨텍스트, 메모리, 그리고 데이터의 힘에 관한 것입니다.</p>
<h2>혁신적인 AI를 위한 이상적인 데이터베이스</h2>
<p>그렇다면 에이전트 AI에 이상적인 데이터베이스는 어떤 모습일까요? 오늘날의 복잡성과 미래의 변화를 반영해야 합니다. AI 언어인 JSON을 사용하는 경우가 늘어나고 있습니다. 원시 데이터, 메타데이터, 임베딩에 걸쳐 정확한 검색뿐 아니라 의미와 의도까지 통합하는 고급 검색 기능을 제공해야 합니다. 개인 데이터와 LLM을 최고 품질의 임베딩 및 리랭커와 연결해야 합니다. 또한 전 세계적으로 미션 크리티컬 애플리케이션을 지원하는 데 필요한 성능, 확장성 및 보안을 제공해야 합니다.</p>
<p>이것이 바로 MongoDB가 제공하는 것입니다. 저희는 이 목록의 항목을 단순히 체크하는 것이 아니라, 직접 정의합니다.</p>
<h2>이제 시작에 불과합니다</h2>
<p>이것이 제가 우리의 미래에 대해 매우 낙관적인 이유입니다. 모든 MongoDB.local 이벤트에서 볼 수 있는 에너지와 창의성은 항상 이 회사의 원동력이 되어 온 열정을 떠올리게 합니다. 고객이 혁신을 거듭하는 가운데, 저는 MongoDB가 AI 시대에서 고객의 성공을 도울 수 있는 완벽한 위치에 있다고 확신합니다.</p>
<p>여러분이 다음 어떤 제품을 빌드할지 정말 기대됩니다.</p>
<div class="callout">
<p>더 많은 공지 사항을 확인하고 최신 제품 업데이트를 받으려면 새로운 기능 페<a href="https://www.mongodb.com/products/updates/">이지</a>를 방문하세요. <a href="https://www.mongodb.com/events/mongodb-local">MongoDB.local</a> 허브로 이동하여 다음 행사가 진행되는 도시를 확인해 보세요.</p>
</div>	]]></description>
      <pubDate>Thu, 18 Sep 2025 12:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/events/local-nyc-2025-defining-ideal-database-for-ai-era-kr</link>
      <guid>https://www.mongodb.com/company/blog/events/local-nyc-2025-defining-ideal-database-for-ai-era-kr</guid>
    </item><item>
      <title>MongoDB.local NYC 2025: Definition der idealen Datenbank für das KI-Zeitalter</title>
      <description><![CDATA[<p>Gestern haben wir Tausende von Entwicklern und Führungskräften bei MongoDB.local NYC begrüßt, der jüngsten Station unserer globalen .local -Reihe. Im vergangenen Jahr haben wir Kontakte zu Zehntausenden von Partnern und Kunden in 20 Städten weltweit geknüpft. Aber es ist besonders bedeutsam, in New York zu sein – wo MongoDB gegründet wurde und wo wir immer noch unseren Hauptsitz haben.</p>
<p>Während der Veranstaltung haben wir neue Funktionen vorgestellt, die die Position von MongoDB als weltweit führende moderne Datenbank weiter stärken. Mit MongoDB 8.2, unserer bisher funktionsreichsten und leistungsstärksten Version, setzen wir neue Maßstäbe für das, was Entwickler erreichen können. Wir haben auch mehr über unsere <a href="https://www.mongodb.com/products/platform/ai-search-and-retrieval">Voyage-AI</a>-Einbettungsmodelle und Reranker erzählt, die für höchste Genauigkeit und Effizienz bei der Entwicklung vertrauenswürdiger, zuverlässiger KI-Anwendungen sorgen. Und da <a href="https://www.mongodb.com/company/blog/product-release-announcements/supercharge-self-managed-apps-search-vector-search-capabilities">Search und Vector Search jetzt sowohl für die MongoDB Community Edition als auch für den Enterprise Server</a> in der öffentlichen Vorschauversion verfügbar sind, stellen wir leistungsstarke Abruffunktionen direkt in die Kundenumgebungen zur Verfügung – wo auch immer sie bevorzugt eingesetzt werden.</p>
<p>Ich freue mich besonders über die <a href="https://www.mongodb.com/company/blog/product-release-announcements/amp-ai-driven-approach-modernization">Einführung der MongoDB-Plattform für die Modernisierung von Anwendungen</a> (AMP). Unternehmen auf der ganzen Welt kämpfen mit den enormen Kosten von Legacy-Systemen, die den Anforderungen der KI nicht gerecht werden können. AMP ist kein einfaches „Lift-and-Shift“. Es handelt sich um eine wiederholbare, durchgängige Plattform, die KI-gestützte Tools, bewährte Techniken und spezialisierte Talente kombiniert, um kritische Geschäftssysteme neu zu gestalten und gleichzeitig Kosten und Risiken zu minimieren. Die ersten Ergebnisse sind beeindruckend: Unternehmen, die von alten Systemen auf MongoDB umsteigen, tun dies zwei- bis dreimal schneller, und Aufgaben wie das Umschreiben von Code beschleunigen sich um ein Vielfaches.</p>
<center><caption><b>Abbildung 1:</b> Keynote MongoDB.local NYC.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-09-17 at 4.12.30 PM-000u0klcze.png" alt="Photo of the stage for the .local NYC keynote" title=" " style="width: 800px"/>
</div> 
	<figcaption class="fl-center">Sehen Sie sich die ganze&nbsp;<a href="https://www.youtube.com/live/LE8hUTNd2Go?si=GcdvxVoX1w3DRCcg">Keynote</a>&nbsp;auf YouTube an.</figcaption>
</figure>
<h2>Entwicklung zur weltweit beliebtesten modernen Datenbank</h2>
<p>Wenn ich über die Reise von MongoDB nachdenke, fällt mir auf, wie weit wir gekommen sind. Als ich vor etwas mehr als einem Jahrzehnt dazukam, hatten wir nur ein paar tausend Kunden. Heute betreut MongoDB fast 60.000 Organisationen aus allen Branchen und Sektoren, darunter mehr als 70 % der Fortune-100-Unternehmen und innovative KI-native Startups.</p>
<p>Doch der Grund für unser Wachstum bleibt derselbe. Relationale Datenbanken, die in den 1970er Jahren entwickelt wurden, waren nie für die Skalierung und Komplexität moderner Anwendungen ausgelegt. Sie waren starr, schwer zu skalieren und ließen sich nur langsam anpassen. Unsere Gründer, die diese Einschränkungen beim Aufbau von DoubleClick aus erster Hand erlebt hatten, machten sich daran, etwas Besseres zu schaffen: ein Datenbankmodell, das auf die Realitäten der modernen Welt zugeschnitten ist. Das Dokumentmodell war geboren.</p>
<p>Das auf JSON basierende <a href="https://www.mongodb.com/resources/basics/databases/document-databases">Dokumentmodell</a> ist intuitiv, flexibel und leistungsstark. Es ermöglicht Entwicklern, komplexe, voneinander abhängige und sich ständig ändernde Daten auf natürliche Weise abzubilden. Und mit dem Eintritt in das Zeitalter der KI sind genau diese Eigenschaften – Anpassungsfähigkeit, Skalierbarkeit und Sicherheit – wichtiger denn je. Die Wahl der Datenbank durch ein Unternehmen ist eine der strategischsten Entscheidungen, die den Erfolg seiner KI-Initiativen bestimmen.</p>
<p>Anwendungen der generativen KI haben bereits Produktivitätssteigerungen gebracht, indem sie Code schreiben, Dokumente entwerfen und Fragen beantworten. Doch die eigentliche Transformation steht uns mit der <a href="https://www.mongodb.com/resources/basics/artificial-intelligence/ai-agents">agentenbasierten KI</a> bevor – Anwendungen, die wahrnehmen, entscheiden und handeln. Diese intelligenten Agenten befolgen nicht einfach nur Arbeitsabläufe, sondern streben nach Ergebnissen und überlegen, welche Schritte am besten geeignet sind, um diese zu erreichen. Und in diesem Kreislauf ist die Datenbank unverzichtbar. Sie liefert das Gedächtnis, das es den Agenten ermöglicht, Zusammenhänge wahrzunehmen, die Fakten, die es ihnen erlauben, intelligente Entscheidungen zu treffen, und den Zustand, der sie in die Lage versetzt, kohärent zu handeln.</p>
<p>Deshalb sind die Daten eines Unternehmens sein wertvollstes Gut. <a href="https://www.mongodb.com/resources/basics/artificial-intelligence/large-language-models">Large Language Models</a> (LLMs) können Antworten generieren, aber es ist die Datenbank, die Kontinuität, Zusammenarbeit und wahre Intelligenz bietet. Die Zukunft der KI liegt nicht nur im logischen Denken, sondern auch im Kontext, im Gedächtnis und in der Macht Ihrer Daten.</p>
<h2>Die ideale Datenbank für transformative KI</h2>
<p>Wie sieht also die ideale Datenbank für agentenbasierte KI aus? Sie muss die Komplexität von heute und den Wandel von morgen widerspiegeln. Sie muss die Sprache der KI sprechen, die zunehmend JSON ist. Sie muss eine fortschrittliche Abfrage von Rohdaten, Metadaten und Einbettungen integrieren – nicht nur einen exakten Abgleich, sondern auch Bedeutung und Absicht. Sie muss private Daten und Large Language Models mit Einbettungen und Rerankern höchster Qualität verbinden. Und sie muss die Leistung, Skalierbarkeit und Sicherheit bieten, die für den Betrieb von unternehmenskritischen Anwendungen auf globaler Skala erforderlich sind.</p>
<p>Genau das bietet MongoDB. Wir haken nicht einfach die Punkte auf dieser Liste ab – wir definieren sie.</p>
<h2>Wir stehen noch ganz am Anfang</h2>
<p>Deshalb bin ich für unsere Zukunft so optimistisch. Die Energie und Kreativität, die wir bei jedem MongoDB.local-Event sehen, erinnern mich an die Leidenschaft, die dieses Unternehmen schon immer angetrieben hat. Da unsere Kunden weiterhin innovativ sind, weiß ich, dass MongoDB in der perfekten Position ist, um ihnen im Zeitalter der KI zum Erfolg zu verhelfen.</p>
<p>Wir können es kaum erwarten zu sehen, was Sie als Nächstes entwickeln.</p>
<div class="callout">
<p><b>Weitere Ankündigungen und die neuesten Produktaktualisierungen finden Sie auf unserer Seite „<a href="https://www.mongodb.com/products/updates/">What's New</a>“. Und besuchen Sie den Hub von <a href="https://www.mongodb.com/events/mongodb-local">MongoDB.local</a>, um zu sehen, wo wir als nächstes Halt machen werden.</b></p>
</div>	]]></description>
      <pubDate>Thu, 18 Sep 2025 12:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/events/local-nyc-2025-defining-ideal-database-for-ai-era-de</link>
      <guid>https://www.mongodb.com/company/blog/events/local-nyc-2025-defining-ideal-database-for-ai-era-de</guid>
    </item><item>
      <title>MongoDB.local NYC 2025: Definire il database ideale per l&#39;era dell&#39;AI</title>
      <description><![CDATA[<p>Ieri abbiamo accolto migliaia di sviluppatori e dirigenti a MongoDB.local NYC, l'ultima tappa del nostro tour globale della serie .local . Nel corso dell'ultimo anno, ci siamo connessi con decine di migliaia di partner e clienti in 20 città in tutto il mondo. Ma è particolarmente significativo essere a New York, dove MongoDB è stata fondata e dove abbiamo ancora la sede centrale.</p>
<p>Durante l'evento, abbiamo introdotto nuove funzionalità che rafforzano la posizione di MongoDB come il principale database moderno a livello mondiale. Con MongoDB 8.2, la nostra versione più ricca di funzionalità e prestazioni, stiamo alzando il livello di ciò che gli sviluppatori possono ottenere. Abbiamo anche condiviso ulteriori informazioni sui nostri modelli di embedding e reranker di <a href="https://www.mongodb.com/products/platform/ai-search-and-retrieval">Voyage AI</a>, che offrono accuratezza ed efficienza all'avanguardia per la creazione di applicazioni AI affidabili e sicure. E con <a href="https://www.mongodb.com/company/blog/product-release-announcements/supercharge-self-managed-apps-search-vector-search-capabilities">Search e Vector Search ora disponibili in public preview sia per MongoDB Community Edition che per Enterprise Server</a>, stiamo inserendo potenti funzionalità di recupero direttamente negli ambienti dei clienti, ovunque preferiscano operare.</p>
<p>Sono particolarmente entusiasta del lancio della <a href="https://www.mongodb.com/company/blog/product-release-announcements/amp-ai-driven-approach-modernization">MongoDB Application Modernization Platform</a>, o AMP. Le aziende di tutto il mondo sono alle prese con gli enormi costi dei sistemi legacy che non sono in grado di supportare le esigenze dell'AI. L'AMP non è un semplice &quot;lift-and-shift&quot;. Si tratta di una piattaforma end-to-end ripetibile che combina strumenti basati sull'AI, tecniche collaudate e talenti specializzati per reinventare i sistemi aziendali critici riducendo al minimo i costi e i rischi. I primi risultati sono impressionanti: le aziende che passano dai vecchi sistemi a MongoDB lo fanno da due a tre volte più velocemente, e attività come la riscrittura del codice stanno accelerando di un ordine di grandezza.</p>
<center><caption><b>Figura 1.</b> Discorso principale al MongoDB.local New York.</center></caption>
<figure>
<div class="fl-center">
<img src="https://webassets.mongodb.com/_com_assets/cms/Screenshot 2025-09-17 at 4.12.30 PM-000u0klcze.png" alt="Photo of the stage for the .local NYC keynote" title=" " style="width: 800px"/>
</div> 
	<figcaption class="fl-center">Guarda il discorso principale completo su&nbsp;<a href="https://www.youtube.com/live/LE8hUTNd2Go?si=GcdvxVoX1w3DRCcg">YouTube</a>. </figcaption>
</figure>
<h2>Diventare il database moderno più popolare al mondo</h2>
<p>Quando rifletto sul percorso di MongoDB, sono colpito da quanto lontano siamo arrivati. Quando sono entrato a far parte dell'azienda poco più di dieci anni fa, avevamo solo poche migliaia di clienti. Oggi, MongoDB serve quasi 60.000 organizzazioni in ogni settore e ambito industriale, inclusi oltre il 70% delle aziende Fortune 100 e startup all'avanguardia native dell'AI.</p>
<p>Tuttavia, il motivo alla base della nostra crescita rimane invariato. I relational database creati negli anni '70 non sono stati progettati per la scalabilità e la complessità delle applicazioni moderne. Erano rigidi, difficili da scalare e lenti ad adattarsi. I nostri fondatori, che avevano vissuto in prima persona questi limiti durante la creazione di DoubleClick, si sono messi all'opera per creare qualcosa di meglio: un modello di database progettato per le realtà del mondo moderno. Così è nato il document model.</p>
<p>Basato su JSON, il <a href="https://www.mongodb.com/resources/basics/databases/document-databases">document model</a> è intuitivo, flessibile e potente. Permette agli sviluppatori di rappresentare dati complessi, interdipendenti e in continua evoluzione in modo naturale. E, mentre entriamo nell'era dell'AI, quelle stesse qualità, ovvero adattabilità, scalabilità e sicurezza, sono più importanti che mai. Il database scelto da un'azienda sarà una delle decisioni più strategiche che determinerà il successo delle sue iniziative legate all'AI.</p>
<p>Le applicazioni di Generative AI hanno già iniziato a migliorare la produttività, a scrivere codice, a redigere documenti e a rispondere alle domande. Ma la vera trasformazione sta <a href="https://www.mongodb.com/resources/basics/artificial-intelligence/ai-agents">nell'AI agentica</a>: applicazioni che percepiscono, decidono e agiscono. Questi agenti intelligenti non seguono solo i flussi di lavoro: perseguono i risultati, ragionando sui passi migliori per raggiungerli. E in questo ciclo, il database è indispensabile. Fornisce la memoria che consente agli agenti di percepire il contesto, i fatti che consentono loro di decidere in modo intelligente e lo stato che consentirà loro di agire in modo coerente.</p>
<p>Ecco perché i dati di un'azienda sono il suo bene più prezioso. I  <a href="https://www.mongodb.com/resources/basics/artificial-intelligence/large-language-models">modelli linguistici di grandi dimensioni</a> (LLM) possono generare risposte, ma è il database che fornisce continuità, collaborazione e vera intelligenza. Il futuro dell'AI non riguarda solo il ragionamento, ma anche il contesto, la memoria e la potenza dei propri dati.</p>
<h2>Il database ideale per l'AI trasformativa</h2>
<p>Quindi, qual è il database ideale per l'AI agentica? Deve riflettere la complessità di oggi e il cambiamento di domani. Deve parlare il linguaggio dell'AI, che è sempre più il JSON. Deve integrare il recupero avanzato dei dati grezzi, dei metadati e degli embedding, non solo la corrispondenza esatta, ma anche il significato e l'intento. Deve collegare dati privati e LLM con embedding e reranker della massima qualità. E deve fornire le prestazioni, la scalabilità e la sicurezza necessarie per alimentare le applicazioni mission-critical su scala globale.</p>
<p>Questo è esattamente ciò che MongoDB offre. Non ci limitiamo a spuntare le caselle di questa lista, le definiamo noi.</p>
<h2>Abbiamo appena iniziato</h2>
<p>Ecco perché sono così ottimista riguardo al nostro futuro. L'energia e la creatività che vediamo in ogni evento di MongoDB.local mi ricordano la passione che ha sempre alimentato questa azienda. Mentre i nostri clienti continuano a innovare, so che MongoDB è nella posizione perfetta per aiutarli ad avere successo nell'era dell'AI.</p>
<p>Non vediamo l'ora di scoprire cosa svilupperai in futuro.</p>
<div class="callout">
<p><b>Per visualizzare ulteriori annunci e ricevere gli ultimi aggiornamenti sui prodotti, visita la nostra pagina <a href="https://www.mongodb.com/products/updates/">Novità</a>. Vai <a href="https://www.mongodb.com/events/mongodb-local">all'hub MongoDB.local</a> per scoprire dove saremo prossimamente.	</b></p>
</div>	]]></description>
      <pubDate>Thu, 18 Sep 2025 12:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/events/local-nyc-2025-defining-ideal-database-for-ai-era-it</link>
      <guid>https://www.mongodb.com/company/blog/events/local-nyc-2025-defining-ideal-database-for-ai-era-it</guid>
    </item><item>
      <title>Celebrating Excellence: MongoDB Global Partner Awards 2025</title>
      <description><![CDATA[<p>In a world being reshaped by AI and rapid technological change, one thing is clear: our partners are powering the future with MongoDB. Together, we help customers modernize legacy systems, solve challenges from security to budget constraints, and build the next wave of AI-powered applications.</p>
<p>That’s why we’re proud to announce the annual MongoDB Global Partner Awards — celebrating partners who led the way in 2025. From pioneering AI and modernization to advancing public sector innovation to building bold go-to-market collaborations, these partners set the standard for excellence. Their leadership doesn’t just move the needle — it redefines what’s possible.</p>
<div class="callout">
<p><b>This post is also available in: <a href="https://www.mongodb.com/company/blog/news/celebrating-excellence-mongodb-global-partner-awards-2025-de" target="_blank">Deutsch</a>, <a href="https://www.mongodb.com/company/blog/news/celebrating-excellence-mongodb-global-partner-awards-2025-fr" target="_blank">Français</a>, <a href="https://www.mongodb.com/company/blog/news/celebrating-excellence-mongodb-global-partner-awards-2025-es" target="_blank">Español</a>, <a href="https://www.mongodb.com/company/blog/news/celebrating-excellence-mongodb-global-partner-awards-2025-br" target="_blank">Português</a>, <a href="https://www.mongodb.com/company/blog/news/celebrating-excellence-mongodb-global-partner-awards-2025-it" target="_blank">Italiano</a>, <a href="https://www.mongodb.com/company/blog/news/celebrating-excellence-mongodb-global-partner-awards-2025-kr" target="_blank">한국어</a>, <a href="https://www.mongodb.com/company/blog/news/celebrating-excellence-mongodb-global-partner-awards-2025-cn" target="_blank">简体中文</a>.</b></p>
</div>	
<h2>Global Cloud Partner of the Year: Microsoft</h2>
<p>We are proud to recognize <a href="https://cloud.mongodb.com/ecosystem/microsoft-power-platform-mongodb-connector">Microsoft</a> for exceptional year-over-year growth as MongoDB’s Global Cloud Partner of the Year. Together, MongoDB and Microsoft have delivered strong momentum across industries such as healthcare, telecommunications, and financial services, helping organizations build great applications that deliver exceptional customer experiences.</p>
<p>Microsoft’s deep commitment to collaboration, customer success, and cloud leadership makes it an indispensable part of MongoDB’s partner ecosystem. The strength of the partnership continues to grow; in fact, MongoDB was recently selected as a Microsoft partner for a “Unify your data solution play,” which enables customers to benefit from the joint integrations and go-to-market (GTM) resources between <a href="https://www.mongodb.com/products/platform/atlas-database">MongoDB Atlas</a> on Azure and Native Microsoft services.</p>
<h2>Global AI Cloud Partner of the Year: Amazon Web Services (AWS)</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/amazon-web-services">AWS</a> has been a driving force in helping customers unlock the full potential of AI with MongoDB, highlighted by our work with <a href="https://www.mongodb.com/solutions/customer-case-studies/novo-nordisk">Novo Nordisk</a>, who leveraged Amazon Bedrock and MongoDB Atlas to build an AI solution that cut one of their most time-intensive workflows from 12 weeks to 10 minutes. The work with Novo Nordisk is just one example of many that showcases the power of our partnership to create business differentiation for customers in the gen AI era.</p>
<p>MongoDB was also a generative AI Competency launch partner for AWS, further tightening our collaboration in AI. From breakthrough generative AI use cases and beyond, our partnership empowers organizations to move faster, innovate more boldly, and transform with confidence. Together, AWS and MongoDB are shaping what’s possible in the AI era.</p>
<h2>Global Cloud GTM Partner of the Year: Google Cloud</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/google-cloud">Google Cloud</a> is being honored for accelerating new business through impactful joint GTM initiatives. MongoDB's partnership with Google Cloud has set the standard for meaningful collaboration—driving new business and delivering impact across some of the world’s most complex global enterprises. The joint Google Cloud and MongoDB Sales Development Representative program has been the cornerstone of this success, ensuring early-stage talent get the opportunity to work with the largest organisations in the world whilst learning a sales playbook that will serve them well for the rest of their career. Google Cloud continues to be a driving force in MongoDB’s global growth thanks to its joint commitment to innovative GTM strategies.</p>
<h2>Global Systems Integrator Partner of the Year: Accenture</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/accenture-mainframe-modernization">Accenture</a> has demonstrated exceptional commitment as a Global SI Partner, establishing a dedicated center of excellence for MongoDB within its software engineering service line.</p>
<p>Together, MongoDB and Accenture have delivered transformative customer outcomes across industries, from payment modernization for a leading bank to data transformation for a major manufacturer. Meanwhile, closer collaboration with Accenture’s BFSI business unit has continued to fuel global customer success. By combining MongoDB’s modern database platform with Accenture’s deep industry expertise, our partnership continues to help customers modernize, unlock data-driven insights, and accelerate digital transformation at enterprise scale.</p>
<h2>Global Public Sector Partner of the Year: Accenture Federal Services</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/accenture-federal-services">Accenture Federal Services</a> has played a pivotal role in advancing MongoDB’s presence in the public sector. Thanks to its scale, expertise, and focus on customer outcomes, it has driven remarkable year-over-year growth and has supported critical government missions in coordination with MongoDB.</p>
<p>MongoDB and Accenture Federal Services are helping government agencies meet their efficiency goals by modernizing legacy applications, seamlessly consolidating platforms, and streamlining architectures, all while reducing costs. We are excited to have Accenture Federal Services as a key sponsor of our inaugural MongoDB Public Sector Summit in January 2026.</p>
<h2>Global Tech Partner of the Year: Confluent</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/confluent">Confluent</a>—the data streaming platform built by the co-creators of Apache Kafka®—continues to be a strategic partner with more than 550 joint customer deployments delivering impact across industries worldwide. Over the past year, MongoDB and Confluent have strengthened global go-to-market (GTM) alignment, focusing acceleration of co-sell engagement across EMEA and APAC.</p>
<p>Together, MongoDB and Confluent have delivered gen AI quickstarts, no-code streaming demos, and co-authored agentic AI thought leadership to help customers accelerate innovation with data in motion and build event-driven AI applications. Our partnership is anchored in strong field collaboration, with ongoing co-sponsored AI workshops and hands-on developer events. A standout highlight of our GTM collaboration was a joint gen AI Developer Day with Confluent and LangChain, where AI leaders engaged 80+ developers to showcase how our combined platforms enable cost-effective, explainable, and personalized multi-agent systems.</p>
<h2>Global ISV Partner of the Year: BigID</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/bigid-data-intelligence-platform">BigID</a> has remained a standout ISV partner for MongoDB, consistently delivering strong results for customers across financial services, insurance, and healthcare. Together, we have launched impactful joint GTM initiatives, from customer events to tailored incentive programs that have accelerated growth opportunities. BigID continues to be recognized as a leader in data security, privacy, and AI data management, and thanks to our close global alignment, is further strengthening MongoDB’s position as a trusted partner for organizations operating in highly regulated industries.</p>
<h2>Global AI Tech Partner of the Year: LangChain</h2>
<p>MongoDB’s partnership with <a href="https://cloud.mongodb.com/ecosystem/langchain">LangChain</a> has unlocked powerful new integrations that make it easier for developers to build <a href="https://www.mongodb.com/resources/basics/artificial-intelligence/retrieval-augmented-generation">retrieval-augmented generation</a> (RAG) applications and intelligent agents on MongoDB.</p>
<p>From hybrid search and parent document retrievers to short- and long-term memory capabilities, these joint solutions are helping developers push the boundaries of what’s possible with AI. Through joint workshops, webinars, and hands-on training, we have equipped developers with the tools and knowledge to adopt these capabilities at scale. Momentum continues to build rapidly, and adoption of both the LangChain/MongoDB and LangGraph/MongoDB packages continues to grow, highlighting the strength of our collaboration and the thriving developer ecosystem that MongoDB and LangChain are enabling together.</p>
<h2>Global AI SI Partner of the Year: Pureinsights</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/pureinsights">Pureinsights</a> accelerates intelligent search and AI application development with its powerful Discovery Platform. A standout capability is its integration with <a href="https://www.mongodb.com/products/platform/ai-search-and-retrieval">Voyage AI by MongoDB</a>, delivering advanced embeddings, multimodal embedding, and result reranking, earning recognition for its strong proof point track record and differentiated value in enterprise-grade use cases. With a focus on implementing generative AI, vector search, and RAG use cases, Pureinsights continues to empower clients to innovate quickly, reliably, and at scale.</p>
<h2>Global Modernization Partner of the Year: gravity9</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/gravity9">gravity9</a> has established itself as a trusted MongoDB partner by delivering consistent impact through modernization and jumpstart projects across industries and geographies, powered by AI. As a strategic implementation partner, gravity9 specializes in designing and delivering cloud-native, scalable solutions that help organizations modernize legacy systems, adopt new technologies, accelerate time-to-value, and prepare for the AI era. By combining deep technical expertise with an agile delivery model, gravity9 enables customers to unlock transformation opportunities, whether moving workloads to the cloud, building new AI experiences, or optimizing existing infrastructure. gravity9’s close collaboration with MongoDB’s Professional Services teams has generated consistently high customer ratings, demonstrating the quality and reliability of their work.</p>
<h2>Global Impact Partner of the Year: IBM</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/mongodb-on-ibm-z-and-linuxone">IBM</a> is being recognized for the Impact Partner of the Year award for their strategic contributions across a variety of large, industry-leading clients. IBM has played a critical role in securing large contracts with several multinational financial institutions and is investing more in expanding the partnership globally. The partnership continues to grow, including with Atlas &amp; Watsonx.ai, and increasing numbers of differentiated projects on the IBM Z Systems or LinuxOne infrastructure. IBM is a trusted vendor for large Enterprises, and is a strategic partner in over 25% of MongoDB's largest customers.</p>
<h2>Global Cloud - Certified DBaaS Partner of the Year: Alibaba</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/alibaba-cloud">Alibaba Cloud</a> has established itself as a strategic MongoDB partner by driving innovation with ApsaraDB for MongoDB and utilizing AI to help organizations build modern applications. With a strong focus on key verticals such as Gaming, Automotive, Retail, and Fintech, Alibaba Cloud is enabling enterprises to modernize faster and unlock new opportunities across industries. By combining cutting-edge data solutions with a bold global expansion strategy, Alibaba Cloud empowers customers worldwide to accelerate transformation, whether scaling digital platforms, delivering new customer experiences, or optimizing mission-critical workloads.</p>
<h2>Looking ahead</h2>
<p>Congratulations to all of the 2025 Global Partner Award winners! Their commitment to innovation, collaboration, and customer success has—and will have—a lasting impact on organizations worldwide. These awards not only recognize the past year’s achievements, but also underscore MongoDB’s vision for what we, alongside our partners, will build together in the future.</p>
<div class="callout">
<p><b>To learn more about the MongoDB Partner Program, please visit our <a href="https://www.mongodb.com/partners?tck=partner_awards_blog_2025">partners page</a>.</b></p>
</div>	]]></description>
      <pubDate>Thu, 18 Sep 2025 00:59:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/news/celebrating-excellence-mongodb-global-partner-awards-2025</link>
      <guid>https://www.mongodb.com/company/blog/news/celebrating-excellence-mongodb-global-partner-awards-2025</guid>
    </item><item>
      <title>庆祝卓越：MongoDB 全球合作伙伴奖 2025</title>
      <description><![CDATA[<p>在这个被人工智能和迅猛技术变革重塑的世界里，有一件事愈发清晰明确：我们的合作伙伴正借助 MongoDB 驱动未来前行。我们携手助力客户实现遗留系统现代化，应对从安全到预算限制的种种挑战，并共同构建新一代由人工智能驱动的应用程序。</p>
<p>这就是为什么我们自豪地宣布举办年度 MongoDB 全球合作伙伴大奖，表彰在 2025 年引领潮流的合作伙伴。从引领人工智能与现代化浪潮，到推动公共部门创新，再到构建突破性的市场进入合作模式，这些合作伙伴树立了卓越典范的标杆。他们的领导不仅推动了进展，还重新定义了可能性。</p>
<h2>年度全球云合作伙伴：Microsoft</h2>
<p>我们很荣幸将年度全球云合作伙伴奖授予 <a href="https://cloud.mongodb.com/ecosystem/microsoft-power-platform-mongodb-connector">Microsoft</a>，以表彰其作为 MongoDB 合作伙伴实现的卓越同比增长。MongoDB 与 Microsoft 强强联合，已在医疗保健、电信及金融服务等行业形成强劲发展势头，共同助力企业构建出能够提供卓越客户体验的优质应用程序。</p>
<p>Microsoft 在协同合作、客户成功与云技术领导力方面的不懈投入，使其成为 MongoDB 合作伙伴生态中不可或缺的重要力量。双方合作伙伴关系持续深化：MongoDB 近期更获选参与 Microsoft“统一数据解决方案”计划，成为其合作伙伴。该合作使客户能够充分利用 <a href="https://www.mongodb.com/products/platform/atlas-database">MongoDB Atlas</a> 在 Azure 平台与 Microsoft 原生服务之间的深度集成优势及联合市场推广资源。</p>
<h2>年度全球 AI 云合作伙伴：Amazon Web Services (AWS)</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/amazon-web-services">AWS</a> 一直是推动客户充分发挥 MongoDB 人工智能潜力的核心力量，其中的典型案例是我们与 Novo Nordisk 的合作：他们利用 Amazon Bedrock 和 MongoDB Atlas 构建了一套 AI 解决方案，将其中一项最耗时的工作流程从 12 周缩短到 10 分钟。与 Novo Nordisk 的合作仅是众多案例之一，它印证了双方合作伙伴关系在生成式 AI 时代为客户创造业务领先优势的强大能力。</p>
<p>MongoDB 也是 AWS 的生成式人工智能能力启动伙伴，进一步加强了我们在 AI 领域的合作。从突破性的生成式 AI 应用案例到更广泛的场景，我们的合作伙伴关系使组织能够更快速行动、更大胆创新，并自信地实现转型。AWS 和 MongoDB 正在共同塑造 AI 时代的可能性。</p>
<h2>年度全球云市场拓展合作伙伴：Google Cloud</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/google-cloud">Google Cloud</a> 正凭借其通过卓有成效的联合市场拓展计划加速新业务增长而获得此项荣誉。MongoDB 与 Google Cloud 的合作树立了深度协同的新标杆，通过驱动新业务增长，并在全球多家最复杂的跨国企业中持续创造价值，展现了合作关系的实质影响力。Google Cloud 与 MongoDB 联合设立的销售发展代表项目是此项成功的基石，它确保新生代人才在掌握一套能终身受益的销售方法论的同时，更能获得与全球顶尖企业合作的宝贵机会。凭借其对创新市场拓展战略的坚定承诺，Google Cloud 持续成为推动 MongoDB 全球增长的重要力量。</p>
<h2>年度全球系统集成商合作伙伴：Accenture</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/accenture-mainframe-modernization">Accenture</a> 作为全球系统集成合作伙伴展现出卓越承诺，在其软件工程服务线内部设立了专注于 MongoDB 的能力中心。</p>
<p>MongoDB 与 Accenture 强强联手，已为多个行业客户带来变革性成果，无论是助力领先银行的支付系统现代化升级，还是推动大型制造商的数据转型，均取得显著成效。同时，与 Accenture BFSI 业务部的密切合作继续推动全球客户成功。通过将 MongoDB 的现代数据库平台与 Accenture 深厚的行业专业知识相结合，我们的合作伙伴关系继续帮助客户实现现代化、解锁数据驱动的见解，并加速企业级的数字化转型。</p>
<h2>年度全球公共部门合作伙伴：Accenture Federal Services</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/accenture-federal-services">Accenture Federal Services</a> 在拓展 MongoDB 公共业务版图方面发挥了关键作用。凭借其规模优势、专业实力以及对客户成果的专注，Accenture Federal Services 不仅实现了显著的同比增长，更在与 MongoDB 的协同合作中，有力支撑了多项关键的政府使命。</p>
<p>MongoDB 和 Accenture Federal Services 正在帮助政府机构通过现代化旧版应用程序、无缝整合平台和简化架构来实现其效率目标，同时降低成本。我们欣然宣布，Accenture Federal Services 将作为核心赞助商，鼎力支持定于 2026 年 1 月举办的首届 MongoDB 公共部门峰会。</p>
<h2>年度全球技术合作伙伴：Confluent</h2>
<p>由 Apache Kafka® 联合创始人打造的数据流平台<a href="https://cloud.mongodb.com/ecosystem/confluent">Confluent</a>，作为 MongoDB 的战略合作伙伴，持续推动全球业务增长，目前双方已有逾 550 个联合客户部署，正为各行业创造实际价值。过去一年间，MongoDB 与 Confluent 持续深化全球市场战略协同，重点加速欧洲、中东、非洲及亚太地区的联合销售落地。</p>
<p>MongoDB 与 Confluent 共同推出了生成式 AI 快速入门、无代码流式演示，并联合撰写了智能体 AI 思想领导力内容，帮助客户加速基于动态数据的创新，并构建事件驱动的 AI 应用程序。我们的合作以紧密的现场协作为基础，持续举办联合赞助的人工智能研讨会和面向开发者的实践活动。我们市场拓展合作的一个突出亮点是与 Confluent 和 LangChain 联合举办的生成式 AI 开发者日活动，在活动中，人工智能领域的领导者与 80 多名开发者互动，展示了我们的联合平台如何实现具有成本效益、可解释性和个性化的多智能体系统。</p>
<h2>年度全球独立软件供应商合作伙伴：BigID</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/bigid-data-intelligence-platform">BigID</a> 一直是 MongoDB 的杰出独立软件供应商 (ISV) 合作伙伴，在金融服务、保险和医疗保健等领域持续为客户交付卓越成果。我们共同推出了具有影响力的联合市场拓展 (GTM) 举措，从客户活动到定制激励计划，均加速了增长机会。BigID 持续被公认为数据安全、隐私和 AI 数据管理领域的领导者，并且由于我们在全球范围内的紧密协作，进一步强化了 MongoDB 作为高度监管行业组织可信赖合作伙伴的地位。</p>
<h2>年度全球 AI 技术合作伙伴：LangChain</h2>
<p>MongoDB 与 <a href="https://cloud.mongodb.com/ecosystem/langchain">LangChain</a> 的合作开启了强大的全新集成功能，使开发者能够更轻松地在 MongoDB 上构建检索增强生成 (<a href="https://www.mongodb.com/resources/basics/artificial-intelligence/retrieval-augmented-generation">RAG</a>) 应用及智能体。</p>
<p>从混合搜索和父文档检索器到短期与长期记忆功能，这些联合解决方案正在帮助开发者不断拓展人工智能的可能性边界。通过联合举办的研讨会、在线讲座及实践培训，我们为开发者提供了必要的工具与知识，使其能够大规模应用这些技术能力。势头持续迅速增长，LangChain/MongoDB 和 LangGraph/MongoDB 软件包的采用率不断上升，这突显了我们合作的实力以及 MongoDB 与 LangChain 共同推动的蓬勃发展的开发者生态系统。</p>
<h2>年度全球 AI SI 合作伙伴：Pureinsights</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/pureinsights">Pureinsights</a> 利用其强大的 Discovery 平台，加速智能搜索和人工智能应用的开发。其一项突出能力是与 MongoDB 的 <a href="https://www.mongodb.com/products/platform/ai-search-and-retrieval">Voyage AI</a> 集成，提供先进的嵌入、多模态嵌入和结果重排，在企业级应用案例中以强有力的验证记录和差异化价值获得认可。Pureinsights 专注于实施生成式 AI、向量搜索和 RAG 应用场景，持续赋能客户快速、可靠且大规模地创新。</p>
<h2>年度全球现代化合作伙伴：gravity9</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/gravity9">gravity9</a> 通过在各行各业和不同地区开展现代化和快速启动项目，并借助人工智能实现持续影响，确立了其作为 MongoDB 值得信赖合作伙伴的地位。作为战略实施合作伙伴，gravity9 专注于设计和交付云原生、可扩展的解决方案，帮助组织实现传统系统现代化、采用新技术、加快价值实现速度，并为人工智能时代做好准备。通过将深厚的技术专长与敏捷交付模式相结合，gravity9 使客户能够抓住转型机遇，无论是将工作负载迁移到云端、构建新的 AI 体验，还是优化现有基础设施。gravity9 与 MongoDB 专业服务团队的紧密合作持续获得高客户评价，彰显了其工作质量和可靠性。</p>
<h2>年度全球影响力合作伙伴：IBM</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/mongodb-on-ibm-z-and-linuxone">IBM</a> 因其在众多大型行业领先客户中的战略性贡献而获得“年度影响力合作伙伴”奖的认可。IBM 在与多家跨国金融机构签订大型合同方面发挥了关键作用，并正加大投资以在全球范围内拓展合作伙伴关系。双方的合作持续扩大，包括在 Atlas 和 Watsonx.ai 上，以及在 IBM Z 系统或 LinuxOne 基础设施上开展越来越多的差异化项目。IBM 是大型企业值得信赖的供应商，并且是 MongoDB 超过 25% 最大客户的战略合作伙伴。</p>
<h2>年度全球云认证数据库即服务 (DBaaS) 合作伙伴：阿里巴巴</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/alibaba-cloud">阿里云</a>通过推动 ApsaraDB for MongoDB 的创新，并利用人工智能帮助组织构建现代化应用，确立了其作为 MongoDB 战略合作伙伴的地位。阿里云重点关注游戏、汽车、零售和金融科技等关键垂直行业，帮助企业更快实现现代化，并在各个行业中发掘新的机遇。通过将尖端数据解决方案与大胆的全球扩张战略相结合，阿里云赋能全球客户加速转型，无论是扩展数字平台、提供新的客户体验，还是优化关键任务工作负载。</p>
<h2>展望未来</h2>
<p>恭喜所有 2025 年度全球合作伙伴奖获得者！他们对创新、合作和客户成功的承诺，已经并将继续对全球组织产生持久影响。这些奖项不仅表彰过去一年的成就，也强调了 MongoDB 对未来愿景的承诺，即我们将与合作伙伴共同打造的成果。</p>
<div class="callout">
<p>要了解更多关于 MongoDB 合作伙伴计划的信息，请访问我们的<a href="https://www.mongodb.com/partners?tck=partner_awards_blog_2024">合作伙伴页面</a>。</p>
</div>	]]></description>
      <pubDate>Thu, 18 Sep 2025 00:59:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/news/celebrating-excellence-mongodb-global-partner-awards-2025-cn</link>
      <guid>https://www.mongodb.com/company/blog/news/celebrating-excellence-mongodb-global-partner-awards-2025-cn</guid>
    </item><item>
      <title>우수성을 기념하기: 2025년 MongoDB 글로벌 파트너 어워드</title>
      <description><![CDATA[<p>AI 와 빠른 기술 변화로 인해 재편되는 세상에서 한 가지 분명한 것은 우리의 파트너들이 MongoDB로 미래를 이끌고 있다는 점입니다. 우리는 함께 고객이 레거시 시스템을 현대화하고, 보안부터 예산 제약에 이르는 과제를 해결하고, 다음 AI 기반 애플리케이션을 빌드할 수 있도록 지원합니다.</p>
<p>그래서 우리는 2025년을 선도하는 파트너를 기념하는 연례 MongoDB 글로벌 파트너 어워드를 발표하게 되어 자랑스럽습니다. 선구적인 AI 및 현대화부터 공공 부문 혁신 추진, 대담한 시장 진출 협업 구축에 이르기까지 이러한 파트너들은 우수성의 기준을 설정합니다. 그들의 리더십은 단순히 변화를 가져오는 것이 아니라, 무엇이 가능한지를 새롭게 정의합니다.</p>
<h2>올해의 글로벌 클라우드 파트너: Microsoft</h2>
<p>매년 탁월한 성장을 이룬 <a href="https://cloud.mongodb.com/ecosystem/microsoft-power-platform-mongodb-connector">Microsoft</a>를 MongoDB의 올해의 글로벌 클라우드 파트너로 선정하게 되어 자랑스럽게 생각합니다. MongoDB 및 Microsoft는 의료, 통신, 금융 서비스 등의 산업 전반에 걸쳐 강력한 추진력을 제공함으로써 조직이 탁월한 고객 경험을 제공하는 훌륭한 애플리케이션을 구축할 수 있도록 지원하고 있습니다.</p>
<p>Microsoft의 협업, 고객 성공, 클라우드 리더십에 대한 깊은 헌신은 MongoDB의 파트너 에코시스템에서 없어서는 안 될 부분입니다. 파트너십의 강점은 계속 강화되고 있습니다. 실제로 MongoDB는 최근 “통합 데이터 솔루션 플레이”의 Microsoft 파트너로 선정되었습니다. 이를 통해 고객은 <a href="https://www.mongodb.com/products/platform/atlas-database">MongoDB Atlas</a> on Azure와 네이티브 Microsoft 서비스 간의 공동 통합 및 시장 출시(GTM) 리소스를 활용할 수 있게 되었습니다.</p>
<h2>올해의 글로벌 AI 클라우드 파트너: Amazon Web Services(AWS)</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/amazon-web-services">AWS</a>는 고객이 MongoDB를 통해 AI의 잠재력을 최대한 발휘할 수 있도록 지원하는 원동력이 되어 왔으며, Amazon Bedrock과 MongoDB Atlas를 활용하여 가장 시간이 많이 걸리는 워크플로를 12주에서 10분으로 단축한 AI 솔루션을 빌드한 Novo Nordisk와의 협업이 대표적인 사례입니다. Novo Nordisk와의 협업은 생성형 AI 시대에 고객을 위한 비즈니스 차별화를 창출하는 파트너십의 힘을 보여주는 많은 사례 중 하나에 불과합니다.</p>
<p>또한 MongoDB는 AWS의 생성형 AI 역량 출시 파트너로 선정되어 AI 분야에서의 협력을 더욱 강화했습니다. 획기적인 생성형 AI 사용 사례와 그 이상을 통해 우리의 파트너십은 조직이 더 빠르게 움직이고, 더 과감하게 혁신하며, 자신감을 가지고 변혁할 수 있도록 지원합니다. AWS와 MongoDB는 함께 AI 시대에 가능성을 열어가고 있습니다.</p>
<h2>올해의 글로벌 클라우드 GTM 파트너: Google Cloud</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/google-cloud">Google Cloud</a>는 효과적인 공동 GTM 이니셔티브를 통해 새로운 사업을 가속화한 공로를 인정받았습니다. MongoDB와 Google Cloud의 파트너십은 세계에서 가장 복잡한 글로벌 엔터프라이즈에서 새로운 비즈니스를 창출하고 영향을 미치는 의미 있는 협업의 기준을 설정했습니다. Google Cloud와 MongoDB의 공동 영업 개발 담당자 프로그램은 이러한 성공의 주춧돌이 되었으며, 초기 단계의 인재들이 세계 최대 조직과 함께 일할 기회를 얻고, 그들의 커리어 전반에 걸쳐 유용하게 제공할 영업 전략을 배울 수 있도록 보장합니다. Google Cloud는 혁신적인 GTM 전략에 대한 공동의 노력 덕분에 MongoDB의 글로벌 성장의 주도적인 힘이 되고 있습니다.</p>
<h2>올해의 글로벌 시스템 통합자 파트너: Accenture</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/accenture-mainframe-modernization">Accenture</a>는 소프트웨어 엔지니어링 서비스 라인 내에 MongoDB를 위한 전담 우수 센터를 설립하여 글로벌 SI 파트너로서 탁월한 노력을 기울였습니다.</p>
<p>MongoDB와 Accenture는 함께 주요 은행의 결제 현대화부터 주요 제조업체의 데이터 전환에 이르기까지 산업 전반에 걸쳐 변혁적인 고객 성과를 제공했습니다. 한편, Accenture의 BFSI 사업부와의 긴밀한 협력은 계속해서 글로벌 고객 성공을 촉진하고 있습니다. MongoDB의 현대적인 데이터베이스 플랫폼과 Accenture의 깊은 산업 전문성을 결합함으로써, 당사의 파트너십은 고객이 현대화하고, 데이터 기반 인사이트를 발굴하며, 엔터프라이즈 규모에서 디지털 혁신을 가속화할 수 있도록 지속적으로 지원합니다.</p>
<h2>올해의 글로벌 공공 기관 파트너: Accenture Federal Services</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/accenture-federal-services">Accenture Federal Services</a>는 공공 부문에서 MongoDB의 존재감을 강화하는 데 중요한 역할을 해왔습니다. 확장성과 전문성, 고객 성과에 대한 집중 덕분에 매년 괄목할 만한 성장을 이뤘으며, MongoDB와 협력하여 중요한 정부 임무를 지원했습니다.</p>
<p>MongoDB와 Accenture Federal Services는 정부 기관이 효율성 목표를 달성할 수 있도록 레거시 애플리케이션을 현대화하고, 플랫폼을 원활하게 통합하며, 아키텍처를 간소화하면서 비용을 절감하는 데 도움을 주고 있습니다. 2026년 1월에 열리는 첫 번째 MongoDB 공공 기관 서밋의 주요 후원자로 Accenture Federal Services를 모시게 되어 기쁩니다.</p>
<h2>올해의 글로벌 테크 파트너: Confluent</h2>
<p>Apache Kafka®의 공동 개발자가 구축한 데이터 스트리밍 플랫폼인 <a href="https://cloud.mongodb.com/ecosystem/confluent">Confluent</a>는 550개 이상의 공동 고객 배포를 통해 전 세계 산업에 영향을 미치며 전략적 파트너로 계속 활동하고 있습니다. 지난 한 해 동안 MongoDB와 Confluent는 글로벌 시장 진출(GTM) 조율을 강화하여 EMEA 및 APAC 지역에서 공동 판매 참여를 가속화하는 데 주력했습니다.</p>
<p>MongoDB와 Confluent는 고객이 데이터 이동 중 혁신을 가속화하고 이벤트 기반 AI 애플리케이션을 빌드할 수 있도록 생성형 AI 퀵스타트, 노코드 스트리밍 데모, 에이전트 AI 사고 리더십을 공동으로 제공해 왔습니다. 우리의 파트너십은 지속적인 공동 후원 AI 워크숍과 개발자 참여 이벤트를 통해 강력한 필드 협업을 기반으로 합니다. GTM 협업의 하이라이트는 Confluent 및 LangChain과 공동으로 진행한 생성형 AI 개발자 데이로, 80명 이상의 개발자가 참여하여 양사의 통합 플랫폼이 어떻게 비용 효율적이고 설명 가능한 개인화된 멀티 에이전트 시스템을 구현하는지를 보여줬습니다.</p>
<h2>올해의 글로벌 ISV 파트너: BigID</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/bigid-data-intelligence-platform">BigID</a>는 금융 서비스, 보험, 의료 분야에서 고객에게 지속적으로 강력한 성과를 제공하며 MongoDB의 뛰어난 ISV 파트너로 자리매김했습니다. 함께 고객 이벤트에서 성장 기회를 가속화하는 맞춤형 인센티브 프로그램에 이르기까지 영향력 있는 공동 GTM 이니셔티브를 시작했습니다. BigID는 데이터 보안, 개인정보 보호 및 AI 데이터 관리 분야의 선두주자로 계속 인정받고 있으며, 전 세계적인 긴밀한 협력을 통해 규제가 엄격한 산업에서 활동하는 조직의 신뢰할 수 있는 파트너로서 MongoDB의 입지를 더욱 강화하고 있습니다.</p>
<h2>올해의 글로벌 AI 기술 파트너: LangChain</h2>
<p>MongoDB와 <a href="https://cloud.mongodb.com/ecosystem/langchain">LangChain</a>의 파트너십은 개발자들이 MongoDB에서 검색 증강 생성(RAG) 애플리케이션과 지능형 에이전트를 보다 쉽게 구축할 수 있도록 강력한 새로운 통합 기능을 제공합니다.</p>
<p>하이브리드 검색과 상위 문서 검색부터 단기 및 장기 메모리 역량에 이르기까지, 이러한 공동 솔루션은 개발자가 AI로 가능성의 경계를 확장하도록 돕고 있습니다. 공동 워크숍, 웨비나 및 실습 교육을 통해 개발자들이 이러한 역량을 확장할 수 있도록 도구와 지식을 제공했습니다. 모멘텀은 계속 빠르게 빌드되고 있으며, LangChain/MongoDB 및 LangGraph/MongoDB 패키지의 채택이 계속 증가하고 있습니다. 이는 MongoDB와 LangChain이 함께 조성하고 있는 개발자 에코시스템과 번창하는 협업의 강점을 강조합니다.</p>
<h2>年度全球 AI SI 合作伙伴：Pureinsights</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/pureinsights">Pureinsights</a>는 강력한 Discovery Platform을 통해 지능형 검색 및 AI 애플리케이션 개발을 가속화합니다. <a href="https://www.mongodb.com/products/platform/ai-search-and-retrieval">Voyage AI by MongoDB</a>와의 통합을 통해 고급 임베딩, 멀티모달 임베딩, 결과 재랭킹을 제공하며 엔터프라이즈급 사용 사례에서 강력한 증명점 추적 기록과 차별화된 가치를 인정받고 있는 점도 돋보이는 역량입니다. Pureinsights는 생성형 AI, 벡터 검색, RAG 사용 사례 구현에 중점을 두고 클라이언트가 신속하고 안정적으로, 확장할 수 있도록 지속적으로 지원합니다.</p>
<h2>올해의 글로벌 현대화 파트너: gravity9</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/gravity9">gravity9</a>은 AI를 활용하여 여러 산업과 지역에 걸쳐 현대화 및 도약 프로젝트를 일관적으로 수행함으로써 신뢰할 수 있는 MongoDB 파트너로 자리매김했습니다. 전략적 구현 파트너인 Gravity9은 조직이 레거시 시스템을 현대화하고, 새로운 기술을 채택하고, 가치 창출 시간을 가속화하고, AI 시대에 대비할 수 있도록 지원하는 확장 가능한 클라우드 네이티브 솔루션을 설계 및 제공하는 것을 전문으로 합니다. gravity9는 심층적인 기술 전문성과 애자일 제공 모델을 결합하여 고객이 워크로드를 클라우드로 이동하거나, 새로운 AI 경험을 구축하거나, 기존 인프라를 최적화하는 등 혁신의 기회를 열 수 있도록 지원합니다. gravity9과 MongoDB의 Professional Services 팀과의 긴밀한 협업은 지속적으로 높은 고객 평가를 받아 그들의 작업 품질과 신뢰성을 입증하고 있습니다.</p>
<h2>올해의 글로벌 임팩트 파트너: IBM</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/mongodb-on-ibm-z-and-linuxone">IBM</a>는 업계를 선도하는 다양한 대형 클라이언트에서 전략적으로 기여한 공로를 인정받아 올해의 임팩트 파트너 상을 수상하게 되었습니다. IBM은 여러 다국적 금융 기관과 대규모 계약을 체결하는 데 중요한 역할을 했으며, 전 세계적으로 파트너십을 확대하기 위해 더 많은 투자를 하고 있습니다. 파트너십은 계속해서 성장하고 있으며, Atlas 및 Watsonx.ai와의 협력을 포함하여 IBM Z Systems 또는 LinuxOne 인프라에서 차별화된 프로젝트의 수가 증가하고 있습니다. IBM은 대기업의 신뢰받는 공급업체이며, MongoDB의 최대 고객 중 25% 이상과 전략적 파트너 관계를 맺고 있습니다.</p>
<h2>올해의 글로벌 클라우드 - 인증 DBaaS 파트너: Alibaba</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/alibaba-cloud">Alibaba Cloud</a>는 MongoDB용 ApsaraDB로 혁신을 주도하고 AI를 활용하여 조직이 최신 애플리케이션을 빌드할 수 있도록 지원함으로써 전략적 MongoDB 파트너로 자리매김했습니다. 게임, 자동차, 소매, 핀테크와 같은 주요 분야에 중점을 둔 Alibaba Cloud는 엔터프라이즈가 더 빠르게 현대화하고 다양한 산업에서 새로운 기회를 창출할 수 있도록 지원합니다. Alibaba Cloud는 최첨단 데이터 솔루션과 과감한 글로벌 확장 전략을 결합하여 전 세계 고객이 디지털 플랫폼을 확장하고, 새로운 고객 경험을 제공하며, 미션 크리티컬 워크로드를 최적화하여 혁신을 가속화할 수 있도록 지원합니다.</p>
<h2>미래 전망</h2>
<p>2025년 글로벌 파트너 어워드 수상자 모두 축하드립니다! 혁신, 협업, 고객 성공을 위한 이들의 노력은 전 세계 조직에 지속적인 영향을 미쳤으며 앞으로도 계속될 것입니다. 이러한 상은 지난 한 해의 성과를 인정할 뿐만 아니라, 파트너와 함께 미래에 함께 빌드할 MongoDB의 비전을 강조합니다.</p>
<div class="callout">
<p>MongoDB 파트너 프로그램에 대해 자세히 알아보려면 <a href="https://www.mongodb.com/partners?tck=partner_awards_blog_2024">파트너 페이지</a>를 방문하세요.</p>
</div>	]]></description>
      <pubDate>Thu, 18 Sep 2025 00:59:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/news/celebrating-excellence-mongodb-global-partner-awards-2025-kr</link>
      <guid>https://www.mongodb.com/company/blog/news/celebrating-excellence-mongodb-global-partner-awards-2025-kr</guid>
    </item><item>
      <title>Celebrando la Excelencia: Premios Globales de Emparejar de MongoDB 2025</title>
      <description><![CDATA[<p>En un mundo que está siendo remodelado por la IA y los rápidos cambios tecnológicos, una cosa está clara: nuestros Emparejar están impulsando el futuro con MongoDB. Juntos, ayudamos a los clientes a modernizar los sistemas heredados, a resolver desafíos que van desde la seguridad hasta las restricciones presupuestarias, y a compilar la siguiente ola de aplicaciones basadas en IA.</p>
<p>Por eso nos enorgullece anunciar los premios anuales MongoDB Global Emparejar Awards, que celebran a los Emparejar que lideraron el camino en 2025. Desde ser pioneros en la IA y la modernización, hasta avanzar en la innovación del sector público y construir colaboraciones audaces para el mercado, estos Emparejar establecen el estándar de excelencia. Su liderazgo no solo marca la diferencia, sino que redefine lo que es posible.</p>
<h2>Emparejar Global de Cloud del Año: Microsoft</h2>
<p>Nos enorgullece reconocer a <a href="https://cloud.mongodb.com/ecosystem/microsoft-power-platform-mongodb-connector">Microsoft</a> por su excepcional crecimiento interanual como Emparejar Global en la Cloud del Año de MongoDB. Juntos, MongoDB y Microsoft han impulsado un fuerte avance en sectores como la atención médica, las telecomunicaciones y los servicios financieros, ayudando a las Organizaciones a compilar grandes aplicaciones que ofrecen experiencias excepcionales al cliente.</p>
<p>El profundo compromiso de Microsoft con la colaboración, el éxito del cliente y el liderazgo en la nube lo convierte en una parte indispensable del ecosistema de Emparejar de MongoDB. La fortaleza de la asociación sigue creciendo; de hecho, MongoDB fue seleccionado recientemente como Emparejar de Microsoft para un “Unificar su solución de datos,” lo que permite a los clientes beneficiarse de las integraciones conjuntas y los Recursos de comercialización (GTM) entre <a href="https://www.mongodb.com/products/platform/atlas-database">MongoDB Atlas</a> en Azure y los servicios nativos de Microsoft.</p>
<h2>Socio global de IA en Cloud del año: Amazon Web Services (AWS)</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/amazon-web-services">AWS</a> ha sido una fuerza impulsora en ayudar a los clientes a desbloquear todo el potencial de la IA con MongoDB, destacado por nuestro trabajo con Novo Nordisk, que aprovechó Amazon Bedrock y MongoDB Atlas para compilar una solución de IA que redujo uno de sus flujos de trabajo más intensivos en tiempo de 12 semanas a 10 minutos. El trabajo con Novo Nordisk es solo un ejemplo de muchos que demuestra el poder de nuestra colaboración para crear una diferenciación empresarial para los clientes en la era de la IA generativa.</p>
<p>MongoDB también fue un Emparejar de lanzamiento de la competencia de IA generativa para AWS, lo que estrecha aún más nuestra colaboración en IA. Desde casos de uso revolucionarios de IA generativa y más allá, nuestra asociación empodera a las organizaciones para moverse más rápido, innovar con más audacia y transformarse con confianza. Juntos, AWS y MongoDB están moldeando lo que es posible en la era de la IA.</p>
<h2>Emparejar global del año de GTM en Cloud: Google Cloud</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/google-cloud">Google Cloud</a> está siendo honrado por acelerar nuevos negocios a través de iniciativas conjuntas de GTM impactantes. La asociación de MongoDB con Google Cloud ha establecido el estándar para una colaboración significativa, impulsando nuevos negocios y generando impacto en algunas de las empresas globales más complejas del mundo. El programa conjunto de Representante de Desarrollo de Ventas de Google Cloud y MongoDB ha sido la piedra angular de este éxito, asegurando que los talentos en etapa inicial tengan la oportunidad de trabajar con las organizaciones más grandes del mundo mientras aprenden un manual de ventas que les servirá bien para el resto de su carrera. Google Cloud sigue siendo una fuerza impulsora en el crecimiento global de MongoDB gracias a su compromiso conjunto con estrategias innovadoras de GTM.</p>
<h2>Emparejar integrador de sistemas global del año: Accenture</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/accenture-mainframe-modernization">Accenture</a> ha demostrado un compromiso excepcional como Emparejar Global de SI, estableciendo un centro de excelencia dedicado para MongoDB dentro de su línea de servicios de ingeniería de software.</p>
<p>Juntos, MongoDB y Accenture han proporcionado resultados transformadores para los clientes en diversas industrias, desde la modernización de pagos para un banco líder hasta la transformación de datos para un importante fabricante. Mientras tanto, una colaboración más estrecha con la unidad de negocio BFSI de Accenture ha seguido impulsando el éxito global del cliente. Al combinar la moderna plataforma de base de datos de MongoDB con la profunda experiencia de Accenture en la industria, nuestra colaboración sigue ayudando a los clientes a modernizar, desbloquear perspectivas basadas en datos y acelerar la transformación digital a escalar empresarial.</p>
<h2>Emparejar del Sector Público Global del Año: Accenture Federal Services</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/accenture-federal-services">Accenture Federal Services</a> ha desempeñado un Rol fundamental en el avance de la presencia de MongoDB en el sector público. Gracias a su escalar, experiencia y enfoque en los resultados para el cliente, ha impulsado un crecimiento notable año tras año y ha respaldado misiones críticas del gobierno en coordinación con MongoDB.</p>
<p>MongoDB y Accenture Federal Services están ayudando a las agencias de gobierno a cumplir sus objetivos de eficiencia mediante la modernización de aplicaciones heredadas, la consolidación fluida de plataformas y la optimización de arquitecturas, todo ello mientras se reducen los costos. Nos complace contar con Accenture Federal Services como patrocinador principal de nuestra Cumbre inaugural del Sector Público de MongoDB en enero de 2026.</p>
<h2>Emparejar tecnológico global del año: Confluent</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/confluent">Confluent</a>, la plataforma de transmisión de datos compilada por los cocreadores de Apache Kafka®, sigue siendo un Emparejar estratégico con más de 550 implementaciones conjuntas de cliente que generan impacto en diversas industrias a nivel mundial. Durante el último año, MongoDB y Confluent han fortalecido la alineación global de comercialización (GTM), enfocándose en acelerar la interacción de co-venta en EMEA y APAC.</p>
<p>Juntos, MongoDB y Confluent han proporcionado inicios rápidos de IA generativa, demostraciones de transmisión sin código y han coescrito liderazgo de pensamiento en IA agencial para ayudar a los clientes a acelerar la innovación con datos en movimiento y compilar aplicaciones de IA impulsadas por eventos. Nuestra asociación está anclada en una sólida colaboración de campo, con talleres de IA en curso copatrocinados y eventos prácticos para desarrolladores. Un aspecto destacado de nuestra colaboración en GTM fue un Día del Desarrollador de IA Generativa conjunto con Confluent y LangChain, donde los líderes de IA involucraron a más de 80 desarrolladores para demostrar cómo nuestras plataformas combinadas permiten sistemas multiagente de costo efectivo, explicables y personalizados.</p>
<h2>Emparejar ISV Global del Año: BigID</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/bigid-data-intelligence-platform">BigID</a> ha seguido siendo un destacado Emparejar ISV para MongoDB, ofreciendo consistentemente resultados sólidos para los cliente en los sectores de servicios financieros, seguros y atención médica. Juntos, hemos lanzado iniciativas conjuntas de GTM impactantes, desde eventos para clientes hasta programas de incentivos personalizados que han acelerado las oportunidades de crecimiento. BigID sigue siendo reconocido como líder en seguridad de datos, privacidad y gestión de datos de IA y, gracias a nuestra estrecha alineación global, está fortaleciendo aún más la posición de MongoDB como un Emparejar de confianza para las Organizaciones que operan en industrias altamente reguladas.</p>
<h2>Emparejar global de tecnología de IA del año: LangChain</h2>
<p>La asociación de MongoDB con <a href="https://cloud.mongodb.com/ecosystem/langchain">LangChain</a> ha desbloqueado nuevas y poderosas integraciones que facilitan a los desarrolladores la compilación de aplicaciones de Generación de recuperación aumentada (RAG) y agentes inteligentes en MongoDB.</p>
<p>Desde la búsqueda híbrida y los recuperadores de documentos padre hasta las capacidades de memoria a corto y largo término, estas soluciones conjuntas están ayudando a los desarrolladores a ampliar los límites de lo que es posible con la IA. A través de talleres conjuntos, seminarios web y entrenamiento práctico, hemos equipado a los desarrolladores con las herramientas y el conocimiento para adoptar estas capacidades a gran escalar. El impulso continúa compilándose rápidamente, y la adopción de los Paquetes LangChain/MongoDB y LangGraph/MongoDB continúa creciendo, destacando la fortaleza de nuestra colaboración y el próspero ecosistema de desarrolladores que MongoDB y LangChain están fomentando juntos.</p>
<h2>Emparejar global del año de IA SI: Pureinsights</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/pureinsights">Pureinsights</a> acelera la búsqueda inteligente y el desarrollo de aplicaciones de IA con su potente plataforma Discovery. Una capacidad destacada es su integración con <a href="https://www.mongodb.com/products/platform/ai-search-and-retrieval">Voyage IA de MongoDB</a>, que ofrece embeddings avanzados, embeddings multimodales y reclasificación de resultados, ganando reconocimiento por su sólida trayectoria de puntos de prueba y valor diferenciado en casos de uso de nivel empresarial. Con un enfoque en implementar IA generativa, búsqueda vectorial y casos de uso de RAG, Pureinsights sigue empoderando a los clientes para que innoven de manera rápida, confiable y a gran escala.</p>
<h2>Emparejar Global de modernización del Año: gravity9</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/gravity9">gravity9</a> se ha establecido como un Emparejar de confianza de MongoDB al ofrecer un impacto coherente a través de Proyectos de modernización y aceleración en diversas industrias y geografías, impulsados por IA. Como Emparejar de implementación estratégica, gravity9 se especializa en diseñar y ofrecer soluciones nativa de la nube y escalable que ayudan a las Organización a modernizar los sistemas heredada, adoptar nuevas tecnologías, acelerar el tiempo de creación de valor y prepararse para la era de la IA. Al combinar una profunda experiencia técnica con un modelo de entrega agile, gravity9 permite a los clientes desbloquear oportunidades de transformación, ya sea trasladando cargas de trabajo a la nube, creando nuevas experiencias de IA u optimizando la infraestructura existente. La estrecha colaboración de gravity9 con los equipos de Professional Services de MongoDB ha generado calificaciones consistentemente altas de los clientes, demostrando la calidad y fiabilidad de su trabajo.</p>
<h2>Emparejar Global de impacto del Año: IBM</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/mongodb-on-ibm-z-and-linuxone">IBM</a> está siendo reconocida por el premio Emparejar del Año por sus contribuciones estratégicas a una variedad de grandes clientes líderes en la industria. IBM ha desempeñado un Rol fundamental en la obtención de grandes contratos con varias instituciones financieras multinacionales y está invirtiendo más en la expansión de la colaboración a nivel mundial. La asociación sigue creciendo, incluyendo con Atlas &amp; Watsonx.IA, y un número cada vez mayor de Proyectos diferenciados en la infraestructura de IBM Z Systems o LinuxOne. IBM es un proveedor de confianza para las grandes empresas y es un Emparejar estratégico en más del 25% de los clientes más grandes de MongoDB.</p>
<h2>Global Cloud - Emparejar certificado de DBaaS del año: Alibaba</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/alibaba-cloud">Alibaba Cloud</a> se ha consolidado como un Emparejar estratégico de MongoDB al impulsar la innovación con ApsaraDB para MongoDB y utilizar la IA para ayudar a las Organizaciones a compilar aplicaciones modernas. Con un fuerte enfoque en verticales clave como juegos, automoción, venta minorista y fintech, Alibaba Cloud está permitiendo a las empresas modernizarse más rápidamente y desbloquear nuevas oportunidades en todas las industrias. Al combinar soluciones de datos de vanguardia con una audaz estrategia de expansión global, Alibaba Cloud permite a los clientes de todo el mundo acelerar la transformación, ya sea escalando plataformas digitales, brindando nuevas experiencias a los clientes u optimizando las cargas de trabajo críticas para la misión.</p>
<h2>Mirando hacia adelante</h2>
<p>¡Felicidades a todos los ganadores de los Global Emparejar Awards 2025! Su compromiso con la innovación, la colaboración y el éxito de los clientes ha tenido y tendrá un impacto duradero en las organizaciones de todo el mundo. Estos premios no solo reconocen los logros del año pasado, sino que también subrayan la visión de MongoDB de lo que nosotros, junto con nuestros Emparejar, compilaremos juntos en el futuro.</p>
<div class="callout">
<p><b>Para aprender más sobre el Programa de Emparejar de MongoDB, visite nuestra <a href="https://www.mongodb.com/partners?tck=partner_awards_blog_2024">página de emparejar</a>.</b></p>
</div>	]]></description>
      <pubDate>Thu, 18 Sep 2025 00:59:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/news/celebrating-excellence-mongodb-global-partner-awards-2025-es</link>
      <guid>https://www.mongodb.com/company/blog/news/celebrating-excellence-mongodb-global-partner-awards-2025-es</guid>
    </item><item>
      <title>Hommage à l’excellence : MongoDB Global Partner Awards 2025</title>
      <description><![CDATA[<p>Dans un monde en pleine transformation par l'IA et les changements technologiques rapides, une chose est certaine : nos partenaires représentent l'avenir grâce à MongoDB. Ensemble, nous aidons les clients à moderniser les systèmes hérités, à résoudre des défis allant de la sécurité aux contraintes budgétaires, et à construire la prochaine vague d'applications alimentées par l'IA.</p>
<p>« C'est pourquoi nous sommes fiers d'annoncer la cérémonie annuelle des MongoDB Global Partner Awards, célébrant les partenaires qui ont ouvert la voie en 2025. » Qu'il s'agisse d’innovation en matière d'IA et de modernisation, de faire progresser l'innovation dans le secteur public ou de mettre en place des collaborations audacieuses pour la mise sur le marché, ces partenaires définissent la norme en matière d'excellence. Leur leadership ne fait pas que faire bouger les choses : il redéfinit ce qui est possible.</p>
<h2>Partenaire cloud mondial de l'année : Microsoft</h2>
<p>Nous sommes fiers de reconnaître <a href="https://cloud.mongodb.com/ecosystem/microsoft-power-platform-mongodb-connector">Microsoft</a> pour sa croissance exceptionnelle d'année en année en tant que Partenaire cloud mondial de l’année de MongoDB. Ensemble, MongoDB et Microsoft ont généré une forte dynamique dans des secteurs tels que la santé, les télécommunications et les services financiers, aidant les entreprises à créer d'excellentes applications qui offrent des expériences client exceptionnelles.</p>
<p>L'engagement profond de Microsoft en faveur de la collaboration, du succès client et du leadership dans le cloud en fait un élément indispensable de l'écosystème de partenaires de MongoDB. La force du partenariat continue de croître. En fait, MongoDB a récemment été sélectionné comme partenaire Microsoft pour une « solution unifiée pour vos données », qui permet aux clients de bénéficier des intégrations conjointes et des ressources de mise sur le marché entre <a href="https://www.mongodb.com/products/platform/atlas-database">MongoDB Atlas</a> sur Azure et les services Microsoft natifs.</p>
<h2>Partenaire international de l'année pour le cloud IA : Amazon Web Services (AWS)</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/amazon-web-services">AWS</a> a été un moteur pour aider les clients à exploiter tout le potentiel de l'IA avec MongoDB, illustré par notre collaboration avec Novo Nordisk, qui a utilisé Amazon Bedrock et MongoDB Atlas pour créer une solution d'IA réduisant un de leurs processus les plus chronophages de 12 semaines à 10 minutes. Le travail avec Novo Nordisk n'est qu'un exemple parmi tant d'autres qui démontre la puissance de notre partenariat pour créer une différenciation commerciale pour les clients à l'ère de l'IA générative.</p>
<p>MongoDB a également été un partenaire de lancement pour la compétence d’IA générative d'AWS, renforçant ainsi notre collaboration en IA. Des cas d'utilisation révolutionnaires de l'IA générative et au-delà, notre partenariat permet aux entreprises de progresser plus rapidement, d'innover plus audacieusement et de se transformer en toute confiance. Ensemble, AWS et MongoDB façonnent ce qui est possible à l'ère de l'IA.</p>
<h2>Partenaire international de l'année pour la mise sur le marché du cloud : Google Cloud</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/google-cloud">Google Cloud</a> est honoré pour avoir accéléré de nouvelles activités grâce à des initiatives de mise sur le marché conjointes percutantes. Le partenariat de MongoDB avec Google Cloud a défini la norme en matière de collaboration significative, générant de nouvelles activités et produisant un impact sur certaines des entreprises internationales les plus complexes. Le programme conjoint de représentants du développement commercial de Google Cloud et MongoDB a été la pierre angulaire de ce succès, garantissant aux jeunes talents la possibilité de travailler avec les plus grandes entreprises du monde tout en apprenant un manuel de vente qui leur sera utile pour le reste de leur carrière. Google Cloud continue d'être une force motrice dans la croissance internationale de MongoDB grâce à son engagement commun dans des stratégies de mise sur le marché innovantes.</p>
<h2>Partenaire international de l'année pour l’intégration des systèmes : Accenture</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/accenture-mainframe-modernization">Accenture</a> a démontré un engagement exceptionnel en tant que partenaire SI international, en établissant un centre d'excellence dédié à MongoDB au sein de sa ligne de services d'ingénierie logicielle.</p>
<p>Ensemble, MongoDB et Accenture ont apporté des résultats clients transformateurs dans tous les secteurs, de la modernisation des paiements pour une banque de premier plan à la transformation des données pour un grand fabricant. Parallèlement, une collaboration plus étroite avec l'unité commerciale BFSI d'Accenture a continué à favoriser le succès client à l'échelle mondiale. « En combinant la plateforme de base de données moderne de MongoDB avec l'expertise sectorielle approfondie d'Accenture, notre partenariat continue d'aider les clients à se moderniser, à libérer des informations basées sur les données et à accélérer la transformation numérique à l’échelle de l’entreprise. »</p>
<h2>Partenaire international de l'année pour le secteur public : Accenture Federal Services</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/accenture-federal-services">Accenture Federal Services</a> a joué un rôle essentiel dans le développement de la présence de MongoDB dans le secteur public. Grâce à sa taille, son expertise et son accent sur les résultats pour les clients, elle a enregistré une croissance remarquable d'année en année et a soutenu des missions gouvernementales essentielles en coordination avec MongoDB.</p>
<p>MongoDB et Accenture Federal Services aident les agences gouvernementales à atteindre leurs objectifs d'efficacité en modernisant les applications existantes, en consolidant de manière transparente les plateformes et en rationalisant les architectures, tout en réduisant les coûts. Nous sommes ravis qu'Accenture Federal Services soit l'un des principaux sponsors de notre premier MongoDB Public Sector Summit, qui se tiendra en janvier 2026.</p>
<h2>Partenaire technologique mondial de l'année : Confluent</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/confluent">Confluent</a>, la plateforme de diffusion de données créée par les co-créateurs d'Apache Kafka®, reste un partenaire stratégique avec plus de 550 déploiements conjoints de clients ayant un impact sur les secteurs du monde entier. L'année dernière, MongoDB et Confluent ont renforcé l'alignement mondial de la mise sur le marché, en se concentrant sur l'accélération de l'engagement de co-vente dans la région Europe-Proche-Orient et Asie-Pacifique.</p>
<p>Ensemble, MongoDB et Confluent ont fourni des guides de démarrage rapide de l’IA générative, des démos de streaming sans code et un leadership éclairé en IA agentique co-écrit pour aider les clients à accélérer l’innovation grâce aux données en mouvement et à créer des applications d’IA basées sur les évènements. Notre partenariat est ancré dans une solide collaboration sur le terrain, avec des ateliers d’IA co-sponsorisés et des évènements pratiques pour les développeurs. L’un des points forts de notre collaboration de mise sur le marché a été une journée conjointe des développeurs d’IA générative avec Confluent et LangChain, où les leaders de l’IA ont engagé plus de 80 développeurs pour montrer comment nos plateformes combinées permettent des systèmes multi-agents rentables, explicables et personnalisés.</p>
<h2>Partenaire ISV mondial de l'année : BigID</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/bigid-data-intelligence-platform">BigID</a> est resté un partenaire ISV de premier plan pour MongoDB, obtenant régulièrement de bons résultats pour ses clients dans les domaines des services financiers, de l'assurance et de la santé. Ensemble, nous avons lancé des initiatives conjointes et percutantes de mise sur le marché, allant des évènements clients aux programmes d’incitation sur mesure qui ont accéléré les possibilités de croissance. BigID continue d'être reconnu comme un leader en matière de sécurité des données, de confidentialité et de gestion des données d'IA, et grâce à notre alignement international étroit, renforce encore la position de MongoDB en tant que partenaire de confiance pour les entreprises opérant dans des secteurs hautement réglementés.</p>
<h2>Partenaire technologique international de l'année en matière d'IA : LangChain</h2>
<p>Le partenariat entre MongoDB et <a href="https://cloud.mongodb.com/ecosystem/langchain">LangChain</a> a débloqué de nouvelles intégrations puissantes qui permettent aux développeurs de créer plus facilement des applications de génération augmentée par récupération et des agents intelligents sur MongoDB.</p>
<p>Des recherches hybrides et des récupérateurs de documents parents aux capacités de mémoire à court et à long terme, ces solutions conjointes aident les développeurs à repousser les limites du possible avec l'IA. Grâce à des ateliers conjoints, des webinaires et des formations pratiques, nous avons doté les développeurs des outils et des connaissances nécessaires pour faire évoluer ces capacités. La dynamique se renforce rapidement, et l'adoption des packages LangChain/MongoDB et LangGraph/MongoDB ne cesse de croître, soulignant la force de notre collaboration et l'écosystème de développement en plein essor que MongoDB et LangChain permettent conjointement.</p>
<h2>Partenaire international de l’année pour la SI IA : Pureinsights</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/pureinsights">Pureinsights</a>  accélère la recherche intelligente et le développement d'applications d'IA grâce à sa puissante plateforme de découverte. L'une des fonctionnalités les plus remarquables est son intégration à Voyage AI de MongoDB, qui permet des intégrations avancées, une intégration multimodale et un reclassement des résultats. Elle est reconnue pour ses solides antécédents en matière de points de preuve et sa valeur différenciée dans les cas d'utilisation destinés aux entreprises. « En mettant l'accent sur la mise en œuvre de l'IA générative, la recherche vectorielle et les cas d'utilisation de génération augmentée par récupération, Pureinsights continue de permettre à ses clients d'innover rapidement, de manière fiable et d’évoluer. »</p>
<h2>Partenaire mondial de l'année pour la modernisation : gravity9</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/gravity9">gravity9</a> s'est imposé comme un partenaire de confiance de MongoDB en offrant un impact cohérent grâce à des projets de modernisation et de démarrage dans les secteurs et les zones géographiques, alimentés par l'IA. En tant que partenaire de mise en œuvre stratégique, gravity9 se spécialise dans la conception et la fourniture de solutions cloud natives et évolutives qui aident les entreprises à moderniser leurs systèmes existants, à adopter de nouvelles technologies, à accélérer la rentabilisation et à se préparer à l'ère de l'IA. En associant une expertise technique approfondie à un modèle de livraison agile, gravity9 permet aux clients de débloquer des potentialités de transformation, qu'il s'agisse de déplacer des charges de travail vers le cloud, de créer de nouvelles expériences d'IA ou d'optimiser l'infrastructure existante. L'étroite collaboration de gravity9 avec les équipes de services professionnels de MongoDB a généré des notes élevées de la part des clients, démontrant la qualité et la fiabilité de leur travail.</p>
<h2>Partenaire de l'année pour l’impact international : IBM</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/mongodb-on-ibm-z-and-linuxone">IBM</a> est reconnu pour le prix du Partenaire de l'année pour l’impact pour ses contributions stratégiques auprès de nombreux grands clients de premier plan du secteur. IBM a joué un rôle essentiel dans l'obtention de contrats importants avec plusieurs institutions financières multinationales et investit davantage dans l'extension du partenariat à l'échelle internationale. Le partenariat continue de se développer, notamment avec Atlas et Watsonx.ai, et de plus en plus de projets différenciés sur l'infrastructure IBM Z Systems ou LinuxONE. IBM est un fournisseur de confiance pour les grandes entreprises et un partenaire stratégique pour plus de 25 % des plus gros clients de MongoDB.</p>
<h2>Global Cloud - Partenaire DBaaS certifié de l'année : Alibaba</h2>
<p><a href="https://cloud.mongodb.com/ecosystem/alibaba-cloud">Alibaba Cloud</a> s’est imposé comme un partenaire stratégique de MongoDB en stimulant l’innovation avec ApsaraDB pour MongoDB et en utilisant l’IA pour aider les entreprises à créer des applications modernes. En mettant l’accent sur les principaux secteurs verticaux tels que les jeux, l’automobile, la vente au détail et la fintech, Alibaba Cloud permet aux entreprises de se moderniser plus rapidement et de débloquer de nouvelles possibilités dans tous les secteurs. En combinant des solutions de données de pointe avec une stratégie d’expansion internationale audacieuse, Alibaba Cloud permet aux clients du monde entier d’accélérer leur transformation, qu’il s’agisse de mettre à l'échelle des plateformes numériques, d’offrir de nouvelles expériences client ou d’optimiser des charges de travail critiques.</p>
<h2>Perspectives d'avenir</h2>
<p>Félicitations à tous les lauréats des Global Partner Awards 2025 ! Leur engagement envers l'innovation, la collaboration et le succès client a, et aura, un impact durable sur les entreprises du monde entier. Ces prix ne reconnaissent pas seulement les réalisations de l'année écoulée, mais soulignent également la vision de MongoDB pour ce que nous, ainsi que nos partenaires, construirons ensemble à l'avenir.</p>
<div class="callout">
<p><b>Pour en savoir plus sur le programme partenaire MongoDB, rendez-vous sur <a href="https://www.mongodb.com/partners?tck=partner_awards_blog_2025">notre page partenaires</a>.</b></p>
</div>	]]></description>
      <pubDate>Thu, 18 Sep 2025 00:59:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/news/celebrating-excellence-mongodb-global-partner-awards-2025-fr</link>
      <guid>https://www.mongodb.com/company/blog/news/celebrating-excellence-mongodb-global-partner-awards-2025-fr</guid>
    </item></channel></rss>