cloud design patterns
（一部の日本の男から盗まれた）
....and other stuff
Multi-server pattern
Multi-az pattern
Floating Ip pattern
Dynamic Scale-out
Scheduled Scale-out
Clone Server Pattern
Bootstrap instance
Stack Deploy/Cloud formation
Server swap*
Weighted Transition
Elastic network interface
You can look it up yourself.
http://docs.amazonwebservices.com/
AWSEC2/latest/UserGuide/using-eni.html
Job Observer Pattern
Alphabet Soup
CloudFront, CloudSearch, CloudWatch, DevPay, DynamoDB, Beanstalk, EBS, EC2, EMR, Elasticache, FPS, FWS, Glacier, Mturk, RDS, Route 53*, SES, S3, SNS, SQS, SWF, SDB, VPC, CloudFormation, Import/Export, Storage Gateway, RedShift*, EDP*
Ok, what do we use?
CloudFront, CloudSearch, CloudWatch**, DevPay, DynamoDB,
Beanstalk, EBS, EC2, EMR*, ElastiCache, FPS,
FWS, Glacier*, Mturk, RDS, Route 53,
SES, S3, SNS, SQS, SWF, SDB, VPC,
CloudFormation, Import/Export, Storage Gateway, RedShift, EDP
New Stuff
RedShift
- Oy
Data Pipeline
- Cool, not super useful
here comes
the other
Stuff
Elastic block store
(this seems to be a weak point on their end)
EBS Volumes are replicated
- But only in AZs, not regions
- This means RDS is, too
ELASTIC BLOCK STORE
RAID on EBS
- Again, EBS is replicated
- No need for 1, 5, 0+1, 10
- Except other people are doing it
- Rumored to work in Windows!
- Provisioned I/O may just work better
Oh, by the way
There's a start-up penalty for each block
in an EBS volume
But it's not that bad
...ish.
Amazon recommends that, on Windows, you do a full partition of new EBS drives.
Obviously, we're not running into this brick wall.
Random Re:Invent notes
Virtual Private Cloud
- Internal Elastic LoadBalancers!
Did you know AMIs aren't multi-region?
- I didn't
- But we only use one [for now] ...