Dependencies you don't own
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
design DR for systems outside your control.
Planned topics
- Your recovery depends on the ERP, payment provider, and identity service recovering too.
- Ask for their RTO and RPO in contracts and agreements; design to the weakest link.
- Decouple with queues and caches so you can keep working while they are down.
- Define degraded modes: accept orders and post later, switch payment methods, cache sign-in sessions.
- Document fallbacks and who triggers them.
Draft outline details
Demonstration
a dependency table: dependency, their stated RTO, our fallback, degraded behavior, owner.
Check your understanding
Why include the ERP in your DR plan if you do not own it?
Show answer
Your recovery cannot be faster than what it depends on without a fallback.
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.