Terminology

2225 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 areas2225 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 Architecture74 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 Architecture69 Streaming & Real-Time Data69 Data Governance & Semantics74 Frontend & Experience Architecture66 Edge, Mobile & IoT68 Regulatory & Data Protection Architecture65 Assurance, Audit & Model Risk69

Kind Any concept801 practice736 pattern377 metric127 case-study77 tool62 protocol45

3 terms shown.

Term	Kind	Topic	What it is
Client State Architecture	practice	Client State Architecture	Separating server state, client state and URL state — the distinction that removes most frontend complexity.
Optimistic Update Reconciliation Optimistic UI Rollback, Client Reconciliation	pattern	Client State Architecture	The policy deciding what happens when a change already shown to the user differs from what the server ultimately accepts - the part of optimistic UI where the real defects live.
Server State Versus UI State	concept	Client State Architecture	The distinction between data owned elsewhere and cached locally, and state that exists only in this session — conflating them causes most client state bugs.