Terminology

2205 terms, tools, patterns and metrics an architect is expected to use precisely. Each one gets a short explanation of what it is, and — where it matters — what it is commonly confused with. Search filters as you type; the column headers sort.

All areas2205 Architecture Fundamentals77 Distributed Systems107 Data Architecture110 Cloud Architecture94 Networking88 API & Integration Architecture82 Reliability & Resilience75 Observability70 Performance & Capacity Engineering72 Security Architecture86 Cost Architecture & FinOps71 Business Architecture67 Architecture Communication67 Enterprise Architecture66 Legacy Modernization71 AI-Era Architecture69 Software Architecture & Engineering71 Architecture Patterns71 Architecture Decision-Making63 The Architect's Meta-Skills61 Delivery & Release Engineering66 Platform Engineering & Developer Experience70 Testing & Quality Architecture66 Data Platform Architecture64 Streaming & Real-Time Data69 Data Governance & Semantics69 Frontend & Experience Architecture66 Edge, Mobile & IoT68 Regulatory & Data Protection Architecture65 Assurance, Audit & Model Risk64

Kind Any concept794 practice734 pattern368 metric125 case-study77 tool62 protocol45

7 terms shown.

Term	Kind	Topic	What it is
At-Least-Once Delivery Redelivery Semantics, Duplicate-Tolerant Delivery	concept	Webhooks	The delivery guarantee that a message will arrive but may arrive more than once - the strongest practical guarantee across an unreliable boundary, which pushes the deduplication responsibility onto the receiver.
Delivery Attempt Log Webhook Delivery History	practice	Webhooks	A customer-visible record of every outbound delivery attempt - its response, timing and payload - which converts a support burden into self-service.
Stable Event Identity Immutable Event ID, Delivery Deduplication Key	pattern	Webhooks	An event identifier that is identical across every delivery attempt of the same event - the single property that makes at-least-once delivery usable, and the one most often broken by regenerating the ID on retry.
Stripe Webhooks: Delivering to Systems You Do Not Control Signed Webhooks	case-study	Webhooks	Outbound event delivery to arbitrary customer endpoints requires signing, retries over days, explicit at-least-once semantics and a replay interface.
Webhook Reliability	practice	Webhooks	The delivery, retry, ordering, verification and replay concerns that separate a production webhook system from a fire-and-forget HTTP POST.
Webhook Retry Policy	concept	Webhooks	The provider's schedule for re-attempting failed deliveries, and the contract the receiver must be built against.
Webhook Signature	practice	Webhooks	An HMAC over the raw request body using a shared secret, letting a receiver verify a webhook genuinely came from the provider.