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

20 terms shown.

Term Kind Topic What it is
Accessibility Architecture Structural Accessibility, Accessibility by Construction practice Accessibility Architecture Placing conformance in the components routing and release pipeline that every team already uses - so accessibility is maintained by construction rather than recovered by an audit each year.
Accessibility Regression Gate Accessibility CI Gate, Conformance Gate practice Accessibility Architecture An automated check plus a named manual pass in the release pipeline that blocks a change which breaks accessibility, so conformance is maintained by the build rather than recovered by an annual audit.
API Shapes for UI practice API Shapes for UI Designing APIs for what screens actually need — reducing round trips without coupling the backend to the interface.
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.
Client State Architecture practice Client State Architecture Separating server state, client state and URL state — the distinction that removes most frontend complexity.
Component Contracts practice Component Contracts The interface a shared UI component presents — where the discipline is refusing options as much as providing them.
Component Library Versioning practice Design Systems Treating a design system as a versioned product with a compatibility policy and a deprecation process, because its consumers cannot all upgrade at once.
Composed Page Budget Aggregate Performance Budget, Whole-Page Budget practice Micro-Frontends A performance budget enforced on the assembled page rather than per independently-owned fragment - because in a composed frontend nobody owns the total that users experience.
Device Class Baseline Reference Device, Slow-Tier Baseline practice Web Performance Budgets A named device and network profile, chosen from the slow end of your real user population, against which every performance budget and acceptance test is measured - so that "fast" means fast for the users who a…
Focus Management practice Accessibility Architecture Deliberately controlling where keyboard focus sits after an interface change, which is what makes a dynamic application usable without a mouse.
Internationalisation i18n practice Internationalisation Designing so that language, region and culture are parameters rather than assumptions — cheap upfront and very expensive to retrofit.
Layout Space Reservation Shift Prevention, Dimension Reservation practice Core Web Vitals Allocating space for content before it arrives, so that late-loading elements fill a gap rather than displacing what the user is already reading.
Locale Aware Formatting practice Internationalisation Rendering dates, numbers, currencies and names according to the user's locale rather than the developer's, using the platform rather than hand-written logic.
Origin Isolation Sandbox Origin, User Content Origin practice Frontend Security Serving user-uploaded or untrusted content from a separate origin, so that content executing there has no access to the application's session, storage or DOM.
Performance Budget Enforcement practice Web Performance Budgets A stated limit on bundle size or a timing metric that fails a build when exceeded, which is what turns performance from a periodic project into a constraint.
Pseudo-Locale Testing Pseudo-Localisation, Accented Locale practice Internationalisation Rendering the interface with algorithmically transformed strings - lengthened, accented, direction-reversed - to expose internationalisation defects before any translation exists.
Representative Device Measurement Measure Where Users Are, Field Distribution practice Real User Monitoring Measuring performance on the devices and networks the audience actually uses, and on the distribution rather than the median - because a build agent and a median user both represent nobody in particular.
Third-Party Script Governance Page as an Execution Environment, Vendor Script Review practice Frontend Security Reviewing and constraining what executes on a page, because every third-party script runs with the page's full privileges - and each one is added individually while the aggregate determines the security posture.
UI Monorepo Strategy practice UI Monorepo Strategy Whether frontend code lives in one repository or many — a trade between atomic change and independent release.
Web Performance Budget practice Web Performance Budgets An enforced limit on payload size, resource counts or timing metrics, checked automatically so regressions fail the build rather than accumulating.