Speedscale

Atlanta, GA, USA
2020
  |  By Nate Lee
Large Language Models, or LLMs, have become a near-ubiquitous technology in recent years. Promising the ability to generate human-like content with simple and direct prompts, LLMs have been integrated across a diverse array of systems, purposes, and functions, including content generation, image identification and curation, and even heuristics-based performance testing for APIs and other software components.
  |  By Kush Mansingh
Microservices are now the architecture of choice for many developers when crafting cloud-native applications. A microservices application is a collection of loosely coupled services that communicate with each other, enhancing collaboration, maintainability, scalability, and deployment. There are several options for enabling this communication between microservices. When it comes to Python, gRPC and REST are two extremely popular directions to go.
  |  By Josh Thornton
Memory leaks happen when a program fails to release memory it no longer needs, and can be a big issue for developers and system administrators alike, as the gradual depletion of available memory often makes for complex troubleshooting and debugging. Given how the consequences of a memory leak can range from decreased system performance to outright crashes, it’s crucial to isolate the root cause of the leak quickly and efficiently.
  |  By Kush Mansingh
As a team, we have spent many years troubleshooting performance problems in production systems. Applications have become so complex that you need a standard methodology to understand performance. Our approach to this problem is called the Golden Signals. By measuring these signals and paying very close attention to these four key metrics, providers can simplify even the most complex systems into an understandable corpus of services and systems.
  |  By James Konik
In the process of developing software, designing and performing testing is a critical aspect of ensuring high software reliability, improving software quality, and deploying strong fit and function. The shift-right testing approach moves testing to later in your production cycle as a way of doing this with more accurate user data and post-production testing practices. Also known as “testing in production,” with shift-right, you test software after it has been deployed.
  |  By James Konik
In the process of developing software, designing and performing testing is a critical aspect of ensuring high software reliability, improving software quality, and deploying strong fit and function. The shift-right testing approach moves testing to later in your production cycle as a way of doing this with more accurate user data and post-production testing practices. Also known as “testing in production,” with shift-right, you test software after it has been deployed.
  |  By Josh Thornton
It’s impossible to learn about containerization without hearing about Docker and Kubernetes. These two tools together dominate the world of containers, both being the de facto standard in what they each do. When you’re first getting started learning about containers, it can be quite a challenge to figure out the differences between these two tools.
  |  By Nate Lee
Today’s complex, dynamic applications demand rigorous resilience testing. A common hurdle is accurately mimicking real user behavior. This post discusses a possible solution: production traffic replication (PTR), a technique that captures actual user interactions to enhance chaos testing, and the principle of intentionally introducing failures to evaluate application recovery.
  |  By Kush Mansingh
Kubernetes is an incredibly powerful solution, but testing the Kubernetes Ingress resources themselves can prove to be quite tricky. This can lead to significant frustration for developers – bugs can pop up in production that weren’t caught during testing, workflows that make sense on paper might fail in practice, and so forth.
  |  By Kush Mansingh
Local preview environments are transforming how developers test and validate code changes before merging them into the main codebase. Acting as temporary cloud environments, they provide a production-like setting where new features and bug fixes can be tested in isolation, catching issues early and streamlining the development code review process. These environments are crucial for enhancing development velocity, especially in CI/CD workflows used by DevOps engineers and QA teams.
  |  By Speedscale
The 2024 DORA report had interesting findings on the impact of AI development. But some statistics were surprising. Listen to Speedscale CTO Matt LeRay break down why some of this news makes sense and others are surprising, with research from other sources.
  |  By Speedscale
Installing Speedscale is quick and easy with our quickstart and available Helm charts.
  |  By Speedscale
Develop and test applications faster using traffic replay: traffic driven environments and tests.
  |  By Speedscale
Building and debugging Kubernetes microservices can be tough, especially when you don't have realistic data or environments. See how Speedscale can quickly mock DBs and APIs based on observed production behavior, so you can debug and develop features quickly. People familiar with GoReplay will notice a more modern and automated approach to turning user behavior into reproducible developer environments.
  |  By Speedscale
Check out Matt LeRay's talk on How to Test in Kubernetes at Star WEST 2024. Distributed architectures like Kubernetes present unique performance challenges. Autoscaling, Load Balancing and other mechanisms help with resiliency but can also serve to cover up fundamental problems. In this video, learn best practices and high level concepts around Kubernetes and achieving high throughput.
  |  By Speedscale
Mocks can be useful, but hard to build. You can use them as backends for development, or even tests (like load and performance testing). Speedscale takes the legwork out of building mocks, by modeling them after real observed traffic. This video covers a real-world example of how to use mocks to backend a JMeter load test.
  |  By Speedscale
There are many ways to bootstrap tests and mocks within Speedscale. Matt LeRay goes over various ways, eg. by using sidecars, agents, postman collections, or even request response pairs.
  |  By Speedscale
Speedscale's Traffic Viewer is the perfect complement to your production monitoring or observability system because it provides detailed information (like request and response payloads, headers, cookies, and more) that actually helps developers debug any issues and requires zero developer intervention--all of the data is provided from traffic.
  |  By Speedscale
In a conversation with Sephora's Senior Performance Engineer, Diana Manulik discusses why their current load testing tool, JMeter, wasn't meeting their needs for reporting, and why they chose Speedscale.
  |  By Speedscale
In this conversation with Sephora's Senior Performance Engineer, Diana Manulik discusses how she uses Speedscale and WireMock to generate mocks much faster.
  |  By Speedscale
Forecast latency, throughput and headroom before every deploy.

Continuous Resiliency from Speedscale gives you the power of a virtual SRE-bot working inside your automated software release pipeline. Forecast the real-world conditions of every build, and know you’ll hit your SLO’s before you go to production.

Feed Speedscale traffic (or let us listen) and we’ll turn it into traffic snapshots and corresponding mock containers. Insert your own service container in between for a robust sanity check every time you commit. Understand latency, throughput, headroom, and errors -- before you release! The best part? You didn’t have to write any scripts or talk to anyone!

Automated Traffic Replay for Every Stakeholder:

  • DevOps / SRE Pros: Understand if your app will break or burn up your error budget before you release.
  • Engineering Leads: Let Speedscale use traffic to autogenerate tests and mocks. Introduce Chaos testing and fuzzing.
  • Application Executives: Understand regression/performance, increase uptime and velocity with automation.

Before you go to production, run the projection.