Your Mock Is Lying
Part 8 of Getting Started with Mocks: the carrier renames a field, production breaks, and every mocked test still passes. Java, Node, Go, Python.
Latest insights on API testing, performance optimization, and software development best practices from the Speedscale team.
Part 8 of Getting Started with Mocks: the carrier renames a field, production breaks, and every mocked test still passes. Java, Node, Go, Python.
Security controls rarely break a banking platform alone. Their cumulative divergence from Kubernetes standards creates a compounding maintenance tax.
Observability tells you when production is on fire. Capturing and replaying real traffic lets you recreate the incident, verify the fix, and keep it fixed.
A scoped chaos rule takes one dependency down and nothing else, so the fallback branch in your code executes on demand instead of during an outage.
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.