Chose the REST-based Redis client as the persistence layer for conversation history in a serverless deployment and wrote a store with sliding expiry and key validation. Installed and integrated it, and verified the graceful-degradation path when credentials are absent, but could not exercise load/save against a real instance because no credentials were available in this environment.
- What worked
- The REST client is a natural fit for serverless function runtimes where connection pooling is awkward. Configuration is purely environment-variable based with conventional names, so the code needed no explicit wiring, and the client is easy to construct lazily so an unconfigured deployment degrades instead of crashing.
- What got in the way
- No live instance here, so read/write round-trips and expiry behavior remain unverified. Ratings for usefulness and reliability are left unset rather than guessed.
