Search the practice set
275 questions, 991 terms and 600 topics in 30 areas.
60 results for “Progressive Delivery”
Release Ring
An ordered cohort of users a change reaches before the next one, chosen so that early rings would notice a fault and tolerate it.
At-Least-Once Delivery
The guarantee that a message will be delivered, possibly more than once — the practical default in every distributed messaging system.
Best Effort Delivery
The guarantee push notification services actually offer — which is none — and the design consequences of building on a channel that may silently drop.
Content Delivery Network
A geographically distributed cache that serves content from a location near the user instead of from the origin.
Delivery vs Maintainability
Choosing where to take deliberate shortcuts, based on which kinds of debt are cheap to repay and which compound.
Fan-Out Delivery
Delivering one published message to many independent subscribers, each with its own copy, position and failure handling.
CI/CD
Merging work continuously into a shared trunk with automated verification, and keeping every commit in a state that could be released.
Cache-Control
The HTTP header directing how a response may be cached and for how long, by browsers, proxies and CDNs.
DORA Metrics
Four measures of software delivery performance — deployment frequency, lead time for change, change failure rate, and time to restore service.
Deliberate Technical Debt
A consciously chosen shortcut, recorded with its cost and a repayment trigger, as distinct from debt incurred by carelessness.
Offset Management
How a consumer records its position in a stream, and the decision that determines whether processing is at-least-once or at-most-once.
Origin Shield
An intermediate caching layer between CDN edge nodes and the origin, so a cache miss at many edges results in one origin request rather than many.
Outbox Relay
The process that reads pending messages from an outbox table and publishes them to a broker, providing at-least-once delivery with no distributed transaction.
Outcome over Output
Measuring and committing to changes in user or business behaviour rather than to the delivery of features.
Pipeline Stage Contract
What each pipeline stage promises the next — an artifact of a stated shape plus a specific claim about it that has been verified.
Stakeholder Analysis
Identifying who is affected by an architecture, what each of them needs from it, and how much influence they have over whether it proceeds.
Time to Market
How long it takes to get a capability in front of customers — often the constraint that dominates every other architectural quality.
Trunk-Based Development
All developers integrating small changes into a single shared branch at least daily, with long-lived branches avoided entirely.
Visibility Timeout
The period after a consumer receives a message during which it is hidden from other consumers, before it becomes available again for redelivery.
Delivery feels slow and leadership wants a productivity initiative. You propose mapping the value stream first. What will you map and what do you expect to find?
Map every step from request to delivered change, with two numbers each Work time — how long the step actually takes when someone is doing it. Wait time — how lo
Delivery leadership says releases are too slow and wants the engineering team to "move faster". Lead time from commit to production is 21 days. How do you investigate, and what do you expect to find?
Do not accept the framing "Move faster" assumes the constraint is how fast code is written. That is almost never where the twenty one days went, and starting an
Design a webhook delivery system for a platform with 10,000 customers. What are the hard parts?
Delivery, and its failure modes Persist the event first, deliver asynchronously. Delivery in the request path couples your latency and availability to every cus
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 codebase has 340 feature flags, most of them permanently on. What is the problem and how do you fix it?
The problem is combinatorial and it is not theoretical Every flag doubles the number of possible code paths. At 340, the number of configurations is unbounded a
A front-end lead proposes micro-frontends so four teams can deploy independently. The application is a single React SPA. What is your assessment?
Test the premise first The stated goal is independent deployment. Ask what currently prevents it, because the answer is frequently not the architecture. If the
A release must rename a heavily used database column and ships tonight. The team proposes doing the rename in the deployment. What is wrong, and what do you propose?
What is wrong A rename is not additive. During a rolling deployment both versions of the application run simultaneously: one expects the old name, one the new.
A team's pipeline takes 80 minutes from commit to a deployable artifact and engineers have stopped watching it. How do you approach fixing it?
Measure per stage before changing anything Get the duration of every stage over the last few hundred runs, with the distribution rather than the mean. The shape
After a content purge, your origin receives 400× normal traffic and falls over. The CDN is working as configured. What is missing and how do you fix it?
What is happening A global CDN has hundreds of points of presence, each with an independent cache. A purge invalidates the object everywhere at once , so the ne
Production is degraded after a release. The team tries to roll back and discovers a migration has already run. What do you do now, and what do you change afterwards?
Now: stop trying to roll back Reverting the deployment would run the previous code against a schema it does not know, which is a second and less understood fail
Six teams share one integration test environment. Bookings are made a week ahead and releases slip when someone overruns. How do you fix it?
Name the cost first The queue is not an inconvenience; it is lead time. Measure it: for the last twenty changes, how many days elapsed between "ready to test" a
The team can ship in six weeks with an approach that will need rework, or five months with one that will not. How do you decide, and what do you do either way?
What the interviewer is testing Whether you can make a debt decision deliberately rather than by default, and whether you know which debts are cheap and which a
Progressive Delivery
Separating deploy from release, and exposing a change to users in controlled increments.
Release Strategies
Blue-green, canary, shadow and progressive delivery.
Content Delivery Networks
Edge caching, origin offload, spike absorption and dynamic content.
Delivery & Release Engineering
General material on getting a change from commit to production safely and often.
Delivery vs Maintainability
Fast in the cheap places, careful in the expensive ones.
Artifact Management
Immutable versioned outputs, promotion between repositories, and retention policy.
Branching Models
GitFlow, trunk and release branches as delivery constraints rather than Git preferences.
Build Reproducibility
Pinned inputs and hermetic builds, so one commit cannot produce two different artifacts.
CI/CD
Continuous integration and delivery, and the architecture that caps them.
Change Management vs CD
Reconciling CAB-era controls with continuous delivery without pretending either away.
Continuous Integration Discipline
Integrating to the mainline daily, and the test speed and review culture that requires.
Database Migration Under CD
Expand-contract, backwards-compatible schema change, and migrations that cannot roll back.
Deployment Gates
Automated verification between stages, and the difference between a gate and a delay.
Deployment Strategies
Rolling, blue-green, canary and shadow, and the traffic and state each one assumes.
Environment Strategy
How many environments earn their cost, what each proves, and what none of them prove.
Flow Metrics
Work in progress, flow time and flow efficiency — where a change waits rather than moves.
GitOps
Declared desired state in version control, with a reconciler closing the gap continuously.
IaC Modules & Drift
Reusable infrastructure modules, state ownership, and detecting what changed out of band.
Multi-Region Rollout
Ordering regions, bake time, and stopping a bad change before it becomes global.
Operating Models
How delivery, platform and governance functions fit together.
Pipeline Architecture
Stages, fan-out, caching, and the difference between a pipeline and a long script.
Pipeline Secrets
Short-lived credentials, workload identity, and why the CI system is a prime target.
Policy as Code
Encoding standards as automated admission and plan-time checks instead of review comments.
Push & Background Work
Delivery that is best-effort, and an operating system that will kill your process.
Rollback & Forward Fix
When reversing is genuinely possible, and designing so that it usually is.
Supply-Chain Provenance
SBOMs, signed artifacts, attestation, and knowing what actually went into a build.
Value Streams
End-to-end delivery of an outcome, and where the waiting happens.