Architecting for AWS - Carlos Conde - AWS Summit Paris

3,737 views

Published on

Architecture presentation given at AWS Summit Paris

Published in: Technology, Business
3 Comments
20 Likes
Statistics
Notes
No Downloads
Views
Total views
3,737
On SlideShare
0
From Embeds
0
Number of Embeds
57
Actions
Shares
0
Downloads
0
Comments
3
Likes
20
Embeds 0
No embeds

No notes for slide

Architecting for AWS - Carlos Conde - AWS Summit Paris

  1. 1. ARCHITECTING FOR AWSCarlos Conde │Solutions Architect
  2. 2. 1. ELASTICITY2. DESIGN FOR FAILURE3. LOOSE COUPLING4. SECURITY5. PERFORMANCE
  3. 3. # 1ELASTICITY ●○○○○
  4. 4. AMAZON EC2ELASTIC COMPUTE CLOUD
  5. 5. AMAZON CLOUDWATCHMONITORING FOR AWS RESOURCES
  6. 6. AUTO SCALINGSCALE UP/DOWN EC2 CAPACITY
  7. 7. ELASTIC LOAD BALANCINGNETWORK TRAFFIC DISTRIBUTION
  8. 8. 6 am
  9. 9. 10 am
  10. 10. 10 am
  11. 11. 10 am
  12. 12. 7 pm
  13. 13. 7 pm
  14. 14. 7 pm
  15. 15. without elasticity you cant accelerate
  16. 16. what you really need is… …adjustable capacityhttp://www.flickr.com/photos/purecaffeine/302682456/
  17. 17. # 2DESIGN FOR FAILURE ●●○○○
  18. 18. « Everything fails all the time » Werner Vogels CTO of Amazon
  19. 19. YOUR GOAL qApplications should continue to function even if the underlying physical hardware fails or is removed or replaced
  20. 20. Avoid single points of failure.Assume everything fails, anddesign backwards.
  21. 21. Avoid single points of failure.Assume everything fails, anddesign backwards.
  22. 22. AMAZON RDSRELATIONAL DATABASE SERVICE
  23. 23. AMAZONROUTE 53DOMAIN NAME SERVICE
  24. 24. AMAZON RDSMULTI-AZDEPLOYMENT
  25. 25. AMAZON CLOUDWATCH ALARMS
  26. 26. AWS BUILDING BLOCKSInherently Fault-Tolerant Fault-TolerantServices with the right Amazon S3  Elastic Load architecture Balancing Amazon SimpleDB  Amazon EC2  AWS IAM Amazon DynamoDB  Amazon EBS  AWS Elastic Amazon CloudFront Beanstalk  Amazon RDS Amazon SWF  Amazon  Amazon VPC Amazon SQS ElastiCache Amazon SNS  Amazon EMR Amazon SES  Amazon CloudSearch Amazon Route53
  27. 27. NETFLIXCHAOS MONKEY
  28. 28. # 3 LOOSECOUPLING ●●●○○
  29. 29. BUILD LOOSELYCOUPLED SYSTEMS q The looser the are coupled, the bigger they scale
  30. 30. Create independentcomponents
  31. 31. Create independentcomponentsDesign everything as aBlack Box
  32. 32. Create independentcomponentsDesign everything as aBlack BoxThink in terms of services
  33. 33. TRANSCODERECEIVE & PUBLISH
  34. 34. TRANSCODERECEIVE & PUBLISH QUEUE
  35. 35. AMAZON SQSSIMPLE QUEUE SERVICE
  36. 36. START CHECK REJECT STOP VIDEO YES NO TOO CAT / SPAM CAT? PUBLISH LONG? CHECK SPAM? & NOTIFYYES NOSHORTEN TRANSCODE VIDEO
  37. 37. AMAZON SWF WORKFLOW SERVICE FORSCALABLE, RESILIENT APPLICATIONS
  38. 38. AMAZON SWF Keeps track of :  State  Executed tasks  Timeouts  Errors
  39. 39. WORKFLOWACTORS
  40. 40. # 4SECURITY ●●●●○
  41. 41. AWS IAMIDENTITY AND ACCESS MANAGEMENT
  42. 42. MULTI-MULTI-FACTORAUTHENTICATION
  43. 43. SECURITY GROUPSLAYERED SECURITY
  44. 44. CERTIFICATIONS & COMPLIANCE SAS 70 Type II audit ISO 27001 Certification Sarbanes-Oxley SOX HIPAA healthcare FISMA US Federal Government DIACAP MAC III Sensitive IATO
  45. 45.  PCI DSS Compliant LEVEL 1 SERVICE PROVIDER
  46. 46. # 5PERFORMANCE ●●●●●
  47. 47. VERTICALSCALING
  48. 48. CLUSTER COMPUTEEIGHT EXTRA LARGE 2x Intel Xeon E5-2670, eight-core Sandy Bridge architecture 60.5 GB of memory – 3.3 TB of storage
  49. 49. CLUSTER GPUQUADRUPLE EXTRA LARGE Intel Xeon X5570, quad-core 2x Nehalem architecture NVIDIA Tesla Fermi 2x M2050 GPUs 22 GB of memory – 1.7 TB of storage
  50. 50. AMAZONELASTICACHEMEMCACHED COMPATIBLE IN-MEMORY CACHE
  51. 51. 1. ELASTICITY2. DESIGN FOR FAILURE3. LOOSE COUPLING4. SECURITY5. PERFORMANCE

×