Portfolio ↗

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

4 terms shown.

Term Kind Topic What it is
Bootstrap Kill Switch Boot-Path Flag, Safe Mode Configuration pattern Client Feature Flags A configuration value read from local storage before any application code initialises, paired with a launch-failure counter, so a client that crashes during start-up can still be disabled and recovered.
Client Feature Flags practice Client Feature Flags Flags evaluated in a browser or mobile app — where the constraints of distribution, caching and offline behaviour make them meaningfully harder than server flags.
Flag Evaluation Latency concept Client Feature Flags The delay between page load and the client knowing which variant to show, which produces a visible flicker unless the flag is resolved before render.
Flag Propagation Time Flag Convergence Time, Kill Switch Latency metric Client Feature Flags The worst-case delay between changing a feature flag and every client acting on the new value - the number that determines whether a flag can be used as a safety control or only as a release convenience.