Search the practice set
275 questions, 991 terms and 600 topics in 30 areas.
53 results for “Workload Isolation”
Compute Isolation Boundary
The line across which one domain's analytical workload cannot affect another's performance, cost attribution or access.
Noisy Neighbour
One tenant or workload consuming shared resources to the detriment of others sharing the same infrastructure.
Warehouse Concurrency Scaling
Adding compute clusters to absorb concurrent queries rather than queueing them, and the cost behaviour that turns a queue into a bill.
Cell Isolation
Bulkheading at the level of a complete system copy, so that any failure — including ones nobody predicted — is contained to the customers assigned to one cell.
Saga Isolation Anomaly
The intermediate states visible to other transactions during a saga, because a saga provides atomicity and durability but not isolation.
Thread Pool Isolation
Giving each downstream dependency its own pool of threads or permits, so one slow dependency cannot consume the capacity needed to serve everything else.
Workload Fit Assessment
Choosing between warehouse, lake and lakehouse by the workloads that must run, rather than by which one is currently fashionable.
Workload Identity
Giving a running workload a cryptographically verifiable identity issued by the platform, so it obtains short-lived credentials without a stored secret.
Workload Identity Federation
A pipeline proving what it is with a short-lived signed token from its own platform, so no long-lived cloud credential is ever stored.
Workload Model
A description of the traffic mix, arrival pattern and data distribution a load test reproduces, which determines whether the test's results mean anything.
Blast Radius
The set of things that break, or become reachable, when one component fails or is compromised.
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.
Bulkhead
Partitioning resources so that exhaustion caused by one dependency or tenant cannot starve the others.
Cell-Based Architecture
Partitioning a service into complete, independent copies of itself, each serving a subset of customers, so a failure is bounded to one cell.
Compute Tier Placement
Deciding which of on-device, on-premises, metro, regional or central compute a workload belongs to, from its latency, data volume and autonomy requirements.
Concurrency Limiting
Bounding the number of simultaneous in-flight operations so that overload produces fast rejection rather than resource exhaustion.
Data Plane Proxy
The per-workload proxy that actually carries mesh traffic, applying mTLS, retries, timeouts, routing and telemetry outside the application.
Egress Filtering
Restricting which destinations a workload may connect to outbound — the control that limits data exfiltration and SSRF impact, and the one most often omitted.
Execution Model Fit
Matching a workload's traffic shape, duration and state requirements to the execution model that suits it, rather than choosing one model for everything.
Fault Domain
A boundary within which a single failure is contained, defined by the infrastructure and dependencies that components inside it share.
Feedback Loop
A circular causal chain in which an effect influences its own cause, producing behaviour that cannot be understood by examining components in isolation.
Instance Family
A group of instance types sharing a resource profile — general purpose, compute optimised, memory optimised, storage optimised, accelerated — chosen by which resource the workload…
Instance Family Selection
Matching a workload's resource profile to a machine type designed for it, which is frequently a larger saving than reducing size.
Interruption Tolerance
The property that determines whether a workload can use heavily discounted pre-emptible capacity, defined by what happens when an instance is reclaimed at short notice.
Microsegmentation
Enforcing fine-grained network policy between individual workloads rather than between broad network zones, so a compromise cannot move laterally.
Monzo's Microservice Estate
Monzo runs a bank on well over a thousand microservices, and the interesting engineering is in the platform and network isolation that makes that number survivable.
OLTP vs OLAP
Two workload shapes with opposite requirements — many small indexed transactions versus few large scans and aggregations — which is why they belong in different stores.
Provider Exit Plan
A documented and tested plan for moving a workload off a provider, whose credibility is measured by what has actually been rehearsed rather than described.
Secret Zero
The credential a workload needs in order to authenticate to the secret manager — the one secret that cannot itself be stored in the secret manager.
Shuffle Sharding
Assigning each customer a random combination of workers rather than a fixed shard, so that any two customers rarely share their whole set.
Two-Phase Locking
The concurrency control protocol behind serializable isolation — acquire locks in a growing phase, release only in a shrinking phase, never interleaving the two.
Virtual Private Cloud
A logically isolated network inside a cloud provider, with an address range you control and explicit rules for what may enter and leave.
Well-Architected Review
A structured self-assessment of a workload against defined pillars — operational excellence, security, reliability, performance, cost, and sustainability.
WhatsApp's Small-Team Scale
WhatsApp served hundreds of millions of users with a few dozen engineers by matching one technology choice precisely to the workload and refusing to add anything else.
Write Skew
An anomaly where two transactions each read a set of rows, make disjoint writes based on what they read, and together violate an invariant neither could have broken alone.
A team wants to move a workload from PostgreSQL to a document store because "the schema keeps changing". What do you ask?
The questions 1. What is actually changing — the shape, or the schema management process? "The schema keeps changing" usually means migrations are painful, not
A service calls four dependencies. How do you size its thread pools, and why is the total often smaller than people expect?
The sizing rule Little's Law, per dependency: concurrency = throughput to that dependency × its latency. Dependency Calls/s Latency Concurrency Pool Auth 500 10
A team proposes circuit breakers on every downstream call. What would you add, and why is the breaker not the most important control?
Why the bulkhead matters more A circuit breaker acts after it has detected a pattern of failure. During the seconds before it trips — and while its threshold is
An estate has database passwords in environment variables across 200 services. Design the migration to a secrets manager.
Sequence it by risk, not by convenience Phase 0 — stop the bleeding. Secret scanning in CI and on the existing repositories, blocking new commits containing cre
One customer's batch job saturates a shared service and degrades everyone. Rate limiting them fixes it, until the next customer does the same. What is the structural answer?
Why per customer rate limits keep failing A static limit is set from what that customer was doing, not from what the service can serve. It is reactive — you dis
You are asked to make a multi-tenant SaaS resilient to "any single failure". You propose cells. What must you find before that claim is true?
What must be found: every shared dependency A cell is isolated only if nothing inside it depends on something shared with another cell. The work of adopting the
Your load tests pass consistently and production still falls over at peak. What is wrong with the tests?
The workload model is almost certainly unrealistic Data distribution is the usual culprit. Synthetic tests spread requests uniformly across keys, which produces
Workload Isolation
Keeping an analyst's query off the pipeline's compute, and both off the dashboard's.
Bulkheads & Isolation
Partitioning resources so one dependency cannot starve the others.
Fault Isolation
Cells, zones, tenants and the partitions that bound a failure.
Transactions & Isolation
ACID, isolation levels, and the anomalies each level permits.
Identity & Access Management
Workload identity, roles, permission boundaries and usage-based review.
Kubernetes
The reconciliation loop, and whether the workload needs what it provides.
Performance Test Design
Workload models, warm-up, think time, and the distribution the average hides.
Pipeline Secrets
Short-lived credentials, workload identity, and why the CI system is a prime target.
Platform Tenancy
Isolating teams sharing a cluster, account or pipeline fleet, and where isolation must be hard.
Polyglot Persistence
Choosing a store per workload, and the operational cost of variety.