Development About 1 min read
Integration patterns
These patterns cover retries, stale state, reconnection, schemas and secrets. Apply them consistently across adapters and document the behaviour your application relies on.
On this page
Overview#
| Page | Problem addressed |
|---|---|
| Adapters, gateways, and translation | Isolate vendor/protocol variation from the domain model |
| Polling, subscriptions, and state reconciliation | Combine snapshots and event streams without inventing state |
| Retries, timeouts, and idempotency | Avoid duplicate or uncertain physical actions |
| Event API contracts, normalisation, and schema evolution | Preserve meaning, provenance and compatibility |
| Reconnect, backpressure, and queues | Bound work during bursts, failure and recovery |
| Secrets, certificates, and configuration | Keep trust material outside code and lifecycle safe |
| Observability and diagnostics | Correlate device, protocol, integration and physical outcomes |