The platform's ephemeral infrastructure on top of Redis: it speeds things up (a cache of frequent reads) and connects them (asynchronous handoff of tasks between modules). It holds no domain knowledge of its own — it's a shared layer the other modules consume through a thin client. Two faces: synchronous ephemeral state on the request path (cache, rate-limit, blacklist) and a background execution environment off the request (queue, scheduler, workers, task lifecycle).
The module's two faces side by side: the synchronous one on the request path and the background one off it, each with its own top-to-bottom flow. Both rest on a shared foundation of three stores; the static “what lives where” principle is on the Redis ⟂ Postgres hard boundary.
Detailed design decisions for the module.
The module has no frontend of its own: the admin sees the state of queues, workers and Redis on the dashboard — → Admin Panel.