JAN 23 2020
HOW TO BE WRONG
KEYNOTE BY RUSS MILES
CEO @ CHAOSIQ
Being wrong is often seen as the WORST THING THAT CAN HAPPEN(tm), especially when you’re build business-critical applications and services. But the increased velocity of modern software development, plus the increased need for our systems to be resilient, reliable, and RIGHT has increased the pressure on developers exponentially. Never before have software owners had such an opportunity, or the power, to BE WRONG!
CHAOS MONKEY FOR SPRING BOOT
TALK BY JOHN FLETCHER AND MANUEL WESSNER,
CHAOS MONKEY EVANGELISTS
Everything you want to know about the useful and popular chaos engineering tool Chaos Monkey for Spring Boot (CMSB) from two of its maintainers.
- How to easily get started with your first Chaos Experiments.
- More exotic applications like dual attacks.
- How to integrate CMSB with automation tools like Chaos Toolkit and Chaos Mesh in order to run tests in your build chain.
- An overview of the history and the changes in the latest version.
- Who should get involved in the project, and how.
- A sneak peek into the next release.
APPLICATION LEVEL CHAOS ENGINEERING IN JVM
TALK BY LONG ZHANG
PHD STUDENT IN COMPUTER SCIENCE
@ KTH ROYAL INSTITUTE OF TECHNOLOGY
During the talk, I will introduce the main research work we did recently on chaos engineering. We focus a lot on application-level chaos engineering in JVM.
For example, ChaosMachine provides unique and actionable analysis on exception-handling capabilities in production, at the level of try-catch blocks. TripleAgent combines monitoring, perturbation, and failure-obliviousness for automated resilience improvement, at the level of methods.
JOURNEY TO RESILIENCE: BUILDING THE RAMP TO ACCELERATE THE ADOPTION OF CHAOS ENGINEERING PRACTICES
A TALK BY VILAS VERARAGHAVAN
DIRECTOR OF ENGINEERING @ WALMART LABS
Chaos engineering has come a long way from its early days at Netflix. Its importance is no longer questioned in the community but as it has gone mainstream, teams quickly learn that adoption is not a given. In this talk, we talk about the challenges that we encountered at Walmart and the techniques used to break through them.
WHO IS RESPONSIBLE FOR CHAOS?
A TALK BY JOYCE LIN
DEVELOPER ADVOCATE LEAD @ POSTMAN
If you’re thinking of starting a chaos program, you might be wondering which job functions are typically responsible for managing chaos within their organizations.
This talk will look across a number of companies to determine who historically initiates chaos programs, as well as reveal new trends in this space.
LEARNING FROM FAILURE
A TALK BY YURY NIÑO ROA
DEVOPS ENGINEER @ AVAL DIGITAL LABS
Practicing Chaos Engineering and reproducing outages have taught us that the culture of postmortems must be open and blameless. That is difficult, in part, due to the social stigma associated with publicly acknowledging the contributions of persons to outages.
SHIPPING QUALITY SOFTWARE
IN HOSTILE ENVIRONMENTS
A TALK BY LUKA KLADARIC
FOUNDER & CHAOS MANAGEMENT SPECIALIST @ SEKURA
Everyone loves features, right? Product loves features. Management loves features. The board loves features. Features are what make the users use and the investors invest, right? They certainly make the media pay attention.
CHAOS ENGINEERING FOR SQL SERVER
A TALK BY ANDREW PRUSKI
SQL SERVER DBA @ CHANNEL ADVISOR
In this session we’ll look at how Chaos Engineering can be implemented with regard to SQL Server. SQL has various different high availability solutions but can we be sure that they’ll react as expected to a real-world issue? Has the HA architecture only ever been tested in a planned maintenance window?
GETTING OUT OF THE STARTING BLOCKS
A TALK BY ADRIAN HORNSBY
PRINCIPAL TECHNOLOGIST, ARCHITECTURE
@ AMAZON WEB SERVICES (AWS)
Architectures are growing increasingly distributed and hard to understand. As a result, software systems have become extremely difficult to debug and test, which increases the risk of failure. With these new challenges, chaos engineering has become attractive to many organizations as a mechanism for underling the behaviour of systems under expected circumstances.
CLOUD-NATIVE CHAOS ENGINEERING
A TALK BY UMASANKAR MUKKARA
CO-FOUNDER AND COO @ MAYADATA
In Cloud-Native Chaos engineering, the developers develop chaos tests as an extension of the development process. These tests are developed using standard Kubernetes Custom Resources or CRs so that they are easier to manipulate according to the environment.
OF CHAOS ENGINEERING
KEYNOTE BY MATTY STRATTON
DEVOPS ADVOCATE @ PAGERDUTY