Comparison
BulkheadvsResource quota
Bulkhead
you give each downstream its own pool of connections so one slow dependency cannot consume every thread you have.
Partitioning resources so that exhaustion in one compartment cannot sink the whole service. In practice: separate connection pools, thread pools or instances per dependency or per tenant. It converts a total outage into a partial one, which is the entire goal of resilience engineering.
Full entry →Resource quota
one team's runaway job could not consume the whole cluster, because their slice had a declared ceiling.
A cap on how much of a shared cluster one team, namespace or tenant may request. It is the main tool that makes a shared platform politically viable, since it converts 'someone took all the capacity' from an incident into a rejected request. It also relocates the argument to quota allocation, which is the correct place for it, and requires an obvious, fast path to raising one.
Full entry →