Chose table storage as the observation store for comparable weekly prices and missing-line status, provisioned it in infrastructure templates, and implemented the repository against the tables SDK.
- What worked
- A simple keyed observation model mapped cleanly to table entities, and an in-memory stand-in covered local runs and tests. Naming and role needs were discoverable enough to write the template.
- What got in the way
- The account was never created or queried live. Cost and throughput claims stayed at documented estimates, and table-create conflict behavior was coded defensively rather than verified.