Layer 3 · self-hosting reality check
What it actually takes to self-host Memcached
The docs say 64 MB. In practice you want Exactly the cache size you allocate. Here is the honest version — real requirements, real monthly cost, what you will be maintaining, and the one thing that catches people out.
Usually reached from Redis alternatives, where Memcached is one of the picks.
| RAM — documented minimum | 64 MB |
|---|---|
| RAM — what it really needs | Exactly the cache size you allocate |
| CPU | 2 vCPU — it is multi-threaded, unlike Redis |
| Disk | None. Memory only, by design. |
| Monthly cost | $6–18/mo depending on cache size |
| Setup time | 15 minutes |
| How you install it | package or container; there is almost nothing to configure |
| Ongoing maintenance | Very low. It is one of the most boring pieces of infrastructure in existence, which is a compliment. |
| Where it stops scaling | Enormously, and it uses all cores properly. For pure key-value caching it often outperforms the richer alternatives. |
The thing that catches people out
No persistence and no replication, deliberately — restart the process and the cache is empty. If your application cannot survive a cold cache, you have built a hard dependency on something explicitly designed to be disposable. A thundering herd against the database after a Memcached restart is the classic outage; add jittered TTLs and a stampede guard before you need them.
When not to self-host Memcached
You need data structures, persistence or pub/sub. That is Redis and Valkey territory — Memcached does one thing.
Every guide here carries this section. A site that only ever tells you to self-host is selling something — the useful answer is sometimes no.
Other Layer 3 self-hosting guides
Common questions
- How much RAM does Memcached actually need?
- Exactly the cache size you allocate in practice. The documented minimum is 64 MB, which is the figure at which the process starts rather than the figure at which it works under real use. 2 vCPU — it is multi-threaded, unlike Redis alongside it.
- What does self-hosting Memcached cost per month?
- $6–18/mo depending on cache size This is commodity VPS pricing and excludes your time, which is the larger cost for most people — budget for very low. It is one of the most boring pieces of infrastructure in existence, which is a compliment.
- How long does it take to set up Memcached?
- 15 minutes, via package or container; there is almost nothing to configure.
- When should I NOT self-host Memcached?
- You need data structures, persistence or pub/sub. That is Redis and Valkey territory — Memcached does one thing.
- What is the most common mistake when self-hosting Memcached?
- No persistence and no replication, deliberately — restart the process and the cache is empty. If your application cannot survive a cold cache, you have built a hard dependency on something explicitly designed to be disposable. A thundering herd against the database after a Memcached restart is the classic outage; add jittered TTLs and a stampede guard before you need them.