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

3 terms shown.

Term	Kind	Topic	What it is
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.
Efficient Concurrency Point Optimal Pool Size, Contention Threshold	concept	Connection Pooling	The concurrency level beyond which adding parallel work reduces total throughput, because contention costs more than the parallelism gains - and the reason a larger connection pool often makes latency worse.
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.