16 FEBRUARY, 18.00 (CET) – Online
Conference Website
Reliability in the Face of Uncertainty
Today’s success of businesses depends on their systems’ stability and reliability. Downtimes are painful: They cause you to lose the trust of your customers and cost your business money. Providing reliable services to your customers is essential to success. Despite the best efforts, the one sure thing about undesirable events like outages is that they will always occur, but the moment chooses you.
Waiting and hoping an outage will not occur is not a strategy. Benjamin will show you how to proactively deal with today’s conditions to improve your reliability and keep your customers happy.
Take a look for yourself:
Youtube content is not loaded per default for privacy reasons.
1.
Designing Chaos Engineering experiments using the drag-and-drop editor is easy. You don’t need to remember command-line interfaces, multiple tools or YAML schemas.
Before running the experiment, use the live target preview to verify that you will hit the intended targets.
2.
Chaos Engineering is an inherently explorative method. Change the parameters of your experiments on the fly and immediately react to insights you got during Chaos Engineering workshops.
Whether you want to increase the blast radius, target a different piece of infrastructure or introduce new steps, everything is at your fingertips in the visual experiment designer.
3.
With the real-time view of the experiment run, you always know what is happening anytime. Stay informed with the live event log.
Dedicated widgets visualize all metrics and checks configured inside the experiment designer, making it easy to spot any unexpected system behavior. You can always review the timeline later on and also analyze all the data from the dashboard.
4.
To apply a baseline of Chaos Experiments to an entire organization, codify your knowledge base using our Resilience Policies, ready-to-use best practices. Resilience Policies define a set of Chaos Experiments and configuration best practices you can enforce for your system components.
Get an overview to which extent those policies are met. The UI provides you full details on the current state. And using our CLI, you can easily integrate those into your CI/CD pipelines.
5.
Limit where teams can break havoc.
With Steadybit, you can precisely define the environments a team can operate on and narrow down the infrastructure they can break. If you think some attacks are too invasive, restrict access to them.
