Introducing Steadybit's Experiment Templates, a powerful new feature designed to transform the way you approach chaos experiments. These customizable and reusable templates streamline experiment creation, allowing teams to focus on what truly matters—enhancing system reliability and efficiency.

Managing cloud costs while maintaining system reliability is a complex challenge. This post delves into how chaos engineering can help organizations optimize their cloud environments, offering actionable insights and strategies to achieve significant cost savings while ensuring robust system performance.

This article examines the Digital Operational Resilience Act (DORA), a forthcoming EU regulation poised to reshape digital risk management by 2025. Focusing on industries widely, especially the financial sector, DORA mandates rigorous ICT risk management practices. We discuss its four main pillars, the significance of resilience testing, and how platforms like Steadybit can aid compliance. The piece provides actionable insights for organizations to prepare for DORA, ensuring readiness for a digitally resilient future.

Exciting developments are underway as we deepen our collaboration with LoadRunner, now integrating with LoadRunner Enterprise. This significant leap forward enhances our mission to provide the most extensible chaos engineering tool available. Here's why it matters and how we're working together to redefine the future of testing.

The primary objective of a Chaos Experiment is to uncover hidden bugs, weaknesses, or non-obvious points of failure in a system that could lead to significant outages, degradation of service, or system failure under unpredictable real-world conditions. 

Let us introduce you to our newest (and super exciting) brainchild at Steadybit: Advice. It's like having a wise guru in your toolkit.

In a world where digital systems form the backbone of our operations, the emphasis often lies on technical robustness. However, the ability of a team to respond to system failures is equally, if not more, crucial. Chaos engineering, often viewed solely as a technical tool, is a vital platform for team development.

This blog is about why chaos engineering is your go-to move in 2024. It's not just about keeping up with tech trends; it's about building systems tough enough to roll with the punches. Let's dive into how chaos engineering can be your company's ticket to staying resilient and reliable when things get shaky.

Reliability is the cornerstone of user satisfaction in today's world. At Steadybit, we understand the critical nature of this reliability, especially in Kubernetes clusters widely adopted across organizations. We're excited to announce our latest suite of enhancements, designed to empower users to detect and remediate potential risks in their Kubernetes environments proactively.

Two years have passed since my first blog post about Retries with resilience4j, where I promised a second post about Circuit Breakers. There it is!

When milliseconds matter, Chaos Engineering is the difference between a five-star review and a one-star catastrophe. Downtime not only erodes customer trust but also costs businesses millions. This makes Chaos Engineering an essential discipline in today's tech landscape. But what exactly is Chaos Engineering? How does it benefit businesses, and how can it be practically implemented using tools like Steadybit? Let's delve in.

The holiday season is a high-stakes period for e-commerce businesses, with traffic and sales often surging to yearly highs. While this presents a significant revenue opportunity, it also puts your systems under immense strain. In this environment, preparing with Chaos Engineering is not just an advantage; it's a necessity. Here's why.

Scalability is a crucial concern for any engineering team. As your operations grow, so does the complexity of your systems. How can you ensure robustness and reliability during this vital phase? The answer is Chaos Engineering. This blog delves into why this methodology is a game-changer for engineering leaders guiding their teams through scale.

We're taking an exciting step into the world of open-source software. The code for Steadybit's Chaos Engineering attacks is now publicly available, offering a new level of transparency and collaboration. But what does this mean for developers and the broader community? Let's delve in.

Improving your system's reliability can be challenging. Initially, you are looking at a large pile of infrastructure components from a dozen teams. They are all somehow connected, and every piece will fail eventually. While you can use Chaos Engineering to reveal the impact of each failure, you can't predict when a failure will happen. This makes it hard to know where to start and where to continue to keep getting the most value from Chaos Engineering. Also, once you have identified the first findings with Chaos Engineering, you need to check what other components suffer from similar issues.

In our continuous journey to enhance user experience and eliminate bottlenecks, we proudly present our latest addition: Experiment Schedules. A feature designed with both simplicity and flexibility in mind, poised to revolutionize how you manage your experimental workflows.

We're super excited to share some insights from a recent episode of the SMC Journal podcast featuring none other than our co-founder and CEO, Benjamin Wilms. A deep dive into the realm of performance engineering, this episode unpacks the world of resilience testing, chaos engineering, and, of course, the role Steadybit is playing in all this. 

By utilizing Steadybit for Chaos Engineering, you not only improve the reliability of your system but also enhance your business's financial resilience and overall success.

In this blog post, we'll take a look at how your team can effectively incorporate Chaos Engineering principles into your organization using the Steadybit platform.

Discover the benefits of chaos engineering, a proactive approach to identifying weaknesses in software systems. By intentionally introducing controlled failures, developers gain valuable insights into system behavior and can implement measures to prevent catastrophic failures. Chaos engineering improves system resilience, helps identify vulnerabilities, and promotes continuous improvement. Embrace controlled failure and use chaos engineering as a powerful tool in building robust systems.

In our most recent webinar, Tailor Chaos Engineering to Scale Your Reliability Journey, our Product Manager Manuel Gerding, discussed how chaos engineering can enhance a system's reliability. The session featured riveting insights on ways to conduct chaos engineering more effortlessly, while demonstrating Steadybit's robust approach to this practice.

Learn how to integrate Chaos Engineering into your GitOps practices using Steadybit. We'll shortly cover in this blog post what GitOps is, followed by where you can benefit from integrating Chaos Engineering. Finally, we integrate Chaos Engineering hands-on using the Steadybit CLI and a GitHub action.

Why purple and blue are the new green and yellow: learn how colours have the power to influence our perceptions and emotions, and how the wrong colour can make or break a product. Let's channel our inner Bob Ross and paint some chaos together and see how this small change can make a big difference in the resilience of our systems.

A step-by-step guide to show how to use the AWS extension to inject failures into AWS Lambda Functions

This article demonstrates how to implement an attack to inject failures for AWS Lambda and integrate it into Steadybit.

This article demonstrates how to implement a discovery for AWS Lambda. This is a prerequisite to inject failures into those.

We have released our integration into Datadog recently. Within Datadog, the Steadybit integration is now available and can be installed. The integration includes a ready-to-go dashboard. Steadybit experiment events can also be inspected in the Datadog event views.

You can extend Steadybit to make it a perfect match for your systems. We already provide some OSS extensions. This article will give you an overview of the available extension points.

Chaos Engineering has been around for several years, and the practice has evolved. Within this post, we will look at past and modern interpretations, industry opinions and what we believe to be critical for you to leverage the practice to reach your goals.

The last blog post taught you how to set up a query language lexer and parser using ANTLR. This post will cover making this setup accessible in a user interface.

In this second part of the query language blog series, we look closely at the implementation of the lexer and parser.

This article will look closely at continuous verification with Steadybit through resilience testing and how it helped us internally.

When managing complex environments it's important to have powerful tools available to keep control. Now, Steadybit enhances the way how to filter targets by introducing the Query Language.

Steadybit wants to change the way outages are handled. Instead of reacting, Steadybit strives for a proactive approach integrated into the development cycle of modern applications.

Since we build software nowadays differently than a couple of years ago, performance testing alone isn't sufficient anymore. Learn how to profit from the synergy of performance testing and Chaos Engineering - a symbiosis of k6 and Steadybit.

If you are also wondering how to shift left Resilience and Chaos Engineering to Developers, you are reading the right article.

If you run chaos experiments, you certainly want to see how these experiments play out in your monitoring tools - even more so when you run experiments.

For this purpose, Steadybit has the possibility to connect various monitoring tools like New Relic, Datadog, Prometheus and Instana.

Is chaos engineering for experts only? No! Learn how we imagine opening up chaos and resilience engineering to wider audiences through declared and reusable expectations!

As you may agree, it is important to test your code. The resilience patterns implemented in your application are code (even if they're just a bunch of annotations). Often I saw that this is not tested thoroughly or not at all.

Do you have defined resource limits for your Kubernetes resources? We hope so! Learn in this post if they are correctly defined and Kubernetes does the expected things when they are reached.

Did you know that your applications can fail if your DNS fails? In this blog post, we explain the logic behind DNS and how you can experiment with DNS failures in Steadybit.

A GameDay is a collaborative exercise to help you as a team find weaknesses in your system in an exploratory space to improve resilience. We explain what you need to keep in mind.

Do you know resilience4j? You definitely should, if you like to build fault tolerant applications. This blog post is about the retry mechanism and how to check its functionality in real world.

If you run chaos experiments, you certainly want to see how these experiments play out in your monitoring tools; of course at the same time when you run your experiments. For this purpose, Steadybit can connect various monitoring tools. These include Instana, Prometheus, Datadog and New Relic. In this blog post, you learn how to set up the connection to New Relic.

In the last few years a lot has happened in the field of Chaos Engineering. From the originally radical new approach of intentionally causing errors and failures, a large community has emerged. The principles have been refined and the popularity of Chaos Engineering is growing.

In this blog post, we'll take a look at what Liveness Probes are for in the first place and how we can use steadybit to verify that they are working correctly.

October is Mental Health Awareness Month. WHO wants to raise awareness of mental health issues around the world and mobilize efforts in support of mental health. The day provides an opportunity for all stakeholders working on mental health issues to talk about their work, and what more needs to be done to make mental health visible. Speaking of mental health in the tech industry, especially in the environment of Chaos Engineering: What mental processes do we go through before tool decisions are made and Chaos Engineering processes can be successfully established? Let's look at Resilience Engineering on a human level: What do we need as a team to function well and build a Culture of Resilience? We think creating a healthy system and ensuring the health of the team requires looking at the people behind the code. That's why we asked Nora, founder and CEO of Jeli.io, who is focusing on the human factor in Chaos Engineering: What do companies need to change in the future so that teams can build a culture of resilience and sleep soundly at night?

Do you have sequential REST calls in your code? If so, how do they behave when the network is slow? Don't know yet? Let’s learn together and cover how easy we can improve our code using Spring WebFlux when fetching data from multiple independent REST endpoints.

If you run chaos experiments, you certainly want to see how these experiments play out in your monitoring tools – of course at the same time when you run the experiments. For this purpose steadybit has the possibility to connect various monitoring tools. These include Instana, New Relic, Datadog and Prometheus.

Have you ever asked yourself on how to measure the steady state of your system while doing Chaos Engineering. This blog post is a good starting point.

The real world is complicated - especially true for distributed systems. This pushed steadybit's experiment engine to their limits when trying to represent the real world (AKA production) in a very simple experiment. In this blog post, we'll unleash a firework of new experiment features that address these shortcomings - and are already loved by many of our users.

Everyone knows that the downtime of systems costs money and one would prefer to avoid it at all costs. Chaos Engineering is always mentioned as a possible solution. But is it really worth it? That's why we want to talk about numbers today.

One of the most fundamental advantages of Spring Boot is the paradigm of convention over configuration reducing the overhead heavily. Even so, there is a tiny pitfall in the default behavior of Spring Boot's RestTemplateBuilder that is probably not what you are really aiming for. So, be sure that you have configured it manually.

To build successful products, you can't get past user-centricity. Especially true for a product-based startup like steadybit. This blog post covers how we work at steadybit and how we put our users first. It tells our story from the founding vision to an amazing product to be used and why you can expect to see a shift in the product coming in the following months.

This blog post gives you an overview of the top 3 weak spots in Kubernetes and demonstrates an example to show how Chaos Engineering can be used to validate whether one's cluster can withstand turbulent conditions in practice.

This blog post gives you an effortless way to test whether your exception handling of Spring Boot's RestTemplate is working. In order to do so we leverage Chaos Engineering and this way can prevent the unattractive path of mocking a part of your system or cumbersome manual testing effort.

The use of cloud services, such as AWS, Azure or GCP, helps us to make software available to our customers in a short time. The resources can be used on demand and are often more cost-effective than hosting your own data center. But a cloud has some special characteristics that need to be considered. For example, individual components may be scaled dynamically and a single server may be replaced by a new server or similar.

In this post we will discuss why it is important to have application start fast and how you can validate this continuously.