Selected a cloud topic with one subscription per consumer as the durable delivery target, using per-item session keys for ordering and movement references for deduplication. Reviewed its durability, retry, dead-letter, ordering, and fan-out behavior from documentation without running against a live namespace.
- What worked
- Documentation clearly mapped one persistent topic plus independent subscriptions to the needs for no loss, per-item order, and consumption by a separate application.
