Your SlideShare is downloading. ×
0
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Architecting for AWS
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Architecting for AWS

4,826

Published on

Published in: Business, Technology
0 Comments
21 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
4,826
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
464
Comments
0
Likes
21
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. ARCHITECTING FOR AWSCarlos Conde │Solutions Architect
  • 2. 1. ELASTICITY2. DESIGN FOR FAILURE3. LOOSE COUPLING4. SECURITY5. PERFORMANCE
  • 3. # 1ELASTICITY ●○○○○
  • 4. AMAZON EC2ELASTIC COMPUTE CLOUD
  • 5. AMAZON CLOUDWATCHMONITORING FOR AWS RESOURCES
  • 6. AUTO SCALINGSCALE UP/DOWN EC2 CAPACITY
  • 7. ELASTIC LOAD BALANCINGNETWORK TRAFFIC DISTRIBUTION
  • 8. 6 am
  • 9. 10 am
  • 10. 10 am
  • 11. 10 am
  • 12. 7 pm
  • 13. 7 pm
  • 14. 7 pm
  • 15. without elasticity you cant accelerate
  • 16. what you really need is… …adjustable capacity
  • 17. # 2DESIGN FOR FAILURE ●●○○○
  • 18. « Everything fails all the time » Werner Vogels CTO of Amazon
  • 19. YOUR GOALApplications should continue to function even if the underlying physical hardware fails or is removed or replaced
  • 20. Avoid single points of failure.Assume everything fails, and designbackwards.
  • 21. Avoid single points of failure.Assume everything fails, and designbackwards.
  • 22. AMAZON RDSRELATIONAL DATABASE SERVICE
  • 23. AMAZONROUTE 53DOMAIN NAME SERVICE
  • 24. AMAZON RDSMULTI-AZDEPLOYMENT
  • 25. AMAZON CLOUDWATCH ALARMS
  • 26. AWS BUILDING BLOCKSInherently Fault-Tolerant Services Fault-Tolerant with the right architecture Amazon S3  Elastic Load Balancing  Amazon EC2 Amazon SimpleDB  AWS IAM  Amazon EBS Amazon DynamoDB  AWS Elastic  Amazon RDS Amazon CloudFront Beanstalk Amazon SWF  Amazon VPC  Amazon Amazon SQS ElastiCache Amazon SNS  Amazon EMR Amazon SES  Amazon CloudSearch Amazon Route53
  • 27. NETFLIXCHAOS MONKEY
  • 28. # 3 LOOSECOUPLING ●●●○○
  • 29. BUILD LOOSELYCOUPLED SYSTEMS The looser the are coupled, the bigger they scale
  • 30. Create independent components
  • 31. Create independent componentsDesign everything as a Black Box
  • 32. Create independent componentsDesign everything as a Black BoxThink in terms of services
  • 33. TRANSCODERECEIVE & PUBLISH
  • 34. TRANSCODERECEIVE & PUBLISH QUEUE
  • 35. AMAZON SQSSIMPLE QUEUE SERVICE
  • 36. START CHECK REJECT STOP VIDEO YES NO TOO SPAM PUBLISH SPAM? LONG? CHECK & NOTIFYYES NO SHORTEN TRANSCODE VIDEO
  • 37. MAINTENANCEAUDITABILITYFLEXIBILITYLOW-LEVEL
  • 38. WHAT ARE WETRYING TO DO?
  • 39. START CHECK REJECT STOP VIDEO YES NO TOO SPAM PUBLISH SPAM? LONG? CHECK & NOTIFYYES NO SHORTEN TRANSCODE VIDEO
  • 40. START CHECK REJECT STOP VIDEO YES NO TOO SPAM PUBLISH SPAM? LONG? CHECK & NOTIFYYES NO SHORTEN TRANSCODE VIDEO
  • 41. START CHECK REJECT STOP VIDEO YES NO TOO SPAM PUBLISH SPAM? LONG? CHECK & NOTIFYYES NO SHORTEN TRANSCODE VIDEO
  • 42. TASKSDECISIONS STATELESS ! HISTORY
  • 43. STATELESS SCALES HORIZONTALLY
  • 44. AMAZON SWFWORKFLOW SERVICE FOR SCALABLE, RESILIENT APPLICATIONS
  • 45. AMAZON SWF Keeps track of :  State  Executed tasks  Timeouts  Errors
  • 46. WORKFLOWACTORS
  • 47. DECIDERS COORDINATION LOGIC1. Poll for work on a decision list Long polling: 60 seconds2. Evaluate workflow execution history SWF sends full history in JSON format3. Return decision to Amazon SWF Usually scheduling another task
  • 48. WORKERS COORDINATION LOGIC1. Poll for work on a specific task list Long polling: 60 seconds2. Execute works, send heartbeats SWF sends input data from deciders3. Return success / failure Detailed data can be provided to deciders
  • 49. ALLHORIZONTAL SCALING PATTERNS APPLY
  • 50. NO NEW LANGUAGE TO LEARNYOUR CODE IS YOUR WORKFLOW LANGUAGE SWF MAINTAINS STATE
  • 51. AWS FLOW FRAMEWORKJava Library • Entire workflow can be expressed in sequential code • Integrated with Java Utils API
  • 52. CHAINED TASKS WITHOUT DECISIONS?RECEIVE TRANSCODE NOTIFY use AMAZON SQS
  • 53. TASK GRAPH WITH DECISIONS? GOOD OKRECEIVE CHECK SPAM TRANSCODE VIDEO LENGTH CHECK LONG SPAM SHORTEN PUBLISH REJECT VIDEO & NOTIFY use AMAZON SWF
  • 54. # 4SECURITY ●●●●○
  • 55. AWS IAMIDENTITY AND ACCESS MANAGEMENT
  • 56. MULTI-MULTI-FACTORAUTHENTICATION
  • 57. SECURITY GROUPS LAYERED SECURITY
  • 58. CERTIFICATIONS& COMPLIANCE SAS 70 Type II audit ISO 27001 Certification Sarbanes-Oxley SOX HIPAA healthcare FISMA US Federal Government DIACAP MAC III Sensitive IATO
  • 59.  PCI DSS Compliant LEVEL 1 SERVICE PROVIDER
  • 60. # 5PERFORMANCE ●●●●●
  • 61. VERTICALSCALING
  • 62. CLUSTER COMPUTEEIGHT EXTRA LARGE 2x Intel Xeon E5-2670, eight-core Sandy Bridge architecture 60.5 GB of memory – 3.3 TB of storage
  • 63. 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
  • 64. AMAZONELASTICACHEMEMCACHED COMPATIBLE IN-MEMORY CACHE
  • 65. SEARCHENGINES
  • 66. Relevance & Ranking
  • 67. Faceting
  • 68. RangeSearching
  • 69. AMAZONCLOUDSEARCHFULLY-MANAGED SEARCH SERVICE
  • 70. +
  • 71. DEMOCRATIZE SEARCH Amazon CloudSearch delivers a fully-managed search service in the cloudthat can be set up and running in less than 1 hour, with automatic scaling for data & traffic, at a price starting at less than $100 per month.
  • 72. HTTP POST author=carlos;date=2012-06-07; article=text; …
  • 73. MEDIA SHARINGREFERENCE ARCHITECTURE
  • 74. HTTP POST author=carlos;date=2012-06-07; article=text; … +
  • 75. 1. ELASTICITY2. DESIGN FOR FAILURE3. LOOSE COUPLING4. SECURITY5. PERFORMANCE
  • 76. « If youre not embarrassed when you ship your first version you waited too long » Matt Mullenweg CEO & Founder of WordPress

×