Softwr

Databases · head to head

Valkey vs Memcached

Valkey logo

Valkey

Databases

Open-source in-memory data store forked from Redis

From
Free
Rated
-
Full reviewWebsite
Memcached logo

Memcached

Databases

Distributed memory object caching system

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Valkey younger project, so its track record is short even though the codebase is not; Memcached no persistence at all: restart a node and its cache is gone, which every design must assume
  • They diverge on capability: Valkey covers Redis-compatible, Memcached covers In-memory key-value cache.

Where they differ

Only the attributes on which Valkey and Memcached actually diverge.

Attributes where Valkey and Memcached differ
AttributeValkeyMemcached
PlatformsLinux, macOS, Docker, Self-hostedLinux, macOS, Windows, Docker, Self-hosted

Identical on both: starting price (Free), pricing model (Open source, no licence fee; managed cloud billed separately), 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 Valkey

  • Redis-compatible
  • BSD licensed
  • Rich data structures
  • Replication and persistence

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.

Valkey

  • Continuing on a permissively licensed in-memory store after the Redis licence changenot Memcached
  • Caching and session storage where a foundation-governed project is a procurement requirementnot Memcached
  • Migrating from Redis without rewriting application codenot Memcached

Memcached

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

Where each one falls short

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

Valkey

  • Younger project, so its track record is short even though the codebase is not
  • Divergence from Redis grows over time, so compatibility is strongest near the fork point and weakens as both evolve
  • Ecosystem tooling and documentation still frequently assume Redis, leaving translation work

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

Valkey

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

Memcached

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

Which should you pick?

Choose Valkey if

  • You need redis-compatible.
  • You want to start without paying.
  • You work on Linux, macOS, Docker, Self-hosted.
  • You also want bsd licensed.
Valkey review

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

Questions people ask

Is Valkey or Memcached better?
Neither clearly leads. Valkey 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, Valkey or Memcached?
Valkey starts at Free and Memcached at Free.
Does Valkey or Memcached run on more platforms?
Valkey runs on Linux, macOS, Docker, Self-hosted. Memcached runs on Linux, macOS, Windows, Docker, Self-hosted.
Can I use Valkey for free?
Both have a free tier, so you can try either at no cost before committing.
What is Valkey best used for?
Valkey is most often used for continuing on a permissively licensed in-memory store after the redis licence change, caching and session storage where a foundation-governed project is a procurement requirement, migrating from redis without rewriting application code. Of those, continuing on a permissively licensed in-memory store after the redis licence change and caching and session storage where a foundation-governed project is a procurement requirement are not what Memcached is typically brought in for.
What can Valkey do that Memcached cannot?
Valkey covers Redis-compatible, BSD licensed, Rich data structures, Replication and persistence. Memcached covers In-memory key-value cache, Multithreaded, Client-side sharding, Predictable memory use.

Answered from the vendors’ own pages

Valkey: Is Valkey free?

Yes, BSD-licensed open source under the Linux Foundation.

Memcached: Is Memcached free?

Yes, open source with no licence fee.

Valkey: Why does Valkey exist?

Redis changed its licence away from BSD in 2024. Valkey is the community fork continuing under permissive terms, backed by AWS, Google Cloud and Oracle among others.

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.

Valkey: Can I switch from Redis to Valkey?

At the fork point it is drop-in compatible with existing clients and data. The further both projects move from that point, the more you should verify the specific features you use.

Memcached: Does Memcached persist data?

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

Share

Related pages

More on Valkey

More on Memcached

Keep looking

Other head to heads