RPO and RTO from business impact
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
set recovery objectives per data set and service from what loss costs.
Planned topics
- RPO (recovery point objective): how much data, measured in time, you can lose. RTO (recovery time objective): how long you can be down.
- Derive each from business impact: lost orders, refunds, regulatory duty, reputation; not from what the technology offers.
- Different data sets differ: orders and payments need a tight RPO; a recommendation cache can be rebuilt.
- Tighter objectives cost more; present the cost per tier so the business chooses.
- The running case has a 15-minute RTO for the order database.
Draft outline details
Demonstration
Tier table: data set | RPO | RTO | rationale | approximate cost tier. Example: orders DB | near zero | 15 min; search index | 24 h | 4 h; session cache | n/a | rebuild.
Check your understanding
Who should decide the RPO for orders?
Show answer
The business, informed by impact and cost, with engineering advising.
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.