Terminology

991 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 areas991 Architecture Fundamentals38 Distributed Systems73 Data Architecture71 Cloud Architecture55 Networking51 API & Integration Architecture45 Reliability & Resilience40 Observability33 Performance & Capacity Engineering34 Security Architecture50 Cost Architecture & FinOps30 Business Architecture28 Architecture Communication27 Enterprise Architecture27 Legacy Modernization27 AI-Era Architecture34 Software Architecture & Engineering37 Architecture Patterns34 Architecture Decision-Making30 The Architect's Meta-Skills27 Delivery & Release Engineering20 Platform Engineering & Developer Experience20 Testing & Quality Architecture20 Data Platform Architecture20 Streaming & Real-Time Data20 Data Governance & Semantics20 Frontend & Experience Architecture20 Edge, Mobile & IoT20 Regulatory & Data Protection Architecture20 Assurance, Audit & Model Risk20

Kind Any concept379 practice294 pattern166 metric55 tool36 protocol35 case-study26

10 terms shown.

Term	Kind	Topic	What it is
Best Effort Delivery	concept	Push & Background Work	The guarantee push notification services actually offer — which is none — and the design consequences of building on a channel that may silently drop.
Clock Drift	concept	Physical-World Failure Modes	Device clocks diverging from real time, which corrupts ordering, expires certificates early or late, and produces data that appears to arrive from the past.
Cold Start at the Edge	concept	Edge Functions	The initialisation delay when a request reaches a location with no warm instance, which at the edge occurs far more often because traffic is spread across many locations.
Compute Tier Placement	concept	Edge Compute Topologies	Deciding which of on-device, on-premises, metro, regional or central compute a workload belongs to, from its latency, data volume and autonomy requirements.
Convergence Without Coordination	concept	CRDTs	The property that replicas applying the same set of updates in any order reach the same state, which is what removes the need for a central arbiter.
Hardware Backed Credential	concept	Device Identity	A private key generated inside a secure element and unable to leave it, so device identity cannot be copied off the device.
Ingest Fan-In	concept	IoT Ingest Architecture	The shape of a system receiving many small messages from very many senders, where connection count rather than data volume is the primary constraint.
Message Overhead Budget	concept	Constrained Protocols	The proportion of each transmission spent on protocol rather than payload, which on a metered or battery-powered link determines the running cost.
Platform Lifecycle Constraint	concept	Mobile App Architecture	The operating system's rules about when your process runs, which are not negotiable and invalidate most assumptions carried over from server code.
Unreachable Node	concept	Edge, Mobile & IoT	A component you cannot log into, restart or inspect, which removes every operational technique that assumes access to the running system.