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

19 terms shown.

Term	Kind	Topic	What it is
A/B Partition Update Dual-Bank Update, Seamless Update	pattern	OTA Updates	Writing a new device image to an inactive partition and switching to it only after verification, so that a failed update falls back to the known-good image instead of bricking the device.
A/B Partition Update	pattern	OTA Updates	Writing firmware to an inactive partition and switching on next boot, so a failed update falls back to the previous image rather than bricking the device.
Attestation Transparency Log Verifiable Transparency, Published Measurement Log	pattern	Edge Security & Attestation	A public append-only log of every software measurement a fleet is allowed to run, checked by the client before it sends data, which removes the possibility of a build served to one user only.
Claim-Code Binding Device Claiming, Ownership Binding, Claim on First Use	pattern	Device Provisioning	Giving a device its cryptographic identity at manufacture but its owner at first use, so the factory line never depends on the cloud and ownership can be transferred without re-keying.
Conflict Copy Conflicted Version, Both-Sides Preservation	pattern	Sync & Conflict Resolution	Preserving both sides of a sync conflict as separate artefacts rather than choosing a winner - the only resolution strategy that never loses user work.
Device Shadow Digital Twin, Reported and Desired State	pattern	Digital Twin	A cloud-side representation of a device's last reported state and its intended state, letting applications interact with devices that are asleep or offline.
Edge Aggregation	pattern	Device Telemetry at Scale	Summarising or filtering telemetry at the device or gateway so that only what is needed leaves, which is usually the difference between a viable and an unaffordable design.
Edge Triage On-Device Filtering, Selective Collection, Interesting-Event Upload	pattern	Fleet Management	Deciding on the device which data is worth transmitting, because a fleet generates far more than any network can carry - and the common, uneventful case is also the least valuable.
IoT Ingest Architecture	pattern	IoT Ingest Architecture	Receiving high-volume telemetry from a large device fleet — where connection count, backpressure and reconnection storms dominate the design.
Last Writer Wins	pattern	Sync & Conflict Resolution	Resolving a conflict by keeping the version with the later timestamp — simple, deterministic, and it silently discards the other change.
Local First Write	pattern	Offline-First	Committing to local storage first and treating the server as an eventual replica, which makes the interface responsive and connectivity an optimisation.
Local Revert On-Device Rollback, A/B Partition Update, Watchdog Revert	pattern	OTA Updates	A device automatically returning to its previous known-good software or configuration when the new one fails, without needing to contact a server - the only mechanism that works when the failure prevents commu…
Offline-First Architecture	pattern	Offline-First	Treating the local device store as the primary source the application reads and writes, with the network as an asynchronous replication channel.
Read Local Write Global	pattern	Edge Data Consistency	Replicating read-only state to every edge location while directing writes to a single authoritative region, which is the arrangement most edge data stores actually provide.
Reported Versus Desired State	pattern	Digital Twin	Holding two representations of a device — what it last said it was, and what it should be — with the gap between them driving reconciliation.
Server-Driven UI Backend-Driven UI, Remote Screen Definition	pattern	Mobile Release Strategy	Describing screens as data returned by the server and rendered by native components - removing the app-store release from the change loop, in exchange for a permanent compatibility contract with every version …
Store-and-Forward Queue On-Device Send Queue, Deferred Send Buffer	pattern	Mobile App Architecture	A durable queue on the device that accepts writes while the network is absent and drains them in order when it returns - with an explicit policy for what happens when it fills or an entry is rejected.
Variant-Aware Purge Tag-Based Invalidation, Vary-Safe Purge	pattern	Edge Data Consistency	Invalidating every cached representation of a resource rather than one URL - because content negotiation and query parameters create many objects under one address, and a URL purge clears only one of them.
Zero-Touch Provisioning Zero-Touch Enrolment, Automatic Enrolment	pattern	Device Provisioning	A device obtaining its identity, configuration and assignment automatically on first connection, so that installation requires no technical procedure from the person performing it.