Redis Patterns
Redis best practices for production: data structures, cache-aside, distributed locks, rate limiting, pub/sub, streams, and connection management.
- What
- Redis best practices for production: data structures, cache-aside, distributed locks, rate limiting, pub/sub, streams, and connection management.
- Cost
- Free
- Needs
- Use "Redis Patterns" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a quick-reference patterns skill for Redis in production backends. It maps use cases to the right data structure (strings for cache, hashes for sessions, sorted sets for leaderboards, streams for durable queues), then gives working recipes: cache-aside and write-through caching, tag-based invalidation, session storage, fixed-window and atomic sliding-window rate limiting with Lua, distributed locks with SET NX PX plus safe token-checked release, pub/sub for fire-and-forget, and Redis Streams with consumer groups for guaranteed delivery. Key naming conventions, TTL strategy tables, connection pooling, cluster and Sentinel setups, and eviction policies round it out, plus an anti-patterns table (KEYS star in production, keys with no TTL, blobs over 100KB, cache-miss stampedes). By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: pure guidance, nothing to install; you need a Redis server to apply any of it, and multi-node locking should use a Redlock-algorithm library rather than hand-rolled SET NX. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Redis Patterns" with your Muse. Prerequisites: a Redis server you can connect to (local or hosted). Pure guidance skill, nothing to install. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/redis-patterns/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Add cache-aside caching with a 5-minute TTL to [this endpoint]" or "Implement sliding-window rate limiting for [this API] following these patterns." 3. For key design review, ask: "Review my Redis key naming and TTL strategy against this cheat sheet." Tip: always set a TTL; keys without one accumulate forever and will eventually hurt you. Safety: a skill is plain-text instructions; it runs nothing by itself. Never run KEYS star or FLUSHALL against production, and review anything Muse proposes before it touches your Redis instance.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.