An Introduction to Chaos Engineering

•

1 like•319 views

Curious about how chaos engineering can make your systems more resilient? Get a comprehensive introduction to the history, principles, and practice of chaos engineering You will walk away from this session with an in-depth understanding of what chaos engineering is, why it’s crucial to prevent outages, and how you can use it to build resilience into your own systems.

Software

Introduction to
Chaos Engineering
Kolton Andrus
CEO and Co-Founder
Gremlin

J. Crew Website down during Black
Friday 2018 sales Newsweek, 11/23/18
Alaska Airlines Flights halted nationwide due
to outage in Seattle Business Insider, 1/6/19
Slack Outage Connectivity issues
hit workplaces WSJ, 6/27/18

Inject something harmful to
build an immunity.

Chaos Engineering
Thoughtful, planned experiments
designed to reveal the
weakness in our systems.

We test proactively, instead of
waiting for an outage.

Distributed Systems
are fragile.
THE PROBLEM

INTERNETDATA CENTER DATA CENTER
BUSINESS LOGICWEB SERVER DATABASE
The “Old” way

Kolton Andrus
CO-FOUNDER & CEO
Matthew Fornaciari
CO-FOUNDER & CTO
We’ve done this before.

Chaos Experiment | Example
Hypothesis (Expected Outcome) No customer impact expected
Attack Condition
Duration: 600s (10 min)
Latency: 400ms
Targets: 50% of available instances
Result (Actual Outcome)
1.2 to 1.6 second latency
Degraded user experience
Returning cached data with 200s
“That’s a real miss in alerting and metrics.”
Slow Response from Database Primary

THE BEGINNING
Chaos Monkey
Level 0
MATURITY REQUIRED
Low
APPROACH TAKEN
Random
VALUE PROVIDED
Prepare for host failures in the cloud

THE FIRST STEP
Infrastructure
Failures
Level 1
MATURITY REQUIRED
Basic Operations
APPROACH TAKEN
Disciplined
VALUE PROVIDED
Prepare for host-level failures

Intermediate
Network Failures
Level 1.5
MATURITY REQUIRED
Networking expertise
APPROACH TAKEN
Gameday
VALUE PROVIDED
Prepare for high impact events

Truly comprehensive
fault injection.
Consume Resources
Change the State
Confuse the Network

World-class safety & security.
SUPPORT FOR SSO & MFA NEVER RUN AS ROOT REVERT

Astonishingly simple
and easy to use.
Intuitive CLI
Elegant API

Chaos Engineering: Why Breaking Things Should Be Practiced - AWS Developer Workshop at Web Summit 2018 Ever wondered how companies delivering global services like Amazon or Netflix are architecting and testing their software systems? If you are curious and want to learn how they do it - this session is for you! With the rise of micro-services and large-scale distributed architectures, software systems have grow increasingly complex and hard to understand. Adding to that complexity, the velocity of software delivery has also dramatically increased, resulting in failures being harder to predict and contain. While the cloud allows for high availability, redundancy and fault-tolerance, no single component can guarantee 100% uptime. Therefore, we have to understand availability but especially learn how to design architectures with failure in mind. And since failures have become more and more chaotic in nature, we must turn to chaos engineering in order to identify failures before they become outages. In this talk, I will deep dive into availability, reliability and large-scale architectures and make an introduction to chaos engineering, a discipline that promotes breaking things on purpose in order to learn how to build more resilient systems. Speaker: Adrian Hornsby - Technical Evangelist, AWS

Introduction to Chaos Engineering

Raymond Adrian (Rad) Butalid

Chaos Engineering

Yury Roa

Chaos Engineering

Amazon Web Services

Chaos Engineering with Gremlin Platform

Anshul Patel

Video and slides synchronized, mp3 and slide download available at URL https://bit.ly/2luk9iS. Tammy Butow shares her experiences using chaos engineering to build resilient systems, when they couldn’t build their systems from scratch. Filmed at qconlondon.com. Tammy Butow is a Principal SRE at Gremlin where she works on Chaos Engineering, the facilitation of controlled experiments to identify systemic weaknesses. Previously, she led SRE teams at Dropbox responsible for Databases and Storage systems used by over 500 million customers.

Chaos Engineering with Kubernetes

Arun Gupta

Principles Of Chaos Engineering - Chaos Engineering Hamburg

Nils Meder

Chaos Engineering with Kubernetes - Berlin / Hamburg Chaos Engineering Meetup...

Ana Medina

Chaos engineering and chaos testing

jeetendra mandal

Chaos engineering & Gameday on AWS

Bilal Aybar

Chaos Engineering 101: A Field Guide

matthewbrahms

Choose your own adventure Chaos Engineering - QCon NYC 2017

Nora Jones

Introduction to Chaos Engineering with Microsoft Azure

Ana Medina

https://www.gremlin.com/webinars/ce-on-azure/ Join us for a walkthrough on how to get started with Chaos Engineering on Azure. Learn the fundamentals of Chaos Engineering and how to build more reliable applications on Azure. In this live session, we’ll show you how to get started running experiments on Azure’s managed Kubernetes (AKS) and how to implement continuous Chaos Engineering using Azure Pipelines. Then be sure to stay until the end for live Q&A. AGENDA - Learn the history, principles and practice of Chaos Engineering - How to get started with Chaos Engineering on Azure - Run chaos experiments to simulate common real-world failures on AKS - How to implement Chaos Engineering Experiments on Azure Pipelines

chaos-engineering-Knolx

Knoldus Inc.

Practical Chaos Engineering

SIGHUP

Cloud Migration WorkshopAmazon Web Services

Hexagonal Architecture

Marcelo Cure

infrastructure as code

Amazon Web Services

While many organizations have started to automate their software development processes, many still engineer their infrastructure largely by hand. Treating your infrastructure just like any other piece of code creates a “programmable infrastructure” that allows you to take full advantage of the scalability and reliability of the AWS cloud. This session will walk through practical examples of how AWS customers have merged infrastructure configuration with application code to create application-specific infrastructure and a truly unified development lifecycle. You will learn how AWS customers have leveraged tools like CloudFormation, orchestration engines, and source control systems to enable their applications to take full advantage of the scalability and reliability of the AWS cloud, create self-reliant applications, and easily recover when things go seriously wrong with their infrastructure.

A Journey from Hexagonal Architecture to Event Sourcing - SymfonyCon Cluj 2017

Carlos Buenosvinos

Event-based architectures such as Event Sourcing provide multiple benefits: scalability, complexity management, auditing, etc. However, let’s face it, getting there is quite hard. We lack skills, expertise and courage. In this talk, I’m going to show you some tips and tricks to painless evolve your current architecture towards Event Sourcing, one small step at a time. We’ll start from an Hexagonal Architecture application and we’ll end up in the Event Sourcing doors. The path that we’ll follow is: Hexagonal Architecture Hexagonal Architecture with Domain Events Stepping Stone Architecture (CQRS without Event Sourcing) Event Sourcing Talk level: Intermediate to Expert Requirements: Basic concepts of Hexagonal Architecture (Entities, Repositories, Application Services, etc.)

Getting started with Site Reliability Engineering (SRE)

Abeer R

"Getting started with Site Reliability Engineering (SRE): A guide to improving systems reliability at production" This is an intro guide to share some of the common concepts of SRE to a non-technical audience. We will look at both technical and organizational changes that should be adopted to increase operational efficiency, ultimately benefiting for global optimizations - such as minimize downtime, improve systems architecture & infrastructure: - improving incident response - Defining error budgets - Better monitoring of systems - Getting the best out of systems alerting - Eliminating manual, repetitive actions (toils) by automation - Designing better on-call shifts/rotations How to design the role of the Site Reliability Engineer (who effectively works between application development teams and operations support teams)

Design patterns for microservice architecture

The Software House

The presentation from our online webinar "Design patterns for microservice architecture". Full video from webinar available here: https://www.youtube.com/watch?v=826aAmG06KM If you’re a CTO or a Lead Developer and you’re planning to design service-oriented architecture, it’s definitely a webinar tailored to your needs. Adrian Zmenda, our Lead Dev, will explain: - when microservice architecture is a safe bet and what are some good alternatives - what are the pros and cons of the most popular design patterns (API Gateway, Backend for Frontend and more) - how to ensure that the communication between services is done right and what to do in case of connection issues - why we’ve decided to use a monorepo (monolithic repository) - what we’ve learned from using the remote procedure call framework gRPC - how to monitor the efficiency of individual services and whole SOA-based systems.

Chaos Engineering: Injecting Failure for Building Resilience in Systems

Yury Roa

(ARC307) Infrastructure as Code

Amazon Web Services

While many organizations have started to automate their software develop processes, many still engineer their infrastructure largely by hand. Treating your infrastructure just like any other piece of code creates a “programmable infrastructure” that allows you to take full advantage of the scalability and reliability of the AWS cloud. This session will walk through practical examples of how AWS customers have merged infrastructure configuration with application code to create application-specific infrastructure and a truly unified development lifecycle. You will learn how AWS customers have leveraged tools like CloudFormation, orchestration engines, and source control systems to enable their applications to take full advantage of the scalability and reliability of the AWS cloud, create self-reliant applications, and easily recover when things go seriously wrong with their infrastructure.

Introduction to the Well-Architected Framework and Tool - SVC208 - Anaheim AW...

Amazon Web Services

Most modern businesses depend on a portfolio of technology solutions to operate and be successful every day. How do you know whether your team is following best practices or what the risks are in your architectures? This session shows how the AWS Well-Architected Framework provides prescriptive advice on best practices and how the AWS Well-Architected Tool enables you to measure and improve your technology portfolio. We explain how other customers are using AWS Well-Architected in their businesses, and we share what we learned from reviewing tens of thousands of architectures across operational excellence, security, reliability, performance efficiency, and cost optimization.

Chapter 4 Case study instructions1. Answer the Case Study Ques.docx

christinemaritza

Chapter 4 Case study instructions 1. Answer the Case Study Questions (found at the end of each case study) in 500-750 words total (not including reference list). 2. Include at least one additional, external reference to sources such as an article or video. Cite the reference(s) in your study. Your case study will be graded on the following: Grading: 20 points Content 80% (how thoroughly and logically you answer the questions, how well you incorporate your reference(s), how well you make arguments and state facts to support your answers). Spelling/Grammar/Punctuation 20% Interactive Session: Organizations Are We Relying Too Much on Computers to Think for Us? Does our ever–burgeoning dependence on computers foster complacency, suppressing our ability to marshal our mental faculties when required? Although computerization has undoubtedly mitigated malfunctions, work stoppages, and breakdowns, are we concurrently losing our ability to assess alternatives independently and make optimal choices? At least one technology writer is sure this is exactly what is happening. Nicholas Carr’s book, The Glass Cage: Automation and Us, lays out the case that our overreliance on computers has dulled our reflexes and eroded expertise. Two cognitive failures undermine performance. Complacency—overconfidence in the computer’s ability—causes our attention to wander. Bias—overconfidence in the accuracy of the data we are receiving from the computer—causes us to disregard outside data sources, including conflicting sensory stimuli. When pilots, soldiers, doctors, or even factory managers lose focus and lack situational awareness, they ignore both suspect data coming from the computer and the external cues that would refute it. The results can be catastrophic. In two instances in 2009, commercial airplane pilots misinterpreted the signals when their autopilot controls disconnected after receiving warnings that the aircraft would stall. Rather than pushing the yoke forward to gain velocity, both pilots heeded faulty control panel data while ignoring environmental cues and pulled back on the yoke, lifting the plane’s nose and decreasing airspeed—the exact opposite of what was required. Loss of automation triggered confusion and panic. Sharply curtailed hands-on flight experience (on a typical passenger flight today, a human pilot mans the controls for just three minutes) resulted in stalled aircraft plunging to earth. Fifty died in Buffalo, New York; 228 perished in the Atlantic Ocean en route to Paris from Rio de Janeiro. The Federal Aviation Administration (FAA) is now pressing airlines to adopt stricter requirements for manual flying hours to offset the risks posed by complacency and bias. Carr’s critics point out that air travel is now safer than ever, with accidents and deaths steadily declining over decades and fatal airline crashes exceedingly rare. Carr concedes this point but still worries that pilots have come to rely so much on computers that they are forg ...

The Quality “Logs”-Jam: Why Alerting for Cybersecurity is Awash with False Po...

Mark Underwood

What happens when the (Observe) Plan-Do-Check-Adjust cycle is undermined by lapses in data integrity? Observations are questioned. Plans may be ill-conceived. Actions may be undertaken that undermine rather than enhance. “Checks” can fail. Adjustments may be guesswork. In cybersecurity, the results of poor data integrity can be expensive outages, ransom requests, breaches, fines -- even bankruptcy (think Cambridge Analytica). But data integrity issues take many forms, ranging from benign to malicious. The full range of these issues is surveyed from a cybersecurity perspective, where logs and alerts are critical for defenders -- as well as quality engineers . Techniques borrowed from model-based systems engineering and ontology AI to are identified that can mitigate these deleterious effects on PDCA.

What's hot

Chaos Engineering: Why the World Needs More Resilient Systems

C4Media

Chaos Engineering with Kubernetes

Arun Gupta

Principles Of Chaos Engineering - Chaos Engineering Hamburg

Nils Meder

Chaos Engineering with Kubernetes - Berlin / Hamburg Chaos Engineering Meetup...

Ana Medina

Chaos engineering and chaos testing

jeetendra mandal

Chaos engineering & Gameday on AWS

Bilal Aybar

Chaos Engineering 101: A Field Guide

matthewbrahms

Choose your own adventure Chaos Engineering - QCon NYC 2017

Nora Jones

Introduction to Chaos Engineering with Microsoft Azure

Ana Medina

chaos-engineering-Knolx

Knoldus Inc.

Practical Chaos Engineering

SIGHUP

Cloud Migration WorkshopAmazon Web Services

Hexagonal Architecture

Marcelo Cure

infrastructure as code

Amazon Web Services

A Journey from Hexagonal Architecture to Event Sourcing - SymfonyCon Cluj 2017

Carlos Buenosvinos

Getting started with Site Reliability Engineering (SRE)

Abeer R

Design patterns for microservice architecture

The Software House

Chaos Engineering: Injecting Failure for Building Resilience in Systems

Yury Roa

(ARC307) Infrastructure as Code

Amazon Web Services

Introduction to the Well-Architected Framework and Tool - SVC208 - Anaheim AW...

Amazon Web Services

What's hot (20)

Chaos Engineering: Why the World Needs More Resilient Systems

Chaos Engineering with Kubernetes

Principles Of Chaos Engineering - Chaos Engineering Hamburg

Chaos Engineering with Kubernetes - Berlin / Hamburg Chaos Engineering Meetup...

Chaos engineering and chaos testing

Chaos engineering & Gameday on AWS

Chaos Engineering 101: A Field Guide

Choose your own adventure Chaos Engineering - QCon NYC 2017

Introduction to Chaos Engineering with Microsoft Azure

chaos-engineering-Knolx

Practical Chaos Engineering

Cloud Migration Workshop

Hexagonal Architecture

infrastructure as code

A Journey from Hexagonal Architecture to Event Sourcing - SymfonyCon Cluj 2017

Getting started with Site Reliability Engineering (SRE)

Design patterns for microservice architecture

Chaos Engineering: Injecting Failure for Building Resilience in Systems

(ARC307) Infrastructure as Code

Introduction to the Well-Architected Framework and Tool - SVC208 - Anaheim AW...

Similar to An Introduction to Chaos Engineering

Chapter 4 Case study instructions1. Answer the Case Study Ques.docx

christinemaritza

The Quality “Logs”-Jam: Why Alerting for Cybersecurity is Awash with False Po...

Mark Underwood

Load testing for Dummies - LDNA 11-2018

Giulio Vian

Limerick DotNet-Azure User Group (LDNA) 18 November 2018 Meetup (https://www.meetup.com/Limerick-DotNet/events/mcqvcqyxpbzb/) Load testing for Dummies About load and stress testing, in the context of web applications and services. An introduction to the tools and techniques to generate load and analyze behavior. - Purpose of testing - Emerging Problems - Basic model - Tools: JMeter, Visual Studio, Gatling - Test rigs: custom, Azure CLT, BlazeMeter

[iROC Webinar] Do I Need to Worry About Soft Errors? iROCTech

MBA 208 - Business Management Information System (with Computer Appl.pdf

faraaanzum2014

MBA 208 - Business Management Information System (with Computer Application) Case Study No. 2: Are We Relying Too Much on Computers to Think for Us? Does our ever-burgeoning dependence on computers foster complacency, suppressing our ability to marshal our mental faculties when required? Although computerization has undoubtedly mitigated malfunctions, work stoppages, and breakdowns, are we concurrently losing our ability to assess alternatives independently and make optimal choices? At least one technology writer is sure this is exactly what is happening. Nicholas Carr's book, The Glass Cage: Automation and Us, lays out the case that our overreliance on computers has dulled our reflexes and eroded expertise. Two cognitive failures undermine performance. Complacency overconfidence in the computer's ability-causes our attention to wander. Bias-overconfidence in the accuracy of the data we are receiving from the computer-causes us to disregard outside data sources, including conflicting sensory stimuli. When pilots, soldiers, doctors, or even factory managers lose focus and lack situational awareness, they ignore both suspect data coming from the computer and the external cues that would refute it. The results can be catastrophic. In two instances in 2009, commercial airplane pilots misinterpreted the signals when their autopilot controls disconnected after receiving warnings that the aircraft would stall. Rather than pushing the yoke forward to gain velocity, both pilots heeded faulty control panel data while ignoring environmental cues and pulled back on the yoke, lifting the plane's nose, and decreasing airspeed-the exact opposite of what was required. Loss of automation triggered confusion and panic. Sharply curtailed hands-on flight experience (on a typical passenger flight today, a human pilot mans the controls for just three minutes) resulted in stalled aircraft plunging to earth. Fifty died in Buffalo, New York; 228 perished in the Atlantic Ocean en route to Paris from Rio de Janeiro. The Federal Aviation Administration (FAA) is now pressing airlines to adopt stricter requirements for manual flying hours to offset the risks posed by complacency and bias. Carr's critics point out that air travel is now safer than ever, with accidents and deaths steadily declining over decades and fatal airline crashes exceedingly rare. Carr concedes this point but still worries that pilots have come to rely so much on computers that they are forgetting how to fly. Andrew McAfee, a researcher at the MIT Sloan School of Management, points out that people have lamented the loss of skills due to technology for many centuries, but on balance, automation has made the world better off. There may be a high-profile crash, but he believes greater automation, not less, is the solution. Although humans have historically believed that allocating tasks to machines liberates us from the mundane and enables us to pursue the extraordinary, computers have ushered in an alt.

2020 KringleCon HolidayHack Report - Brazzell

Curtis Brazzell

Internet of Things, Connected Infrastructure & The Modern Supply Chain

Jeff Risley

Green Custard Friday Talk 19: Chaos Engineering

Green Custard

In Green Custard's 19th Friday talk, Zoltan explores the subject of Chaos Engineering Topics covered: - What is chaos engineering? - Why would anyone do this? - Availability - Chaos engineering in practice - The four golden signals - Chaos engineering in practice - Chaos Monkey - The Simian Army Green Custard is a custom software development consultancy. To discover more about their work and the team visit www.green-custard.com.

Using functional programming within an industrial product group: perspectives...

Anil Madhavapeddy

The need for a fluid data centre, what that actually means, and the hurdles i...

Nordic Digital Business Summit

Goran Sandahl - Machine Learning. Literally.

SogetiLabs

Cloudexpokeynote5 090518103820 Phpapp02Scott Winter

Building Great Companies on the CloudRoman Stanek

BlackHat_2015_Slides_Krotofil_FINALMarina Krotofil

Running head THREATS, ATTACKS AND VULNERABILITY ASSESSMENT .docx

todd521

Running head: THREATS, ATTACKS AND VULNERABILITY ASSESSMENT THREATS, ATTACKS AND VULNERABILITY ASSESSMENT 8 Threats, Attacks and Vulnerability Assessment Anthony bahlman CMGT/400 03/30/2019 Google LLC is a technological company from America which specializes in Internet-related products and services. Some of the products and services which are offered by Google include search engines, cloud computing, hardware, software, and online advertising technologies. It is considered among the Big Four companies which also include Apple, Amazon, and Facebook. The organization was founded by Larry Page and Sergey Brin in 1998. The founders were Ph.D. students at Stanford University in California. All facilities are subject to a certain level of risk which can be associated with different threats. The threats may be as a result of natural events, intentional acts by human beings to cause harm or accidents (Maglaras et al., 2018). The owners of companies have the responsibility of limiting or managing the risks arising from the threats to the maximum extent possible. Tangible Assets Google is one of the best technology companies in the world with a high number of tangible assets within its premises, especially in the headquarters located in Mountain View, California. The information systems, critical infrastructure, and cyber-related interests to be tested include the software of the company, hardware, system interfaces with consideration of internal and external connectivity, data and information, and people who use and support IT system. The aspects will be assessed because they are crucial to the day to day operations of the facility, and a breach in any aspect may lead to major disruption of services. The aspects which will not be assessed include IT system functional requirements, system users, current network topology system security policies which guide the use of the IT system and the architecture of security of the system. The aspects will not be assessed because of the minimal threat they pose to the system, and low probability of risk to arise from them. Moreover, the disruption of the items does not lead to significant interference in the operation of the organization. Asset Descriptions The following is a diagram of the flow of assessment activities: The assets descriptions are outlined below: · Hardware- Physical parts of the computers. · IT personnel- Individuals operating computer systems. Threat Agents and Possible Attacks There are several threat agents and possible attacks that may face the organization. the company may be subject to floods which may be as a result of excessive rainfall or overflowing ocean water. Tornadoes are also a possible threat to the organization, and these are violent and destructive rotating winds. Other possible natural threats to the organization headquarters include earthquakes, electrical storms, and avalanches. Electrical storms involve the violent disturbance of the electr.

2018 ThoughtWorks XConf NA - AI and the Developer role

Vishal Bardoloi

DOST 2016 Cloud Without Failures

Jorge Cardoso

Gartner analyzed data centers for a period of 10 years and found that 47% of all problems were caused by cloud services outages. The duration of outages ranged between 40 minutes and five days. Ponemon Institute studied the financial impact and found that on average outages cost US$ 690.204, with an average downtime cost of US$ 6.828 per minute. These results are important due to the economic impact of unplanned outages on cloud operations which calls for higher platform reliability. The first part of this talk will present the mechanisms that pioneers, such as Amazon, Google, and Netflix, have already developed to increase the reliability of their cloud platforms. The second part of the talk will describe how Huawei Research is exploring the use of fault-injection mechanisms to effectively increase the reliability of the Open Telekom Cloud platform from Deutsche Telekom.

Transforming Computational Fluid Dynamics (CFD) with GPUs on AWS (CMP327) - A...

Amazon Web Services

Cybersecurity for Control Systems: Current State and Future Vision pt.1EnergySec

Cloud Operations and Analytics: Improving Distributed Systems Reliability usi...

Jorge Cardoso

Similar to An Introduction to Chaos Engineering (20)

Chapter 4 Case study instructions1. Answer the Case Study Ques.docx

The Quality “Logs”-Jam: Why Alerting for Cybersecurity is Awash with False Po...

Load testing for Dummies - LDNA 11-2018

[iROC Webinar] Do I Need to Worry About Soft Errors?

MBA 208 - Business Management Information System (with Computer Appl.pdf

2020 KringleCon HolidayHack Report - Brazzell

Internet of Things, Connected Infrastructure & The Modern Supply Chain

Green Custard Friday Talk 19: Chaos Engineering

Using functional programming within an industrial product group: perspectives...

The need for a fluid data centre, what that actually means, and the hurdles i...

Goran Sandahl - Machine Learning. Literally.

Cloudexpokeynote5 090518103820 Phpapp02

Building Great Companies on the Cloud

BlackHat_2015_Slides_Krotofil_FINAL

Running head THREATS, ATTACKS AND VULNERABILITY ASSESSMENT .docx

2018 ThoughtWorks XConf NA - AI and the Developer role

DOST 2016 Cloud Without Failures

Transforming Computational Fluid Dynamics (CFD) with GPUs on AWS (CMP327) - A...

Cybersecurity for Control Systems: Current State and Future Vision pt.1

Cloud Operations and Analytics: Improving Distributed Systems Reliability usi...

Recently uploaded

Vitthal Shirke Microservices Resume Montevideo

Vitthal Shirke

Top Features to Include in Your Winzo Clone App for Business Growth (4).pptx

rickgrimesss22

Globus Compute Introduction - GlobusWorld 2024

Globus

OpenFOAM solver for Helmholtz equation, helmholtzFoam / helmholtzBubbleFoam

takuyayamamoto1800

Lecture 1 Introduction to games development

abdulrafaychaudhry

2024 RoOUG Security model for the cloud.pptx

Georgi Kodinov

Dominate Social Media with TubeTrivia AI’s Addictive Quiz Videos.pdf

AMB-Review

Dominate Social Media with TubeTrivia AI’s Addictive Quiz Videos https://www.amb-review.com/tubetrivia-ai Exclusive Features: AI-Powered Questions, Wide Range of Categories, Adaptive Difficulty, User-Friendly Interface, Multiplayer Mode, Regular Updates. #TubeTriviaAI #QuizVideoMagic #ViralQuizVideos #AIQuizGenerator #EngageExciteExplode #MarketingRevolution #BoostYourTraffic #SocialMediaSuccess #AIContentCreation #UnlimitedTraffic

A Sighting of filterA in Typelevel Rite of Passage

Philip Schwarz

Large Language Models and the End of Programming

Matt Welsh

Cracking the code review at SpringIO 2024

Paco van Beckhoven

Code reviews are vital for ensuring good code quality. They serve as one of our last lines of defense against bugs and subpar code reaching production. Yet, they often turn into annoying tasks riddled with frustration, hostility, unclear feedback and lack of standards. How can we improve this crucial process? In this session we will cover: - The Art of Effective Code Reviews - Streamlining the Review Process - Elevating Reviews with Automated Tools By the end of this presentation, you'll have the knowledge on how to organize and improve your code review proces

Accelerate Enterprise Software Engineering with Platformless

WSO2

Key takeaways: Challenges of building platforms and the benefits of platformless. Key principles of platformless, including API-first, cloud-native middleware, platform engineering, and developer experience. How Choreo enables the platformless experience. How key concepts like application architecture, domain-driven design, zero trust, and cell-based architecture are inherently a part of Choreo. Demo of an end-to-end app built and deployed on Choreo.

Orion Context Broker introduction 20240604

Fermin Galan

Field Employee Tracking System| MiTrack App| Best Employee Tracking Solution|...

informapgpstrackings

Enhancing Project Management Efficiency_ Leveraging AI Tools like ChatGPT.pdf

Jay Das

BoxLang: Review our Visionary Licenses of 2024

Ortus Solutions, Corp

TROUBLESHOOTING 9 TYPES OF OUTOFMEMORYERROR

Tier1 app

Even though at surface level ‘java.lang.OutOfMemoryError’ appears as one single error; underlyingly there are 9 types of OutOfMemoryError. Each type of OutOfMemoryError has different causes, diagnosis approaches and solutions. This session equips you with the knowledge, tools, and techniques needed to troubleshoot and conquer OutOfMemoryError in all its forms, ensuring smoother, more efficient Java applications.

GlobusWorld 2024 Opening Keynote session

Globus

Beyond Event Sourcing - Embracing CRUD for Wix Platform - Java.IL

Natan Silnitsky

In software engineering, the right architecture is essential for robust, scalable platforms. Wix has undergone a pivotal shift from event sourcing to a CRUD-based model for its microservices. This talk will chart the course of this pivotal journey. Event sourcing, which records state changes as immutable events, provided robust auditing and "time travel" debugging for Wix Stores' microservices. Despite its benefits, the complexity it introduced in state management slowed development. Wix responded by adopting a simpler, unified CRUD model. This talk will explore the challenges of event sourcing and the advantages of Wix's new "CRUD on steroids" approach, which streamlines API integration and domain event management while preserving data integrity and system resilience. Participants will gain valuable insights into Wix's strategies for ensuring atomicity in database updates and event production, as well as caching, materialization, and performance optimization techniques within a distributed system. Join us to discover how Wix has mastered the art of balancing simplicity and extensibility, and learn how the re-adoption of the modest CRUD has turbocharged their development velocity, resilience, and scalability in a high-growth environment.

In 2015, I used to write extensions for Joomla, WordPress, phpBB3, etc and I ...

Juraj Vysvader

Enhancing Research Orchestration Capabilities at ORNL.pdf

Globus

Cross-facility research orchestration comes with ever-changing constraints regarding the availability and suitability of various compute and data resources. In short, a flexible data and processing fabric is needed to enable the dynamic redirection of data and compute tasks throughout the lifecycle of an experiment. In this talk, we illustrate how we easily leveraged Globus services to instrument the ACE research testbed at the Oak Ridge Leadership Computing Facility with flexible data and task orchestration capabilities.

Recently uploaded (20)

Vitthal Shirke Microservices Resume Montevideo

Top Features to Include in Your Winzo Clone App for Business Growth (4).pptx

Globus Compute Introduction - GlobusWorld 2024

OpenFOAM solver for Helmholtz equation, helmholtzFoam / helmholtzBubbleFoam

Lecture 1 Introduction to games development

2024 RoOUG Security model for the cloud.pptx

Dominate Social Media with TubeTrivia AI’s Addictive Quiz Videos.pdf

A Sighting of filterA in Typelevel Rite of Passage

Large Language Models and the End of Programming

Cracking the code review at SpringIO 2024

Accelerate Enterprise Software Engineering with Platformless

Orion Context Broker introduction 20240604

Field Employee Tracking System| MiTrack App| Best Employee Tracking Solution|...

Enhancing Project Management Efficiency_ Leveraging AI Tools like ChatGPT.pdf

BoxLang: Review our Visionary Licenses of 2024

TROUBLESHOOTING 9 TYPES OF OUTOFMEMORYERROR

GlobusWorld 2024 Opening Keynote session

Beyond Event Sourcing - Embracing CRUD for Wix Platform - Java.IL

In 2015, I used to write extensions for Joomla, WordPress, phpBB3, etc and I ...

Enhancing Research Orchestration Capabilities at ORNL.pdf

An Introduction to Chaos Engineering

1. Introduction to Chaos Engineering Kolton Andrus CEO and Co-Founder Gremlin

2. J. Crew Website down during Black Friday 2018 sales Newsweek, 11/23/18 Alaska Airlines Flights halted nationwide due to outage in Seattle Business Insider, 1/6/19 Slack Outage Connectivity issues hit workplaces WSJ, 6/27/18

3. What is Chaos Engineering?

4. Inject something harmful to build an immunity.

5. Chaos Engineering Thoughtful, planned experiments designed to reveal the weakness in our systems.

6. We test proactively, instead of waiting for an outage.

7. Distributed Systems are fragile. THE PROBLEM

8. INTERNETDATA CENTER DATA CENTER BUSINESS LOGICWEB SERVER DATABASE The “Old” way

9. Kolton Andrus CO-FOUNDER & CEO Matthew Fornaciari CO-FOUNDER & CTO We’ve done this before.

10.

11. How?

12. Design Thoughtful Experiments

13. Chaos Experiment | Example Hypothesis (Expected Outcome) No customer impact expected Attack Condition Duration: 600s (10 min) Latency: 400ms Targets: 50% of available instances Result (Actual Outcome) 1.2 to 1.6 second latency Degraded user experience Returning cached data with 200s “That’s a real miss in alerting and metrics.” Slow Response from Database Primary

14. THE BEGINNING Chaos Monkey Level 0 MATURITY REQUIRED Low APPROACH TAKEN Random VALUE PROVIDED Prepare for host failures in the cloud

15. THE FIRST STEP Infrastructure Failures Level 1 MATURITY REQUIRED Basic Operations APPROACH TAKEN Disciplined VALUE PROVIDED Prepare for host-level failures

16. Intermediate Network Failures Level 1.5 MATURITY REQUIRED Networking expertise APPROACH TAKEN Gameday VALUE PROVIDED Prepare for high impact events

17. Truly comprehensive fault injection. Consume Resources Change the State Confuse the Network

18. World-class safety & security. SUPPORT FOR SSO & MFA NEVER RUN AS ROOT REVERT

19. Astonishingly simple and easy to use. Intuitive CLI Elegant API

20. Trusted by teams worldwide

21. Thank you.

An Introduction to Chaos Engineering

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to An Introduction to Chaos Engineering

Similar to An Introduction to Chaos Engineering (20)

Recently uploaded

Recently uploaded (20)

An Introduction to Chaos Engineering