Operations | Monitoring | ITSM | DevOps | Cloud

In software development, load testing plays a critical role in ensuring that applications perform optimally under any imaginable load condition. To do this, developers subject applications to several types of load tests, including scalability, spike, endurance, and stress testing. The ultimate goal of these performance tests is to pinpoint potential bottlenecks and ensure the reliability of the overall system where the software application runs before reaching production.

This is a guest post from Saskia Parks. If you're exploring test data management (TDM) solutions, you probably know your current practices aren't ideal, but you're skeptical investing in a solution is worth the budget and effort. We hear the same concerns. The perception is that proper TDM is expensive, complicated, and takes months of painful implementation.

Imagine you want to launch an application without first building and managing the servers that run it. You write the code, pick how it should run, and then let a platform take care of the rest. That’s the core promise of AWS Elastic Beanstalk. In this snackable guide, you’ll understand AWS Elastic Beanstalk well enough to decide if it belongs in your AWS architecture.

During the October 20th AWS outage, not one Control Plane customer went down. Here’s the architecture that made that possible, and how to assess your own.

The modern world runs on mission-critical software. It moves our money, drives our cars, diagnoses our illnesses, and fundamentally improves our lives. But, organizations building this critical software face a paradox: they need to move fast to stay competitive, but they also need rigorous governance to manage risk. This has created a lot of tension in regulated industries.

"I wish I knew about this a couple years ago..." Over my seven years as a cofounder, I've heard some version of that line more than any other. Usually, it comes at the end of a demo to someone who has spent a year getting to something not even close to what they're seeing on my screen. The story is always the same. An organization adopts Kubernetes and arrives at the inevitable conclusion that they need a platform.

A few months ago I wrote about BygoneSSL and the 1.5 million domains with valid certificates owned by someone else. Domains change hands but certificates don’t know. The old owner keeps their private key, and the certificate keeps working. It’s an industry problem, but it turns out it’s our problem too. We purchased certkit.dev for internal development and demos.