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

4 terms shown.

Term	Kind	Topic	What it is
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.
Frontend Security Boundary	concept	Frontend Security	The rule that nothing enforced in the browser is a security control, and the browser-side mechanisms that reduce blast radius anyway.
Origin Isolation Sandbox Origin, User Content Origin	practice	Frontend Security	Serving user-uploaded or untrusted content from a separate origin, so that content executing there has no access to the application's session, storage or DOM.
Third-Party Script Governance Page as an Execution Environment, Vendor Script Review	practice	Frontend Security	Reviewing and constraining what executes on a page, because every third-party script runs with the page's full privileges - and each one is added individually while the aggregate determines the security posture.