How to be Wrong (or How to be Successful at Being Wrong)

•

2 gefällt mir•742 views

In this talk Russ Miles, CEO at ChaosIQ, explores how to turn "Being Wrong" into a super-power through establishing a Resilience Engineering Capability that practices Chaos Engineering.

Technologie

How to be Wrong
or … “How to be Great at Being Wrong”
Russ Miles - @russmiles

Russ Miles
CEO, co-founder
Your Host Today
Sylvain Hellegouarch
CTO, co-founder
ChaosIQ

“To support our users in establishing
their own  
Resilience Engineering Capability”

…“action or conduct inﬂicting harm
without due provocation or just
cause”

“a violation or invasion of the legal
rights of another”

“the state of being mistaken or
incorrect”

What about tests? gates? pipelines?
isolation?

“One Hour of Downtime Costs >
$100K For 95% of Enterprises”
http://itic-corp.com/blog/2013/07/one-hour-of-downtime-costs-100k-for-95-of-enterprises/

“lost revenue and lost end user
productivity"
http://itic-corp.com/blog/2013/07/one-hour-of-downtime-costs-100k-for-95-of-enterprises/

“not take into account the cost of additional penalties for
regulatory non-compliance or “good will” gestures made
to the organization’s customers and business partners that
were negatively impacted by a system or network failure. In
fact, these two conditions can cause downtime costs to
skyrocket even further”
http://itic-corp.com/blog/2013/07/one-hour-of-downtime-costs-100k-for-95-of-enterprises/

Microservices-based systems tend to
look like…

“To be fully described, there are many
details, not few”
John Allspaw: https://queue.acm.org/detail.cfm?id=2353017

“The rate of change is high; the
systems change before a full
description (and therefore
understanding) can be completed.”
John Allspaw: https://queue.acm.org/detail.cfm?id=2353017

“How components function is partly
unknown, as they resonate with each
other across varying conditions.”
John Allspaw: https://queue.acm.org/detail.cfm?id=2353017

“Processes are heterogeneous and
possibly irregular.”
John Allspaw: https://queue.acm.org/detail.cfm?id=2353017

“prepare for undesirable
circumstances” - John Allspaw

Deliberately Practice
Being Wrong
=
Chaos Engineering

Outage
Detection
Diagnosis
Fix
“Normal”
Learning

Outage
Detection
Diagnosis
FixImprovement
(Robustness)
“Normal”
Learning

“Never Let an Outage Go To Waste” -
Casey Rosenthal

“Chaos Engineering is the discipline of
experimenting on a distributed system 
in order to build conﬁdence in the system’s
capability to withstand turbulent conditions in
production.”
- principlesofchaos.org

Game Day /
Automated Chaos Experiment
“Normal”

Game Day /
Automated Chaos Experiment
Detection
Diagnosis
Fix
“Normal”

Game Day /
Automated Chaos Experiment
Detection
Diagnosis
FixImprovement
(Robustness)
“Normal”
Learning

Chaos
Infrastructure
Platform
Applications
People, Practices & Process
Game Days
Automated 
Experiments
Automated 
Experiments
Automated 
Experiments

We can learn after outages…
but it’s even better to  
learn from weaknesses before an outage.

Being Wrong can be a super power, if
it leads to learning

Establish a Platform for  
Pre-mortem, Deliberate Practice
“Being Wrong”

Establish a Platform for  
Pre-mortem, Deliberate Practice
“Chaos Engineering”

Automate Chaos Experiments
Chaos Engineering
Control Plane

Later on today…
Sylvain Hellegouarch
CTO, co-founder
+

Start a conversation…
ChaosIQ
www.chaosplatform.com
contact@chaosiq.io
O’Reilly Safari Online Courses Available
Upcoming Conferences
DevOpsCon Munich KubeCon Seattle
O’Reilly Book on 
“Chaos Engineering”  
Coming Soon!
https://www.chaostoolkit.org
Slack: https://join.chaostoolkit.org

Weitere ähnliche Inhalte

Ähnlich wie How to be Wrong (or How to be Successful at Being Wrong)

Security incident response is a reactive and chaotic exercise. What if it were possible to flip the scenario on its head? Security focused chaos engineering takes the approach of advancing the security incident response apparatus by reversing the postmortem and preparation phases. Contrary to Purple Team or Red Team game days, Security Chaos Engineering does not use threat actor tactics, techniques and procedures. It develops teams through unique configuration, cyber threat and user error scenarios that challenge responders to react to events outside their playbooks and comfort zones. Security Chaos Engineering allows incident response and product teams to derive new information about the state of security within their distributed systems that was previously unknown. Within this new paradigm of instrumentation where we proactively conduct “Pre-Incident” vs. “Post-Incident” reviews we are now able to more accurately measure how effective our security incident response teams, tools, skills, and procedures are during the manic of the Incident Response function. In this session Aaron Rinehart, the mind behind the first Open Source Security Chaos Engineering tool ChaoSlingr, will introduce how Security Chaos Engineering can be applied to create highly secure, performant, and resilient distributed systems.

Craft 2019 - Security Chaos Engineering - Security Precognition

Aaron Rinehart

The software has bugs. The systems sometimes fail. People make mistakes. These are fundamental truths of technology. Hiring the best engineers in the world won’t change this. The best-performing teams and companies build reliable software despite bugs and mistakes. These “unicorn” companies are pushing the boundaries of software reliability through chaos engineering and by embracing resilience engineering. They hire the best and brightest systems engineers to work alongside their software developers to build more reliable systems. But do companies that aren’t unicorns need to become experts in human factors and experts in their software stack in order to engineer reliable systems? Jessica DeVita tells the story of how a team at Microsoft challenged themselves to retrospect their retrospectives and shares what they learned about applying human factors ideas to software development. You’ll learn how a nonexpert can contribute to software robustness and resilience, gain ideas on how to approach an unfamiliar software engineering system, and discover how to investigate the roles that language, accountability, error propagation, and hidden system resilience play in a software engineering system.

Retrospecting our Retrospectives

Jessica DeVita

Large scale distributed systems have unpredictable and complex outcomes that are costly when security incidents occur. Security incident response today is mostly a reactive and chaotic exercise. Chaos engineering allows security incident response teams to proactively experiment on recurring incident patterns to derive new information about underlying factors that were previously unknown. What if you could flip that scenario on its head? Chaos engineering advances the security incident response framework by reversing the postmortem and preparation phase. This is done by developing live fire exercises that can be measured and managed. Contrary to red team game days, chaos engineering doesn’t use threat actor tactics, techniques, and procedures. Instead it develops teams through unique configuration, cyberthreat, and user error scenarios that challenge responders to react to events outside their playbooks and comfort zones. Join Aaron Rinehart to explore the hidden costs of security incidents, learn a new technique for uncovering system weaknesses in systems security, and more. You’ll also get a glimpse of ChaoSlingr, an open source security chaos engineering tool built and deployed within a Fortune 5 company. Aaron explains how the tool helped his team discover that many of their security controls didn’t function as intended and how, as a result, they were able to proactively improve them before they caused any real problems.

Velocity 2019 - Security Precognition 2019 Slides - San Jose 2019

Aaron Rinehart

It doesn’t matter how beautiful, loosely coupled, scalable, highly concurrent, non-blocking, responsive and performant your application is—if it isn't running, then it's 100% useless. Without resilience, nothing else matters. Most developers understand what the word resilience means, at least superficially, but way too many lack a deeper understanding of what it really means in the context of the system that they are working on now. I find it really sad to see, since understanding and managing failure is more important today than ever. Outages are incredibly costly—for many definitions of cost—and can sometimes take down whole businesses. In this talk we will explore the essence of resilience. What does it really mean? What is its mechanics and characterizing traits? How do other sciences and industries manage it, and what can we learn from that? We will see that everything hints at the same conclusion; that failure is inevitable and needs to be embraced, and that resilience is by design.

Without Resilience, Nothing Else Matters

Jonas Bonér

Allianz Global CISO october-2015-draft

Eoin Keary

Distributed systems, microservices, containers and schedulers, polyglot persistence .. modern infrastructure patterns are fluid and dynamic, chaotic and transient. So why are we still using LAMP-stack era tools to debug and monitor them? We'll cover some of the many shortcomings of traditional metrics and logs (and APM tools backed by metrics or logs), and show how complexity is their kryptonite. So how do we handle the coming complexity Armageddon? What are the implications for teams and roles and the way we build and ship software? Let's talk about the industry-wide shifts underway from metrics to events, from monitoring to observability, and from caring about the system as whole to the health of each and every request.

Observability for Emerging Infra (what got you here won't get you there)

Charity Majors

CAST 2014 New York: The Art and Science of Testing The Association for Software Testing www.associationforsoftwaretesting.org COURSE DESCRIPTION Automated tools provide test professionals with the capability to make relevant observations even in the fastest-paced environments. Automated testing is also a powerful tool for improving communication between software engineers. This is important because good communication is a prerequisite for growing a great software engineering organization. This workshop will explore the continuous testing of software systems. Special focus will be given to the situation where the engineering team is deploying code to production so frequently that it is not possible to perform deep regression testing before each release. People who participate in this course will learn pragmatic automated testing strategies like: * Data analysis on the command line with find, grep and wc. * Network analysis with Chrome Inspector, Charles and netcat. * Using code churn to predict hotspots where bugs may occur. * Putting stack traces in context with automated SCM blame emails. * Using statsd to instrument a whole application. * Testing in production. * Monitoring-as-testing. Technical level: participants should have some familiarity with the command line and with editing code using a text editor or IDE. Familiarity with Git, SVN or another version control system is helpful but not required. Likewise some knowledge of Web servers is helpful but not required. It is desirable for participants to bring laptops. BIO From 2010 to 2012 Noah was a Test Architect at Etsy. He helped build Etsy's continuous integration system, and has helped countless other engineers develop successful automated testing strategies.These days Noah is an independent consultant in New York. He is passionate about helping engineers understand and use automated tools as they work to scale their applications more effectively.

Continuous Automated Testing - Cast conference workshop august 2014

Noah Sussman

NTXISSACSC3 - 7 Security Mindsets to Adopt Today by Ted Gruenloh

North Texas Chapter of the ISSA

Blameless Retrospectives in DevSecOps (at Global Healthcare Giants)

DJ Schleen

R af d

William L. McGill

Risk Analysis for Dummies

William L. McGill

Mistakes and failure are inevitable. Instead of being afraid of them, we should use them as lessons that help identify weak points in our organisations and systems. One way to do this is by writing blameless postmortems. Daniel details exactly how postmortems can help organizations and teams focus on improvement, and how that boosts work morale, makes products better, and strengthens your relationship with customers.

More Aim, Less Blame: How to use postmortems to turn failures into something ...

Daniel Kanchev

Accident Investigations - Blame and Shame or Listen and Learn?

SAMTRAC International

AI for Finance

Dr. Kim (Kyllesbech Larsen)

Primer for Information Security Programs

Richard Greenberg, CISSP

do you see what I see?

Andrew Shafer

As devops practitioners we focus on improving the culture of collaboration so that others play nicely with us & we play nicely with others - but what if the biggest thing holding us back from change is our own brains? Cognitive biases can deeply affect our behaviours towards others by herding us towards mental shortcuts that are optimised for timeliness over accuracy, at the expense of rationalising irrational behaviour. You are probably pushing these biases onto other people every day but don't even know it. Does that idea make you feel unconfortable? You are probably experiencing the Semmelweis reflex kicking your confirmation bias right now. Knowing is half the battle. This talk will delve into some of the well-known and less well-known biases that may be affecting your ability to work with your peers, and your team's ability to work constructively with other teams. Attendees will leave the talk with an overview of biases they run into every day, how to hack their brains to use these biases to their advantage, and some tips on how to mitigate the effects of the limitations baked into their wetware. We have met the enemy and he is us. Speaker: Lindsay Holmwood Lindsay Holmwood is a engineering manager living in the Australian Blue Mountains. He is the creator of Visage & cucumber-nagios, and organises the Sydney DevOps Meetup. He runs a distributed infracoders team at Bulletproof Networks, that builds hassle free tools, and was responsible for ensuring 100% uptime for the 2010 + 2011 + 2012 Movember campaigns. In his spare time, Lindsay organises the monthly Sydney DevOps Meetups. He also won third place at the 1996 Sydney Royal Easter Show LEGO building competition.

DevOps Days Tel Aviv 2013: The DevOps field guide to cognitive biases - Linds...

DevOpsDays Tel Aviv

DevOps Connect: Josh Corman and Gene Kim discuss DevOpsSec

Sonatype

How to Secure America

SecurityStudio

The agile manifesto says directly that "We are uncovering better ways of developing software by doing it and helping others do it." If this continual improvement is true, what new topics are currently being discussed and talked about at agile conferences? What are teams across the world struggling and experimenting with? What topics are the most heated? In this session, I'll give an overview of some of the new and hot agile topics.

Trends in Agile Software

Steve Rogalsky

Ähnlich wie How to be Wrong (or How to be Successful at Being Wrong) (20)

Craft 2019 - Security Chaos Engineering - Security Precognition

Retrospecting our Retrospectives

Velocity 2019 - Security Precognition 2019 Slides - San Jose 2019

Without Resilience, Nothing Else Matters

Allianz Global CISO october-2015-draft

Observability for Emerging Infra (what got you here won't get you there)

Continuous Automated Testing - Cast conference workshop august 2014

NTXISSACSC3 - 7 Security Mindsets to Adopt Today by Ted Gruenloh

Blameless Retrospectives in DevSecOps (at Global Healthcare Giants)

R af d

Risk Analysis for Dummies

More Aim, Less Blame: How to use postmortems to turn failures into something ...

Accident Investigations - Blame and Shame or Listen and Learn?

AI for Finance

Primer for Information Security Programs

do you see what I see?

DevOps Days Tel Aviv 2013: The DevOps field guide to cognitive biases - Linds...

DevOps Connect: Josh Corman and Gene Kim discuss DevOpsSec

How to Secure America

Trends in Agile Software

Mehr von Russell Miles

Don't be a victim of your own success: Using Service Levels to give a Consist...

Russell Miles

Service Level Objectives and SRE: Service Level Overkill with Mick Roper

Russell Miles

From Chaos to Verification at Expedia Group, London

Russell Miles

Break stuff - Confessions of a misguided chaos engineer

Russell Miles

Trust and Confidence through Chaos Keynote for W-JAX Munich 2018

Russell Miles

Production Microservices @ Jazoon

Russell Miles

Chaos Engineering 101 by Russ Miles

Russell Miles

Machine Learning is coming out of the halls of Academia and straight into the arms of those businesses looking for a competitive edge. This session by the experts of GoDataScience.io on machine learning is designed to give a high level overview of the field of machine learning for business consumers covering: - What Machine Learning is - Where it came from - Why we need it - Why now - How to make it real with the various toolkits and processes.

Applying Machine Learning and Artificial Intelligence to Business

Russell Miles

The Future of Machine Learning

Russell Miles

Mehr von Russell Miles (9)

Don't be a victim of your own success: Using Service Levels to give a Consist...

Service Level Objectives and SRE: Service Level Overkill with Mick Roper

From Chaos to Verification at Expedia Group, London

Break stuff - Confessions of a misguided chaos engineer

Trust and Confidence through Chaos Keynote for W-JAX Munich 2018

Production Microservices @ Jazoon

Chaos Engineering 101 by Russ Miles

Applying Machine Learning and Artificial Intelligence to Business

The Future of Machine Learning

Kürzlich hochgeladen

ICT role in 21st century education and its challenges

rafiqahmad00786416

presentation ICT roal in 21st century education

jfdjdjcjdnsjd

Polkadot JAM Slides - Token2049 - By Dr. Gavin Wood

Juan lago vázquez

Axa Assurance Maroc - Insurer Innovation Award 2024

The Digital Insurer

AWS Community Day CPH - Three problems of Terraform

Andrey Devyatkin

2024: Domino Containers - The Next Step. News from the Domino Container commu...

Martijn de Jong

Strategies for Landing an Oracle DBA Job as a Fresher

Remote DBA Services

The Good, the Bad and the Governed - Why is governance a dirty word? David O'Neill, Chief Operating Officer - APIContext Apidays New York 2024: The API Economy in the AI Era (April 30 & May 1, 2024) ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/

Apidays New York 2024 - The Good, the Bad and the Governed by David O'Neill, ...

apidays

Architecting Cloud Native Applications

WSO2

AXA XL - Insurer Innovation Award Americas 2024

The Digital Insurer

Join our latest Connector Corner webinar to discover how UiPath Integration Service revolutionizes API-centric automation in a 'Quote to Cash' process—and how that automation empowers businesses to accelerate revenue generation. A comprehensive demo will explore connecting systems, GenAI, and people, through powerful pre-built connectors designed to speed process cycle times. Speakers: James Dickson, Senior Software Engineer Charlie Greenberg, Host, Product Marketing Manager

Connector Corner: Accelerate revenue generation using UiPath API-centric busi...

DianaGray10

Webinar Recording: https://www.panagenda.com/webinars/why-teams-call-analytics-is-critical-to-your-entire-business Nothing is as frustrating and noticeable as being in an important call and being unable to see or hear the other person. Not surprising then, that issues with Teams calls are among the most common problems users call their helpdesk for. Having in depth insight into everything relevant going on at the user’s device, local network, ISP and Microsoft itself during the call is crucial for good Microsoft Teams Call quality support. To ensure a quick and adequate solution and to ensure your users get the most out of their Microsoft 365. But did you know that ‘bad calls’ are also an excellent indicator of other problems arising? Precisely because it is so noticeable!? Like the canary in the mine, bad calls can be early indicators of problems. Problems that might otherwise not have been noticed for a while but can have a big impact on productivity and satisfaction. Join this session by Christoph Adler to learn how true Microsoft Teams call quality analytics helped other organizations troubleshoot bad calls and identify and fix problems that impacted Teams calls or the use of Microsoft365 in general. See what it can do to keep your users happy and productive! In this session we will cover - Why CQD data alone is not enough to troubleshoot call problems - The importance of attributing call problems to the right call participant - What call quality analytics can do to help you quickly find, fix-, and prevent problems - Why having retrospective detailed insights matters - Real life examples of how others have used Microsoft Teams call quality monitoring to problem shoot problems with their ISP, network, device health and more.

Why Teams call analytics are critical to your entire business

panagenda

Manulife - Insurer Transformation Award 2024

The Digital Insurer

Dubai, often portrayed as a shimmering oasis in the desert, faces its own set of challenges, including the occasional threat of flooding. Despite its reputation for opulence and modernity, the emirate is not immune to the forces of nature. In recent years, Dubai has experienced sporadic but significant floods, testing the resilience of its infrastructure and communities. Among the critical lifelines in this bustling metropolis is the Dubai International Airport, a bustling hub that connects the city to the world. This article explores the intersection of Dubai flood events and the resilience demonstrated by the Dubai International Airport in the face of such challenges.

Navigating the Deluge_ Dubai Floods and the Resilience of Dubai International...

Orbitshub

Exploring Multimodal Embeddings with Milvus

Zilliz

Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows. We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases. This video focuses on the deployment of external web forms using Jotform for Bonterra Impact Management. This solution can be customized to your organization’s needs and deployed to support the common use cases below: - Intake and consent - Assessments - Surveys - Applications - Program registration Interested in deploying web form automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.

Web Form Automation for Bonterra Impact Management (fka Social Solutions Apri...

Jeffrey Haguewood

EMPOWERMENT TECHNOLOGY GRADE 11 QUARTER 2 REVIEWER

MadyBayot

The microservices honeymoon is over. When starting a new project or revamping a legacy monolith, teams started looking for alternatives to microservices. The Modular Monolith, or 'Modulith', is an architecture that reaps the benefits of (vertical) functional decoupling without the high costs associated with separate deployments. This talk will delve into the advantages and challenges of this progressive architecture, beginning with exploring the concept of a 'module', its internal structure, public API, and inter-module communication patterns. Supported by spring-modulith, the talk provides practical guidance on addressing the main challenges of a Modultith Architecture: finding and guarding module boundaries, data decoupling, and integration module-testing. You should not miss this talk if you are a software architect or tech lead seeking practical, scalable solutions. About the author With two decades of experience, Victor is a Java Champion working as a trainer for top companies in Europe. Five thousands developers in 120 companies attended his workshops, so he gets to debate every week the challenges that various projects struggle with. In return, Victor summarizes key points from these workshops in conference talks and online meetups for the European Software Crafters, the world’s largest developer community around architecture, refactoring, and testing. Discover how Victor can help you on victorrentea.ro : company training catalog, consultancy and YouTube playlists.

Modular Monolith - a Practical Alternative to Microservices @ Devoxx UK 2024

Victor Rentea

Emergent Methods: Multi-lingual narrative tracking in the news - real-time ex...

Zilliz

[BuildWithAI] Introduction to Gemini.pdf

Sandro Moreira

Kürzlich hochgeladen (20)

ICT role in 21st century education and its challenges

presentation ICT roal in 21st century education

Polkadot JAM Slides - Token2049 - By Dr. Gavin Wood

Axa Assurance Maroc - Insurer Innovation Award 2024

AWS Community Day CPH - Three problems of Terraform

2024: Domino Containers - The Next Step. News from the Domino Container commu...

Strategies for Landing an Oracle DBA Job as a Fresher

Apidays New York 2024 - The Good, the Bad and the Governed by David O'Neill, ...

Architecting Cloud Native Applications

AXA XL - Insurer Innovation Award Americas 2024

Connector Corner: Accelerate revenue generation using UiPath API-centric busi...

Why Teams call analytics are critical to your entire business

Manulife - Insurer Transformation Award 2024

Navigating the Deluge_ Dubai Floods and the Resilience of Dubai International...

Exploring Multimodal Embeddings with Milvus

Web Form Automation for Bonterra Impact Management (fka Social Solutions Apri...

EMPOWERMENT TECHNOLOGY GRADE 11 QUARTER 2 REVIEWER

Modular Monolith - a Practical Alternative to Microservices @ Devoxx UK 2024

Emergent Methods: Multi-lingual narrative tracking in the news - real-time ex...

[BuildWithAI] Introduction to Gemini.pdf

How to be Wrong (or How to be Successful at Being Wrong)

1. How to be Wrong or … “How to be Great at Being Wrong” Russ Miles - @russmiles

2. Who are you?

3. @russmiles

4. Also…

5. Russ Miles CEO, co-founder Your Host Today Sylvain Hellegouarch CTO, co-founder ChaosIQ

6. “To support our users in establishing their own   Resilience Engineering Capability”

7. What is “Wrong”?

8. And why are we scared of it?

9. “not correct or true; incorrect.”

10. “an injurious, unfair, or unjust act”…

11. …“action or conduct inﬂicting harm without due provocation or just cause”

12. “a violation or invasion of the legal rights of another”

13. When are we ever wrong?

14. “the state of being mistaken or incorrect”

15. I’ve got some bad news for you…

16. We’re wrong all the time.

17. We’re wrong all the time.

18. Why is wrong scary?

19. Risk?

20. Consequences.

21. Why us?!

22. Two factors

23. Feature Velocity

24. Striving for Reliability

25. Feature Velocity VS. Reliability

26. Good news!

27. No conﬂict!

28. Feature Velocity VS. Reliability

29. Feature Velocity + Reliability

30.

31.

32.

33.

34. But … Microservices!?

35. What about tests? gates? pipelines? isolation?

36. We’re covered…

37. A Story…

38.

39.

40.

41. And it gets worse…

42. Dark Debt…

43.

44. And over to the business…

45. “One Hour of Downtime Costs > $100K For 95% of Enterprises” http://itic-corp.com/blog/2013/07/one-hour-of-downtime-costs-100k-for-95-of-enterprises/

46. “lost revenue and lost end user productivity" http://itic-corp.com/blog/2013/07/one-hour-of-downtime-costs-100k-for-95-of-enterprises/

47. “not take into account the cost of additional penalties for regulatory non-compliance or “good will” gestures made to the organization’s customers and business partners that were negatively impacted by a system or network failure. In fact, these two conditions can cause downtime costs to skyrocket even further” http://itic-corp.com/blog/2013/07/one-hour-of-downtime-costs-100k-for-95-of-enterprises/

48. Bad news…

49. You’re not covered

50. Microservices-based systems tend to look like…

51. “To be fully described, there are many details, not few” John Allspaw: https://queue.acm.org/detail.cfm?id=2353017

52. “The rate of change is high; the systems change before a full description (and therefore understanding) can be completed.” John Allspaw: https://queue.acm.org/detail.cfm?id=2353017

53. “How components function is partly unknown, as they resonate with each other across varying conditions.” John Allspaw: https://queue.acm.org/detail.cfm?id=2353017

54. “Processes are heterogeneous and possibly irregular.” John Allspaw: https://queue.acm.org/detail.cfm?id=2353017

55. Reactions?

56. Ugly Risk Avoidance!

57. Blame.

58. A better reaction?

59. Being wrong is a   key software skill

60. Get Better At Being Wrong™

61. Make it Safe(r) to be wrong.

62. Technical Robustness

63. Zero Blame

64. Go Beyond Blame

65. Remember “Dark Debt”

66. Deliberately Practice Being Wrong

67. “prepare for undesirable circumstances” - John Allspaw

68. Deliberately Practice Being Wrong = Chaos Engineering

69. Invest in Resilience

70. Resilience is a Learning Loop

71. “Normal”

72. Outage “Normal”

73. Outage Detection Diagnosis Fix “Normal”

74. Outage Detection Diagnosis Fix “Normal” Learning

75. Outage Detection Diagnosis FixImprovement (Robustness) “Normal” Learning

76. “Never Let an Outage Go To Waste” - Casey Rosenthal

77. Post-mortem Learning   is Good

78. Pre-mortem Learning   is Better!

79. “Chaos Engineering is the discipline of experimenting on a distributed system  in order to build conﬁdence in the system’s capability to withstand turbulent conditions in production.” - principlesofchaos.org

80. “Normal”

81. Game Day / Automated Chaos Experiment “Normal”

82. Game Day / Automated Chaos Experiment Detection Diagnosis Fix “Normal”

83. Game Day / Automated Chaos Experiment Detection Diagnosis FixImprovement (Robustness) “Normal” Learning

84. Chaos Infrastructure Platform Applications People, Practices & Process Game Days Automated  Experiments Automated  Experiments Automated  Experiments

85. We can learn after outages… but it’s even better to   learn from weaknesses before an outage.

86. Being Wrong can be a super power, if it leads to learning

87. Establish a Platform for   Pre-mortem, Deliberate Practice “Being Wrong”

88. Establish a Platform for   Pre-mortem, Deliberate Practice “Chaos Engineering”

89. Automate Chaos Experiments Chaos Engineering Control Plane

90. Reading Recommendations

91. Later on today… Sylvain Hellegouarch CTO, co-founder +

92. Start a conversation… ChaosIQ www.chaosplatform.com contact@chaosiq.io O’Reilly Safari Online Courses Available Upcoming Conferences DevOpsCon Munich KubeCon Seattle O’Reilly Book on  “Chaos Engineering”   Coming Soon! https://www.chaostoolkit.org Slack: https://join.chaostoolkit.org

How to be Wrong (or How to be Successful at Being Wrong)

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Ähnlich wie How to be Wrong (or How to be Successful at Being Wrong)

Ähnlich wie How to be Wrong (or How to be Successful at Being Wrong) (20)

Mehr von Russell Miles

Mehr von Russell Miles (9)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

How to be Wrong (or How to be Successful at Being Wrong)