redis-domain-delivery

What problem does it solve?

Redis implementations often become risky because cache/store/queue/lock behaviors, TTL/eviction rules, topology constraints, and failure modes are easy to get subtly wrong and hard to prove before files change.

Core Features & Use Cases

• Redis keyspace contract design: Classifies each prefix as cache, store, queue, lock, rate limiter, or ephemeral session, including data-loss tolerance, cardinality, and value-size expectations.
• Production-safe implementation procedure: Guides selecting correct data structures, enforcing TTL and eviction policy, bounding commands, reviewing Lua atomicity, and validating Streams, locks, and cluster/sentinel topology.
• Verification-first delivery: Requires evidence from scoped checks, records pass/fail status, and defines rollback/repair steps (including key versioning and restore/replay drills when needed).

Quick Start

Use redis-domain-delivery to implement and verify a small Redis change by following the required source-of-truth inspection, scoped checks, evidence recording, and rollback path for your specific Redis stack context.