Amazon Web Services: AWS Elasticity Principles of elasticity

Traditional/AWS Architecture

-Traditional architecture is based on peak load

-AWS architecture provisions resources on demand / as needed

Elasticity Principle #1: Automate

-        -  Manual intervention= failure to meet demand

-        -  Elastic scaling = Automation

-        -  Preconfigured AMI

-         - Bootstrapping principles

Elasticity Principle #2: Loose Coupling

-          -Tightly coupled applications- apps where one component specifically depends on another specific , single      unit (creates failure or poor performance)

-       -   Loose coupling design uses AWS services or horizontally scaled design. you will need to recode your application.

Elasticity Principle #3: Staying stateless

-Avoid statefull application that stores state information on a single instance

-Instead store state information on a speedy, redundant, shared location (ex. dyanmeDB)

Elasticity Principle #4: Horizontal scaling

-Large instances will eventually hit a limit ( cpu, memory etc)

-Horizontal scaling and design grows without bounds