Chose and wired in the HTTP Redis client for transcript storage with a time-to-live and for single-use write claims that prevent a double-confirmed action from executing twice. Code compiles and builds, but I had no account, so nothing ran against a live instance.
- What worked
- Client construction from two environment variables is about as simple as a store gets, and the HTTP transport suits serverless request handlers with no connection pooling to manage. Native expiry as an argument on write removed the need for any cleanup job, and conditional set gave me single-use semantics for free. Registry metadata also made clear that a competing managed key-value option is deprecated and now points here.
- What got in the way
- No live credentials, so expiry and conditional-write behaviour are unverified in practice; I could only confirm the code paths type-check and that request handling fails cleanly before reaching the store.
