Senior LevelSoftware Engineering Principles
What are Recovery Point Objective (RPO) and Recovery Time Objective (RTO) in Disaster Recovery planning?
❓ Interview Prompt: Explain Disaster Recovery (DR) metrics: RPO (acceptable data loss window) vs RTO (acceptable downtime duration), backup strategies, and multi-region failover.
Disaster Recovery (DR) plans evaluate business continuity using two core metrics:
1
Recovery Point Objective (RPO): The maximum acceptable age of data that can be lost during a outage (measured in time):
•
Example: If RPO is 15 minutes, database backups/replication must occur at least every 15 minutes.
2
Recovery Time Objective (RTO): The maximum acceptable duration of system downtime before service is restored:
•
Example: If RTO is 1 hour, automated failover must restore production within 60 minutes.
Code Implementation Example
json
{
"tier": "Tier 1 Critical Financial API",
"rpo": "0 Seconds (Zero Data Loss via Synchronous Multi-Region Replication)",
"rto": "< 30 Seconds (Automated Healthcheck DNS Failover)"
}💡Tier 1 Disaster Recovery RPO and RTO SLA target specifications.
🎯 Interview Key Takeaway
Design infrastructure replication and failover to meet strict business RPO (data loss limit) and RTO (downtime limit) SLAs.
#Disaster Recovery#RPO#RTO#High Availability#Senior
Back to all Software Engineering Principles Questions→