Using proxymock with AWS Services
Record AWS API calls with proxymock, inspect the capture, and run local mocks while keeping IAM, signing, and cloud-state integration tests.
Browse 76 posts in this category
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.
A practical hybrid workflow that uses costly LLM APIs for planning and local models (via Ollama + OpenCode) for execution, guarded by deterministic evals.
UI synthetics only tell you something is broken. Traffic replay per microservice isolates failures before any human walks up. Zero scripts required.
Learn the 4 golden signals — latency, traffic, errors, and saturation — and how to use them for monitoring, alerting, and pre-release testing.
What do good tests look like, and do you even need a Golang testing framework? It’s a loaded question with an open answer.
Microservices are now the architecture of choice for many developers when crafting cloud-native applications.
Use traffic replay via MCP to create a tight feedback loop for AI coding agents, preventing hallucinated success by validating against immutable.
Connect an MCP server to your LLM coding assistant so it can pull real production data on demand, validate its assumptions.
Choose the desktop proxymock or the hosted cloud trial to get started.