17
Building for the Cloud Architecting Applications for the Cloud – The Key to Success in AWS Bob Harris - CTO Channel 4 Television
| Date post: | 22-Apr-2015 |
| Category: |
Technology |
| Upload: | amazon-web-services |
| View: | 913 times |
| Download: | 2 times |
Building for the Cloud
Architecting Applications for the Cloud –
The Key to Success in AWS
Bob Harris - CTO Channel 4 Television
C4 and AWS
• Discovered AWS (EC2) in mid 2008
• Launched our first applications in September 2008
C4 and AWS
C4 and AWS
• Discovered AWS (EC2) in mid 2008
• Launched our first applications in September 2008
• Began with simple applications; complexity grew with experience
• Today, AWS is our “Platform of Choice” for all web-facing applications
• Selected Elastic Map Reduce to underpin our Big Data initiatives in 2011
Why do C4 use AWS?
• Agility
– Reduced time to build and deploy new platforms and applications
– Increased productivity in Teams moving toward a DevOps approach
• Scalability & Resilience
– We deploy inherently resilient applications with minimal additional cost
– Ability to align platform capacity with “peaky” workloads
Why do C4 use AWS?
Why do C4 use AWS?
• Agility
– Reduced time to build and deploy new platforms and applications
– Increased productivity in Teams moving toward a DevOps approach
• Scalability & Resilience
– We deploy inherently resilient applications with minimal additional cost
– Ability to align platform capacity with “peaky” workloads
• Cost Management
– Lower TCO than our physical infrastructure (Measured)
– Capex to Opex
Approaching AWS
• Familiarisation
– Read the “Overview of Amazon Web Services” Whitepaper
– Create an account – Fire-up the console
Approaching AWS
Approaching AWS
• Familiarisation
– Read the “Overview of Amazon Web Services” Whitepaper
– Create an account – Fire-up the console
• Take Security Head-On
– Involve your CISO and Internal Audit from the outset
– Read the “Overview of Security Processes” Whitepaper
• Take a test-drive
– Migrate an existing application
– But watch-out for the limitations of vertical scaling!
Architecting for AWS
• Don’t be tempted to re-invent the wheel
– Choose from the vast range of pre-configured AMIs
Architecting for AWS
Architecting for AWS
• Don’t be tempted to re-invent the wheel
– Choose from the vast range of pre-configured AMIs
• Design security in up-front
– Read the AWS Virtual Private Cloud User Guide
• Architect for Horizontal Scaling
– Look at Autoscaling, Cloudwatch
Architecting for AWS
Auto scaling Group
Availability Zone
Region
EC2 Instance 1
EC2 Instance 2
EC2 Instance 4
EC2 Instance 3
Architecting for AWS
• Don’t be tempted to re-invent the wheel
– Choose from the vast range of pre-configured AMIs
• Design security in up-front
– Read the AWS Virtual Private Cloud User Guide
• Architect for Horizontal Scaling
– Look at Autoscaling, Cloudwatch
• Design for Failure
– Start with an inherently resilient design – Multi AZ, Multi Region
Beyond IaaS
• Review your operational practices
– Evolve your operational approach as you grow
– To maximise productivity migrate toward DevOps
• Check-out Platform as a Service (PaaS)
– Huge productivity gains during development
– Pay particular attention to Dynamo, RedShift, and Glacier
• Looking at Big Data?
– Investigate Elastic Map Reduce the SaaS (Software as a Service)
Hadoop implementation
