Introduction to Web Application Hosting in AWS Cloud

Subscribe Send me a message home page tags


Related Readings

Introduction

In a traditional web hosting architecture, dense peak traffic periods and wild swings in traffic patterns result in low utilization rates of expensive hardware. This yields high operating costs to maintain idle hardware, and inefficient use of capital for underused hardware.

web_capacity_model.png

The ability to adapt to the traffic and scale in real-time is the key selling point of cloud computing platform.

A typical web hosting architecture is separated into presentation, application and persistence layers.

traditional_three_tier_architecture.png

An equivalent architecture in AWS would look as follows and each tier can scale independently.

web_hosting_in_AWS_old.png

There is another diagram with more details in the next section.

AWS Web Hosting Best Practice

Probably the most important shift in how you might architect your AWS application is that Amazon EC2 hosts should be considered ephemeral and dynamic. Any application built for the AWS Cloud should not assume that a host will always be available and should be designed with the knowledge that any data that is not on an EBS volume will be lost if an EC2 instance fails. Additionally, when a new host is brought up, you shouldn't make assumptions about the IP address or location within an Availability Zone of the host.
web_hosting_in_AWS_new.png

----- END -----

Welcome to join reddit self-learning community.
Send me a message Subscribe to blog updates

Want some fun stuff?

/static/shopping_demo.png