Databases · head to head
CosmosDB vs Memcached

CosmosDB
Databases
Globally distributed, multi-model database service from Azure
- From
- Free
- Rated
- -
The short version
- Each has a real cost: CosmosDB autoscale provisioned throughput enforces a minimum of 1,000 RU/s, billed hourly whether or not the database is used; Memcached no persistence at all: restart a node and its cache is gone, which every design must assume
- They diverge on capability: CosmosDB covers Global Distribution, Memcached covers In-memory key-value cache.
- Prices and features above were last checked on 1 September 2026.
Where they differ
Only the attributes on which CosmosDB and Memcached actually diverge.
Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated), category (Databases).
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 CosmosDB
- Global Distribution
- Multi-model APIs
- Elastic Scaling
- Five Consistency Levels
- SLA-backed Latency
- Automatic Indexing
- Serverless
- Azure Functions
Only in Memcached
- In-memory key-value cache
- Multithreaded
- Client-side sharding
- Predictable memory use
What people use each for
The jobs each tool is most often brought in to do.
CosmosDB
- Running a globally distributed multi model database on Azurenot Memcached
- Serving low latency reads and writes from multiple Azure regionsnot Memcached
- Storing document, key value and graph data behind a managed servicenot Memcached
Memcached
- Caching expensive database query results to cut loadnot CosmosDB
- Session storage where losing sessions on restart is acceptablenot CosmosDB
- Fronting an API whose responses are costly and change slowlynot CosmosDB
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
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
Memcached
- No persistence at all: restart a node and its cache is gone, which every design must assume
- No replication or failover, so losing a node loses that share of the cache
- Only simple key-value, with none of the lists, sorted sets or streams Redis offers
- Values are capped at 1MB by default, which surprises teams caching large documents
Pricing, plan by plan
CosmosDB
Free- Free TierFree
- 1000 RU/s
- 25GB storage
- First 12 months
- ServerlessFree
- Pay per request
- Auto-scaling
- Event-driven workloads
Memcached
Free- MemcachedFree
- Full functionality
- Self-hosted
- No usage limits
Which should you pick?
Choose CosmosDB if
- You need global distribution.
- You want to start without paying.
- You work on Web, Azure.
- You also want multi-model apis.
Choose Memcached if
- You need in-memory key-value cache.
- You want to start without paying.
- You work on Linux, macOS, Windows, Docker, Self-hosted.
- You also want multithreaded.
Questions people ask
- Is CosmosDB or Memcached better?
- Neither clearly leads. CosmosDB starts at Free and Memcached at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, CosmosDB or Memcached?
- CosmosDB starts at Free and Memcached at Free.
- Does CosmosDB or Memcached run on more platforms?
- CosmosDB runs on Web, Azure. Memcached runs on Linux, macOS, Windows, Docker, Self-hosted.
- Can I use CosmosDB for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is CosmosDB best used for?
- CosmosDB is most often used for running a globally distributed multi model database on azure, serving low latency reads and writes from multiple azure regions, storing document, key value and graph data behind a managed service. Of those, running a globally distributed multi model database on azure and serving low latency reads and writes from multiple azure regions are not what Memcached is typically brought in for.
- What can CosmosDB do that Memcached cannot?
- CosmosDB covers Global Distribution, Multi-model APIs, Elastic Scaling, Five Consistency Levels. Memcached covers In-memory key-value cache, Multithreaded, Client-side sharding, Predictable memory use.
Answered from the vendors’ own pages
CosmosDB: Is there a free tier for Azure Cosmos DB?
Yes, Cosmos DB offers a free tier with 1,000 RU/s of throughput and 25 GB of storage per month for the lifetime of the account, available to new accounts.
SourceMemcached: Is Memcached free?
Yes, open source with no licence fee.
CosmosDB: How is Cosmos DB priced after the free tier?
Cosmos DB uses three billing models: provisioned throughput billed per request unit per second, vCore pricing for certain APIs, or serverless consumption pricing where you pay only for requests processed. Reserved capacity offers 20% discount for one year or 30% for three years.
SourceMemcached: Memcached or Redis?
Memcached is a pure cache: simpler, multithreaded and very predictable. Redis adds persistence, replication and rich data structures, which is why it is the default choice unless you specifically want a cache and nothing more.
CosmosDB: Can I change my pricing model after choosing one?
No. Once you select a compute pricing model and API, they cannot be changed. This choice is permanent for that database.
SourceMemcached: Does Memcached persist data?
No. Everything is in memory and lost on restart, by design.
CosmosDB: Is there a trial period for Cosmos DB beyond the free tier?
Azure offers a 30-day free trial account for all Azure services. Additionally, Azure AI customers may be eligible for a 90-day free Cosmos DB subscription through the Azure AI Advantage program.
SourceRelated pages
Other head to heads
- CosmosDB vs Amazon Aurora
- CosmosDB vs Cockroach Labs
- CosmosDB vs Airtable
- CosmosDB vs PostgreSQL
- CosmosDB vs Google Cloud SQL
- CosmosDB vs ArangoDB
- CosmosDB vs DataStax
- CosmosDB vs FaunaDB
- CosmosDB vs Firebolt
- CosmosDB vs turbopuffer
- CosmosDB vs VerneMQ
- CosmosDB vs Vespa
- CosmosDB vs Xata
- CosmosDB vs YugabyteDB
- CosmosDB vs Zilliz
- CosmosDB vs Amazon Redshift
- CosmosDB vs BigQuery
- CosmosDB vs Amazon RDS
- CosmosDB vs Dragonfly
- CosmosDB vs Valkey
- CosmosDB vs Readyset
- CosmosDB vs DuckDB
- CosmosDB vs DynamoDB
- CosmosDB vs NATS
- CosmosDB vs Apache Pulsar
- CosmosDB vs Presto
- CosmosDB vs Timeplus
- CosmosDB vs RabbitMQ
- CosmosDB vs EMQX
- CosmosDB vs Firebase Realtime Database
- CosmosDB vs MotherDuck
- CosmosDB vs Neo4j
- CosmosDB vs Apache Kafka
- CosmosDB vs Firestore
- Memcached vs Amazon Aurora
- Memcached vs Cockroach Labs
- Memcached vs Airtable
- Memcached vs PostgreSQL
- Memcached vs Google Cloud SQL
- Memcached vs ArangoDB
- Memcached vs DataStax
- Memcached vs FaunaDB
- Memcached vs Firebolt
- Memcached vs turbopuffer
- Memcached vs VerneMQ
- Memcached vs Vespa
- Memcached vs Xata
- Memcached vs YugabyteDB
- Memcached vs Zilliz
- Memcached vs Amazon Redshift
- Memcached vs BigQuery
- Memcached vs Amazon RDS
- Memcached vs Dragonfly
- Memcached vs Valkey
- Memcached vs Readyset
- Memcached vs DuckDB
- Memcached vs DynamoDB
- Memcached vs NATS
- Memcached vs Apache Pulsar
- Memcached vs Presto
- Memcached vs Timeplus
- Memcached vs RabbitMQ
- Memcached vs EMQX
- Memcached vs Firebase Realtime Database
- Memcached vs MotherDuck
- Memcached vs Neo4j
- Memcached vs Apache Kafka
- Memcached vs Firestore
