Caching & KV Stores
Managed Redis and key-value stores compared — serverless cache, sessions, and rate limiting.
alternativas (3)
★ Upstash Redis
Ideal para: Serverless Redis
Serverless Redis with per-request pricing — REST and Redis protocol, global replication, and edge-friendly.
- +Serverless pricing
- +REST API
- +Global replicas
- −Not traditional always-on Redis
Vercel KV
Ideal para: Vercel app caching
Redis-compatible KV store integrated with Vercel — simple SDK for cache, sessions, and rate limits.
- +Native Vercel DX
- +Simple SDK
- +Redis-compatible
- −Vercel ecosystem
Dragonfly
Ideal para: High-performance Redis replacement
High-performance Redis/Memcached alternative — multi-threaded, memory-efficient, drop-in compatible.
- +Very fast
- +Redis compatible
- +Self-host or cloud
- −Newer than Redis incumbents
Comparar
Marca las que quieras comparar
| Alternativa | Model | Serverless | Best for |
|---|---|---|---|
| ★Upstash Redis | Serverless Redis | Yes | Edge & serverless apps |
| Vercel KV | Managed KV | Yes | Vercel deployments |
| Dragonfly | In-memory store | Partial | High-throughput cache |
This is cache and KV — not SQL databases. See Serverless Databases for Postgres/MySQL. Upstash is the default for serverless and edge Redis. Vercel KV if you’re all-in on Vercel. Dragonfly when you need maximum throughput with Redis compatibility.