Softwr

Databases · head to head

Memcached vs Thanos

M

Memcached

Databases

Distributed memory object caching system

From
Free
Rated
-
Thanos logo

Thanos

Cloud

Highly available Prometheus with long-term object storage

From
Free
Rated
-

The short version

  • Each has a real cost: Memcached no persistence at all: restart a node and its cache is gone, which every design must assume; Thanos several components — sidecar, store, querier, compactor, ruler — each with its own configuration and failure modes
  • They diverge on capability: Memcached covers In-memory key-value cache, Thanos covers Global query.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Memcached and Thanos actually diverge.

Attributes where Memcached and Thanos differ
AttributeMemcachedThanos
Pricing modelOpen source, no licence fee; managed cloud billed separatelyOpen source, no licence fee
PlatformsLinux, macOS, Windows, Docker, Self-hostedKubernetes, Linux, Docker
CategoryDatabasesCloud

Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated).

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 Memcached

  • In-memory key-value cache
  • Multithreaded
  • Client-side sharding
  • Predictable memory use

Only in Thanos

  • Global query
  • Object storage retention
  • Deduplication
  • Downsampling

What people use each for

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

Memcached

  • Caching expensive database query results to cut loadnot Thanos
  • Session storage where losing sessions on restart is acceptablenot Thanos
  • Fronting an API whose responses are costly and change slowlynot Thanos

Thanos

  • Querying metrics across many clusters or regions from one placenot Memcached
  • Retaining metrics for years without local disk growthnot Memcached
  • Removing the gap that appears when a single Prometheus instance restartsnot Memcached

Where each one falls short

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

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

Thanos

  • Several components — sidecar, store, querier, compactor, ruler — each with its own configuration and failure modes
  • The compactor is a common source of operational trouble and must not run twice against the same bucket
  • Query latency over object storage is meaningfully higher than local Prometheus
  • Object storage costs and API request charges become real at high volume

Pricing, plan by plan

Memcached

Free
  • MemcachedFree
    • Full functionality
    • Self-hosted
    • No usage limits

Thanos

Free
  • ThanosFree
    • Full functionality
    • No usage limits
    • Community support

Which should you pick?

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.

Choose Thanos if

  • You need global query.
  • You want to start without paying.
  • You work on Kubernetes, Linux, Docker.
  • You also want object storage retention.

Questions people ask

Is Memcached or Thanos better?
Neither clearly leads. Memcached starts at Free and Thanos at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Memcached or Thanos?
Memcached starts at Free and Thanos at Free.
Does Memcached or Thanos run on more platforms?
Memcached runs on Linux, macOS, Windows, Docker, Self-hosted. Thanos runs on Kubernetes, Linux, Docker.
Can I use Memcached for free?
Both have a free tier, so you can try either at no cost before committing.
What is Memcached best used for?
Memcached is most often used for caching expensive database query results to cut load, session storage where losing sessions on restart is acceptable, fronting an api whose responses are costly and change slowly. Of those, caching expensive database query results to cut load and session storage where losing sessions on restart is acceptable are not what Thanos is typically brought in for.
What can Memcached do that Thanos cannot?
Memcached covers In-memory key-value cache, Multithreaded, Client-side sharding, Predictable memory use. Thanos covers Global query, Object storage retention, Deduplication, Downsampling.

Answered from the vendors’ own pages

Memcached: Is Memcached free?

Yes, open source with no licence fee.

Thanos: Is Thanos free?

Yes, open source and CNCF-incubating. Costs are the object storage it uses.

Memcached: 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.

Thanos: Does Thanos replace Prometheus?

No. It runs alongside existing Prometheus servers, adding global query, deduplication and long-term storage.

Memcached: Does Memcached persist data?

No. Everything is in memory and lost on restart, by design.

Thanos: Thanos or VictoriaMetrics?

Thanos layers onto Prometheus using object storage and is the more established multi-cluster answer. VictoriaMetrics is a separate store aiming at lower resource use and fewer moving parts.

Share

Related pages

Other head to heads