This article on Architecting Disaster Recovery infrastructure using Amazon Web Services (AWS ) explores the following blue prints
Blue print1 : Both Main Web Site and Disaster Recovery site in Amazon Web Services (AWS) Cloud
Blue print2 : Main site in Amazon Web Services cloud and Disaster recovery site in Traditional customer data center
Blue print3 : Main site in customer data center and Disaster recovery site in AWS cloudThe architecture blueprints also contains advanced elements like Managed DNS servers , Load Balancers and Data replicators into consideration. AWS technologies like AWS Security groups ,AWS Elastic Load balancing,AWS Auto Scaling,AWS EC2 ,AWS EBS ,AWS CloudWatch ,AWS Elastic IP and AWS S3 are used in the setup.
Blue print 1 : Both Main Site and Disaster recovery site in AWS Cloud is suitable for web applications , Mobile apps , social and gaming websites with Unpredictable load bursts and growing load requirements
Blue print 2 : Main site in AWS cloud and Disaster recovery site in Traditional customer data center is suitable for Enterprise web applications, online Media companies etc which already have 1-2 years contracts signed with traditional data centers. Their load is fairly predictable or “On & Off” workload bursts
Blue print3 : Main site in customer data center and Disaster recovery site in AWS cloud Suitable for applications with predictable loads , SMB companies which already have 1-2 years contracts signed with traditional data centers.
Disaster Recovery using Amazon Web Services (AWS)
Need Consulting help ?
All posts, comments, views expressed in this blog are my own and does not represent the positions or views of my past, present or future employers. The intention of this blog is to share my experience and views. Content is subject to change without any notice. While I would do my best to quote the original author or copyright owners wherever I reference them, if you find any of the content / images violating copyright, please let me know and I will act upon it immediately. Lastly, I encourage you to share the content of this blog in general with other online communities for non-commercial and educational purposes.