This introductory slidedeck talks about the challenge of modern production systems under the pressure of increased feature velocity and change, and at the same time needing to be more business critical and reliable than ever.

1. Production Microservices
Russ Miles
CEO, ChaosIQ.io

2. TBD
@russmiles

11. The Collective.

12. A History of Chaos
Engineering…

13. 2010
The Netflix Eng Tools team created Chaos Monkey. Chaos
Monkey was created in response to Netflix’s move from
physical infrastructure to cloud infrastructure provided by
Amazon Web Services, and the need to be sure that a loss
of an Amazon instance wouldn’t affect the Netflix
streaming experience.
https://www.gremlin.com/community/tutorials/chaos-engineering-the-history-principles-and-practice/

14. An Alternative…

15. https://www.wired.com/2015/10/margaret-hamilton-nasa-apollo/

17. “she caused a “mission” to crash by selecting
the DSKY keys in an unexpected way, alerting
the team as to what would happen if the
prelaunch program, P01, were inadvertently
selected by a real astronaut during a real
mission, during real midcourse.”
Murphy, Niall Richard; Beyer, Betsy; Jones,
Chris; Petoff, Jennifer. Site Reliability
Engineering: How Google Runs Production
Systems . O'Reilly Media. Kindle Edition.

19. $2…

20. “Reliability”

21. So what’s the problem?

22. “Production Hates You.”

23. “We Hate Us Too.”

24. Expectations have Grown

26. You are here

27. Distributed Systems?
External Dependencies?

28. You are here

29. Building cloud native
microservices…

30. … that evolve quickly …

31. (Which was the point)

32. You are here!

33. Attack Vectors on
“Reliability”

34. Infrastructure

35. Infrastructure
Platform

36. Infrastructure
Platform
Applications

37. Infrastructure
Platform
Applications
People, Practices & Process

38. TBD
Wouldn’t it be
great if there was a
proactive practice for
exploring and diminishing
system weaknesses
before they affected
users?
Probably a pipe
dream…

39. Chaos Engineering

40. A mindset,
a process,
some ethics
some practices,
and some tools,
a minimum bar

41. The Chaos Engineering
Mindset

42. "never let an outage go
to waste" -
@caseyrosenthal

43. “Chaos Engineering allows us to have
‘pre-mortems’ instead of post-mortems.”
- Michael Barrett, Head of Infrastructure
Engineering, Remind

44. The Chaos Engineering
Process

45. 1. Form a hypothesis.
2. Communicate to your team.
3. Run experiments.
4. Analyze the results.
5. Increase the scope.
6. Automate experiments.
https://blog.codeship.com/embracing-the-chaos-of-chaos-engineering/

46. The Chaos Engineering
Ethics

47. “Skin in the game”

48. Two Key Practices

49. Game Days Chaos Experiments
Automate

50. How do non-technical
folks react???

51. Drop the term!

52. Talk Production
Incidents

53. Rules of
Chaos “Club”

54. Rule 1:
Don’t talk about Chaos
Club…
ChaosIQ.io

55. Rule 2:
It’s about “Learning”
ChaosIQ.io

56. Rule 3:
Chaos is not a surprise
ChaosIQ.io

57. Rule 4:
ChaosIQ.io
If you know the
consequences, don’t do
the experiment

58. See you on the road!
(Ride Safe)
Russ Miles
CEO, ChaosIQ.io
@russmiles
Blog: www.russmiles.com