Comparison
Blocking data testvsCircuit breaker
Blocking data test
the failed check stops the pipeline so the bad numbers never reach the dashboard, and someone gets paged instead.
A data test whose failure halts publication rather than merely recording a warning. Choosing which tests block is the whole design: block on everything and the pipeline stops nightly, block on nothing and the tests are decoration. The useful rule is that a test blocks when serving wrong data is worse than serving stale data, which is a question for the consumer.
Full entry →Circuit breaker
after enough consecutive failures you stop calling the provider at all for a while, instead of queueing thousands of doomed requests behind a dead dependency.
After sustained failures or latency spikes from a provider, stop calling it for a cooling period and serve fallbacks, rather than queueing doomed requests. Your existing resilience pattern, unchanged.
Full entry →