《亚马逊云架构》由会员分享，可在线阅读，更多相关《亚马逊云架构（47页珍藏版）》请在金锄头文库上搜索。
1、Architectural Design Patterns in Cloud Computing Jinesh Varia Technology Evangelist jvaria They sent me here to talk But I am here to listen Please Send Feedback jvaria Twitter jinman Cloud Best Practices Whitepaper Prescriptive guidance to Cloud Architects Just Google for Cloud Best Practices to fi
2、nd the link Abstract Resources Focus on your needs not on hardware specs As your needs change so should your resources On Demand Provisioning Ask for what you need exactly when you need it Get rid of it when you don t need ScalabilityScale out or in depending on usage needs No Up Front Costs No cont
3、racts or long term commitments Pay only for what you use Efficiency of Experts Utilize the skills knowledge and resources of experts Cloud Computing Attributes What makes the Cloud so attractive The Living and Evolving Cloud The Cloud AWS services and features Most Applications Need 1 Compute 2 Stor
4、age 3 Messaging 4 Payment 5 Distribution 6 Scale 7 Analytics Amazon RDS High Memory Instances Lower EC2 Pricing AWS Multi Factor Authentication Virtual Private Cloud Lower Reserved Instance Pricing AWS Security Center Reserved Instances in EU Region Elastic MapReduce SQS in EU Region New SimpleDB Fe
5、atures FPS General Availability Lower pricing tiers for Amazon CloudFront AWS Management Console Amazon EC2 with Windows Amazon EC2 in EU Region AWS Toolkit for Eclipse Amazon EC2 Reserved Instances AWS Import Export New CloudFront Feature Monitoring Auto Scaling Elastic Load Balancing Amazon Elasti
6、c MapReduce in Europe EBS Shared Snapshots SimpleDB in EU Region Monitoring Auto Scaling Elastic Load Balancing in EU Amazon CloudFront Private Content SAS70 Type II Audit AWS SDK for NET Amazon EC2 with Windows Server 2008 Spot Instances Boot from Amazon EBS Amazon CloudFront Streaming Amazon VPC e
7、nters Unlimited Beta AWS Region in Northern California International Support for AWS Import Export Amazon EC2 Reserved Instances with Windows Extra Large High Memory Instances Amazon S3 Versioning Feature Consolidated Billing for AWS Lower pricing for Outbound Data Transfer The Living and Evolving C
8、loud At Amazon Every Day is a Launch Day New Features and Services Scalability Characteristics of Truly Scalable Service Build Scalable Architecture on AWS A scalable architecture is critical to take advantage of a scalable infrastructure Increasing resources results in a proportional increase in pe
9、rformance A scalable service is capable of handling heterogeneity A scalable service is operationally efficient A scalable service is resilient A scalable service becomes more cost effective when it grows Cloud Architecture Lessons 1 Design for failure and nothing fails 2 Loose coupling sets you fre
10、e 3 Implement Elasticity 4 Build Security in every layer 5 Don t fear constraints 6 Think Parallel 7 Leverage different storage options using Amazon Web Services 1 Design for Failure Everything fails all the time Werner Vogels CTO A and nothing will really fail Avoid single points of failure Assume
11、everything fails and design backwards Goal Applications should continue to function even if the underlying physical hardware fails or is removed or replaced Design for Failure with AWS Tools to make your life easier Use Elastic IP addresses for consistent and re mappable routes Use multiple Amazon E
12、C2 Availability Zones AZs Create multiple database slaves across AZs Use real time monitoring Amazon CloudWatch Use Amazon Elastic Block Store EBS for persistent file systems EC2 Instance AEC2 Instance B YourWebTwoDotZeroN LOG Volume DATA Volume EC2 Instance A YourWebTwoDotZeroN LOG Volume DATA Volu
13、me EC2 Instance B Amazon S3 Availability Zone 1 Availability Zone 2 2 Build Loosely Coupled Systems The looser they re coupled the bigger they scale Independent components Design everything as a Black Box De coupling for Hybrid models Load balance clusters Controller AController BController C Contro
14、ller AController BController C QQQ Tight Coupling Loose Coupling using Queues Use Amazon SQS as Buffers MySQL Master Web Server MyWebS MySQL Slave App ServerApp Server LB Web Server LB App server Tapes Data Tier Database Server machines with master and local running separately Network storage for St
15、atic objects App Server Tier Fleet of machines handling Application specific workloads Caching server machines can be implemented at this layer App Load Balancer Hardware or Software solution to spread traffic over app servers Web Tier Fleet of machines handling HTTP requests Web Load Balancer Hardw
16、are or Software solution to distribute traffic over web servers Exterior Firewall Hardware or Software Solution to open standard Ports 80 443 Backend Firewall Limits access to application tier from web tier Backups on Tapes Periodic backups stored on Tapes usually managed by 3rd party at their site Availability Zone n Availability Zone 1 Auto scaling group App Tier Availability Zone 2 Auto scaling group Web TierAuto scaling group Web Tier RDS Master Web Server MyWebS ELB Web Tier App Server Clou
