MongoDB Atlas

Parent: MongoDB Expert Knowledge · Published reference · snapshot 2026-09-08 · skill mongodb-atlas-expert

Generated from docs/mongodb-atlas-expert-context.md. Use it as a MongoDB Atlas platform reference when planning Atlas architecture, automating Atlas administration, connecting applica

These notes link each claim to its source. Some citations identify archived research reports that are no longer hosted on this site. A published reference means the content is available; it does not certify independent review or accuracy.Read the editorial policy and follow the sources before relying on a claim.

MongoDB Atlas Expert

Generated from docs/mongodb-atlas-expert-context.md. Use it as a MongoDB Atlas platform reference when planning Atlas architecture, automating Atlas administration, connecting applications, designing Atlas-backed schemas and queries, or reviewing Atlas operational posture. Start from the context below, then defer to the linked official MongoDB Atlas docs, MongoDB Manual, and driver docs as the source of truth for exact endpoint, command, operator, and version details. For a deep sub-area, match the task to the Sub-skill routing table below and read the listed references/…md file before answering. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#mongodb-atlas-expert]

Sub-skill routing table

This skill consolidates 27 Atlas sub-skills as on-demand references - match the task to the table and Read the listed references/…md file before answering deep questions. Do not rely on this table alone for depth. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#sub-skill-routing-table]

Atlas platform and architecture

Atlas docs home: deployment types, regions, access control, connection, alerts, optimization entry points <https://www.mongodb.com/docs/atlas/> [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-platform-and-architecture]
Atlas Architecture Center: Atlas well-architected guidance across operational efficiency, security, reliability, performance, and cost optimization <https://www.mongodb.com/docs/atlas/architecture/current/> [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-platform-and-architecture]

Atlas administration and automation

Atlas Admin API v2 reference: canonical Atlas administration endpoint inventory and auth model <https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/> [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-administration-and-automation]
Configure Atlas API access: service-account/API-key setup, IP access list behavior, and the REST/data-plane boundary <https://www.mongodb.com/docs/atlas/configure-api-access/> [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-administration-and-automation]
Atlas CLI docs: command-line Atlas management surface and setup flow <https://www.mongodb.com/docs/atlas/cli/current/> [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-administration-and-automation]
Atlas Terraform provider guide: infrastructure-as-code surface for Atlas provisioning and lifecycle management <https://www.mongodb.com/docs/atlas/terraform/> [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-administration-and-automation]
Atlas Kubernetes Operator: Kubernetes control-plane integration and lifecycle caveats <https://www.mongodb.com/docs/atlas/operator/stable/> [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-administration-and-automation]

Connection, security, and access control

Connect to a database deployment: connection prerequisites, private networking choices, firewall requirements, and data-plane connection flow <https://www.mongodb.com/docs/atlas/connect-to-database-deployment/> [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#connection-security-and-access-control]
Atlas IP access list: project-scoped client network allow-list behavior, limits, temporary entries, and CLI entry points <https://www.mongodb.com/docs/atlas/security/ip-access-list/> [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#connection-security-and-access-control]
Atlas database users: Atlas-vs-database-user boundary, auth mechanisms, role model, and operational limits <https://www.mongodb.com/docs/atlas/security-add-mongodb-users/> [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#connection-security-and-access-control]

Data access and MongoDB application design

MongoDB drivers: official application client surfaces by language <https://www.mongodb.com/docs/drivers/> [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#data-access-and-mongodb-application-design]
MongoDB data modeling: access-pattern-first schema design, embedding vs referencing, and flexible-schema guidance <https://www.mongodb.com/docs/manual/data-modeling/> [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#data-access-and-mongodb-application-design]
MongoDB indexes: index types, write/read tradeoffs, Atlas UI/CLI index management, and Performance Advisor entry points <https://www.mongodb.com/docs/manual/indexes/> [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#data-access-and-mongodb-application-design]
MongoDB aggregation: preferred aggregation-pipeline model and stage-based data processing <https://www.mongodb.com/docs/manual/aggregation/> [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#data-access-and-mongodb-application-design]

Atlas search and AI surfaces

Atlas Search: full-text search, analyzers, mappings, $search, $searchMeta, pagination, faceting, and autocomplete <https://www.mongodb.com/docs/atlas/atlas-search/> [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-search-and-ai-surfaces]
Atlas Vector Search: ANN/ENN vector search, hybrid search, RAG, automated embedding, and version availability <https://www.mongodb.com/docs/atlas/atlas-vector-search/> [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-search-and-ai-surfaces]

Streaming, encryption, and newer surfaces

Atlas Stream Processing: continuous stream processing using aggregation-pipeline syntax over Atlas and Kafka sources <https://www.mongodb.com/docs/atlas/atlas-stream-processing/> [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#streaming-encryption-and-newer-surfaces]
Queryable Encryption: query encrypted fields without exposing plaintext; equality/range GA, prefix/suffix/substring in preview on 8.2+ <https://www.mongodb.com/docs/manual/core/queryable-encryption/> [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#streaming-encryption-and-newer-surfaces]
Atlas AI Integrations: consolidated RAG, agent memory, and embedding pattern documentation <https://www.mongodb.com/docs/atlas/ai-integrations/> [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#streaming-encryption-and-newer-surfaces]

Operations, backup, observability, and limits

Atlas alerts: alert conditions, lifecycle, acknowledgement, and org/project settings <https://www.mongodb.com/docs/atlas/alerts/> [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#operations-backup-observability-and-limits]
Atlas cluster metrics: health metrics, real-time metrics, search metrics, and operator-facing signals <https://www.mongodb.com/docs/atlas/monitor-cluster-metrics/> [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#operations-backup-observability-and-limits]
Atlas Cloud Backup overview: backup enablement, redundancy, compliance, restore-role requirements, and topology caveats <https://www.mongodb.com/docs/atlas/backup/cloud-backup/overview/> [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#operations-backup-observability-and-limits]
Atlas limits: component, connection, and topology limits that shape designs and operating posture <https://www.mongodb.com/docs/atlas/reference/atlas-limits/> [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#operations-backup-observability-and-limits]
Atlas Performance Advisor: slow-query analysis, index suggestions, and read-vs-write tradeoff reminders <https://www.mongodb.com/docs/atlas/performance-advisor/> [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#operations-backup-observability-and-limits]

Atlas quick rules

Treat Atlas as the control plane and MongoDB drivers / mongosh as the main data-plane application surfaces. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-quick-rules]
Prefer service accounts over legacy API keys for new Atlas Admin API automation. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-quick-rules]
Remember the Atlas Admin API does not read or write your cluster data; it manages Atlas resources and access configuration. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-quick-rules]
Design schemas around access patterns; data accessed together should generally live together. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-quick-rules]
Prefer embedding when it lets common reads complete as a single-document fetch; use transactions only when requirements truly cross document boundaries. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-quick-rules]
Add indexes for repeated query patterns, but account for the write cost of every index. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-quick-rules]
Use Performance Advisor, cluster metrics, alerts, and limits together; Atlas performance work is not just about query syntax. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-quick-rules]
Treat IP access lists, private networking, database users, and Atlas users as distinct security controls with different scopes. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-quick-rules]
Use Atlas Search for full-text/relevance workloads and Atlas Vector Search for semantic similarity/RAG workloads; they are related but not the same feature. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-quick-rules]
Check deployment tier, MongoDB version, and Atlas limits before giving prescriptive advice. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-quick-rules]
Know the Flex / Free / Dedicated tier model; Serverless and M2/M5 are deprecated. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-quick-rules]
Consider Atlas Stream Processing for event-driven and real-time ETL workloads before building external pipelines. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-quick-rules]
For hybrid retrieval, use $rankFusion (MongoDB 8.1+) to merge full-text and vector results in a single query. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-quick-rules]
Use Queryable Encryption for sensitive fields that still need to be queried; equality/range queries are GA, prefix/suffix/substring are in preview on 8.2+. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-quick-rules]

What Atlas expertise should mean

An Atlas-focused assistant should be able to reason across: [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#what-atlas-expertise-should-mean]
- control plane design: organizations, projects, deployments, users, network boundaries, backups, monitoring, limits, and automation [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#what-atlas-expertise-should-mean]
- application access: drivers, connection strings, connection pooling, query/index fit, aggregation, search, vector search [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#what-atlas-expertise-should-mean]
- operations: alerts, metrics, performance advisor, capacity, topology, and backup/disaster-recovery posture [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#what-atlas-expertise-should-mean]
- delivery models: UI, Admin API, CLI, Terraform, and Atlas Kubernetes Operator [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#what-atlas-expertise-should-mean]
- streaming and event-driven: Atlas Stream Processing for real-time pipelines and time-series ingestion [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#what-atlas-expertise-should-mean]
- AI and agentic patterns: automated embedding, vector search, hybrid search, RAG, agent memory, and framework integrations [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#what-atlas-expertise-should-mean]

Shared responsibility

Atlas Architecture Center explicitly frames Atlas through a shared responsibility model: MongoDB operates the underlying platform, while customers own their configuration, access control, and data policies. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#shared-responsibility]
Atlas architectural guidance is organized around five pillars: operational efficiency, security, reliability, performance, and cost optimization. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#shared-responsibility]

Core control-plane hierarchy

Atlas operations are anchored around organizations, projects, and deployments/clusters. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#core-control-plane-hierarchy]
Many role assignments and operational actions are scoped differently at the organization vs project layer, so advice should always name the required scope. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#core-control-plane-hierarchy]

Deployment and connectivity model

Atlas lets teams choose deployment tier (Free, Flex, or Dedicated), cloud provider, and region based on application latency, cost, and security requirements. Serverless instances and M2/M5 clusters are deprecated; Flex is their replacement. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#deployment-and-connectivity-model]
Application environments must satisfy both network access and database-user authentication to reach an Atlas deployment. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#deployment-and-connectivity-model]
Private connectivity choices include VPC/VNet peering and private endpoints, while public connectivity requires IP allow-listing. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#deployment-and-connectivity-model]

Atlas interaction methods inventory

This is the high-value inventory of how you can work with Atlas. For exact subcommands or endpoints, follow the linked source sections. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-interaction-methods-inventory]

Atlas Admin API standards

The Atlas Admin API is a REST-style control-plane API for Atlas resource administration. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-admin-api-standards]
The preferred authentication method is OAuth2 service-account access tokens; HTTP Digest API keys are a legacy option. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-admin-api-standards]
Service-account tokens are obtained from POST https://cloud.mongodb.com/api/oauth/token and are reusable for about one hour. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-admin-api-standards]
If your organization requires an API IP access list, token generation can happen from any IP, but API calls that use the token must come from an allowed IP. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-admin-api-standards]
The Admin API does not expose application data access; reading and writing database documents still happens through cluster auth plus a driver or other data-plane client. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-admin-api-standards]
As of March 2026, the Admin API enforces standardized rate limiting using a token-bucket algorithm. Automation code must handle 429 Too Many Requests responses and respect Retry-After headers. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-admin-api-standards]

Admin API categories to expect

For exact endpoints, use the API reference. In practice, Atlas Admin API work usually falls into these buckets: [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#admin-api-categories-to-expect]
- organizations and projects [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#admin-api-categories-to-expect]
- deployments / clusters / topology [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#admin-api-categories-to-expect]
- database users and access [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#admin-api-categories-to-expect]
- network access and IP lists [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#admin-api-categories-to-expect]
- alerts and monitoring metadata [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#admin-api-categories-to-expect]
- backup and restore administration [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#admin-api-categories-to-expect]
- inventory, IP address, and project metadata [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#admin-api-categories-to-expect]

Atlas CLI standards

Atlas CLI is the terminal-native Atlas control-plane surface. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-cli-standards]
atlas setup is the fast-start command that signs up or authenticates, creates a free database, loads sample data, adds the current IP to the access list, creates a database user, and connects with mongosh. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-cli-standards]
Atlas CLI is appropriate for operator workflows and scripts, but when a task needs stable, reviewable automation, the Admin API or Terraform may be a better fit. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-cli-standards]
Atlas docs explicitly surface CLI entry points for actions like access list inspection and other Atlas resource operations. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-cli-standards]

Terraform

Use Terraform when you want declarative Atlas infrastructure management. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#terraform]
The Atlas Terraform provider is the main Atlas IaC surface for provisioning/managing clusters and related Atlas resources from code. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#terraform]
MongoDB’s guide expects service-account authentication for provider configuration. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#terraform]
Provider 2.0 (2025) introduced semantic versioning with no-breaking-change guarantees in minor/patch releases. Projects on 1.x must follow the 2.0.0 Upgrade Guide before upgrading. See the refresh section below for details. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#terraform]

Atlas Kubernetes Operator

Use Atlas Kubernetes Operator when Atlas resources need to be managed from a Kubernetes control plane. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-kubernetes-operator]
AKO manages Atlas state from custom resources like AtlasProject, AtlasDeployment, and AtlasDatabaseUser. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-kubernetes-operator]
AKO 2.0 changed deletion behavior: deleting a Kubernetes custom resource no longer deletes the Atlas resource by default. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-kubernetes-operator]
The docs explicitly warn to define desired config values explicitly to avoid inheriting Atlas defaults that can cause reconciliation loops. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-kubernetes-operator]

Network boundaries

Atlas only allows cluster client connections from the project’s IP access list unless you use private networking. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#network-boundaries]
IP access lists are project-wide, not per cluster. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#network-boundaries]
Atlas supports temporary IP access list entries with configurable expiration. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#network-boundaries]
For application connectivity, Atlas docs call out three main patterns: public IP allow-listing, VPC/VNet peering, and private endpoints. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#network-boundaries]

Identity boundaries

Atlas users are not the same as database users. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#identity-boundaries]
Atlas users access the Atlas control plane; database users access MongoDB data-plane resources. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#identity-boundaries]
Database users can be scoped with built-in roles, specific privileges, and custom roles. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#identity-boundaries]
Atlas supports multiple database-user auth methods, including SCRAM and X.509, with environment-sensitive guidance in the docs. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#identity-boundaries]

Practical security defaults

Prefer private networking for higher-security production environments. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#practical-security-defaults]
Prefer service accounts for Atlas control-plane automation. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#practical-security-defaults]
Keep API and cluster network allow-lists narrow and time-bound where possible. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#practical-security-defaults]
Use the minimum project/organization role that can perform the task. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#practical-security-defaults]
Keep the distinction between control-plane auth and data-plane auth explicit in design docs and code. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#practical-security-defaults]

Schema design

Model data around application access patterns. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#schema-design]
Keep data that is accessed together together. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#schema-design]
Use embedding when it reduces joins and multi-document coordination. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#schema-design]
Use referencing when data has a different access cadence, lifecycle, or cardinality profile. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#schema-design]

Query and index design

Add indexes for repeated query shapes. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#query-and-index-design]
Remember every additional index raises write cost. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#query-and-index-design]
Atlas Performance Advisor is useful, but recommended indexes still need human judgment about workload frequency and write tradeoffs. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#query-and-index-design]
Large arrays and $lookup-heavy designs are called out in Atlas docs as common sources of slow-query pain. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#query-and-index-design]

Write and transaction design

Single-document operations are atomic; many practical designs should exploit that instead of defaulting to transactions. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#write-and-transaction-design]
Include expected current state in update filters or use intent-specific operators like $inc where concurrency matters. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#write-and-transaction-design]
Use transactions only when multi-document, multi-collection, or cross-shard atomicity is actually required. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#write-and-transaction-design]

Driver usage

Production application code should usually target an official MongoDB driver. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#driver-usage]
Atlas expertise includes choosing the right driver-level behavior for the language/runtime, not only knowing Atlas admin features. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#driver-usage]

Atlas Search

Atlas Search is the embedded full-text and relevance-search system for Atlas. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-search]
Search queries are expressed through aggregation pipeline stages such as $search and $searchMeta. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-search]
Atlas Search supports analyzers, autocomplete, pagination, faceting, scoring, static mappings, and dynamic mappings. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-search]
Use Atlas Search when the workload is fundamentally about relevance-based text retrieval. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-search]

Atlas Vector Search

Atlas Vector Search is the semantic/vector retrieval surface for Atlas. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-vector-search]
Use it for semantic search, hybrid search, and RAG/agentic retrieval patterns. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-vector-search]
Atlas docs call out ANN and ENN availability by MongoDB version; do not give vector-search guidance without checking version support. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-vector-search]
Automated Embedding uses the autoEmbed index field type with built-in Voyage AI models (voyage-4-large, voyage-4, voyage-4-lite, voyage-code-3) to generate embeddings on insert, update, and query without an external pipeline. Public preview as of May 2026. See the refresh section below for pricing and model details. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-vector-search]

Backup, reliability, and disaster-recovery standards

Atlas Cloud Backup uses the cloud provider’s native snapshot functionality and inherits provider redundancy guarantees. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#backup-reliability-and-disaster-recovery-standards]
Atlas supports multi-region snapshot distribution for added redundancy and region-failure recovery posture. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#backup-reliability-and-disaster-recovery-standards]
Backup restore/admin operations require the appropriate project backup roles; org-level access alone is not sufficient until explicitly added to the project. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#backup-reliability-and-disaster-recovery-standards]
Topology matters: Atlas docs note restore caveats for sharded clusters after shard-count changes. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#backup-reliability-and-disaster-recovery-standards]

Alerts

Atlas alerts are configured around conditions, thresholds, notification methods, and lifecycle management. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#alerts]
Alert policies can exist at the organization or project level. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#alerts]
Atlas supports acknowledge/unacknowledge, disable/enable, and delete flows for alerts. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#alerts]

Metrics

Atlas collects metrics across servers, databases, and MongoDB processes. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#metrics]
High-signal metrics called out in the docs include connections, disk IOPS, disk usage, query targeting, and normalized system CPU. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#metrics]
Atlas exposes real-time metrics and Atlas Search metrics in addition to cluster views. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#metrics]

Capacity and limits

Atlas limits around connections, shards, nodes, and topology are design inputs, not just operational trivia. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#capacity-and-limits]
Atlas docs explicitly recommend connection pooling, application tuning, autoscaling, and tier scaling when nearing connection limits. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#capacity-and-limits]

High-value method inventory

This is the condensed inventory to keep handy. For exhaustive method lists, use the linked references directly. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#high-value-method-inventory]

Practical defaults for future Atlas coding/review tasks

Start with which Atlas surface the task belongs to: UI, Admin API, CLI, Terraform, AKO, or application driver. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#practical-defaults-for-future-atlas-codingreview-tasks]
Separate Atlas control-plane actions from MongoDB data-plane actions before proposing code. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#practical-defaults-for-future-atlas-codingreview-tasks]
For application design, start with access patterns, then schema, then indexes, then aggregation/search/vector shape. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#practical-defaults-for-future-atlas-codingreview-tasks]
For operations, review alerts + metrics + limits + backup posture together. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#practical-defaults-for-future-atlas-codingreview-tasks]
For security, review network path + identity model + required role + auth method together. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#practical-defaults-for-future-atlas-codingreview-tasks]
For AI/search work, choose explicitly between Atlas Search, Atlas Vector Search, or hybrid patterns. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#practical-defaults-for-future-atlas-codingreview-tasks]

Recent platform changes (2025-2026 refresh)

This section captures major Atlas and MongoDB platform changes since late 2024. Last refreshed: 2026-05-25. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#recent-platform-changes-2025-2026-refresh]

MongoDB server versions on Atlas

MongoDB 8.0 (GA October 2024): 32% query throughput improvement, 56% faster bulk writes, 200% faster time-series aggregations, 50x faster data distribution for sharding at 50% lower cost. Introduced default maximum time limits for queries and the ability to reject recurring problem queries. <https://www.mongodb.com/docs/manual/release-notes/8.0/> [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#mongodb-server-versions-on-atlas]
MongoDB 8.2 (2025): Public preview of enhanced Queryable Encryption (prefix, suffix, substring queries on encrypted fields), $currentDate in aggregate(), standardized spill-to-disk metrics in explain output. <https://www.mongodb.com/docs/manual/release-notes/8.2/> [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#mongodb-server-versions-on-atlas]
MongoDB 8.3 (May 2026): ~45% more reads and ~35% more writes vs 8.0, sub-100ms retrieval targets for agent workloads, new $hash and $hexHash aggregation expressions (MD5, SHA-256, XXH64), arrayIndexAs field in $map/$filter/$reduce, removeShard deprecated in favor of four new drain/removal commands, security hardening and native type-coercion expressions. <https://www.mongodb.com/docs/manual/release-notes/8.3/> [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#mongodb-server-versions-on-atlas]

Flex clusters (replaces Shared and Serverless tiers)

Atlas Flex tier is the unified replacement for M2, M5, and Serverless instances. It combines the best of Shared and Serverless into a single offering with dynamic scaling. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#flex-clusters-replaces-shared-and-serverless-tiers]
As of March 2025, Serverless instances are no longer supported; existing instances were migrated to Free, Flex, or Dedicated clusters. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#flex-clusters-replaces-shared-and-serverless-tiers]
As of May 2025, all M2/M5 clusters have been auto-migrated to Flex. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#flex-clusters-replaces-shared-and-serverless-tiers]
As of January 2026, the old createGroupCluster (M2/M5) and createGroupServerlessInstance API endpoints only support Flex clusters. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#flex-clusters-replaces-shared-and-serverless-tiers]
Flex includes 100 ops/sec and 5 GB storage by default, scales to 500 ops/sec dynamically, $8 base + usage-based billing capped at $30/month. <https://www.mongodb.com/docs/atlas/manage-flex-clusters/> [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#flex-clusters-replaces-shared-and-serverless-tiers]
Flex key limits: 500 connections max, 5 GB storage hard cap (no auto-expand), 500 collections max, 100 databases max, MongoDB 8.0 minimum (auto-upgrade only). [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#flex-clusters-replaces-shared-and-serverless-tiers]
Flex does NOT support: Private Endpoints (no PrivateLink/VPC peering), Continuous Backup/PITR (daily snapshot only), BYOK encryption at rest, Database Auditing, Performance Advisor, Rolling index builds, allowDiskUse, server-side JS. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#flex-clusters-replaces-shared-and-serverless-tiers]
Flex DOES support (unlike old M2/M5): Atlas Search, Atlas Vector Search, Change Streams, Triggers - but Vector Search shares resources with mongod on Flex; upgrade to M10+ with dedicated Search Nodes before production Vector Search. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#flex-clusters-replaces-shared-and-serverless-tiers]
Migration is one-way: Flex → dedicated is supported (downtime required); dedicated → Flex downgrade is NOT supported. Download Flex snapshots before upgrading as they do not transfer to dedicated clusters. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#flex-clusters-replaces-shared-and-serverless-tiers]
For full Flex decision matrix, pricing breakdown, and tooling migration, see mongodb-atlas-flex-serverless skill. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#flex-clusters-replaces-shared-and-serverless-tiers]

Atlas Stream Processing (GA)

Atlas Stream Processing reached general availability as of March 2025. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-stream-processing-ga]
Enables continuous stream processing pipelines over Atlas data using aggregation-pipeline syntax. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-stream-processing-ga]
Supports emitting to Time Series Collections, Kafka headers, and multiple tiers (SP10 for low-traffic, SP30 for production). [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-stream-processing-ga]
Available on AWS and Azure across global regions. <https://www.mongodb.com/docs/atlas/atlas-stream-processing/> [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-stream-processing-ga]

Voyage AI acquisition and Automated Embedding

MongoDB acquired Voyage AI in February 2025 (~$220M) to embed high-accuracy embedding models directly into Atlas Vector Search. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#voyage-ai-acquisition-and-automated-embedding]
Automated Embedding (public preview May 2026) uses the autoEmbed index field type to automatically generate Voyage AI vector embeddings on insert, update, and query -- no external pipeline needed. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#voyage-ai-acquisition-and-automated-embedding]
Available models: voyage-4-large, voyage-4, voyage-4-lite, voyage-code-3. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#voyage-ai-acquisition-and-automated-embedding]
Pricing: per million tokens ($0.12 large / $0.06 standard / $0.02 lite); first 200M tokens free per account; Batch API gives 33% discount. <https://www.mongodb.com/docs/atlas/atlas-vector-search/> [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#voyage-ai-acquisition-and-automated-embedding]

Lexical Prefilters for Vector Search

Lexical Prefilters allow advanced text and geo analysis filters (fuzzy search, phrase matching, wildcards, geoWithin) as prefilters before vector similarity search. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#lexical-prefilters-for-vector-search]
Unlike standard $vectorSearch filters (equals, range, exists), lexical prefilters use full analyzed-text capabilities from Atlas Search operators. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#lexical-prefilters-for-vector-search]
Create a $search index with vector type fields and use $search.vectorSearch in aggregation pipelines. <https://www.mongodb.com/company/blog/product-release-announcements/semantic-power-lexical-precision-advanced-filtering-for-vector-search> [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#lexical-prefilters-for-vector-search]

Hybrid Search with `$rankFusion`

The $rankFusion aggregation operator merges and re-ranks results from multiple search pipelines (full-text + vector). [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#hybrid-search-with-rankfusion]
Requires MongoDB 8.1+ on Atlas. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#hybrid-search-with-rankfusion]
Enables true hybrid search combining keyword precision with semantic intelligence in a single query. <https://www.mongodb.com/docs/atlas/atlas-vector-search/hybrid-search/> [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#hybrid-search-with-rankfusion]

Search Nodes (dedicated search infrastructure)

Search Nodes are generally available on AWS, Google Cloud, and Azure for both development and production deployments. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#search-nodes-dedicated-search-infrastructure]
Provide dedicated infrastructure for Atlas Search and Vector Search, independent of database compute, with up to 60% query-time reduction. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#search-nodes-dedicated-search-infrastructure]
Multi-region Search Nodes are available in preview for multi-region and multi-cloud clusters. <https://www.mongodb.com/docs/atlas/atlas-search/> [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#search-nodes-dedicated-search-infrastructure]

Queryable Encryption enhancements

Equality and range queries on encrypted fields are GA and production-ready at no additional cost on Atlas, Enterprise Advanced, and Community Edition. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#queryable-encryption-enhancements]
Prefix, suffix, and substring queries on encrypted string fields are in public preview starting MongoDB 8.2. <https://www.mongodb.com/docs/manual/core/queryable-encryption/> [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#queryable-encryption-enhancements]

Terraform Provider 2.0

MongoDB Atlas Terraform Provider 2.0 shipped in 2025 with semantic versioning, no-breaking-change guarantees in minor/patch releases, eliminated hanging timeouts, and simplified advanced-cluster migrations. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#terraform-provider-20]
Migration required from 1.x; see the 2.0.0 Upgrade Guide. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#terraform-provider-20]
Atlas Architecture Center examples now target Provider 2.x. <https://www.mongodb.com/products/updates/terraform-mongodb-atlas-provider-2-0-now-available/> [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#terraform-provider-20]

Atlas Admin API standardized rate limiting

Standardized rate limiting for the Atlas Admin API v2 became GA in March 2026, using a token-bucket algorithm. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-admin-api-standardized-rate-limiting]
Automation and integration code should handle 429 Too Many Requests responses and respect Retry-After headers. <https://www.mongodb.com/company/blog/product-release-announcements/introducing-standardized-atlas-admin-api-rate-limiting> [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-admin-api-standardized-rate-limiting]

Atlas Architecture Center compliance additions

PCI DSS Compliance page added February 2026. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-architecture-center-compliance-additions]
HIPAA Compliance page added February 2026. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-architecture-center-compliance-additions]
Multi-region opinionated guidance, Reliability section, and Operational Readiness Checklist added August 2025. <https://www.mongodb.com/docs/atlas/architecture/current/changelog/> [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-architecture-center-compliance-additions]

Atlas CLI updates (2025-2026)

atlas api subcommand reached GA in October 2025. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-cli-updates-2025-2026]
TLS 1.3 support added for atlas api clusters commands (December 2025). [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-cli-updates-2025-2026]
atlas api aiModelRateLimits resetModelRateLimit command added April 2026. <https://www.mongodb.com/docs/atlas/cli/current/atlas-cli-changelog/> [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#atlas-cli-updates-2025-2026]

AI and agentic positioning

MongoDB is positioning Atlas as a converged datastore for agentic AI: operational data + vector search + stream processing + agent memory in one platform. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#ai-and-agentic-positioning]
First-class integrations with LangGraph.js (long-term memory store, GA), and major agent frameworks. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#ai-and-agentic-positioning]
Atlas AI Integrations documentation consolidates RAG, agent, and embedding patterns. <https://www.mongodb.com/docs/atlas/ai-integrations/> [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#ai-and-agentic-positioning]

Known ambiguities and guardrails

“All Atlas methods” is too large for a single static file. Use this context as the condensed expert map, then jump to the linked Admin API, CLI, driver, and Atlas feature references for exact syntax and complete inventories. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#known-ambiguities-and-guardrails]
Atlas docs are versioned and living. For vector search, API behavior, CLI commands, and limits, always confirm the current version or page timestamp when precision matters. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#known-ambiguities-and-guardrails]
Atlas advice often differs by cluster tier, deployment topology, cloud provider, and MongoDB version. Good answers should say which of those variables matter. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#known-ambiguities-and-guardrails]

Cross-hub map — where every MongoDB topic lives

All MongoDB knowledge is split across four hubs (plus mongodb-kb for KB-article lookups). If a task's deep material is not in this hub's Sub-skill routing table, it is a reference file under a sibling hub - activate that hub or Read its references/<name>.md directly. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#cross-hub-map-where-every-mongodb-topic-lives]
High-overlap routing notes: [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#cross-hub-map-where-every-mongodb-topic-lives]
- Performance symptom triage (high CPU, cache pressure, slow queries, latency spikes) starts at atlas-diagnostics-expert, but storage-engine root-cause internals (WiredTiger cache fill / dirty trigger / eviction threads / reconciliation / checkpoints) are owned by mongodb-expert - cross-load mongodb-expert/references/mongodb-wiredtiger-internals.md (and mongodb-wiredtiger.md) for depth. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#cross-hub-map-where-every-mongodb-topic-lives]
- Migration symptoms vs migration execution: live-cluster diagnosis → atlas-diagnostics-expert; the migration/mongosync runbook → mongodb-operations-expert. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#cross-hub-map-where-every-mongodb-topic-lives]
- Atlas Search/Vector query syntax & index design → mongodb-atlas-expert; the slowness triage of a running search → atlas-diagnostics-expert. [archived source: https://llms-explorer.com/sources/mdb-context-hub/mongodb-atlas-expert/#cross-hub-map-where-every-mongodb-topic-lives]

Where this helps

Planning which Atlas surface to use for a task — UI, Admin API, CLI, Terraform, or the Kubernetes Operator — before writing any automation. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
Deciding between Atlas Search and Atlas Vector Search, or a hybrid $rankFusion query, when a feature needs both relevance-ranked text and semantic retrieval. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
Reviewing an Atlas deployment's security posture across network access, database-user auth, and Atlas-user roles, which are three distinct controls with different scopes. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
Choosing between Free, Flex, and Dedicated tiers for a new project, given that Serverless and M2/M5 are deprecated and Flex is now the default entry tier. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.

Project ideas

Stand up an Atlas Admin API automation using service-account OAuth2 tokens instead of legacy API keys, and build retry/backoff handling for the standardized 429 rate limiting. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
Build a hybrid retrieval feature that combines Atlas Search (BM25) and Atlas Vector Search results with $rankFusion on MongoDB 8.1+. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
Provision a project's clusters, network access, and database users declaratively with the Atlas Terraform provider (2.0+), then intentionally make a manual UI change to observe drift detection. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
Prototype an Atlas Stream Processing pipeline that reads from Atlas or Kafka and emits to a Time Series Collection, to evaluate ASP against building a separate Kafka Streams/Flink deployment. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.

Antipatterns

Treating the Atlas Admin API as a data-plane API — it manages Atlas resources and access configuration only; reading and writing documents still goes through a driver or mongosh. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
Defaulting to multi-document transactions instead of exploiting single-document atomicity, when the actual requirement doesn't cross document boundaries. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
Adding indexes for every query shape without weighing the write-cost tradeoff of each additional index. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
Giving vector-search guidance without checking ANN/ENN availability by MongoDB version, since Atlas Vector Search behavior is version-gated. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.

Known issues

Serverless instances and M2/M5 shared clusters are deprecated; anything written against those tiers needs to account for automatic migration to Flex. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
Backup restore/admin operations require project-level backup roles specifically — org-level access alone is not sufficient until it's explicitly granted at the project. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
Automated Embedding (autoEmbed with Voyage AI models) was still in public preview as of May 2026, so its behavior and availability should be treated as evolving rather than settled. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
Atlas docs and behavior are versioned and living — CLI commands, API behavior, and limits should be reconfirmed against the current version rather than assumed static. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.

Children

Frontier under this node: MongoDB Atlas Data Federation

← the whole tree · 3D view· how to read this page