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

4 terms shown.

Term Kind Topic What it is
Database per Service pattern Polyglot Persistence Each service owning its own datastore, with no other service reading or writing it directly.
Derived Store Discipline One Authoritative Store Per Fact, No Dual Authority concept Polyglot Persistence The rule that every fact has exactly one authoritative store and every other copy is explicitly derived, rebuildable and populated by a documented pipeline - the discipline that makes multiple datastores defensible.
Operational vs Analytical Store concept Polyglot Persistence The separation between the store serving the application's transactions and the one serving reporting and analysis, and the mechanism connecting them.
Polyglot Persistence concept Polyglot Persistence Using different storage engines for different workloads within one system — justified by genuine workload divergence, and frequently not.