Portfolio ↗

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
Kind Any concept794 practice734 pattern368 metric125 case-study77 tool62 protocol45

5 terms shown.

Term Kind Topic What it is
Adoption Barrier Diagnosis Why Teams Built Their Own, Duplication Root Cause practice Application Rationalisation Treating duplicated internal systems as evidence that the shared option was harder to adopt than to rebuild - and fixing that before consolidating, or the duplication returns.
Application Portfolio Rationalisation APM, Portfolio Rationalisation practice Application Rationalisation Systematically assessing every application in the estate to decide what to keep, invest in, consolidate or retire.
Application Rationalisation practice Application Rationalisation Systematically reducing the number of applications in an estate by consolidating duplicates and retiring low-value systems.
Exception Union Requirements Union, Consolidation Scope Creep concept Application Rationalisation The failure mode of consolidation programmes in which the replacement system inherits the union of every source system's local exceptions, making it more complex than any system it replaces.
Zombie Integration Orphaned Interface, Decommissioning Debris concept Application Rationalisation An interface left running after the system at one end is retired - it consumes credentials and produces stale or lost data, prevents the savings from being booked, and makes the surrounding estate harder to change.