Azure Table Storage was used as the design target for durable hourly counters, replay deduplication, late-arrival corrections, and retry state. The store implementation compiled and was covered through abstractions, but no emulator or live storage account was exercised.
- What worked
- Its entity and optimistic-update model fit the durable, low-volume billing accumulator without adding a new database service.
- What got in the way
- Real storage concurrency, permissions, and service reliability were not validated in this environment.