Softwr

Databases · head to head

Memcached vs Typesense

Memcached logo

Memcached

Databases

Distributed memory object caching system

From
Free
Rated
-
Full reviewWebsite
Typesense logo

Typesense

Databases

Open-source typo-tolerant search engine as an Algolia alternative

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; Typesense holding the index in memory caps dataset size by available RAM, which becomes expensive at scale
  • They diverge on capability: Memcached covers In-memory key-value cache, Typesense covers In-memory index.

Where they differ

Only the attributes on which Memcached and Typesense actually diverge.

Attributes where Memcached and Typesense differ
AttributeMemcachedTypesense
PlatformsLinux, macOS, Windows, Docker, Self-hostedLinux, macOS, 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 Memcached

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

Only in Typesense

  • In-memory index
  • Typo tolerance
  • Faceting and filtering
  • Vector search

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

Typesense

  • Replacing Algolia when per-search pricing outgrows the valuenot Memcached
  • Instant search over a product catalogue or documentation sitenot Memcached
  • Hybrid keyword and vector search without running two systemsnot 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

Typesense

  • Holding the index in memory caps dataset size by available RAM, which becomes expensive at scale
  • Narrower than Elasticsearch by design: no log analytics or complex aggregation pipelines
  • Smaller ecosystem and community than Algolia or Elasticsearch, so fewer integrations exist off the shelf

Pricing, plan by plan

Memcached

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

Typesense

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

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 Typesense if

  • You need in-memory index.
  • You want to start without paying.
  • You work on Linux, macOS, Docker, Self-hosted.
  • You also want typo tolerance.
Typesense review

Questions people ask

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

Answered from the vendors’ own pages

Memcached: Is Memcached free?

Yes, open source with no licence fee.

Typesense: Is Typesense free?

The engine is open source and free to self-host. Typesense Cloud is a paid managed option.

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.

Typesense: Why choose Typesense over Algolia?

Cost and control. Algolia charges per search and per record; Typesense can be self-hosted with no per-query fee, at the cost of running it yourself.

Memcached: Does Memcached persist data?

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

Typesense: Does Typesense support vector search?

Yes, including hybrid search combining keyword and semantic matching in one query.

Share

Related pages

More on Memcached

More on Typesense

Keep looking

Other head to heads