Operations | Monitoring | ITSM | DevOps | Cloud

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.

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.

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.

Stop Getting Charged for Test Emails! #speedscale #aws #ses

Tired of local development using AWS SES leading to spam, cloud costs, and unnecessary API calls? When testing your app, you shouldn't have to connect to a live cloud environment just to send a test email. Learn how to set up your own local ProxyMock server to intercept and record real SES calls, so you can replay them instantly and accurately without ever leaving your desktop.

MOCK AWS SES Locally! Stop Sending Test Emails & Cut Cloud Costs

In this quick guide, Speedscale's Matt LeRay shows you how to free your local development environment from direct AWS SES dependencies. When your application sends an email during local testing, it usually triggers a live AWS transaction, leading to slow tests, unnecessary cloud costs, and sometimes even spam filter issues.

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.

The Load Testing Start Guide! #speedscale #stresstest #loadtesting #mocking #startup

Are you ready to get serious about load and stress testing, but don't know where to start? This guide highlights the trap most serious engineers fall into: trying to build a custom DIY testing environment. The traditional path means signing your team up for maintaining load drivers, test case frameworks, ephemeral environments, and endless custom mocks a massive drain on time and resources. There's a better, cheaper, and faster solution: Traffic Replay.

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.

Stop Debugging Blindly! How Traffic Capture Can Help Your Code #speedscale #trafficcapture #ai

Is AI "slop" or new code pushing tons of bugs into production? You can't test everything forever. Learn how traffic capture is the most efficient way to understand how your code is actually running in the real world. By grabbing data from sidecars, packet captures, or logs, you get the context you need to prevent bugs and improve performance.