Redis
In-memory data structure store
Memcached
Distributed memory caching system
Redis is a rich data-structure server (strings, hashes, streams, pub/sub, scripts, persistence). Memcached is a minimalist multi-threaded in-memory key/value cache. Pick Memcached if you literally only need a cache; Redis does that plus everything else.
Pick Redis when you want queues, pub/sub, persistence, rate limits, or sorted sets.
Pick Memcached when you need pure cache, no durability, with simple multi-threaded performance.
| Feature | 🔴Redis | 💾Memcached | Winner |
|---|---|---|---|
| Data structures | Hashes, lists, sets, streams, JSON | Strings only | A |
| Persistence | RDB + AOF | None (pure cache) | A |
| Threading | Mostly single-threaded (I/O MT) | Multi-threaded | B |
| Pub/Sub + streams | Yes | No | A |
| Cluster support | Redis Cluster built-in | Client-side sharding | A |
| Memory efficiency (pure KV) | Good | Excellent (slab allocator) | B |
| Scripting | Lua + Functions | None | A |
| License change impact | RSALv2/SSPLv1 (then v8 moved to AGPL-3) | BSD | B |
Data structures
ARedis
Hashes, lists, sets, streams, JSON
Memcached
Strings only
Persistence
ARedis
RDB + AOF
Memcached
None (pure cache)
Threading
BRedis
Mostly single-threaded (I/O MT)
Memcached
Multi-threaded
Pub/Sub + streams
ARedis
Yes
Memcached
No
Cluster support
ARedis
Redis Cluster built-in
Memcached
Client-side sharding
Memory efficiency (pure KV)
BRedis
Good
Memcached
Excellent (slab allocator)
Scripting
ARedis
Lua + Functions
Memcached
None
License change impact
BRedis
RSALv2/SSPLv1 (then v8 moved to AGPL-3)
Memcached
BSD
Best for
Best for
Moving from Memcached to Redis is usually a drop-in swap at the client layer — both speak simple GET/SET. Rewrite any binary protocol code, and take advantage of Redis hashes to replace compound keys. The other direction is rare; if you must, strip all non-KV code paths and accept no persistence.
Redis is a rich data-structure server (strings, hashes, streams, pub/sub, scripts, persistence). Memcached is a minimalist multi-threaded in-memory key/value cache. Pick Memcached if you literally only need a cache; Redis does that plus everything else. In short: Redis — In-memory data structure store. Memcached — Distributed memory caching system.
Pick Redis when you want queues, pub/sub, persistence, rate limits, or sorted sets.
Pick Memcached when you need pure cache, no durability, with simple multi-threaded performance.
Moving from Memcached to Redis is usually a drop-in swap at the client layer — both speak simple GET/SET. Rewrite any binary protocol code, and take advantage of Redis hashes to replace compound keys. The other direction is rare; if you must, strip all non-KV code paths and accept no persistence.
Yes. Both have MCP servers installable via MCPizy (mcpizy install redis and mcpizy install memcached). They work identically across Claude Code, Claude Desktop, Cursor, Windsurf, and any other MCP-compatible client. You can install both side by side and route queries in your agent's prompt.
Supabase is managed Postgres plus auth, storage, edge functions, and realtime. Plain Postgres gives you the same battle-tested engine without the batteries — you run it yourself. Supabase wins for speed-to-product; Postgres wins for full control and cost at scale.
Both are BaaS offerings. Supabase is Postgres-based (relational, SQL, open-source), Firebase is Firestore-based (NoSQL, proprietary, Google Cloud). Supabase wins if you want SQL, lower lock-in, and predictable pricing. Firebase wins for mobile-first apps tied to Google's ecosystem.
Both are mature open-source relational databases. Postgres has richer SQL (CTEs, window functions, JSON, arrays, extensions), stricter standards compliance, and better for complex analytics. MySQL is simpler, often faster on basic read-heavy workloads, and dominates WordPress/PHP ecosystems.
Not sure? Run both side by side — swap between them in your AI agent with a single config line.