From the course: AWS for DevOps: High Availability and Elasticity

Unlock the full course today

Join today to access over 22,600 courses taught by industry experts or purchase this course individually.

About self-healing architectures

About self-healing architectures - Amazon Web Services (AWS) Tutorial

From the course: AWS for DevOps: High Availability and Elasticity

Start my 1-month free trial

About self-healing architectures

“

- [Instructor] A pattern in this space is called self-healing architecture. What does that mean? It means that if an application is either going to go down or crash, or be slow, it fails what's called gracefully. So application performance might slow down, but it usually won't stop. So we're going to look at strategies around the various services to alert when service boundaries are being hit, and then to spin up alternative or more services. This is called also an event response pattern. So Amazon events, often CloudWatch alarms, although there's other type events that you can set up, will drive server or service responses, so for example, when, as I was saying earlier, an EC2 instance, the CPU becomes what's called throttled by hitting a metric, it's often 80% over a period of time, you might choose to spin up an additional EC2 instance and put it in your particular application. In the case of a docker container, similar type of performance levels might be hit and you might spin out…

Contents