Softwr

Database & Data Management · head to head

Amazon Aurora vs CosmosDB

Amazon Aurora logo

Amazon Aurora

Database & Data Management

MySQL and PostgreSQL-compatible relational database built for the cloud

From
Free
Rated
-
CosmosDB logo

CosmosDB

Database & Data Management

Globally distributed, multi-model database service from Azure

From
Free
Rated
-

The short version

  • Each has a real cost: Amazon Aurora aurora requires AWS ecosystem knowledge and integration with other AWS services; CosmosDB autoscale provisioned throughput enforces a minimum of 1,000 RU/s, billed hourly whether or not the database is used
  • They diverge on capability: Amazon Aurora covers MySQL/PostgreSQL Compatible, CosmosDB covers Global Distribution.

Where they differ

Only the attributes on which Amazon Aurora and CosmosDB actually diverge.

Attributes where Amazon Aurora and CosmosDB differ
AttributeAmazon AuroraCosmosDB
PlatformsAWS CloudWeb, Azure
Founded20061975

Identical on both: starting price (Free), pricing model (usage-based), free tier (Yes), user rating (Not yet rated), category (Database & Data Management).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Amazon Aurora

  • MySQL/PostgreSQL Compatible
  • 5x MySQL Performance
  • Auto-scaling Storage
  • Global Database
  • Serverless v2
  • Multi-master
  • Fault Tolerant
  • AWS Lambda

Only in CosmosDB

  • Global Distribution
  • Multi-model APIs
  • Elastic Scaling
  • Five Consistency Levels
  • SLA-backed Latency
  • Automatic Indexing
  • Serverless
  • Azure Functions

Both cover

  • Web support

What people use each for

The jobs each tool is most often brought in to do.

Amazon Aurora

  • Transaction processingnot CosmosDB
  • Data storagenot CosmosDB
  • Application backendnot CosmosDB
  • Reportingnot CosmosDB
  • Data analyticsnot CosmosDB

CosmosDB

  • Running a globally distributed multi model database on Azurenot Amazon Aurora
  • Serving low latency reads and writes from multiple Azure regionsnot Amazon Aurora
  • Storing document, key value and graph data behind a managed servicenot Amazon Aurora

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Amazon Aurora

  • Aurora requires AWS ecosystem knowledge and integration with other AWS services
  • Pricing can become expensive with high-traffic applications using many read replicas
  • Limited support for non-relational data types compared to NoSQL alternatives

CosmosDB

  • Autoscale provisioned throughput enforces a minimum of 1,000 RU/s, billed hourly whether or not the database is used
  • Provisioned throughput is charged in every region the account is replicated to, so multi region accounts multiply the RU bill
  • Storage charges cover data, indexes and backups in each replicated region
  • Egress out of Azure and between regions is charged, though ingress is free
  • The free allowance is one account per Azure subscription, limited to 1,000 RU/s and 25 GB
  • RU/s rates vary by region and are only shown through the pricing calculator rather than a flat published rate

Pricing, plan by plan

Amazon Aurora

Free
  • Serverless v2$0.12/hour
    • Auto-scaling
    • Pay per ACU
    • Instant scaling
  • Provisioned$29/month
    • Dedicated instances
    • Predictable performance
    • Reserved capacity

CosmosDB

Free
  • Free TierFree
    • 1000 RU/s
    • 25GB storage
    • First 12 months
  • ServerlessFree
    • Pay per request
    • Auto-scaling
    • Event-driven workloads

Which should you pick?

Choose Amazon Aurora if

  • You need mysql/postgresql compatible.
  • You want to start without paying.
  • You work on AWS Cloud.
  • You also want 5x mysql performance.

Choose CosmosDB if

  • You need global distribution.
  • You want to start without paying.
  • You work on Web, Azure.
  • You also want multi-model apis.

Questions people ask

Is Amazon Aurora or CosmosDB better?
Neither clearly leads. Amazon Aurora starts at Free and CosmosDB at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Amazon Aurora or CosmosDB?
Amazon Aurora starts at Free and CosmosDB at Free.
Does Amazon Aurora or CosmosDB run on more platforms?
Amazon Aurora runs on AWS Cloud. CosmosDB runs on Web, Azure.
Can I use Amazon Aurora for free?
Both have a free tier, so you can try either at no cost before committing.
What is Amazon Aurora best used for?
Amazon Aurora is most often used for transaction processing, data storage, application backend, reporting. Of those, transaction processing and data storage are not what CosmosDB is typically brought in for.
What can Amazon Aurora do that CosmosDB cannot?
Amazon Aurora covers MySQL/PostgreSQL Compatible, 5x MySQL Performance, Auto-scaling Storage, Global Database. CosmosDB covers Global Distribution, Multi-model APIs, Elastic Scaling, Five Consistency Levels. Both handle Web support.

Answered from the vendors’ own pages

Amazon Aurora: Is Amazon Aurora compatible with MySQL and PostgreSQL?

Yes, Amazon Aurora offers MySQL and PostgreSQL compatibility with full compatibility to their open-source counterparts, allowing you to migrate existing databases with standard tools.

Source
Amazon Aurora: What uptime SLA does Amazon Aurora provide?

Aurora is designed for up to 99.99% single-region uptime and 99.999% multi-region uptime with automatic failover.

Source
Amazon Aurora: How much does Amazon Aurora cost?

Aurora uses serverless, usage-based pricing where you pay only for consumed capacity. Typical pricing ranges from $50-70 per month for minimal setups to $400-600 per month for small production clusters.

Source
Amazon Aurora: Can Amazon Aurora scale automatically?

Yes, Aurora automatically scales to match workload demands without performance degradation, supporting both read and write scaling.

Source
Amazon Aurora: How many read replicas does Aurora support?

Aurora supports up to 15 low-latency read replicas for distributing read traffic across your application.

Source

Related pages

Other head to heads