Member-only story
Architecture Reliability
It is often confusing between DR and HA. High Availability (HA) focuses on continuously operating for a desirably long period while Disaster Recovery (DR) focuses on enabling the recovery following a natural or human-induced disaster.
To make your application replicable, you should able to restore service quickly and without lost data. Let’s talk about the most important terms, RTO (Recovery Time Objective) and RPO (Recovery Point Objectives).
The Recovery Time Objective (RTO) is the targeted duration of time and a service level within which a business process must be restored after a disruption in order to avoid a break in business continuity.
A Recovery Point Objective (RPO) is the maximum acceptable interval during which transactional data is lost from an IT service.
To ease your understanding, RPO is related to how frequently you make the backup. If you do the daily backup, your RPO will be 24 hours. RTO will be 1 hour if the technician comes to the site in 30 mins and fix it in 30 mins.
In architectural reliability, the most critical part to be protected is the data, so reasonably replicating data is the main topic to discuss when it comes to reliability.
