Terminology

454 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 areas454 Architecture Fundamentals16 Distributed Systems73 Data Architecture71 Cloud Architecture55 Networking13 API & Integration Architecture17 Reliability & Resilience16 Observability14 Performance & Capacity Engineering13 Security Architecture50 Cost Architecture & FinOps12 Business Architecture9 Architecture Communication8 Enterprise Architecture8 Legacy Modernization11 AI-Era Architecture15 Software Architecture & Engineering19 Architecture Patterns15 Architecture Decision-Making11 The Architect's Meta-Skills8

Kind Any concept166 practice107 pattern93 case-study26 tool26 protocol22 metric14

3 terms shown.

Term	Kind	Topic	What it is
Feature Parity Trap	concept	Rebuild vs Re-architect	The expectation that a replacement system must match every behaviour of the old one before it can be adopted, which is what makes rewrites never finish.
Re-architect vs Rebuild	concept	Legacy Modernization	Restructuring an existing system incrementally versus writing a replacement from scratch — and the strong evidence that incremental wins.
Six Rs of Migration 6 Rs, Migration Strategies	concept	Legacy Modernization	The standard menu of options for each application in a migration — rehost, replatform, refactor, repurchase, retire, retain.