03 · Scale
Infrastructure that survives production.
Signed ingestion, idempotent delivery, bounded retry, dead-letter replay — every piece of production-grade event plumbing, composed and audited under one control plane.
What you get
- Sub-second P95 ingest
- Idempotency-enforced delivery
- Exponential backoff retry
- Dead-letter replay
- Kafka-topic isolation
- Complete event log
Eight-step ingest validation.
Every inbound event at /api/events/ingest passes through tenant identity, connector credential, cryptographic signature verification, monthly volume enforcement, schema compliance, idempotency check, envelope normalization, and Kafka-compatible topic publication. Rejections are never silent; every failure writes to airotech_events_rejected with full reason detail for compliance review.
Idempotency by compound index.
Every event carries an idempotency key enforced by a compound unique index on (source_connector_id, source_event_id). Duplicate submissions return the original response without reprocessing. Senders can safely retry without double-delivery, and operators can replay from the source without fear.
Bounded backoff. Persistent dead-letter.
Delivery failures enter an exponential-backoff retry cycle at 1s, 3s, 9s, 27s — four attempts. Events that exhaust all four attempts move to a persistent dead-letter queue with manual replay and dismiss controls. The dead-letter view surfaces the full error detail, downstream status code, response body, and normalized envelope for root-cause analysis.
Observability as a first-class citizen.
The admin console polls the live event stream at three-second intervals, the connector map at four seconds, and the failed-events queue at seven seconds. Every event row expands into a four-block detail drawer — inbound payload, normalized envelope, transformed adapter output, downstream response — with copy-to-clipboard on each block.
Continue reading