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

20 terms shown.

Term	Kind	Topic	What it is
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.
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.
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.
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.
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.
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.
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.
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.
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.
Secure Boot Chain	protocol	Edge Security & Attestation	Each boot stage verifying the signature of the next before executing it, anchored in immutable hardware, so only authorised software runs.
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.
Zero Touch Provisioning	pattern	Device Provisioning	A device obtaining its identity and configuration on first boot without a human configuring it, which is the only approach that scales past a few hundred units.