Terminology

2240 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 areas2240 Architecture Fundamentals77 Distributed Systems107 Data Architecture110 Cloud Architecture94 Networking88 API & Integration Architecture82 Reliability & Resilience80 Observability75 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 Architecture71 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 concept806 practice738 pattern379 metric133 case-study77 tool62 protocol45

4 terms shown.

Term	Kind	Topic	What it is
Module Federation Micro Frontends	pattern	Module Federation	Composing a frontend from independently deployed pieces — solving an organisational problem at a real technical cost.
Remote Module Loading	pattern	Module Federation	Importing code from another application's build at runtime, with the versioning, availability and failure questions that a normal import does not have.
Runtime Composition Risk Remote Module Risk, Deferred Integration Failure	concept	Module Federation	The class of failures created by resolving module existence, export shape and shared-dependency versions in the user's browser instead of at build time - including the inability to roll back a remote you do not own.
Shared Singleton Skew Duplicate Framework Instance, Singleton Version Mismatch	concept	Module Federation	The failure class created when independently built front-end bundles expect different versions of a library that must exist once per page, producing either incompatible reuse or two isolated copies that share …