Softwr

Databases · head to head

Memcached vs Apache Solr

Memcached logo

Memcached

Databases

Distributed memory object caching system

From
Free
Rated
-
Apache Solr logo

Apache Solr

Databases

Enterprise search platform built on Apache Lucene

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; Apache Solr xML-heavy configuration and a developer experience that feels dated beside newer engines
  • They diverge on capability: Memcached covers In-memory key-value cache, Apache Solr covers Lucene-based indexing.

Where they differ

Only the attributes on which Memcached and Apache Solr actually diverge.

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

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 Apache Solr

  • Lucene-based indexing
  • Faceted search
  • SolrCloud
  • Schema control

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

Apache Solr

  • Library, archive and catalogue search where faceting is centralnot Memcached
  • Long-lived enterprise deployments valuing stability over noveltynot Memcached
  • Search requiring precise, explicitly configured relevance tuningnot 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

Apache Solr

  • XML-heavy configuration and a developer experience that feels dated beside newer engines
  • SolrCloud depends on ZooKeeper, adding a component Elasticsearch removed years ago
  • Smaller mindshare now, so newer tutorials, hiring and integrations favour Elasticsearch
  • Considerably heavier than a purpose-built application search engine

Pricing, plan by plan

Memcached

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

Apache Solr

Free
  • Apache SolrFree
    • 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 Apache Solr if

  • You need lucene-based indexing.
  • You want to start without paying.
  • You work on Linux, Docker, Kubernetes, Self-hosted.
  • You also want faceted search.

Questions people ask

Is Memcached or Apache Solr better?
Neither clearly leads. Memcached starts at Free and Apache Solr at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Memcached or Apache Solr?
Memcached starts at Free and Apache Solr at Free.
Does Memcached or Apache Solr run on more platforms?
Memcached runs on Linux, macOS, Windows, Docker, Self-hosted. Apache Solr runs on Linux, Docker, Kubernetes, Self-hosted.
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 Apache Solr is typically brought in for.
What can Memcached do that Apache Solr cannot?
Memcached covers In-memory key-value cache, Multithreaded, Client-side sharding, Predictable memory use. Apache Solr covers Lucene-based indexing, Faceted search, SolrCloud, Schema control.

Answered from the vendors’ own pages

Memcached: Is Memcached free?

Yes, open source with no licence fee.

Apache Solr: Is Apache Solr free?

Yes, open source under the Apache Software Foundation.

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.

Apache Solr: Solr or Elasticsearch?

Both are built on Lucene. Elasticsearch has the larger ecosystem and a friendlier API; Solr is very mature and strong on faceted search, and remains common in library and catalogue systems.

Memcached: Does Memcached persist data?

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

Apache Solr: Is Solr still maintained?

Yes, actively, as a top-level Apache project.

Share

Related pages

Other head to heads