Portfolio ↗

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
Fleet-Wide Change Reach Platform Change Propagation concept Service Templates How long it takes a platform change to reach the majority of the services built on it - the measure of whether a platform can actually change anything.
Service Scaffolding tool Service Templates Generating a new service with observability, CI, security and ownership already wired in, so the standard is the default rather than a checklist.
Service Template Scaffold, Cookiecutter Template, Software Template tool Service Templates A generator that creates a new service already wired into the organisation's pipeline, telemetry, security and operational conventions.
Template Propagation Getting Improvements Into Existing Services, Template Drift practice Service Templates The mechanism by which improvements to a service template reach the services already generated from it - the hardest part of the template model and the part most often omitted.