Ravi Sir's Cards › AWS
Redis vs Memcached
This revision card explains Redis vs Memcached. It starts from the need that picking Memcached when you need locks or streams forces a painful migrate later. It describes redis — rich types, replication, persistence options, common default. Memcached: simple multi-node object cache. The how-to section notes choose Redis unless you have a clear Memcached-only pattern and tooling. An example on the card is session store + rate limit counters fit Redis; a pure blob cache can use either.
Read card text
What this card says
Why do we need it?
Picking Memcached when you need locks or streams forces a painful migrate later.
What is it?
Redis: rich types, replication, persistence options, common default. Memcached: simple multi-node object cache.
prefer Redis
How to do it
Choose Redis unless you have a clear Memcached-only pattern and tooling.
Example
Session store + rate limit counters fit Redis; a pure blob cache can use either.