Search the practice set
275 questions, 991 terms and 600 topics in 30 areas.
55 results for “BFF for Experience”
Backend for Frontend
A separate, narrow backend per client experience, which aggregates and reshapes downstream services for exactly that client's needs.
Screen Shaped Endpoint
An endpoint that returns exactly what one screen needs in one request, shaped by the interface rather than by the domain model.
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.
Field Data Versus Lab Data
The difference between what real users on real devices experience and what a synthetic run measures, and why the second is systematically optimistic.
Inner Loop Latency
The time from changing a line to observing its effect, repeated dozens of times a day and therefore the highest-leverage number in developer experience.
Mentoring Ladder
Adjusting the level of direction given to someone according to their experience with the specific task, from demonstration through to sponsorship.
Pattern Recognition
Recognising that a novel-looking problem is an instance of one you have seen before, and knowing which parts of the previous solution transfer.
Leadership asks whether to build an internal developer platform or buy one. Twelve teams, forty services, growing. How do you frame the decision?
Reject the framing as a binary Nobody builds or buys a whole platform. A platform is an assembly: source control, CI, artifact registry, infrastructure provisio
Partner integrations take four months from contract signature to production traffic. Engineering says the work is three days. Where does the time go and how do you cut it?
Map the elapsed time honestly The engineering estimate is correct and irrelevant. The four months are: Legal and contractual review. Security questionnaires and
You are forming a platform team of four to serve twelve product teams. What do you build first?
Not a platform. One golden path. Four people cannot build an internal developer platform for twelve teams. They can make one journey excellent, and expand from
Your internal platform has been live for a year. Six of twenty teams use it; the rest built their own pipelines. The CTO proposes mandating it. What is your advice?
Advise against the mandate, and say why in terms of evidence A mandate converts a usability problem into a compliance problem. It will produce adoption numbers
BFF for Experience
One backend per experience, shaped by the screen rather than by the domain.
Frontend & Experience Architecture
General material on architecting the surface the user actually touches.
API Shapes for UI
REST, GraphQL and RPC judged by over-fetching, round trips and client coupling.
APIs as Products
Ownership, lifecycle, deprecation policy and developer experience.
Abstraction Level Choice
How much to hide, and the leak that turns a helpful abstraction into a trap.
Accessibility Architecture
Semantics, focus management and announcements designed in rather than audited in.
Backend for Frontend
A narrow backend per client experience, owned by that client's team.
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.
Client State Architecture
Server state, UI state and derived state, and why conflating them causes most bugs.
Cluster Architecture
How many clusters, split by what, and the blast radius each split buys.
Component Contracts
Props, slots and events as an interface, and the breaking change hidden in a style.
Container Image Strategy
Base images, layer hygiene, rebuild cadence, and patching a fleet of images.
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.
Developer Environments
Local, remote and ephemeral environments, and the fidelity each can honestly claim.
Edge Rendering
Running the render close to the user, and the personalisation and cache trade it implies.
Frontend Security
CSP, XSS, CSRF, token storage, and the trust boundary that ends at the browser.
Guardrails vs Gates
Preventing a class of mistake automatically versus stopping to ask a human.
Hydration Cost
The gap between visible and interactive, and the JavaScript that closes it.
Inner Loop & Outer Loop
Where an engineer's time actually goes, and which loop a platform investment shortens.
Internal Developer Platform
The assembled surface teams actually touch, and what belongs behind 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.
Paved Road & Golden Path
A supported default route that is easier than the alternatives rather than mandatory.
Platform API Deprecation
Removing something dozens of internal teams depend on, on a timeline that holds.
Platform APIs
Treating the platform's own interfaces as contracts with consumers and compatibility rules.
Platform Adoption
Migrating existing teams onto a platform without a mandate, and reading the adoption curve.
Platform Engineering
General material on internal platforms as products with users, adoption and lifecycles.
Platform Funding
Central cost, showback, chargeback, and justifying a team that ships no customer feature.
Platform SLOs
Committing to reliability for internal consumers who cannot choose another provider.
Platform Team Topologies
Stream-aligned, enabling, complicated-subsystem and platform teams, and their interactions.
Platform Telemetry
Instrumenting the platform itself: usage, friction, and where teams leave the paved road.
Platform Tenancy
Isolating teams sharing a cluster, account or pipeline fleet, and where isolation must be hard.
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.
Self-Service Provisioning
Teams getting infrastructure without a ticket, and the guardrails that make that safe.
Service Mesh Operations
What a mesh genuinely solves, its failure modes, and the cost of running one.
Service Templates
Scaffolding new services with observability, CI and security already wired in.
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.