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

8 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.
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.
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.
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.