MongoDB Atlas Setup: Complete Guide

MongoDB Atlas is a fully managed cloud database service. This guide explains how to set up MongoDB Atlas, design your data model, and scale your database for production use.

Deploy Atlas

Phase 1: Environment provisioning (Atlas setup)

Establish your core infrastructure. This phase focuses on identity, network isolation, and cluster architecture to create a secure, high-availability baseline.

Phase 2: Data engineering

Transition into document modeling. Align your schema with application logic. Migrate existing datasets using managed synchronization tools.

Phase 3: Optimization and scale

Optionally, consider implementing search and AI capabilities. Configure performance safeguards. Automate infrastructure management for repeatable deployments.

FAQs

Free tier supports up to 512MB. Upgrade for more storage and features.

View pricing

Choose your MongoDB Atlas cluster tier by aligning its resources with your specific application workload, data size, and performance needs, differentiating between Free/Flex tiers for development and Dedicated M30+ clusters for production and high-traffic performance.

Key considerations include:

Free Tier (M0): Best for learning and exploring, with limited resources.
Flex: Ideal for development and testing, offering the lowest cost option with certain feature limitations.
Dedicated (M10 & M20): Suitable for pre-production and small, non-critical workloads. These tiers utilize shared vCPUs and support replica set deployments offering fully featured access to Atlas.

Dedicated (M30+): Recommended for performance-critical and high-traffic workloads, supporting both replica sets and sharded clusters with fully featured access to Atlas with dedicated vCPUs.

Clusters can always be scaled up from any tier as requirements expand. If unsure, MongoDB recommends starting with a lower tier and monitoring performance before adjusting. For all Dedicated tiers, use auto-scaling to adjust cluster tier and storage as workloads evolve.

How to select your cluster tier →

Atlas cluster sizing and tier selection →

Free tier is more for learning and testing than production. For production apps, use M10/M20 for pre-production and smaller-scale production applications, and M30+ for high-traffic, performance-critical production workloads.

Upgrade now

If you hit the limit on a cluster free tier, you can upgrade to a dedicated tier for more resources and access to more features.

Upgrade cluster

To effectively manage and reduce MongoDB Atlas costs, right-size clusters with auto-scaling, optimize data management by leveraging Online Archive for cold data, minimize data transfer using query projections and co-locating clusters, and continuously monitor spending with the Billing Cost Explorer and alerts.

Right-size clusters: Pause development or testing clusters when not in use. Alternatively, terminate them if no longer required. For Dedicated clusters, use auto-scaling to adjust cluster storage and/or use a tier-based approach for real-time CPU and memory utilization.

Optimize data management: Design efficient schemas and use strategic indexing to improve query performance while minimizing resource consumption. Regularly review clusters, databases, and collections to eliminate duplication, outdated data, and unused sample datasets. For Dedicated clusters, use Atlas Online Archive to tier infrequently accessed data, which will reduce primary storage costs.

Minimize data transfer: Reduce data transfer costs by heeding the following best practices:

Avoid queries that re-read client data or re-write existing cluster data.
Use query projections to only retrieve necessary fields.
Deploy applications in the same cloud region as the Atlas cluster.

Enable network compression in client drivers to reduce data volume.

Monitor & alerts: Regularly review spending patterns using the Billing Cost Explorer tool in Atlas. Additionally, set up billing alerts to be notified of unexpected cost spikes or when usage approaches predefined thresholds.