Terminology
2185 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 areas2185
Architecture Fundamentals77
Distributed Systems107
Data Architecture110
Cloud Architecture89
Networking88
API & Integration Architecture82
Reliability & Resilience75
Observability70
Performance & Capacity Engineering72
Security Architecture81
Cost Architecture & FinOps66
Business Architecture67
Architecture Communication67
Enterprise Architecture66
Legacy Modernization66
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
9 terms shown.
| Term | Kind | Topic | What it is |
|---|---|---|---|
| Coexistence Period | concept | Coexistence Patterns | The interval during which old and new systems both operate and must be kept consistent, which is longer, more expensive and riskier than most plans assume. |
| 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. |
| Greenfield Velocity Illusion Rewrite Head Start, Front-Loaded Rewrite Progress | concept | Rebuild vs Re-architect | The early speed advantage a from-scratch rebuild shows because it is running with all the real constraints switched off, which makes its estimate systematically wrong in the same direction every time. |
| Managed Service Upgrade Calendar Provider Support Lifecycle Exposure, Vendor Upgrade Clock | concept | Replatforming | The obligation, transferred to the provider at replatform time, to upgrade before a published end-of-standard-support date, which converts an indefinitely deferrable version upgrade into a dated one the team d… |
| 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. |
| Rearchitecture Threshold | concept | Refactoring & Re-architecting | The conditions under which rebuilding a system is justified, given that it is the most expensive treatment and is chosen far more often than it is warranted. |
| Reference Data Drift Code List Divergence, Static Data Staleness | concept | Data Migration Strategies | The divergence between a source system's lookup tables and the copy taken at the start of a long migration, which turns into silent transaction rejections in the new system months later. |
| Repurchase Displacement Cost Buy-Instead-Of-Build Migration Load, SaaS Substitution Overhead | concept | The Six Rs | The data migration, process change, integration rebuild and customisation retirement that replacing a bespoke application with a purchased product creates, none of which appears in the licence comparison that … |
| 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. |
Nothing on this page matches. Search the whole glossary.