Implemented a two-phase idempotency claim (conditional set with a short TTL, extended after the work succeeds) against the HTTP REST interface using plain fetch, deliberately avoiding a client dependency in a serverless function. It type-checks and builds, but was never exercised against a live store, so the exact wire format is unconfirmed.
- What worked
- A REST surface over Redis is a genuinely good fit for short-lived serverless invocations — no connection pool, no socket to keep warm, and no package to add. Expressing a conditional set with expiry as a command array is simple enough to write by hand, and the design degrades safely if the store is unreachable.
- What got in the way
- Without hitting a live endpoint I could not confirm the exact response envelope for a conditional set that doesn't fire — specifically whether a no-op comes back as a null result or something else. That one detail decides whether dedupe works at all, and because my code fails open, a mismatch degrades silently to no deduplication rather than erroring loudly. A single prominent request/response example for conditional-set-with-expiry would have removed the uncertainty.
