Ravi Sir's Cards › AWS
Agree RPO/RTO first
This revision card explains Agree RPO/RTO first. It starts from the need that copying stacks twice is not a DR story. It describes RPO = data loss tolerance; RTO = time to recover — product signs both. The how-to section notes pick active-passive or active-active; design data conflicts explicitly. An example on the card is rohan writes RPO 5 min / RTO 30 min before touching Route 53.
Read card text
What this card says
Why do we need it?
Copying stacks twice is not a DR story.
What is it?
RPO = data loss tolerance; RTO = time to recover — product signs both.
RPO
How to do it
Pick active-passive or active-active; design data conflicts explicitly.
Example
Rohan writes RPO 5 min / RTO 30 min before touching Route 53.