Professional Documents
Culture Documents
Architecture Blueprints
Harish Ganesan
Co founder & CTO
8KMiles
www.twitter.com/harish11g
http://www.linkedin.com/in/harishganesan
Introduction
• Managed DNS
• LAMP (or) LAMJ stack
• MySQL Master- Master replication
• SOLr Search servers
• Schedulers and Back ground programs
Blue Print 1 : Main and DR website in AWS
Main website in
AWS Cloud
Disaster Recovery
website in AWS
Cloud
Blue Print 1: Main and DR website in AWS
GEO IP / Directional DNS Servers directs the user requests to
Main site in AWS USA region. In case of Disaster in Main site
1 AWS USA region , the web requests are directed to DR site in
Europe
• Auto Scaling
– Auto Scaling allows you to automatically scale your
Amazon EC2 capacity up or down according to
conditions you define.
– Auto Scaling is particularly well suited for
applications that experience hourly, daily, or weekly
variability in usage.
– Our Use case : EC2 Server instances dynamically
Scaled up and Down depending upon the Load using
the Auto scaling
Solution Components : AWS CloudWatch
• AWS CloudWatch
– Amazon CloudWatch enables you to monitor your
Amazon web services in real-time.
– Amazon CloudWatch helps us to access up-to-the-
minute statistics, graphs, and set alarms for our
metric data.
– Our Use case : EC2 servers , EBS , ELB are monitored
and alerts are sent using AWS CloudWatch
Solution Components : Managed DNS
• Managed DNS
– a solution that can monitor the health of multiple
endpoints or websites and automatically failover at
DNS level in case of a failure at the primary website
– Our Use case : Used for transparent switch between
Main and Disaster recovery website during failures
Solution Components : MySQL replication
• MySQL Replication
– MySQL will be setup in Master – Master replication
mode
– M-M setup offers failover inside data center as well
as across Data centers
– Data Replication will be done asynchronously
– Our Use case : Data is replicated between Main and
DR website MySQL database using Master-Master
replication
Blue Print 2 : Main site in AWS
Main website in
AWS Cloud
DR website in
Traditional data
center
Blue Print 2: Main site in AWS – DR site in Traditional DC
GEO IP / Directional DNS Servers directs the user requests to
Main site in AWS USA region. In case of Disaster in Main site,
1 the web requests are directed to DR site in USA West
DR website in AWS
Cloud
Main website in
Traditional data
center
Blue Print 3: DR site in AWS – Main site in Traditional DC
GEO IP / Directional DNS Servers directs the user requests to
Main site in USA east region. In case of Disaster in Main site,
1 the web requests are directed to DR site in AWS USA West
region
Continued
Blue Print 3 : Architecture Explanation
Continued
Blue Print 3 : Architecture Explanation
Continued
Blue Print 3 : Architecture Explanation
cloud@8kmiles.com
http://cloudblog.8kmiles.com
http://cloud.8kmiles.com