Search the practice set
275 questions, 991 terms and 600 topics in 30 areas.
60 results for “Contract Testing at Scale”
Contract Verification Gate
A provider's pipeline stage that replays every consumer's recorded expectations and fails the build if any would break.
Contract Testing
Verifying that a provider satisfies the expectations each of its consumers actually relies on, without running all the services together.
Consumer-Driven Contract
A contract derived from what consumers actually use, published to the provider, and verified in the provider's own build.
Provider Verification
The provider-side stage that replays every consumer's recorded expectations against the real implementation.
Bidirectional Contract
A contract verified from both sides — the consumer's expectations and the provider's actual behaviour — without either running the other's tests directly.
Bronze Layer Contract
What the raw landing zone promises and refuses to promise — a faithful replayable copy of the source, with no correction applied.
Consumer Contract
A machine-readable record of exactly which parts of a provider's response one consumer relies on, generated from that consumer's own tests.
Data Contract
An explicit, versioned, enforced agreement between a data producer and its consumers about schema, semantics, quality and change policy.
Expand-Contract Migration
Changing a schema in additive steps that keep old and new code both working, so deployment and migration never have to be simultaneous.
Failure Injection Testing
Deliberately introducing faults into a system under test to verify that timeouts, retries, fallbacks and circuit breakers behave as designed.
Google Maps and Planetary-Scale Spatial Serving
Map serving is fast because almost nothing is computed on request — the world is precomputed into a pyramid of tiles, and space is indexed onto a one-dimensional curve.
Load Testing
Driving a system with realistic traffic at a target volume to verify it meets its performance targets before real users do.
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.
Platform Contract
The platform's promise to its consumers about interface stability, behaviour and support, treated with the same seriousness as an external API.
Scale Cube
A model describing three independent axes of scaling — cloning, functional decomposition, and data partitioning — each addressing a different limit.
Testing Strategy Shape
The distribution of tests across levels, chosen so that feedback is fast where it can be and confidence is real where it must be.
Testing Trophy
A distribution weighted towards integration tests rather than unit tests, appropriate where most of the risk lives at boundaries rather than in logic.
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.
Zoom's Pandemic Scale-Up
Zoom grew from around 10 million to over 300 million daily meeting participants in roughly three months, absorbed by a hybrid architecture and a distributed media routing design.
Abstraction
Exposing what a component does while hiding how it does it, so callers depend on the contract rather than the mechanism.
Adversarial Evaluation
Deliberately attempting to make a model behave badly, because a probabilistic system with no fixed expected output cannot be verified by conventional testing.
Approximate Nearest Neighbour Index
An index that trades exactness for speed when finding similar vectors, making large-scale semantic search feasible.
Automated Accessibility Coverage
The proportion of accessibility criteria a tool can decide mechanically — around a third — and the explicit acknowledgement that the rest needs people.
Booking.com's Experimentation Platform
Booking.com runs over a thousand concurrent experiments and treats the ability to test any change safely as a platform capability rather than a product feature.
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.
Chaos Engineering
Deliberately injecting failure into a system to discover, before an incident does, which of your resilience assumptions are false.
Three teams keep breaking each other's services with API changes. Someone proposes contract testing. How do you introduce it without a six-month programme?
Start with one pair, not with the estate Pick the pair of services that has broken each other most recently. Instrument that one relationship end to end: the co
Integration failures between 30 services are found in a shared staging environment, days after merge. Propose a change.
Why the current model fails A shared staging environment is a serialised, high latency feedback channel . Failures are found late, attribution is ambiguous (who
A serverless API works in testing and fails under load with connection errors. The database is at 5% CPU. Explain and fix.
The mechanism Serverless functions scale by creating independent execution environments , each with its own process and its own connection pool. Two hundred con
A service autoscales on CPU. During incidents it never scales out, even as latency triples. Why, and what would you scale on instead?
Why CPU never triggers The service is latency bound, not compute bound. Its threads are waiting — on a database, a downstream API, a lock, or a connection pool
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
The business has selected a SaaS product. You are asked to review the integration architecture after the contract is signed. What do you do?
Accept the position and be useful within it The selection cannot be reopened, and arguing about the process will spend credibility for nothing. What can still c
A brief database slowdown caused a two-hour full outage. Explain the likely amplification chain and the fixes at each stage.
The chain Slow database → queries that took 10 ms take 2 s. Thread pool exhaustion. Requests hold threads for 200× longer. A pool of 50 that handled the load ea
A team's CI suite fails roughly one run in three for reasons unrelated to the change. Everyone reruns until green. How do you recover the situation?
Recognise what has actually been lost The suite is no longer a gate. Once the team's reflex on red is "rerun", that reflex is applied to genuine failures too, a
After a five-minute network outage at your ingest tier, 200,000 devices reconnect simultaneously and the authentication service collapses. How do you fix this?
The mechanism Every device detected the disconnection at roughly the same moment and retried immediately. Reconnection is the most expensive operation in the fl
An end-to-end suite of 340 tests takes four hours and fails spuriously about half the time. The team wants to parallelise it. Is that the right move?
Parallelising treats the symptom It might halve the runtime. It will not touch the flakiness — in fact parallelisation often worsens it, by exposing shared stat
Contract Testing at Scale
Keeping dozens of services compatible without an environment that runs all of them.
Contract Testing
Verifying what consumers actually rely on, without a shared environment.
Testing Strategies
The pyramid, and the contract tests distributed systems add to it.
Accessibility Testing
Automated checks, their ceiling, and the manual testing that has to sit above it.
Contract Tests
Capturing what consumers actually use, not what the API documents.
DR Testing
Restore drills, timed against the stated RTO, into a clean environment.
Device Telemetry at Scale
Deciding what a device sends, how often, and what is aggregated before it leaves.
Load Testing
Realistic data, realistic mix, and a ramp rather than a step.
Mutation Testing
Measuring whether tests would actually notice a defect, not just cover a line.
Resilience Testing
Exercising retries, breakers and fallbacks that are otherwise never run.
Security Testing in the Pipeline
SAST, DAST, dependency and secret scanning, and what to do with the findings.
Soak Testing
Long runs that surface leaks and slow degradation.
Stress Testing
Pushing past target to learn what breaks first and how it fails.
Testing & Quality Architecture
General material on designing a testing strategy as an architectural concern.
Testing in Production
Synthetic transactions, dark launches and shadow traffic, done deliberately and safely.
API Documentation
OpenAPI as a machine-checked contract rather than as prose.
Abstraction & Encapsulation
Hiding mechanism behind contract, and protecting invariants by owning state.
Chaos as a Test
Fault injection with a hypothesis, a blast radius and an abort condition.
Consumer-Driven Contracts
Consumers declaring what they rely on, and providers verifying against those declarations.
Continuous Controls Monitoring
Testing controls continuously instead of sampling them once a year.
Data Governance & Semantics
General material on ownership, meaning, quality and control of data at enterprise scale.
Database Migration Under CD
Expand-contract, backwards-compatible schema change, and migrations that cannot roll back.