REST APIs and webhook orchestration
Systems announce changes with signed webhooks and an orchestrator calls APIs idempotently.
Read the pattern
Resources · Integration patterns
Description, when to use it and when not, a reference diagram, prerequisites, security controls, failure modes and observability — for every pattern.
11 of 11 patterns
Systems announce changes with signed webhooks and an orchestrator calls APIs idempotently.
Read the pattern
Producers publish events to a broker and consumers process them independently and repeatably.
Read the pattern
One clearly named master system for each type of data, identifier mapping and safe, repeatable synchronisation.
Read the pattern
Documents are indexed with their permissions and the model answers only from permitted, cited passages.
Read the pattern
Actions with an effect wait for a person's decision; decisions are recorded immutably with identity.
Read the pattern
An account or subscription hierarchy, a central network, policies and logging as the foundation for workloads.
Read the pattern
Infrastructure and environments are code; changes go through review, a plan and automatic apply.
Read the pattern
Team namespaces, admission policies, GitOps, autoscaling and standard observability.
Read the pattern
Standard telemetry through a collector with masking, sampling and export to a chosen backend.
Read the pattern
Single sign-on with MFA, task-based roles, workload identity and a central store with rotation.
Read the pattern
Model access goes through an adapter with limits, output validation and a fallback.
Read the pattern