Search the practice set
126 questions, 454 terms and 400 topics in 20 areas.
31 results for “Deployment Diagrams”
Blue-Green Deployment
Running two identical production environments and switching traffic from the old one to the new one in a single cut, with the old kept warm for rollback.
Etsy's Continuous Deployment
Etsy moved from infrequent, risky releases to dozens of deploys a day, demonstrating that deployment frequency and stability improve together rather than trading off.
Artifact Signing
Cryptographically signing build outputs so that deployment can verify what is being run was produced by the expected pipeline from the expected source.
Blast Radius Reduction
The set of deliberate partitions — accounts, regions, zones, cells, tenants, deployment stages — that bound how far any single failure or compromise can reach.
Blue-Green Database Schema
The constraint that makes fast rollback actually work — both application versions must be able to run against one schema at the same time.
C4 Model
A set of four nested diagram levels — context, container, component, code — that keeps each diagram at one consistent level of abstraction.
CI/CD
Merging work continuously into a shared trunk with automated verification, and keeping every commit in a state that could be released.
Canary Release
Routing a small fraction of traffic to a new version, watching its metrics, and expanding or rolling back based on what they show.
Cross-Zone Data Transfer
Charges incurred when data moves between availability zones within a region — invisible on architecture diagrams and a recurring surprise on cloud bills.
DORA Metrics
Four measures of software delivery performance — deployment frequency, lead time for change, change failure rate, and time to restore service.
Data-Flow Diagram
A diagram of how data moves between processes, stores and external entities, with trust boundaries drawn on it.
Feature Flag
A runtime switch that decouples deploying code from releasing behaviour, so unfinished or risky work can ship dark.
Image Registry
The store from which container images are pulled, and an under-appreciated availability and security dependency of every deployment and every autoscale event.
Microservices
An architectural style where an application is a set of independently deployable services, each owning its data and aligned to a business capability.
Monolith vs Microservices
A trade of deployment independence against distributed-systems complexity, decided by team topology far more often than by technology.
Prompt Registry
A versioned store of production prompts with their model bindings, parameters and evaluation results, so a prompt change is a reviewable, traceable, reversible deployment.
Prompt Versioning
Treating prompts as versioned, reviewed, tested artefacts rather than as strings edited in place.
Sequence Diagram
A diagram showing the ordered exchange of messages between participants over time, used to make an interaction's control flow and failure points explicit.
Zero-Downtime Migration
Changing a schema or system while it stays in service, by adding the new alongside the old, migrating, then removing the old.
Every deployment produces a small spike of 502s that the team has learned to ignore. Fix it.
The cause In flight requests are being severed because the instance terminates before the load balancer has stopped sending to it, or before existing requests c
Knight Capital lost roughly $460M in 45 minutes in 2012 after a deployment reached seven of eight servers. Which architectural failures made that possible, and which one would you fix first?
The case, as publicly reported Per the SEC's 2013 order, Knight Capital deployed new order routing code to eight production servers ahead of a NYSE programme la
p99 latency on checkout tripled overnight. Dashboards look normal, no deployment went out, and every service reports healthy. How do you find it?
What the interviewer is testing Systematic diagnosis in a distributed system when the obvious signals are clean — which is the realistic version of this problem
In July 2019 a single regex deployed globally took Cloudflare's network to 100% CPU within seconds. What does this say about how configuration should be released?
The case, as publicly reported On 2 July 2019, Cloudflare deployed a new managed WAF rule. It contained a regular expression that caused catastrophic backtracki
Deployment Diagrams
What runs where, in which zone, behind which boundary.
Architecture Diagrams
Choosing an audience and refusing to mix levels of abstraction.
Context Diagrams
The system as one box, with its users and external systems.
Data-Flow Diagrams
Following the data across trust boundaries rather than the calls.
Sequence Diagrams
Ordered message exchange, and walking the failure of each arrow.
C4 Model
Context, container, component and code as four separate diagrams.
Containers
Images, registries, immutability and the deployment model they enable.
ML Platform
Feature stores, training pipelines, registries and deployment.