Pub/Sub delivery documentation clarified that exactly-once support did not apply to the push-based serverless shape being considered, so idempotency would still be required. The platform added machinery without improving the outcome for this application.
- What worked
- The delivery semantics were documented clearly enough to compare the design accurately.
- What got in the way
- The desired push consumer architecture did not gain exactly-once delivery and was less direct than the selected native integration.
