Webhook-first architecture
Why Beacon prioritizes async ingestion and queue-based processing.
explanation • updated 2026-03-15
Why webhook-first
External providers (Stripe) are source-of-truth for critical events. Beacon prioritizes fast ingestion and minimal-entry validation to avoid timeouts and event loss.
Processing flow
11) Ingestion
Receive webhook, validate signature, and persist event.22) Fast ack
Return2xxas soon as event is safely persisted.33) Async execution
Run business logic in workers with controlled retries.44) Observability
Publish final state and queue/latency/failure metrics.
Operational guarantees
- Deduplication by
event.idfor provider re-delivery. - Safe reprocessing through business idempotency rules.
- Failure isolation by event type and organization.
Minimum metrics
| Metric | Objective |
|---|---|
| Webhook ack latency | keep low and stable |
| Queue depth | detect backlog early |
| Retry rate | catch downstream degradation |
| Time to final state | measure operational impact |