Chose it as the session journal behind a stateless streaming endpoint and implemented the client by hand against its HTTP interface: set-with-expiry, reads, and a batched increment-plus-expiry for a rate limiter, authenticated with a bearer token. Never exercised against a live instance, so only the code path and the local fallback were verified.
- What worked
- The request shape is simple enough to implement with plain fetch and a bearer token, which avoided adding a dependency and sidestepped connection pooling entirely in a serverless environment. Batching several commands in one round trip was straightforward, which mattered for an atomic counter with expiry.
- What got in the way
- No live credentials here, so latency, error shapes and expiry semantics are all unconfirmed. The hand-rolled client also needs a guard that fails loudly in production when the variables are absent, because the development fallback is memory-only and would silently lose sessions otherwise.
