Terminology

2240 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 areas2240 Architecture Fundamentals77 Distributed Systems107 Data Architecture110 Cloud Architecture94 Networking88 API & Integration Architecture82 Reliability & Resilience80 Observability75 Performance & Capacity Engineering72 Security Architecture86 Cost Architecture & FinOps71 Business Architecture67 Architecture Communication67 Enterprise Architecture66 Legacy Modernization71 AI-Era Architecture74 Software Architecture & Engineering71 Architecture Patterns71 Architecture Decision-Making63 The Architect's Meta-Skills61 Delivery & Release Engineering66 Platform Engineering & Developer Experience70 Testing & Quality Architecture71 Data Platform Architecture69 Streaming & Real-Time Data69 Data Governance & Semantics74 Frontend & Experience Architecture66 Edge, Mobile & IoT68 Regulatory & Data Protection Architecture65 Assurance, Audit & Model Risk69

Kind Any concept806 practice738 pattern379 metric133 case-study77 tool62 protocol45

5 terms shown.

Term	Kind	Topic	What it is
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.
Exception Path Frequency Normal Exceptions, Physical Divergence Rate	metric	Physical-World Failure Modes	The rate at which physical operations diverge from the system's model - a business metric to be managed rather than a defect rate to be eliminated, and the input to how the exception path should be resourced.
Invalid-Clock Boot Epoch Boot, Clock-Zero Boot, Time-Before-Trust Problem	concept	Physical-World Failure Modes	A device booting with no trustworthy notion of time, which makes certificate validity unverifiable and creates a dependency loop - correct time needs a trusted connection and a trusted connection needs correct time.
Physical World Failure Mode	concept	Physical-World Failure Modes	The failure classes that only exist once software controls or observes physical equipment, where the system cannot be restarted and the consequences are not confined to data.
Sensor Input Validation Telemetry Plausibility Checking, Physical Input Sanitisation	practice	Physical-World Failure Modes	Treating readings from physical devices as untrusted input requiring plausibility checks - because a sensor that fails toward a well-formed wrong value is far more damaging than one that stops reporting.