Terminology

2225 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 areas2225 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 Architecture74 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 Architecture69 Streaming & Real-Time Data69 Data Governance & Semantics74 Frontend & Experience Architecture66 Edge, Mobile & IoT68 Regulatory & Data Protection Architecture65 Assurance, Audit & Model Risk69

Kind Any concept801 practice736 pattern377 metric127 case-study77 tool62 protocol45

10 terms shown.

Term	Kind	Topic	What it is
Command Validity Window Command Expiry, Time-Bounded Actuation	practice	Fleet Management	An expiry attached to a command sent to a device, so that an instruction delivered after the situation has changed is discarded rather than executed.
Conflatable Classification Superseding vs Discrete Events, What May Be Dropped	practice	Device Telemetry at Scale	Explicitly classifying each telemetry stream as superseding or discrete, because conflation is the correct overload behaviour for one and silent data loss for the other.
Device Group Rollout	practice	Fleet Management	Applying configuration or firmware to a fleet in ordered cohorts with health checks between them, because a bad change applied to everything at once has no remedy.
Device Provisioning	practice	Device Provisioning	Giving a device a unique cryptographic identity and its initial configuration in a way that scales to millions and survives a hostile supply chain.
Explicit Staleness As-Of Semantics, Freshness Disclosure	practice	Digital Twin	Publishing how old a modelled or cached value is alongside the value itself, so consumers can judge whether it is usable rather than assuming it is current.
Fleet Management	practice	Fleet Management	Operating a large population of physical devices — knowing what is deployed, where, on which version, in what health, and acting on that at scale.
Forced Upgrade	practice	Mobile Release Strategy	Blocking an installed client version from operating until it updates, which is the only lever available and is disruptive enough to need a policy.
Mobile Release Strategy	practice	Mobile Release Strategy	Shipping to an app store where review adds latency, users choose when to update, and old versions therefore stay live indefinitely.
Over-the-Air Update OTA, Firmware Update	practice	OTA Updates	Updating software on deployed physical devices remotely, where a failed update can require someone to physically visit the device.
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.