Operations | Monitoring | ITSM | DevOps | Cloud

Mocking PostgreSQL the Easy Way: Simplifying Testing with Speedscale Proxymock

Every developer who’s worked with PostgreSQL knows the pain: testing against a real database slows everything down. You need the database running locally, loaded with the right data, and configured to match production as closely as possible. Every time you run a new test or build, you’re forced to repeat that setup migrate schemas, seed test data, and clean everything up again. It’s time-consuming, brittle, and hard to scale across a team.

Better integration tests in Cursor using proxymock

Cursor is fantastic at cranking out code changes. I recently used it to splice a brand-new downstream API call into one of our Go microservices, and the diff looked great. The unit tests finished before I lifted my coffee mug, yet I still had zero certainty the change would survive contact with real traffic. That gap is all about integration tests, so I paired Cursor with proxymock and the outerspace-go demo service to prove the behavior end to end.

KubeCon + CloudNativeCon 2025: Recap

Hi everyone, my name is Bailey Ahrens, and I’m a marketing intern at Speedscale! I just returned a few days ago from KubeCon + CloudNativeCon North America 2025. While it was only my second trade show, it felt like a huge step forward in my confidence, skills, and future direction. My first conference (API World) was all about stepping outside my comfort zone. KubeCon was where I started leaning into that confidence and finding my place in the tech community.

Part 3: Building a Production-Grade Traffic Capture and Replay System

At a previous company, we had over 100 microservices. I’d make what seemed like a simple change to one service and deploy it, only to discover it broke something completely unrelated. A change to the user service would break checkout. An update to notifications would break reporting. We spent more time fixing unexpected bugs than shipping features. The problem was our test scenarios were too simple.
Sponsored Post

Cascading Failures Aren't Inevitable: Lessons from the AWS DNS Outage

AWS outages grab headlines because they affect millions, but the root cause often comes down to something invisible: DNS failures and cascading service dependencies. The complexity of modern cloud systems, combined with the advanced technology powering platforms like AWS, makes these outages particularly challenging to diagnose and resolve. The recent AWS outage proves one thing: you can't prevent every DNS issue, but you can create resilient architectures and prevent a single failure from taking down your entire service if you test for it.

Speedscale Proxymock: Freely testing cloud native apps alongside AI code assistants

We’ll always remember 2025 as the year AI code assistants went big. Copilot, Cursor, Claude, Windsurf, whatever. Developers went from mistrusting these tools, to being expected to turn over much of their coding labor to them. Even if, according to an extensive Stack Overflow survey, only 3 percent of professional developers say they ‘highly trust’ AI coding tools.

Part 2: Building a Production-Grade Traffic Capture, Transform and Replay System

When developers try to build realistic mocks and automated tests from production network traffic, the real challenge isn’t just in the capturing—it’s in the data manipulation. Raw traffic is a chaotic sea of patterns, dynamic tokens, environment-specific secrets, and tangled dependencies that seem impossible to untangle by hand. Over my two decades of building these sytems, I learned that solving this problem requires more than brute-force parsing or ad hoc scripts.

Settle Your QA Debt Before the Bugs Start Breaking Kneecaps

In Part One, we discussed how QA debt builds silently over time — causing slower releases, late-night firefights, and unpredictable test cycles. The next step is understanding how much debt you have and where it hides. This post goes deeper into measuring QA debt — what to track, how to collect data, and how to use those insights to create a sustainable plan for improvement.

Mitmproxy vs Proxymock: Replaying Traffic for Realistic API Testing

Replaying traffic is a core tool in your toolbox when you need to reproduce a tricky bug or validate how your app behaves. Traffic replay is especially valuable for testing complex software applications that rely on APIs and microservices, where integration and functionality must be thoroughly validated.

Part 1: Building a Production-Grade Traffic Capture and Replay System

A few years ago I was on call during the Super Bowl. At the time I was working for an observability vendor and one of our customers had an outage caused by a surge in user traffic. But our monitoring system didn’t have enough data to know what went wrong and I sat on a call for 2 hours painfully listening to them spinning up more servers and trying to catch up with the user load.