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

20 terms shown.

Term	Kind	Topic	What it is
Beacon Survivorship RUM Survivorship Bias, Abandonment Bias	concept	Real User Monitoring	The bias in field performance data caused by users abandoning a page before the measurement beacon is sent - so the slowest sessions are excluded and the metric improves as the experience gets worse.
Build Graph Scoping	concept	UI Monorepo Strategy	Determining which packages a change actually affects, so a monorepo builds and tests a subset rather than everything on every commit.
Client Request Waterfall Fetch Waterfall, Client-Side N Plus One	concept	API Shapes for UI	A chain of requests where each one can only start after the previous response arrives, so the screen's load time is set by the depth of the chain times the round trip rather than by bandwidth.
Client Runtime Constraint	concept	Frontend & Experience Architecture	The properties of the browser or device you do not control — CPU, network, version, extensions — which make the client a distributed system component rather than a rendering surface.
Commitment Read Never Commit From Cache, Authoritative at the Point of Action	concept	Client Caching & Data Layer	The rule that the read immediately preceding an irreversible action must come from the authoritative source, which is what allows everything else in the interface to be aggressively cached.
Data Proximity Compute-Data Locality, Edge Distance Problem, Origin Pull	concept	Edge Rendering	The observation that moving compute toward the user moves it away from the data, so edge execution helps only for computations that do not need a central round trip - and hurts for the ones people most want to…
Design System	concept	Design Systems	A versioned library of components, tokens and patterns that encodes an organisation's interface decisions as reusable code.
Field Data Versus Lab Data	concept	Real User Monitoring	The difference between what real users on real devices experience and what a synthetic run measures, and why the second is systematically optimistic.
Flag Evaluation Latency	concept	Client Feature Flags	The delay between page load and the client knowing which variant to show, which produces a visible flicker unless the flag is resolved before render.
Frontend Architecture	concept	Frontend & Experience Architecture	The structural decisions in client applications — rendering strategy, state ownership, boundaries and delivery — which have the same character as backend ones and are frequently made by default.
Frontend Security Boundary	concept	Frontend Security	The rule that nothing enforced in the browser is a security control, and the browser-side mechanisms that reduce blast radius anyway.
Hydration	concept	Hydration Cost	The browser attaching interactivity to server-rendered HTML by re-running component logic, during which the page looks ready and is not.
Observable Component Contract Rendered Surface Contract, Implicit Component API	concept	Component Contracts	The full set of things a consumer can depend on in a shared component - DOM structure, class names, computed spacing, specificity and render timing - as distinct from its declared props, which is the only part…
Over-Fetching	concept	API Shapes for UI	Transferring fields the interface will not display, which costs bandwidth and parse time on exactly the devices least able to afford them.
Prop Interface Stability	concept	Component Contracts	The commitment a component makes about its props, slots, events and emitted structure — including the parts consumers depend on that were never intended as interface.
Render Location Decision	concept	Rendering Strategies	Where HTML is produced — build time, server, edge or browser — chosen per route by how personalised and how cacheable that route is.
Rendering Strategy SSR, CSR, SSG, ISR	concept	Rendering Strategies	The decision about where and when HTML is produced — build time, server request time, or in the browser — which drives performance, cost and complexity.
Runtime Composition Risk Remote Module Risk, Deferred Integration Failure	concept	Module Federation	The class of failures created by resolving module existence, export shape and shared-dependency versions in the user's browser instead of at build time - including the inability to roll back a remote you do not own.
Server State Versus UI State	concept	Client State Architecture	The distinction between data owned elsewhere and cached locally, and state that exists only in this session — conflating them causes most client state bugs.
Shared Singleton Skew Duplicate Framework Instance, Singleton Version Mismatch	concept	Module Federation	The failure class created when independently built front-end bundles expect different versions of a library that must exist once per page, producing either incompatible reuse or two isolated copies that share …