2. InfoQ.com: News & Community Site
• 750,000 unique visitors/month
• Published in 4 languages (English, Chinese, Japanese and Brazilian
Portuguese)
• Post content from our QCon conferences
• News 15-20 / week
• Articles 3-4 / week
• Presentations (videos) 12-15 / week
• Interviews 2-3 / week
• Books 1 / month
Watch the video with slide
synchronization on InfoQ.com!
https://www.infoq.com/presentations/
adopt-chaos-engineering

3. Presented at QCon New York
www.qconnewyork.com
Purpose of QCon
- to empower software development by facilitating the spread of
knowledge and innovation
Strategy
- practitioner-driven conference designed for YOU: influencers of
change and innovation in your teams
- speakers and topics driving the evolution and innovation
- connecting and catalyzing the influencers and innovators
Highlights
- attended by more than 12,000 delegates since 2007
- held in 9 cities worldwide

4. In this talk
●
●
●
●
@nora_js

5. In this talk
●
●
●
●
@nora_js

6. Known ways of testing for
availability
●
●
●
●

9. You can’t keep blaming your cloud
provider
@nora_js

10. Why is there a fear of Chaos when it’s
inevitable?

12. Meet “Chaos Carol”

13. Where is Carol starting her Chaos?

15. Start with a steady state
●
●
@nora_js

17. There isn’t always money in microservices

18. Randomly turn things
off?
Recreate things that
already happened?

20. Let people know?
Let the Chaos run
automatically?

25. Socialization
●
●
●

30. ● Focus more on asking the questions, rather than
answering them.
● Find customers willing to try first. Then share their stories.
● Be honest. Don’t make false promises about what Chaos
will do.

33. ●
●
●
●

56. ChAP
●
●
●
●
@nora_js

62. Targeted Chaos: Kafka Problems
●
●
●
@nora_js

63. Targeted Chaos: Kafka Ideas
●
●
●
●
●
●
@nora_js

66. @nora_js
“We ran a chaos experiment which
verifies that our fallback path works
(crucial for our availability) and it
successfully caught a issue in the
fallback path and the issue was
resolved before it resulted in any
availability incident!”

67. “While [failing calls] we discovered an increase in
license requests for the experiment cluster even
though fallbacks were all successful. This likely
means that whoever was consuming the fallback
was retrying the call, causing an increase in
license requests.”
@nora_js

68. ●
●
●
@nora_js

69. Should you develop
experiments for the
service teams?
Let them do it on their
own?

70. Takeaways
●
●
●
@nora_js

72. Watch the video with slide
synchronization on InfoQ.com!
https://www.infoq.com/presentations/
adopt-chaos-engineering