Search the practice set
275 questions, 991 terms and 600 topics in 30 areas.
34 results for “Paved Road & Golden Path”
Golden Path
One opinionated end-to-end route from idea to production that is genuinely easier than the alternatives, and is supported rather than mandated.
Paved Road
A supported, opinionated default way to build and run a service, made easy enough that teams choose it rather than being required to.
Golden Path Adoption
The proportion of teams voluntarily using the supported path, which is the honest measure of whether a platform is solving real problems.
Paved Road Telemetry
Instrumenting the platform's own usage — where teams succeed, where they stall, where they leave — so its roadmap is driven by evidence.
Architect Career Path
The progression from technical depth through breadth to organisational effect, and the skill shifts each stage requires.
Egress Path Analysis
Tracing where data physically moves in an architecture, because transfer charges follow paths that appear nowhere on the diagram.
Golden Record
The single authoritative version of an entity assembled from conflicting sources, and the survivorship rules that decide which value wins.
Golden Signals
The four measurements that cover most of what matters for a request-driven service: latency, traffic, errors and saturation.
Inference Request Path
The sequence of stages an LLM application request passes through, each with distinct latency, cost and failure characteristics.
Path MTU Discovery
The mechanism by which a sender discovers the largest packet size a path supports, and a common cause of connections that establish and then hang.
Architecture Sinkhole
A request that passes through every layer of a layered architecture without any layer adding logic, indicating that the layering is pure overhead for that path.
Cutover Runbook
The step-by-step plan for a migration event, including verification points, decision criteria and the rollback path, rehearsed before it is used.
Data Product Interface
The stable surface a data product exposes — its schema, its access path, its documentation and its guarantees — as distinct from the pipeline behind it.
Deployment Pipeline
The automated path from commit to production, structured so that each stage increases confidence and the whole is fast enough to be run on every change.
Distributed Trace
A causally-linked record of one request's path across services, composed of spans that carry timing, attributes and parent relationships.
Encryption at Rest and in Transit
Protecting stored data from disclosure if the medium is obtained, and network data from disclosure if the path is observed — two different controls against two different threats.
In-Country Processing
Keeping data within a jurisdiction across every path it takes — including backups, logs, telemetry, support access and the disaster recovery region.
Latency Budget Decomposition
Allocating a total response-time target across the components of a request path, so each layer has an explicit share and overruns are attributable.
Layer 4 vs Layer 7 Load Balancing
Balancing on connection metadata (IP and port) versus on the content of the request (path, host, headers).
Netflix's Recommendation Architecture
Netflix splits personalisation into offline, nearline and online layers so that expensive computation happens ahead of time and the request path stays fast.
Replay Pipeline
A single processing path that produces both live and historical results by re-running the same code over retained input, replacing the two-path Lambda arrangement.
Reprocessing Window
How far back a pipeline can be replayed, set by the shortest retention anywhere along the path rather than by intent.
Subject Access Fulfilment
The operational path from a request to a complete, verified, delivered response within the statutory period, across systems that were never designed for it.
Three teams have independently chosen three different message brokers. Design the selection and governance process going forward.
Understand why it happened before correcting it Three independent choices usually mean there was no easy default, no forum for the decision, or a central proces
You inherit an enterprise architecture function that delivery teams route around and executives consider overhead. What do you change?
Diagnose the two failures separately Teams route around it because it is a queue that adds latency without adding value — decisions made by people distant from
A downstream service slows from 50 ms to 3 s. Within two minutes every service in the request path is down, including ones that do not call it. Explain the mechanism and how you would have prevented it.
What the interviewer is testing Whether you understand that most outages are amplification, not failure — and whether you can name the specific mechanism rather
Paved Road & Golden Path
A supported default route that is easier than the alternatives rather than mandatory.
Paved Roads
Making the supported path the easiest path, with a way to leave it.
Platform Telemetry
Instrumenting the platform itself: usage, friction, and where teams leave the paved road.
Distributed Tracing
Reconstructing one request's path across every service it touched.
LLM Application Architecture
The shape of a production system with a model in the request path.
Networking
General material on the network path underneath an architecture.