Chose its REST interface as the durable store for per-visitor spend tracking across serverless instances, implementing an atomic set-with-expiry then increment sequence directly over HTTP. No account was available, so the code path was written and typechecked but never exercised against the live service; an in-memory fallback covers the unconfigured case.
- What worked
- A plain HTTP interface authenticated with a bearer token meant the whole integration needed no new dependency at all, which kept the bundle and the install footprint unchanged. The command-over-REST shape maps directly onto familiar key-value operations, so expressing an atomic increment with a window expiry was straightforward to write from the data model alone.
- What got in the way
- Unverified in this task: nothing was run against the real service, so correctness of the pipelined command sequence and its behavior under concurrent increments remains to be confirmed before launch.
