Which Disaster Recovery Pattern would you suggest for a business-critical customer-facing e-retail application where you are required to recover the user-facing application and data and minimal downtime quickly?
Click on the arrows to vote for the correct answer
A. B. C. D.Correct Answer: C.
Option A is incorrect because the Cold DR pattern leads to some delay while accessing the data.
Option B is incorrect because the Warm DR pattern is best suitable for systems that are not business-critical.
Option C is correct because a Hot DR pattern is best suited for business-critical applications and data.
Option D is incorrect because this is just a distractor, there is nothing like Live pattern DR pattern.
Reference Link:
https://cloud.google.com/architecture/dr-scenarios-planning-guide#design_according_to_your_recovery_goalsThe Disaster Recovery (DR) pattern is a crucial component of any cloud-based solution that ensures business continuity in the event of a disaster. There are several DR patterns, and the choice of the right pattern depends on various factors, such as Recovery Time Objective (RTO) and Recovery Point Objective (RPO), the criticality of the application, budget, and complexity of the infrastructure.
In the given scenario, the business-critical customer-facing e-retail application needs to be recovered with minimal downtime quickly. Based on this requirement, the most suitable DR pattern would be the Hot pattern.
The Hot DR pattern is designed to minimize the downtime by ensuring that the recovery site is always available and up-to-date. In this pattern, the recovery site is fully operational and actively processing data, mirroring the primary site. Therefore, in case of a disaster, failover to the recovery site can be almost instant. This pattern is the most expensive among all DR patterns and requires constant synchronization of data between the primary and the recovery site.
On the other hand, the Cold DR pattern is the least expensive but requires significant downtime for recovery. In this pattern, the recovery site is not operational until a disaster occurs. Therefore, recovering from this pattern can take hours or even days.
The Warm DR pattern is a balance between the Hot and Cold DR patterns. It involves maintaining a partially operational recovery site, which can be quickly scaled up to meet the demand during a disaster. This pattern requires moderate synchronization of data and infrastructure between the primary and the recovery site, making it less expensive than the Hot pattern but with a longer RTO.
Lastly, the Live DR pattern is not a well-known pattern and not commonly used in industry. It involves maintaining multiple active sites that are in constant use, but it can be expensive and complex.
In conclusion, based on the scenario of a business-critical customer-facing e-retail application that needs to be recovered with minimal downtime quickly, the most suitable DR pattern would be the Hot pattern.