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

3 terms shown.

Term	Kind	Topic	What it is
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.
Shell Personalisation Cache the Shared, Personalise the Edge, Hole Punching	pattern	Rendering Strategies	Generating and caching the page that is identical for everyone, then applying per-user variation at the edge or on the client - preserving the cache hit rate that personalising the whole page destroys.