Search the practice set
275 questions, 991 terms and 600 topics in 30 areas.
60 results for “Frontend & Experience Architecture”
Backend for Frontend
A separate, narrow backend per client experience, which aggregates and reshapes downstream services for exactly that client's needs.
Client Runtime Constraint
The properties of the browser or device you do not control — CPU, network, version, extensions — which make the client a distributed system component rather than a rendering surface.
Architecture Cost Model
A calculation, made during design, of what an architecture will cost to run at expected and at peak volume.
Architecture Decision Log
The ordered, immutable collection of a system's decision records, read as a history rather than as a specification.
Architecture Decision Record
A short, immutable document capturing one architectural decision, its context, the alternatives, and its consequences.
Architecture Development Method
TOGAF's iterative cycle for developing enterprise architecture, which is valuable as a checklist of concerns and harmful when followed literally.
Architecture Principle
A durable, agreed rule that constrains design decisions in advance, stated with its rationale and its implications.
Architecture Review Board
A forum that reviews significant designs against standards, risks and strategy before commitment.
Architecture Roadmap
A sequenced plan of architectural change expressed as capability outcomes and decision points rather than as a fixed timeline of projects.
A front-end team wants to replace their global state library because "state management is unmanageable". How do you evaluate the request?
Ask what is actually in the store The complaint almost always resolves to one distinction not having been made: server state versus UI state . Server state is d
Six weeks before launch, an accessibility audit returns 200 issues. The team's automated checks were green. Why, and what do you do?
Why the checks were green Automated tooling reliably decides roughly a third of the criteria: missing alternative text, insufficient contrast, absent form label
A CFO asks why the architecture function should be funded when it ships no features. You have five minutes. What do you say?
Do not answer with activities "We produce standards, run a review board and maintain the technology radar" describes what the function does, not what the busine
A regulator asks how you ensure marketing consent withdrawal is honoured everywhere. What does the architecture need to show?
The answer they want is mechanism plus evidence Not "we have a consent database". They want to see how a withdrawal reaches every system that could act on it, a
Frontend & Experience Architecture
General material on architecting the surface the user actually touches.
Accessibility Architecture
Semantics, focus management and announcements designed in rather than audited in.
BFF for Experience
One backend per experience, shaped by the screen rather than by the domain.
Backend for Frontend
A narrow backend per client experience, owned by that client's team.
Client State Architecture
Server state, UI state and derived state, and why conflating them causes most bugs.
Frontend Security
CSP, XSS, CSRF, token storage, and the trust boundary that ends at the browser.
API Shapes for UI
REST, GraphQL and RPC judged by over-fetching, round trips and client coupling.
Client Caching & Data Layer
Stale-while-revalidate, invalidation and optimistic updates on the client.
Client Feature Flags
Flag evaluation on a device you do not control, and the flicker and staleness it brings.
Component Contracts
Props, slots and events as an interface, and the breaking change hidden in a style.
Core Web Vitals
LCP, INP and CLS — what they measure, and the architecture that moves them.
Design Systems
Components as a versioned internal product, with adoption and deprecation like any API.
Edge Rendering
Running the render close to the user, and the personalisation and cache trade it implies.
Hydration Cost
The gap between visible and interactive, and the JavaScript that closes it.
Internationalisation
Locale, direction, pluralisation and dates as structural concerns, not string tables.
Micro-Frontends
Independent deployment of UI slices, and the shared runtime that undermines it.
Module Federation
Loading code from another build at runtime, with versioning and failure to think about.
Real User Monitoring
Field data from real devices and networks, against the synthetic run that looked fine.
Rendering Strategies
Client, server, static and incremental rendering, and what each costs on first paint.
UI Monorepo Strategy
One repository for many front ends, and the build graph that makes it viable.
Web Performance Budgets
A number a build can fail against, rather than a performance sprint once a year.
Cluster Architecture
How many clusters, split by what, and the blast radius each split buys.
APIs as Products
Ownership, lifecycle, deprecation policy and developer experience.
AI-Era Architecture
General material on architecting systems that include models.
Application Architecture
The application estate as a designed portfolio rather than an accumulation.
Architecture Communication
General material on communicating architecture.
Architecture Compliance Checks
Automating conformance to standards so review effort goes to the genuinely novel.
Architecture Cost Modelling
Pricing a design before building it, at expected and at ten times volume.
Architecture Decision Records
One decision, its context, alternatives and consequences, kept immutable.
Architecture Decision-Making
General material on making and recording architectural decisions.
Architecture Diagrams
Choosing an audience and refusing to mix levels of abstraction.
Architecture Documentation
What to write down, at what altitude, and what nobody will ever read.
Architecture Fundamentals
General material on what solution architecture is and what an architect is accountable for.
Architecture Governance
Preventive, automated controls rather than review meetings.
Architecture Patterns
General material on architectural patterns and their trade-offs.
Architecture Principles
Durable agreed rules that rule options out, stated with rationale and implications.
Architecture Review Boards
Thresholds, early engagement and a real route to accept deviation.
Architecture Reviews
Reviewing early enough to influence rather than to veto.
Frontend & Experience Architecture
The client as a distributed system component with its own state, cache and failure modes.
AI-Era Architecture
AI workloads meeting security, data, networking, reliability and cost.
API & Integration Architecture
Contracts between systems, and the compatibility discipline that keeps them working.
Architecture Communication
Explain the same architecture to a CEO, an engineering manager and an engineer.
Architecture Decision-Making
Where senior engineer becomes architect: evaluate, choose, write it down.
Architecture Fundamentals
What architecture actually is: drivers, constraints, trade-offs and the principles behind them.
Architecture Patterns
Patterns as tools for recurring problems, with forces and consequences.