Skip to content
cccskills
FreePublished on GitHub

redis-best-practices

Redis best practices for caching, data structures, and in-memory data architecture

The English summary is being prepared. Showing the original description.

Works withRedis
See how to install

Files included (1)

  • SKILL.md1.8 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Redis Best Practices

Caching Patterns

Cache-Aside (CRITICAL)

  • Read: check cache → miss → read DB → set cache
  • Write: update DB → invalidate cache
  • Best for read-heavy workloads

Write-Through

  • Write: update cache AND DB simultaneously
  • Ensures consistency
  • Higher write latency

Write-Behind

  • Write: update cache → async DB update
  • Lowest latency
  • Risk of data loss

Data Structures

String

  • Simple key-value: SET key value
  • Counters: INCR, DECR, INCRBY
  • Bit operations: SETBIT, BITCOUNT

Hash

  • Object storage: HSET user:1 name "Alice"
  • Partial updates: HINCRBY user:1 visits 1
  • Memory efficient for small hashes

List

  • Queues: LPUSH, RPOP (FIFO)
  • Stacks: LPUSH, LPOP (LIFO)
  • Capped collections: LTRIM

Set

  • Unique collections: SADD, SMEMBERS
  • Intersections: SINTER
  • Random sampling: SRANDMEMBER

Sorted Set

  • Leaderboards: ZADD, ZRANGEBYSCORE
  • Rate limiting: ZADD timestamp
  • Priority queues

Stream

  • Event log: XADD, XREAD
  • Consumer groups: XGROUP, XACK
  • Pub/Sub with persistence

Performance

Memory Optimization

  • Set maxmemory policy: allkeys-lru, volatile-lru
  • Monitor memory: INFO memory
  • Use appropriate data structures (Hash vs String)

Pipelining

  • Batch multiple commands
  • Reduces round-trip latency
  • Use for bulk operations

High Availability

Redis Cluster

  • Horizontal scaling
  • Automatic sharding (16384 slots)
  • Multi-master replication

Redis Sentinel

  • Automatic failover
  • Monitoring and notifications
  • Configuration provider

References

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Pre-action boundary checking — validates agent tool calls against declared capabilities and task contracts

The English summary is being prepared. Showing the original description.

baekenough/second-brain15Updated Oct 8, 2026

Auto-detect project context and optimize harness — deactivate unused agents/skills, suggest missing experts, generate project profile

The English summary is being prepared. Showing the original description.

baekenough/second-brain15Updated Oct 8, 2026

Adversarial code review using attacker mindset — trust boundary, attack surface, business logic, and defense evaluation

The English summary is being prepared. Showing the original description.

baekenough/second-brain15Updated Oct 8, 2026

Apache Airflow best practices for DAG authoring, testing, and production deployment

The English summary is being prepared. Showing the original description.

baekenough/second-brain15Updated Oct 8, 2026

Alembic migration patterns for naming conventions, safety checks, expand-contract, env.py configuration, and CI integration

The English summary is being prepared. Showing the original description.

baekenough/second-brain15Updated Oct 8, 2026

Pre-routing ambiguity analysis — scores request clarity and asks clarifying questions when needed (inspired by ouroboros)

The English summary is being prepared. Showing the original description.

baekenough/second-brain15Updated Oct 8, 2026

See all skills by baekenough

Report a problem with this skill