Enforces clear boundaries and handoff between Redis application behavior guidance and Redis infrastructure operations.
Boundary module for Redis concerns.
| Excuse | Reality |
|---|---|
| "Redis is one topic, keep it together" | Behavior and infrastructure have different owners and rollout paths. |
| "Provisioning details help app guidance" | Embedded infra setup in app guidance creates coupling and drift. |
| "Security hardening is app-level here" | TLS/ACL and topology hardening are infra operations. |
| "We'll split concerns later" | Deferred separation becomes long-term boundary erosion. |
| "Prototype can ignore separation" | Early boundary debt hardens into production architecture risk. |
Application-level Redis guidance includes:
Infrastructure Redis guidance includes:
Do not merge these concern sets in one implementation plan.
When app-level patterns depend on infra capabilities, document assumptions and handoff requirements without embedding provisioning steps.
digraph redis_separation_flow {
req [label="Redis request", shape=ellipse];
app [label="Application behavior concern?", shape=diamond];
infra [label="Infrastructure concern?", shape=diamond];
appRoute [label="Route to backend-redis-application-patterns", shape=box];
infraRoute [label="Route to infra skill path", shape=box];
split [label="Split concerns and handoff", shape=box];
req -> app;
app -> appRoute [label="Yes"];
app -> infra [label="No"];
infra -> infraRoute [label="Yes"];
infra -> split [label="Mixed/unclear"];
appRoute -> split;
infraRoute -> split;
}
When flagged: Stop -> split concern sets -> route each path -> continue.
openspec-proposalbackend-defensive-engineeringbackend-redis-application-patternsIf request includes provisioning, cluster management, infra security hardening, or platform-specific Redis operations, route to infra skill path.