Break One Dependency, Not The Whole Cluster
Scoped chaos rules are now in proxymock: pick traffic with a filter query, perturb it, and label every injected failure so it is never mistaken for a real one.
Latest insights on API testing, performance optimization, and software development best practices from the Speedscale team.
Scoped chaos rules are now in proxymock: pick traffic with a filter query, perturb it, and label every injected failure so it is never mistaken for a real one.
I pointed a classifier at 7,943 API calls to find business workflows. It worked, then showed where my assumptions about sessions and patterns fell apart.
See why reliability engineering must span code, testing, telemetry, and incidents as AI agents erase the boundary between pre-production and production.
Compare eBPF, sidecars, telemetry agents, OpenTelemetry, APM, and proxies through an evolving ladder of production visibility.
Infrastructure and application chaos break different layers and find different bugs. Netflix built two systems for a reason. Most enterprises buy just one.
Diagnose a p95 latency regression that CPU profiling cannot explain using Prometheus histograms, then prove the fix with identical proxymock replays.
Find the rare payload that sends a service down a retry path, correlate it to the recorded response, and prove the fix with proxymock replay.
Use Cilium Hubble flow evidence and proxymock replay to prove whether a Kubernetes timeout came from your code, a dependency, or a dropped packet.
Synthetic monitoring depends on scripts engineers maintain by hand. Capturing and replaying real production transactions turns customer behavior into tests.