Terminology

2185 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 areas2185 Architecture Fundamentals77 Distributed Systems107 Data Architecture110 Cloud Architecture89 Networking88 API & Integration Architecture82 Reliability & Resilience75 Observability70 Performance & Capacity Engineering72 Security Architecture81 Cost Architecture & FinOps66 Business Architecture67 Architecture Communication67 Enterprise Architecture66 Legacy Modernization66 AI-Era Architecture69 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 Architecture64 Streaming & Real-Time Data69 Data Governance & Semantics69 Frontend & Experience Architecture66 Edge, Mobile & IoT68 Regulatory & Data Protection Architecture65 Assurance, Audit & Model Risk64

Kind Any concept785 practice729 pattern362 metric125 case-study77 tool62 protocol45

25 terms shown.

Term	Kind	Topic	What it is
Bottleneck Analysis	practice	Bottleneck Analysis	Finding the single resource that limits the system, because improving anything else changes nothing.
Breaking-Point Testing Test to Failure, Constraint Discovery	practice	Load Testing	Pushing a load test past the target until the system fails, because the purpose of a load test is to locate the constraint and the failure mode rather than to confirm a number.
Capacity Modelling	practice	Capacity Modelling	Predicting the resources a workload will need, from measured unit costs and a demand forecast, with deliberate headroom.
Connection Pool Sizing	practice	Connection Pooling	Choosing how many concurrent connections a service holds to a datastore, where both too many and too few cause outages.
Database Performance	practice	Database Performance	The interventions that resolve database bottlenecks, in the order they should be attempted.
Demand Forecasting	practice	Capacity Modelling	Projecting future load from historical trends, business plans and known events, and translating it into resource requirements with explicit lead times.
Latency Budget Decomposition	practice	Latency	Allocating a total response-time target across the components of a request path, so each layer has an explicit share and overruns are attributable.
Little's Law Applied to Pools	practice	Connection Pooling	Using L = λW to size connection and thread pools from measured throughput and latency rather than from a default.
Load Testing	practice	Performance & Capacity	Driving a system with realistic traffic at a target volume to verify it meets its performance targets before real users do.
Load Testing in Practice	practice	Load Testing	Verifying behaviour under expected load — where realism of workload and data matters more than the number of virtual users.
Network Performance Tuning	practice	Network Performance Tuning	The application-level and connection-level changes that actually improve networked performance, in order of effect.
Peak Event Readiness	practice	Peak Event Readiness	Preparing for a known, dated, high-stakes traffic event — where the discipline is as much organisational as technical.
Peak Readiness Rehearsal Pre-Event Verification, Scheduled Peak Drill	practice	Peak Event Readiness	The set of pre-peak actions and verifications - warm caches, warm pools, confirmed dependency headroom, a change freeze, a rehearsed shedding path - without which correct capacity still fails.
Performance Budget	practice	Performance Budgets	A stated numeric limit on a performance characteristic, enforced automatically so that regressions fail a build rather than accumulating.
Performance Budget for Backends	practice	Performance Budgets	A latency or resource allowance allocated per component of a request path, so that the end-to-end target is composed rather than hoped for.
Pre-Scaling Scheduled Scaling, Warm Provisioning, Capacity Staging	practice	Peak Event Readiness	Provisioning capacity in advance of a known event rather than relying on autoscaling, because the arrival spike at a scheduled moment is faster than any reactive control loop can respond to.
Profiling and Optimisation	practice	Profiling & Optimisation	The discipline of measuring before changing, optimising the dominant term, and stopping when the objective is met.
Queue Length Estimation	practice	Little's Law	Using the relationship between arrival rate, residence time and items in the system to size pools, predict backlogs and sanity-check capacity claims.
Resource Saturation Audit	practice	Bottleneck Analysis	A systematic checklist for locating resource bottlenecks by examining utilisation, saturation and errors for every resource in the system.
Soak Test	practice	Soak Testing	Running sustained realistic load for hours or days to expose defects that accumulate over time rather than appearing under peak load.
Soak Testing	practice	Soak Testing	Running at sustained realistic load for hours or days to find the failures that only appear with time.
Stress Test	practice	Stress Testing	Driving load beyond expected capacity to observe how the system behaves at and past its breaking point.
Stress Testing	practice	Stress Testing	Deliberately exceeding capacity to find where the system breaks and — more importantly — how.
Utilisation Target	practice	Queueing Theory	The operating point chosen from a latency requirement rather than from cost efficiency, because queueing delay rises non-linearly as utilisation approaches saturation.
Workload Model	practice	Load Testing	A description of the traffic mix, arrival pattern and data distribution a load test reproduces, which determines whether the test's results mean anything.