@volter/twin-redis
v1.0.0
Published
The redis twin (Protocol 3).
Readme
@volter/twin-redis
Redis Open Source 7.4.0 over its RESP2 TCP wire, serving Twenty's queues, cache, sessions and subscriptions, Postiz's upload and login state, and Cal.com's API cache and throttling. Postiz uses Temporal workers at its pinned revision. Demand records the application and pinned client calls; decisions records their semantics and evidence.
Declare Redis in the World's world.infrastructure.yml. World commands own its lifecycle and inject REDIS_URL; the managed backing invokes world-redis serve --port <port> --root <tree>. The manifest declares the wire, storage and literal gap. Stored data is created through Redis commands. There are no account, credential or hosted-vendor doors. Commands outside demand answer the declared unknown-command gap, including HELLO and unused client command builders.
Redis's unchanged server command metadata and command pages are pinned with provenance in SOURCE.md. RESP2 commands can use transactions, Lua scripts, subscriptions and blocking sorted-set pops. Redis's EXEC executes queued commands in order; SELECT selects the connection's database; QUIT closes the connection.
A key's expiry belongs to that key. Whole-value SET replacement clears it unless KEEPTTL is requested; in-place collection edits retain it, while deleting the key removes it. RPOPLPUSH retains a same-key rotation's expiry and an existing destination's expiry. GETEX can update/remove expiry, and MSET replacements clear it; both remain outside demand. See Redis's EXPIRE, SET, GETEX and MSET references and the per-operation decisions.
Redis's signed integer arguments use canonical decimal spellings and the signed 64-bit range; counts and ranks apply their command-specific sign/zero rules. SCAN cursors and stream ID components use the unsigned 64-bit parser. RPOP, LPOS and XTRIM describe their options. Each served command's arguments and parsers are recorded in its decision.
The life and published examples describe the calls and assert their effects. The World-managed BullMQ execution, reset and teardown proof is the cookbook recipe, with committed-source captures.
