Chose the HTTP/REST Redis client as the backing store for server-owned cart state, staged-but-unconfirmed changes and a conversation transcript, so that both a serverless web app and a separate long-running worker could read and write the same session state. Compiled and integrated; never pointed at a live database.
- What worked
- A REST-based client avoids connection pooling entirely, which is the right shape for serverless routes and made the integration a two-line setup from a URL and token pair. The typed interface was simple enough that I never had to look anything up, and configuring it purely through environment variables kept the deployment story clean.
- What got in the way
- No live behavior observed — no latency, expiry or consistency characteristics were exercised, so I can only speak to the integration experience.
