 |
|
| FriendFeed is the easiest way to share online. Learn more » |
Amazon Cloud Comp Workshop 6/2010:
Dawei lin
Matt Tavis, AWS Solutions architect: Architecting for the AWS Cloud
June 8, 2010
- Comment
- Like
- Share
Has a German Literature degree
- Dawei lin
working with customer to discuss what works and work do not works
- Dawei lin
Cloud Best practice while paper is online
- Dawei lin
Scalability: a scalable architecture to take advantage of scalable infrastructure (Amazon)
- Dawei lin
Design for Failure ( HW/SW)
- Dawei lin
Everything fails, all the time, Werner Vogels, CTO Amazon.com
- Dawei lin
Avoid single points of failture, assume everything fails, and design backwards. Application should run even HW fails
- Dawei lin
2. Loose coupling sets you free
- Dawei lin
decouple layers can make architecture more resilient
- Dawei lin
It is a function of Amazon SNS.
- Dawei lin
3. Implement Elasticity, a fundamental property of the cloud
- Dawei lin
Configuration overhead is a significant for cloud computing because the time to startup a server is short
- Dawei lin
Self configuration is important
- Dawei lin
4. Build Security in every later
- Dawei lin
each machine can be locked down in cloud
- Dawei lin
With cloud, physical control reduced but not ownership
- Dawei lin
Three tier approach: Web, App, DB security group
- Dawei lin
5. Do not fear constraints
- Dawei lin
More RAM, can it be split?
- Dawei lin
That may drive to good architectural change
- Dawei lin
Better IOPS on my database? multiple readlony/sharding/DB
- Dawei lin
6. Think Parallel (serial and sequential is now history)
- Dawei lin
Run parallel MapReduce jobs, use Elastic Load Balancing to distribute load across multiple servers.
- Dawei lin
7. Leverage many storage options
- Dawei lin
S3 large static objects, CloudFront: content distribution, SimpleDB: simple data indexing/querying, EC2 local disc drive: transient data
- Dawei lin
EBS for off-instance persistent
- Dawei lin