Disasters that actually happen
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
list the realistic disasters a subsystem must survive.
Planned topics
- Common causes are human and software: a bad migration, a deleted volume, a leaked or expired credential, a corrupt deploy, a ransomware or account lockout.
- Infrastructure disasters (zone or region loss) are real but rarer than operator error.
- High availability (surviving a node) is not disaster recovery (surviving the loss of data or a whole site); replication copies mistakes too.
- Scope the subsystem: data stores, event streams, secrets, DNS, configuration, and the people and access needed.
Draft outline details
Demonstration
A table: disaster | likelihood | impact | does HA cover it? | what recovers it. Rows: dropped table, zone outage, region outage, expired certificate, lost cloud account access.
Check your understanding
Why does replication not protect against an accidental table drop?
Show answer
The drop replicates to the copies.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.