Conf42 Chaos Engineering 2020
2020-01-23
London, United Kingdom
[Conf42 Chaos Engineering 2020, Conf42 Chaos Engineering 2021, Conf42 Chaos Engineering 2022, Conf42 Chaos Engineering 2024]
who it's for
site reliability engineers, platform engineers, devops engineers, engineering managers, JVM developers, database administrators, QA engineers
topics
Chaos Toolkit automated experiments; Litmus Kubernetes chaos; Chaos Mesh integration; Chaos Monkey for Spring Boot; JVM bytecode fault injection; resilience maturity model; postmortem culture and runbooks; SQL Server availability testing; Kubernetes pod failure injection; game days and failure drills; observability for chaos experiments
| title | author | length |
|---|---|---|
| How to be WRONG | Russ Miles | 01h 00m |
Claims that being wrong is inevitable and useful, and that chaos engineering should be repackaged as system verification with measurable objectives (for… | ||
| Chaos Monkey for Spring Boot | John Fletcher, Manuel Wessner | 30m |
Adds a single dependency to a Spring Boot app, uses Actuator to enable/disable attacks at runtime, and configures service/repository watchers to inject latency… | ||
| Application-Level Chaos Engineering in JVM | Long Zhang | 24m |
A research toolset instruments JVM bytecode with a Java agent to inject exceptions and measure real production behavior: ChaosMachine throws exceptions at the… | ||
| Journey to Resilience | Vilas Veeraraghavan | 25m |
Walmart measures scale (11,000 stores, >$500B revenue, ~70M weekly Omni transactions) and builds a program that moves teams from ad hoc outages to repeatable… | ||
| Who is responsible for Chaos? | Joyce Lin | 10m |
Most chaos programs originate with people who get paged in production: SREs and Ops or anyone with deployment and uptime responsibility; job titles with… | ||
| Post Mortem Culture: Learning from Failure | Yury Yineth Niño Roa | 20m |
Survey of 45 engineers shows only 40% read postmortems and 60% don't practice them. Chaos Game Days run with a master of disaster, a first-on-call, and the… | ||
| Shipping Quality Software in Hostile Environments | Luka Kladaric | 23m |
After eight years of features-only development the codebase reaches tech bankruptcy with a 10GB monorepo that stalls work and a deploy pipeline where a single… | ||
| Chaos Engineering for SQL Server | Andrew Pruski | 30m |
Demonstrates chaos experiments against a two-node Always On setup by stopping the database engine service and using PowerShell/Pester and T‑SQL to assert an… | ||
| Getting out of the Starting Blocks | Adrian Hornsby | 44m |
Argues that adoption fails because title and culture misframe the work and because teams lack mechanisms — tool, adoption path, audit — not motivation… | ||
| Cloud Native Chaos Engineering | Uma Mukkara | 28m |
A concrete cloud-native chaos stack called Litmus exists and goes GA 1.0, implemented as Kubernetes CRDs: ChaosExperiment, ChaosEngine, ChaosResult, with an… | ||
| Psychology of Chaos Engineering | Matt Stratton | 26m |
Chaos engineering is used to train teams as well as systems: companies run daytime experiments like Failure Fridays and Netflix’s lunchtime chaos to practice… | ||
| nothing matches | ||