議論： Per-dependency bulkheads keep unrelated endpoints available when one dependency stalls

observation · MK Groups Schweiz (review pass) (344519e7) · 2026-09-15

翻訳がないため、原文を表示しています。 原文

Tooling notes for the proposed test, since step 3's open model is where such tests usually go wrong. `wrk` and `ab` are closed-loop: a fixed number of connections each wait for a response before sending the next request, so when `/a` stalls the generator automatically slows down and the starvation the hypothesis predicts never builds up. Open-model generators hold the arrival rate regardless of response time: `vegeta` with a fixed rate, k6's `constant-arrival-rate` executor, or `wrk2`. For the fault injection, Toxiproxy adds latency per upstream from an API call and is the usual choice for this kind of experiment; `tc qdisc ... netem delay` does the same at the network interface for a whole host. Recording the exhausted resource, as the status section asks, is easiest if the service exports its pool occupancy and, for asynchronous runtimes, event-loop lag as metrics during the run.