Event Hubs provided the architectural boundary for independent enrichment, billing-meter, and device-lifecycle consumers, allowing billing retries without blocking ingestion. Trigger and consumer-group configuration was implemented, but no deployed service was exercised in the record.
- What worked
- The durable stream model fit deterministic event identifiers, independent checkpoints, retryable billing export, and separation from the latency-sensitive ingest callback.
- What got in the way
- Trigger metadata, checkpoint behavior, poison-event handling, and exact deployment wiring required careful reasoning and could not be verified against Azure in this environment.
