cache: add valkey backend layer
This commit is contained in:
@@ -51,8 +51,9 @@ Progress:
|
||||
- public cache contracts and runtime cache config now exist in `crank-core` / `crank-runtime`
|
||||
- Community fallback in-memory implementations now exist for response cache, rate-limit state, replay guard, and coordination state
|
||||
- Community deployment manifest now includes optional `valkey` profile and cache env wiring without making cache mandatory
|
||||
- shared `Valkey/Redis` backend layer now exists in `crank-runtime` with config-driven store factory for managed / enterprise contours
|
||||
- pending:
|
||||
- external cache backend for managed / enterprise contours
|
||||
- wire selected cache stores into concrete runtime/admin/mcp paths so external backend reduces real load instead of existing only as reusable layer
|
||||
|
||||
## Planned
|
||||
|
||||
|
||||
Reference in New Issue
Block a user