In the real world, the systems can be a victim of a cyber-attack or even a natural disaster that can disturb the functionality of the server. In such cases, we need to recover the lost data as much as possible from another location where the data was backed up. Hence comes Disaster Recovery. It replicates the data in an off-premises location that remained intact even after the disaster or was far away from where it couldn’t have been backed up.
The concept of disaster recovery is to keep the data on some secondary locations in case the primary fails or is stuck in a disaster.
Recovery Time Objective (RTO)
RTO can be defined as an acceptable delay between the service interruption and restoration respectively. It tells us about the acceptable time window for service unavailability.
Recovery Point Objective (RPO)
RPO is the acceptable time since the last data recovery point. It tells us about an acceptable loss of data between the last recovery point and service interruption time.
Strategies for disaster recovery
There are some strategies we can use for disaster recovery.
Backup
Backup is a simple strategy for disaster recovery where we store the data off-site or in a removable drive that is safe from cyber-attacks and such things.Cold site
The cold site lets us arrange the basic data and infrastructure on a second site.Hot site
Further, the hot site keeps up the data up to date in the copies which might be time-consuming and expensive, but they make up for that in downtime reduction.
Why do we need disaster recovery?
- Restoration is fast.
- Downtime is reduced.
- Customer retention is better.
- Damages are limited.
- Interruption is minimized.
pragyaasapkota
/
System-Design-Concepts
Though the concepts of system design might be tricky, let's see them individually to their core concepts and have a better understanding.
System Design
Systems design is the process of defining elements of a system like modules, architecture, components and their interfaces and data for a system based on the specified requirements.
This is a index for the concepts of system.
If you wish to open these in a new tab, Press CTRL+click
| S.N. | Table of Content |
|---|---|
| 1. | Caching |
| 2. | Network Protocols |
| 3. | Storage: The Underrated Topic |
| 4. | Latency and Throughput |
| 5. | System Availability |
| 6. | Leader Election |
| 7. | Proxies |
| 8. | Load Balancing |
| 9. | Endpoint Protection |
| 10. | HTTPS: Is it better than HTTP? |
| 11. | Polling and Streaming |
| 12. | Long Polling |
| 13. | Hashing |
| 14. | CAP Theorem |
| 15. | PACELC Theorem |
| 16. | Messaging and Pub-Sub |
| 17. | Database |
| 18. | Logging, Monitoring, and Alerting |
| 19. | Distributed System |
| 20. | Scaling |
| 21. | Event Driven Architecture (EDA) |
| 22. | CQRS |
| 23. | Message Queue |
| 24. | Architectural Patterns |
| 25. | Enterprise Service Bus (ESB) |
| 26. | SLA, SLO, and SLI |
| 27. | Heartbeat |
I hope this article was helpful to you.
Please don’t forget to follow me!!!
Any kind of feedback or comment is welcome!!!
Thank you for your time and support!!!!
Keep Reading!! Keep Learning!!!
Top comments (0)