Operations | Monitoring | ITSM | DevOps | Cloud

The Checkly team is continually working to improve our platform to meet—and exceed—the current and future monitoring needs of our customers, and we’re thrilled to share another batch of new product features and enhancements during Checkly Launch Week 2.

Checkly is the synthetic monitoring platform that scales. A core part of the Checkly platform is our monitoring as code workflow, which just got a massive boost with the launch of our TS/JS native Checkly CLI which is now in beta!

Continuous load testing is a powerful way of preparing for surges in traffic, without needing real users. Imagine you’re a software engineer working on a website that’s seen a recent surge in traffic. Despite initial testing indicating that the website should be capable of handling the increased load, the website crashes during peak hours. Load Testing is the process of simulating real-world usage of a website or application.

A mock server can prove useful in many circumstances. Imagine you’re an engineer working on optimizing a feature inside of an existing API that relies on multiple other microservices to function properly. To fully test the optimizations, you’ll have to set up test versions of all the dependencies, which quickly proves to be quite a task in and of itself. This is where a mocks—a server that simulates the behavior of a real server—can be very beneficial.

In this third and final part, you’ll get to see a few examples that aren’t strictly related to configuration changes or new tools, but rather ways that traffic replay can help streamline the development process for those deploying in Kubernetes.

The use of APIs is at the forefront of automation. There are many ways for developers and applications to make use of APIs, and GraphQL is one way to make the most of the data. As technologies continue to grow and evolve, especially with drivers like the DevOps methodology, it is important to keep on top of better and quicker ways to meet our business goals. This is one of the reasons I find GraphQL to be so exciting, and why everyone should understand it.

Today’s web consists of lots of 3rd party resources. Let it be your fonts, transformed and optimized media assets, or analytics and ad scripts, many sites out there include resources that they don’t own. Your website probably has a lot of those dependencies, too! And while implementing third-party resources has downsides for performance and you should self-host your assets when possible, sometimes relying on external files is unavoidable.