Monday, August 25, 2014

Amazon Web Services: Global Best Practices

I will be writing series of blog on Amazon Cloud. This blog is about Global best practices for public cloud created by Amazon

Why should you use the AWS cloud?
-Service based vs Resource based
-Instant Delivery
-Non-Commit architecture
-predictable, pay as you go cost model
-proven, expert design


Best Practice #1: Redundant Design
-No Single point of failure
-Many AWS services assume redundancy

Best Practice #2: Loose coupling

-Loose coupling design principle : Each application component is independent
-Use Integration with AWS services instead of “Hard Ties”
Example
-Elastic Load balancer
-Simple notification service
-Simple Queue service 


Best Practice #3: Elasticity
-Grow or shrink architecture on demand
-Instances are “drones” reporting for duty: tasked during provision
-Bootstrapping/dynamic configuration
-health Monitoring\no faith in any of the system

Best Practice #4: Think Security
-AWS is secure…until they invited us! Shared Responsibility
-Use Iron wall security principles rather than fish net principles
-Encrypt everything you can
-Use MFA (multi factor authentication) when possible

Best Practice #5: Things work better in parallel
-New paradigm….IT resource limitations removed
-Farming: advantage of using one plow/five hrs or five plows /one hr?
-Use parallel processing( with elastic principles) to accomplish goals faster


Best Practice #6: Use Multiple storage types
-Multiple AWS offerings for multiple scenarios:
   -S3-Object Storage
   -Cloud front-Edge Caching (CDN)
   -EBS- block storage
   -RDS-Relational Database
   -Dynamo DB-NOSQL DB


No comments:

Post a Comment

Featured Post

Amazon Route 53

Amazon Route 53 is a highly available and scalable Domain Name System (DNS) web service.Route 53  perform three main functions in any...