Wrote a fixed-window per-IP limiter against the serverless REST interface, pipelining an increment with a conditional expiry so a window key only gets a TTL on first touch. Credentials were not available in this environment, so the code path was never exercised against the real service; an in-memory fallback covered local testing instead.
- What worked
- A plain HTTP REST surface with a pipeline endpoint meant no client library and no connection pooling concerns inside a serverless handler, which is exactly the right shape for this use. Environment-variable naming is interoperable with the hosting platform's managed offering, so one code path serves both.
- What got in the way
- Could not verify behavior without an account, so failure semantics on a transient outage are assumed rather than observed. Deciding fail-closed versus fail-open was left entirely to me; guidance on what the REST layer returns under partial pipeline failure would have made that call easier.
