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
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 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.
Component Library Versioning	practice	Design Systems	Treating a design system as a versioned product with a compatibility policy and a deprecation process, because its consumers cannot all upgrade at once.
Content Security Policy	protocol	Frontend Security	A response header declaring which sources of script, style and other resources the browser may load, which turns a script injection from a compromise into a blocked request.
Cumulative Layout Shift	metric	Core Web Vitals	The extent to which visible content moves unexpectedly during load, which correlates with mis-taps and is almost entirely preventable by reserving space.
Edge Personalisation	pattern	Edge Rendering	Varying a cached response at the edge on a small number of attributes, so the page stays cacheable while still differing per visitor segment.
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.
Focus Management	practice	Accessibility Architecture	Deliberately controlling where keyboard focus sits after an interface change, which is what makes a dynamic application usable without a mouse.
Locale Aware Formatting	practice	Internationalisation	Rendering dates, numbers, currencies and names according to the user's locale rather than the developer's, using the platform rather than hand-written logic.
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.
Performance Budget Enforcement	practice	Web Performance Budgets	A stated limit on bundle size or a timing metric that fails a build when exceeded, which is what turns performance from a periodic project into a constraint.
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.
Remote Module Loading	pattern	Module Federation	Importing code from another application's build at runtime, with the versioning, availability and failure questions that a normal import does not have.
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.
Runtime Composition	pattern	Micro-Frontends	Assembling one page from independently deployed fragments at request or render time, which is what makes micro-frontends more than separate builds.
Screen Shaped Endpoint	pattern	BFF for Experience	An endpoint that returns exactly what one screen needs in one request, shaped by the interface rather than by the domain model.
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.
Stale While Revalidate	pattern	Client Caching & Data Layer	Serving cached data immediately while fetching a fresh copy in the background, which makes an interface feel instant at the cost of a brief inconsistency.
Time to Interactive Gap	metric	Hydration Cost	The interval between a page appearing complete and actually responding to input, during which the user's taps do nothing.