Architectural Design Patterns in Cloud Computing 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 find 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 Scalability Scale out or in depending on usage needs No Up Front Costs No contracts 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 Cloud AWS services and features Most Applications Need 1 Compute 2 Storage 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 Features 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 Veb Layer open IDn erne 5 Don t fear constraints Re think architectural constraints More RAM Distribute load across machines Shared distributed cache Better IOPS on my database Multiple read only sharding DB clustering Your hardware failed or messed up config simply throw it away and switch to new hardware with no additional cost Performance Caching at different levels Page Render DB Hardware Config does not match Implement Elasticity 6 Think Parallel Serial and Sequential is now history Experiment different architectures in parallel Multi treading and Concurrent requests to cloud services Run parallel MapReduce Jobs Decompose a Job into its simplest form 6 Leverage many storage options One size DOES NOT fit all Amazon S3 large static objects Amazon Cloudfront content distribution Amazon SimpleDB simple data indexing querying Amazon EC2 local disc drive transient data Amazon EBS persistent storage for any RDBMS Snapshots on S3 Amazon RDS RDBMS service Automated and Managed MySQL 6 Leverage many storage options Which storage option to use when Amazon S3 CF Amazon EC2 Ephemeral Store Amazon EBSAmazon SimpleDB Amazon RDS Ideal forStoring LargeStoring non Off instanceQuerying light Storing and write once persistentpersistentweight attributequerying read manytransientstorage for anydatastructured types ofupdateskind of data Relational and objects Staticreferential ContentData Distribution Ideal examplesMedia files Config Data Clusters bootQuerying Complex audio video scratch files data Log orMapping transactional images TempDBdata oftagging click systems Backups commercialstream logs inventory archives RDBMS likemetadata management versioningOracle DB2shared stateand order management fulfillment indexingsystems NotQuerying StoringRelational joins recommendedSearchingDatabase logsquery foror backups customer data NotDatabase FileSensitive dataContentOLTP DW cubeSimple recommendedSystemsDistributionrollupslookups examples Cloud Architecture Lessons Best Practices 1 Design for failure and nothing fails 2 Loose coupling sets you free 3 Design for dynamism 4 Build Security in every layer 5 Don t fear constraints 6 Think Parallel 7 Leverage many storage options AWS community and Ecosystem Find help guidance assistance when you need it AWS Ecosystem AWS Community Photo La Pedrera Casa Mil Barcelona Antonio Gaudi Migrating a Web Application to AWS Migrating your Web Application Step by Step towards AWS A typical Web App needs Compute Power Storage capacity Content Distribution Database storage Messaging Load balancing Monitoring Application Server Business Logic Web Server Presentation Layer Client Browser Database Migrating your Web Application 1 8 Typical Web App Architecture Store persistent files in Amazon S3 for lower costs higher reliability Client Browser Migrating your Web Application 2 8 Amazon S3 for Storage Use Amazon CloudFront Amazon CloudFront is a content delivery network that caches data stored in Amazon S3 across a network of 14 edge locations around the world Client Browser Migrating your Web Application 3 8 Amazon CloudFront for distribution Configure Amazon EC2 running your choice of web server to handle all incoming web requests Client Browser Migrating your Web Application 4 8 Amazon EC2 for your choice of web servers Configure multiple Amazon EC2 instances running your choice of application server to process requests Use Availability Zones and Elastic IPs for greater reliability and resiliency Utilize Auto scaling and Elastic LB service Client Browser Migrating your Web Application 4 8 Scale out App servers on Amazon EC2 Use Amazon