Softwr

Databases · head to head

Typesense vs Memcached

Typesense logo

Typesense

Databases

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

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: Typesense holding the index in memory caps dataset size by available RAM, which becomes expensive at scale; Memcached no persistence at all: restart a node and its cache is gone, which every design must assume
  • They diverge on capability: Typesense covers In-memory index, Memcached covers In-memory key-value cache.

Where they differ

Only the attributes on which Typesense and Memcached actually diverge.

Attributes where Typesense and Memcached differ
AttributeTypesenseMemcached
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 Typesense

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

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.

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

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

Where each one falls short

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

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

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

Typesense

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

Memcached

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

Which should you pick?

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

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 Typesense or Memcached better?
Neither clearly leads. Typesense 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, Typesense or Memcached?
Typesense starts at Free and Memcached at Free.
Does Typesense or Memcached run on more platforms?
Typesense runs on Linux, macOS, Docker, Self-hosted. Memcached runs on Linux, macOS, Windows, Docker, Self-hosted.
Can I use Typesense for free?
Both have a free tier, so you can try either at no cost before committing.
What is Typesense best used for?
Typesense is most often used for replacing algolia when per-search pricing outgrows the value, instant search over a product catalogue or documentation site, hybrid keyword and vector search without running two systems. Of those, replacing algolia when per-search pricing outgrows the value and instant search over a product catalogue or documentation site are not what Memcached is typically brought in for.
What can Typesense do that Memcached cannot?
Typesense covers In-memory index, Typo tolerance, Faceting and filtering, Vector search. Memcached covers In-memory key-value cache, Multithreaded, Client-side sharding, Predictable memory use.

Answered from the vendors’ own pages

Typesense: Is Typesense free?

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

Memcached: Is Memcached free?

Yes, open source with no licence fee.

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: 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: Does Typesense support vector search?

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

Memcached: Does Memcached persist data?

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

Share

Related pages

More on Typesense

More on Memcached

Keep looking

Other head to heads