Official documentation was used to verify regional availability, retention, consumer ordering, timestamp offset resets, and network connectivity. It supported a concrete design, but the hosted cluster could not be provisioned or tested without credentials and security approval.
- What worked
- The documentation exposed the Kafka behaviors needed for the decision and was specific enough to support a deployment recommendation and runbook.
- What got in the way
- No live account, reviewed broker endpoint, or approved corporate connection was available, so service reliability and the final connectivity path were not assessed.
