Terminology
2205 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 areas2205
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 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
3 terms shown.
| Term | Kind | Topic | What it is |
|---|---|---|---|
| Legacy Side-Effect Inventory Trigger Inventory, Write Consequence Map | practice | Strangler Fig | The enumerated list of triggers, stored procedures, scheduled jobs and integrations that fire as a consequence of a legacy write, which determines whether a capability can be moved incrementally at all. |
| Seam Identification | practice | Strangler Fig | Locating the places in a legacy system where behaviour can be intercepted and redirected, which determines whether an incremental migration is feasible at all. |
| Strangler Fig | pattern | Strangler Fig | Replacing a legacy system incrementally by routing individual capabilities to new implementations until nothing is left running on the old one. |
Nothing on this page matches. Search the whole glossary.