In this Postman load testing tutorial, you'll learn how to run a large scale load test in Kubernetes using your existing Postman collections. Because HTTP services don't have a graphical user interface, it's common to build collections of requests using Postman during the development process. These collections are useful for running quick functionality tests as you develop each endpoint. However, as the service grows you eventually need to test it in a more realistic way with larger volume. This is called a load or stress test. Speedscale is a Production Data Simulation Platform that includes this stress/load testing capability out of the box.
By combining traffic replay capabilities from Speedscale with observability from Datadog, SRE Teams can deploy with confidence. It makes sense to centralize your monitoring data into as few silos as possible. With this integration, Speedscale will push the results of various traffic replay conditions into Datadog so it can be combined with the other observability data. Being able to preview application performance by simulating production conditions allows better release decisions. Moreover, a baseline to compare production metrics can provide even earlier signals on degradation and scale problems. Speedscale joined the Datadog Marketplace so customers can shift-left the discovery of performance issues.
API Observability isn't exactly new, however it's popularity has seen rapid growth in the past few years in terms of popularity. API Observability using open source is different from regular API monitoring, as it allows you to get deeper and extract more valuable insights. Although it takes a bit more effort to set up, once you've got an observability infrastructure running it can be immensely helpful not only in catching errors and making debugging easier, but also in finding areas that can be optimized.
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 what the differences are between these two tools.