• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
ARC302 AWS Cloud Design Patterns - AWS re: Invent 2012
 

ARC302 AWS Cloud Design Patterns - AWS re: Invent 2012

on

  • 6,953 views

AWS Cloud Design Patterns (a.k.a. CDP) are generally repeatable solutions to commonly occurring problems in cloud architecting. In this session, we introduce CDP and explain how you can apply CDPs in ...

AWS Cloud Design Patterns (a.k.a. CDP) are generally repeatable solutions to commonly occurring problems in cloud architecting. In this session, we introduce CDP and explain how you can apply CDPs in practical scenarios such as photo sharing, e-commerce, and web site campaigns.

Statistics

Views

Total Views
6,953
Views on SlideShare
6,456
Embed Views
497

Actions

Likes
29
Downloads
0
Comments
2

6 Embeds 497

http://d.hatena.ne.jp 398
https://twitter.com 71
http://yoshidashingo.hatenablog.com 20
http://twitter.com 6
http://tweetedtimes.com 1
http://moderation.local 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel

12 of 2 previous next

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    ARC302 AWS Cloud Design Patterns - AWS re: Invent 2012 ARC302 AWS Cloud Design Patterns - AWS re: Invent 2012 Presentation Transcript

    • CDP
    • CDP
    • “This allows builders to create advanced models with simple parts”
    • Example of “Cloud Design Pattern” Amazon Route 53 “Floating IP Pattern” Elastic IP EC2 EC2
    • Floating AC Adaptor
    • “Weighted Transition” Pattern Route 53 α% 100-α% Elastic Load ELB Balancing (ELB) Web/AP Web/AP Web/AP Web/AP Web/AP Web/AP EC2 EC2 DB DB EC2 EC2
    • “Job Observer” Pattern CloudWatch Auto Scaling Put EC2 New SQS EC2 Get EC2
    • • Wanted to exchange servers with a shorter amount of down time• Solution (no AWS terminology) • Using IP address to exchange an existing server to a newly launched server Route 53• Implementation (AWS terminology) • Using EIP to exchange an existing EC2 instance to a Elastic IP newly launched one• Diagram• Pros • Can exchange servers regardless of DNS TTL EC2 EC2• Notes• Others
    • Other Examples Cache Distribution Direct Hosting Cache Proxy Deep Health Check Multi Data Center Stamp
    • Basic Static Contents Batch Processing Snapshot Web Storage Queuing Chain Stamp Direct Hosting Priority Queue Scale Up Private Distribution Job Observer On-Demand Disk Cache Distribution Scheduled Auto Scaling Rename DistributionAvailability Maintenance Multi-Server Data Uploading Bootstrap Multi Data Center Write Proxy Cloud DI Floating IP Storage Index Stack Deployment Deep Health Check Direct Object Upload Server Swapping Monitoring IntegrationScaling Relational Database Web Storage Archive Scale Out DB Replication Clone Server Read Replica Networking NFS Sharding In-Memory DB Cache On-Demand NAT NFS Replica Sharding Write Backnet State Sharing Functional Firewall URL Rewriting Operational Firewall Rewrite Proxy Multi Load Balancer Cache Proxy WAF Proxy Scheduled Scale Out CloudHub
    • “Amazon Web Services CDP – Design Guidebook”http://www.amazon.co.jp/dp/4822211967/“This was a test marketing in Japan, and it worked very well! Now we started translating this into English!”
    • http://aws.clouddesignpattern.org - “sorry, Japanese only!”
    • • Example of Implementation Scenario • Content Distribution • Distribute static content to large number of users • E-Commerce • Implement fault-tolerance application • Campaign Site • Deal with unpredictable massive traffic • and others… • Streaming, batch processing, monitoring, VPC migration, etc.
    • Content Distribution Scenario
    • Environments Amazon Linux (64bit) Movable Type 5.12 (MTOS) Apache HTTP Server 2.2.21 MySQL 5.1.52 Perl 5.10.1 S3FS 1.61 21
    • Initial Design Amazon www.clouddesignpattern.org Route 53 EIP Blog System EC2 Instance (t1.micro) 22
    • manseki.exblog.jp
    • ProblemNeed to distribute photos andvideos in a cost-effective way offloadImplementationHost heavy files by Amazon S3 Web(web hosting feature) and users S3 EC2will download them from S3directly
    • Apply “Web Storage” Pattern data.clouddesignpattern.org www.clouddesignpattern.org EIP Download Link Blog Videos System S3 EC2 Instance (t1.micro) 25
    • rocketnews24.com
    • ProblemNeed to host website in acost-effective wayImplementation upload WebUse Amazon S3 website hostingfeature. Dynamically upload EC2updated contents from Amazon S3EC2
    • Apply “Direct Hosting” Pattern data.clouddesignpattern.org www.clouddesignpattern.org EIP Blog System 28
    • Editor’s choice : No1 “Clouds” blog
    • Apply “Cache Distribution” Pattern Blog contents www.clouddesignpattern.org www.clouddesignpattern.org.s3.amazonaws.com Videos/Images data.clouddesignpattern.org data.clouddesignpattern.org.s3.amazonaws.com Blog post Blog posting/ Search Management EIP mt.clouddesignpattern.org 30
    • Web Storage Direct Hosting Cache Distribution
    • E-Commerce Site Scenario
    • Environments Amazon Linux (64bit) Apache HTTP Server 2.2.21 EC-Cube 2.11.3 PHP 5.3.8 MySQL 5.1.52 34
    • Initial Design Amazon ec.clouddesignpattern.org Route 53 EIP EC System EC2 Instance (t1.micro) 35
    • Apply “Floating IP” Amazon Route 53 ec.clouddesignpattern.org EIP ④change EIPEIP「46.51.xxx.xxx」 Prod Test ③Updating and testing EC2 EC2 ①Create AMI ②Launch Test environment EC2 AMI 37
    • @Studio 4Directions
    • Apply “Server Swapping” EC2 EC2 Data Data AMI EBS EBS 39
    • Apply “Multi-Server” ELB Original Duplicate EC2 EC2 DB Instance 41
    • 42
    • Apply “Multi-Server” ELB Original Duplicate EC2 EC2 DB Instance 43
    • Adding EC2 instances
    • Apply “DB Replication” ELB Original Duplicate EC2 EC2 Sync AZ - 1a AZ – 1b 49
    • @gigazine
    • Apply “Multi Data Center” ELB Original Duplicate EC2 EC2 Sync AZ - 1a AZ – 1b 51
    • Server Swapping Multi Server DB replication Multi Data Center
    • Campaign Site Scenario
    • Environments Amazon Linux (32bit) Apache HTTP Server 2.2.21 MySQL 5.1.52 PHP 5.3.8 WordPress 3.3.1 55
    • Initial Design• Small start• Stand-alone server configuration 56
    • Apply “Clone Server” Pattern 58
    • Apply “Scale Out” Pattern 59
    • Apply “NFS Sharing” Pattern NFS 61
    • Apply “NFS Replica” Pattern 63
    • Apply “URL Rewriting” Pattern• Off-load static contents to S3• Rewrite the URLs by using mod_ext_filter 65
    • http://aws.clouddesignpattern.org• https://www.facebook.com/awscdp http://www.amazon.co.jp/dp/4822211967/• Created by ARCHITYP• http://www.archetyp.jp
    • We are sincerely eager to hear your feedback on thispresentation and on re:Invent. Please fill out an evaluation form when you have a chance.