Chaos Monkey Won't Find Your Bug
Infrastructure and application chaos break different layers and find different bugs. Netflix built two systems for a reason. Most enterprises buy just one.
Latest insights on API testing, performance optimization, and software development best practices from the Speedscale team.
Infrastructure and application chaos break different layers and find different bugs. Netflix built two systems for a reason. Most enterprises buy just one.
Record AWS API calls with proxymock, inspect the capture, and run local mocks while keeping IAM, signing, and cloud-state integration tests.
Record Google Cloud API calls with proxymock and test locally. Understand the limits around IAM, OAuth, quotas, and stateful behavior.
Test growing data volume independently from concurrency. Prepare representative datasets, reset state, and inspect query plans and resource limits.
Diagnose Kubernetes OOMKilled events. Separate memory limits from CPU throttling, inspect termination evidence, and size resources from measured workloads.
Start load testing with a bounded workload, representative data, measured duration, and explicit latency, error, and correctness goals.
Use service virtualization to replace selected dependencies. Keep fixtures current, define state behavior, and retain real-provider integration checks.
Keploy's Speedscale comparison gets the architecture wrong. Check its claims against the docs for eBPF capture, TLS, automatic mocks, and local testing.
Part 1 of Getting Started with Mocks: the one job a mock does, the five situations where you need one, and what a green mocked test does not prove.