Build WireMock mappings fast from real traffic
Skip hand-writing WireMock stubs. Speedscale records your real request and response traffic and exports it straight to WireMock mappings.
Browse 92 posts in this category
Skip hand-writing WireMock stubs. Speedscale records your real request and response traffic and exports it straight to WireMock mappings.
Logs, metrics, and traces are a lossy compression of production. Five things you can do with a traffic data lake that observability can't.
Replay an authenticated flow and the protected calls fail with 403. Here is how proxymock recommendations fix the expired bearer token in one click.
Production traffic is the most complete record of what your system does, and most teams throw it away. One capture powers reproduce, validate, and sandbox.
Spring Boot upgrades silently change JSON contracts and autoconfiguration. Use traffic replay to catch every regression before production.
AI-generated code breaks traditional mocking. Here's how BYOC capture and replay with proxymock keeps verification grounded in real production traffic.
I tested 100 bugs across 240 microservices the model has never seen. Alert only: 51% pass rate, wrong service 34% of the time. Traffic captures: 77%.
A 2026 take on WireMock alternatives. Keep WireMock for what it's good at; add Microcks (now CNCF Incubating) or proxymock for the gaps. The honest map.
Export recorded proxymock traffic to Datadog Synthetics in one command. Auth headers redacted, global variables created. No scripting, no flaky journeys.