AWS Enterprise Summit London 2013 - Bob Harris - Channel 4

834 views
656 views

Published on

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

  • Be the first to like this

No Downloads
Views
Total views
834
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
54
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

AWS Enterprise Summit London 2013 - Bob Harris - Channel 4

  1. 1. Building for the Cloud Architecting Applications for the Cloud – The Key to Success in AWS Bob Harris - CTO Channel 4 Television
  2. 2. C4 and AWS • Discovered AWS (EC2) in mid 2008 • Launched our first applications in September 2008
  3. 3. C4 and AWS
  4. 4. 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
  5. 5. 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
  6. 6. Why do C4 use AWS?
  7. 7. 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
  8. 8. Approaching AWS • Familiarisation – Read the “Overview of Amazon Web Services” Whitepaper – Create an account – Fire-up the console
  9. 9. Approaching AWS
  10. 10. 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!
  11. 11. Architecting for AWS • Don’t be tempted to re-invent the wheel – Choose from the vast range of pre-configured AMIs
  12. 12. Architecting for AWS
  13. 13. 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
  14. 14. Architecting for AWS Auto scaling Group Availability Zone Region EC2 Instance 1 EC2 Instance 2 EC2 Instance 4 EC2 Instance 3
  15. 15. 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
  16. 16. 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
  17. 17. That’s all Folks! bharris@channel4.co.uk @bobharrisuk uk.linkedin.com/in/bobharrisuk01

×