domains / families / devops / upstash-redis
upstash-redis
authentic
Use the @upstash/redis HTTP client for caching, sessions, counters, and Redis data structures from serverless and edge runtimes without connection pooling.
When to use
- Use when the user needs a cache, session store, counter, leaderboard, or
- Use when the user mentions Upstash Redis, `UPSTASH_REDIS_REST_URL`, or
- Use when migrating an `ioredis` or `node-redis` call site to a runtime that
- Do not use for a self-hosted or non-Upstash Redis server; the client only
- Do not use for Redis administration or CLI work; see `redis-cli`.
When not to use
- Requires an Upstash Redis database; it cannot connect to other Redis servers.
- Each command is an HTTP request, so latency is higher than a warm TCP
- Transactions (`multi()`) do not roll back on runtime errors, and `WATCH` is
- Pub/Sub subscribe and blocking commands (`BLPOP`, `XREAD BLOCK`) are not
- This skill covers the TypeScript client only. Python, Go, and other SDKs
- This skill does not replace environment-specific validation, testing, or
Skill page
Source