gRPC Mocks, Tests and Contract Checks From a .proto
Turn a .proto file into gRPC mocks and tests with proxymock, record real responses, and catch field type changes that protobuf decoding silently accepts.
Speedscale Blog
Latest insights on Agentic AI workflows, cloud native architectures, and performance optimization best practices from the Speedscale team.
Search answers across the full blog library
Featured Post
Recent Posts
5 Questions to Ask Before the Next Cloud Outage
A power failure in one Google Cloud London zone took down banking apps for hours. Five questions to answer with real traffic before the next outage answers them for you.
Load Test One Endpoint, Watch the Rest
Load test one endpoint while keeping another steady. See how separate schedules and latency goals reveal slowdowns an overall average can hide.
Observability Never Really Shifted Left
We shifted testing, security, and CI/CD left. Observability stayed in production. With AI writing code faster, validation is the bottleneck.
Mock vs stub: differences and testing examples
A stub supplies responses; a mock verifies interactions. Compare both with runnable Python examples and learn when API traffic mocks help.
Postman load testing: a practical API tutorial
Run a Postman performance test, choose virtual users, inspect latency and errors, and isolate dependencies with recorded API mocks.
k6 tutorial: captured traffic with mocked backends
Capture API traffic with Speedscale, export a k6 load scenario, and mock backend dependencies in Kubernetes with speedctl or locally with proxymock.
Traffic mirroring in Kubernetes: Istio vs Speedscale
Compare Istio traffic mirroring with Speedscale replay in Kubernetes. Use capture, redaction, and dependency isolation for repeatable regression tests.
WireMock vs MockServer vs proxymock for API testing
Compare HTTP stubs, request verification, and recorded dependency mocks. Choose WireMock, MockServer, or proxymock for your Java API tests.
Traffic Replay Tutorial: Capture, Replay, Read Results
Capture one service's API traffic, replay it against a Kubernetes test workload, and use the report to tell a regression from a replay setup problem.