Softwr

Databases · head to head

Memcached vs NATS

Memcached logo

Memcached

Databases

Distributed memory object caching system

From
Free
Rated
-
Full reviewWebsite
NATS logo

NATS

Databases

High-performance messaging system for cloud-native applications

From
Free
Rated
-
Full reviewWebsite

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; NATS core NATS has no persistence at all, so messages are lost if no subscriber is listening
  • They diverge on capability: Memcached covers In-memory key-value cache, NATS covers Very low latency.

Where they differ

Only the attributes on which Memcached and NATS actually diverge.

Attributes where Memcached and NATS differ
AttributeMemcachedNATS
Pricing modelOpen source, no licence fee; managed cloud billed separatelyOpen source, no licence fee
PlatformsLinux, macOS, Windows, Docker, Self-hostedLinux, macOS, Windows, Docker, Kubernetes

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 Memcached

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

Only in NATS

  • Very low latency
  • JetStream
  • Single binary
  • Request-reply

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 NATS
  • Session storage where losing sessions on restart is acceptablenot NATS
  • Fronting an API whose responses are costly and change slowlynot NATS

NATS

  • Service-to-service messaging where latency is the binding constraintnot Memcached
  • Edge and IoT messaging where a lightweight broker mattersnot Memcached
  • Replacing a heavier broker when the workload does not need its guaranteesnot 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

NATS

  • Core NATS has no persistence at all, so messages are lost if no subscriber is listening
  • JetStream adds the durability but also the operational complexity NATS is chosen to avoid
  • A much smaller ecosystem than Kafka or RabbitMQ, with fewer connectors and integrations
  • Fewer people know it, so hiring and existing organisational knowledge favour the alternatives

Pricing, plan by plan

Memcached

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

NATS

Free
  • NATSFree
    • 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.
Memcached review

Choose NATS if

  • You need very low latency.
  • You want to start without paying.
  • You work on Linux, macOS, Windows, Docker, Kubernetes.
  • You also want jetstream.
NATS review

Questions people ask

Is Memcached or NATS better?
Neither clearly leads. Memcached starts at Free and NATS at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Memcached or NATS?
Memcached starts at Free and NATS at Free.
Does Memcached or NATS run on more platforms?
Memcached runs on Linux, macOS, Windows, Docker, Self-hosted. NATS runs on Linux, macOS, Windows, Docker, Kubernetes.
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 NATS is typically brought in for.
What can Memcached do that NATS cannot?
Memcached covers In-memory key-value cache, Multithreaded, Client-side sharding, Predictable memory use. NATS covers Very low latency, JetStream, Single binary, Request-reply.

Answered from the vendors’ own pages

Memcached: Is Memcached free?

Yes, open source with no licence fee.

NATS: Is NATS free?

Yes, open source and CNCF-graduated. Synadia sells a managed service.

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.

NATS: Does NATS persist messages?

Core NATS does not — it is fire-and-forget. JetStream adds persistence, streaming and replay when you need them.

Memcached: Does Memcached persist data?

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

NATS: NATS or Kafka?

NATS is far lighter and lower latency, and much simpler to run. Kafka is the answer when you need a durable replayable log and a large connector ecosystem.

Share

Related pages

More on Memcached

More on NATS

Keep looking

Other head to heads