High Volume Meeting Platform

Architecture Summary

Core Rules

1. Keep command and event planes separate.
2. Require idempotency keys on all meeting-creation requests.
3. Queue everything that touches Zoom when you need backpressure control.
4. Verify webhook signatures before durable write.
5. Reconcile state from REST when event delivery is delayed or incomplete.

Concrete Fallbacks

• 429 / 5xx from Zoom REST API -> retry with jitter, then queue for delayed retry.
• Token refresh contention -> single token broker refresh under distributed lock.
• Webhook processor outage -> accept only after queue write, use DLQ replay.
• Missing lifecycle events -> scheduled reconciliation poller repairs the projection.
• Downstream Zoom outage -> circuit breaker opens and create commands stay queued.

When to Use This

Use this pattern when:

• multiple workers or services create meetings concurrently
• you need durable event processing
• missed webhook events are unacceptable
• you need a degraded-but-safe mode during Zoom or network instability