Break One Dependency, Not The Whole Cluster
Blog post from Speedscale
Proxymock v2.5.892 introduces scoped application-level chaos rules that select recorded HTTP traffic with filter queries, perturb real dependency responses through effects such as status changes, latency, connection failures, body corruption, or payload-field modifications, and mark every injected response with an X-Speedscale-Chaos header for attribution. Unlike infrastructure chaos tools that disrupt pods, networks, or hosts and commonly produce timeouts or connection errors, this approach targets specific endpoints, hosts, or headers and tests how applications handle realistic but altered dependency behavior, including valid-looking 200 responses with malformed data. Rules support frequency, timing windows, reproducible seeded behavior, sticky outcomes, and composable effects, with first-match rule evaluation. Chaos-affected traffic is excluded from drift and match-rate calculations to preserve those metrics but remains included in pass/fail results, while original recordings are retained unchanged for future replays. The feature can be used locally, in CI, or through TrafficReplay configurations, though it currently applies only to outbound HTTP dependencies and complements rather than replaces infrastructure-focused chaos testing.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.