MongoDB Atlas Comparison

Yes

AWS, Azure & Google Cloud, including multi-cloud clusters spanning all three cloud platforms

Yes

Runs native MongoDB

Yes

Run v7.0, 6.0, 5.0 or v4.4.

Yes

Storage: 512 MB, RAM: Variable

Yes

Resistant to initial interruptions, filterable, topology agnostic.

Yes

Multiple instance sizes and classes

BSON

(Binary JSON) Regular JSON + longs, doubles, floats, decimal, dates, and times

Yes

MongoDB aggregation pipeline and Atlas Search

Yes

Yes

Yes

Performance Advisor with schema and index recommendations

Up to 50 replicas

All replicas configured as data-bearing nodes

Yes

Scale writes horizontally across multiple nodes. Store multiple TB of data on a single shard.

Ability to refine shard key as application requirements evolve.

Since 7.0, shard key advisor commands provide metrics that facilitate shard key refining.

Yes

Directly in Atlas UI, or via MongoDB Compass

Yes

Yes

Yes

Yes

Atlas for the Edge provides Atlas Device Sync & SDKs

No

Claims compatibility with v4.0 API, which is only partially true. No MongoDB server side code

No

Claims compatibility with v4.0 API, which is only partially true.

Yes

Available as separate paid service

Limited

Around a dozen instances only, all of a single AWS class, limiting flexibility in accommodating different workload profiles

Limited

Missing features, fail over half of transaction tests in standard MongoDB test suite

Primitive JSON

and some advanced data types, but does not support decimal

No

All schema controls must be written in the app tier

Partial

No integrated text search

Up to 15 replicas

Replicas are not data-bearing. DocumentDB maintains 6 copies of data at the storage layer

No sharding support

All writes must be made to a single primary node only.

No

Claims compatibility with v4.0 API, actually closer to 3.6. No MongoDB server side code.

Fails 66% of compatibility tests.

No

Claims compatibility with v4.0 API, actually closer to 3.6.

Limited

Just for the first 400 RU/s. Not sandboxed, so no way to avoid cost if usage increases beyond the 400RU limit

Yes

Only for eligible accounts

No

Configuration based on provisioned throughput. No way to independently select underlying hardware configurations

Limited

Multi-document transactions are supported only within a single, unsharded collection; almost all of MongoDB's transaction tests fail

BSON

Some data types have restrictions, including the inability to modify them once set

No

All schema controls must be written in the app tier

Partial

No integrated text search

Yes

However, no support to refine the chosen shard key, forcing a full database migration should the shard key need to change in any way.

Yes

Power BI and Qlik Sense only

No

Single AWS region only, only one writeable node

Limited

Read operations only. Writes locked to primary only

Yes

Risk of data loss due to conflict resolution. Reads can be eventually consistent (returning stale or deleted data)

Yes

Reads can be eventually consistent (returning stale or deleted data)

Yes

MongoDB Atlas UI & support for APM platforms (i.e., New Relic)

No.

Storage only

Partial

Only a limited number of account-level metrics are exposed

N/a

Sharding not supported

Yes

50% upcharge for autoscaling, can only scale within a certain tier

Partial

Only a limited number of account-level metrics are exposed

No

Snapshots taken every 4 hours. Service ticket must be raised for Cosmos DB support to restore the backup. Must be completed within 8 hours or snapshots are overwritten and data is lost

Yes

TLS/SSL as standard

No

AWS KMS only

Partial

Limited coarse-grained roles only

Partial

Preview only and limited capabilities

No

Azure key vault only

Partial

Limited coarse-grained roles only

Yes

Available with an optional support contract

Yes