• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Leveraging Amazon Web Services for Scalable Media Distribution and Analytics - Kingsley Wood, Amazon Web Services
 

Leveraging Amazon Web Services for Scalable Media Distribution and Analytics - Kingsley Wood, Amazon Web Services

on

  • 1,228 views

 

Statistics

Views

Total Views
1,228
Views on SlideShare
1,226
Embed Views
2

Actions

Likes
7
Downloads
0
Comments
0

1 Embed 2

https://twitter.com 2

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • In this webinar I am going to introduce Amazon Web Services, also known as AWS, and some of the fundamental concepts behind the Amazon Cloud.
  • And just like an electricity grid, where you would not wire every factory to the same power station, the AWS infrastructure is global, with multiple regions around the globe from which services are available. This means you have control over things like where you applications run, where you data is stored, and where best to serve your customers from.
  • Each AWS region is also split into Availability Zones, making highly available applications possible from within a region.
  • And the whole footprint is supported by many edge locations, places from which content can be served to your customers for the fast possible response times.
  • Let's take a quick look at what that means with a tangible example. Here, two commands are issued against AWS to create servers, or EC2 instances, in two zones in the EU. We're creating 8 instances of differing sizes, running geopgrahically distinct for availability purposes, all from 2 simple commands. Once booted, in a matter of a minute or two, those server instances are available to you to run your own applications on. Amazon has done the heavy lifting for you, so you can focus on using the compute resources available to you.
  • and lastly, by way of illustration, creating an auto-scaling group that will expand to 200 servers if a spike in load occurs, changing firewall rules and adding load balancing.
  • And of course, all of this functionality is available through a web console, so whether you want to drive the cloud by the click of a mouse or the call of an API, the power is at your disposal.
  • The comfort you gain from knowing that your users won't be presented with messages such as 503 response codes mean you can sleep easy.
  • Elasticity works from just 1 EC2 instance to many thousands. Just dial up and down as required.
  • Back in 2008, they launched a Facebook application that lets people tell their friends when they've uploaded a video that includes that friend. When people saw the music videos their friends created when the application shared it with them, they wanted to go out and create their own videos. Shortly after launching their social networking modification, they were featured on Techcrunch. As you can imagine, this brought them a lot of unexpected traffic. In the course of 3 days, they went from running on 40 instances to 5,000 instances. Because they were using Amazon Web Services, they were able to handle all of this incoming traffic without having to do a thing. AWS managed it all for them.
  • Our goal, and what our customers tell us they see, is that this ratio is inverted after moving to AWS. When you move your infrastructure to the cloud, this changes things drastically. Only 30% of your time should be spent architecting for the cloud and configuring your assets. This gives you 70% of your time to focus on your business. Project teams are free to add value to the business and it's customers, to innovate more quickly, and to deliver products to market quickly as well.
  • Our goal, and what our customers tell us they see, is that this ratio is inverted after moving to AWS. When you move your infrastructure to the cloud, this changes things drastically. Only 30% of your time should be spent architecting for the cloud and configuring your assets. This gives you 70% of your time to focus on your business. Project teams are free to add value to the business and it's customers, to innovate more quickly, and to deliver products to market quickly as well.
  • services that are normally expensive to manage or difficult to use become available on-demand, in a uniform and available way, and only paid for when used. Just like electricity.This is what AWS does. It takes away the hard work from providing infrastructure IT services and makes them available to anyone on a pay as you go basis.
  • In this webinar I am going to introduce Amazon Web Services, also known as AWS, and some of the fundamental concepts behind the Amazon Cloud.

Leveraging Amazon Web Services for Scalable Media Distribution and Analytics - Kingsley Wood, Amazon Web Services Leveraging Amazon Web Services for Scalable Media Distribution and Analytics - Kingsley Wood, Amazon Web Services Presentation Transcript

  • Leveraging Amazon Web Services for Scalable Media Distribution and Analytics Kingsley Wood Business Development Manager
  • On a global footprint Region US-WEST (N. California) EU-WEST (Ireland) GOV CLOUD ASIA PAC (Tokyo) US-EAST (Virginia) US-WEST (Oregon) ASIA PAC (Singapore) SOUTH AMERICA (Sao Paulo) ASIA PAC (Sydney)
  • On a global footprint Availability Zone
  • On a global footprint Edge Locations London(2) Seattle New York (2) South Bend Amsterdam Newark Stockholm Dublin Palo Alto Tokyo Seoul San Jose Frankfurt(2) Paris(2) Ashburn(2) Los Angeles (2) Milan Osaka Jacksonville Hong Kong Dallas(2) St.Louis India (2) Miami Singapore(2) Sao Paulo Sydney
  • At the end of a web service ec2-run-instances ami-b232d0db --instance-count 3 --availability-zone eu-west-1a --instance-type m1.small ec2-run-instances ami-b232d0db --instance-count 5 --availability-zone eu-west-1c --instance-type m1.medium
  • At the end of a web service ec2-authorize default -p 80 elb-create-lb myLoadBalancer as-create-auto-scaling-group MyGroup --launch-configuration MyConfig --availability-zones eu-west-1c --min-size 2 --max-size 200
  • and rich console services
  • 503 Service Temporarily Unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
  • 503 Service Temporarily Unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
  • From one instance…
  • …to thousands
  • 40 servers to 5000 in 3 days Number of EC2 Instances EC2 scaled to peak of 5000 instances “Techcrunched” Launch of Facebook modification Steady state of ~40 instances 4/12/2008 4/13/2008 4/14/2008 4/15/2008 4/16/2008 4/17/2008 4/18/2008 4/19/2008 4/20/2008
  • Delivering scalable, cost-efficient websites
  • Rule 1: Service all web requests a) Make sure requests get to your ‘front door’ DNS Application Data
  • Rule 1: Service all web requests a) Make sure requests get to your ‘front door’ Request DNS Application Data
  • Rule 1: Service all web requests a) Make sure requests get to your ‘front door’ Request DNS Application Data
  • Rule 1: Service all web requests a) Make sure requests get to your ‘front door’ Request DNS Clients can’t resolve you? Application Data …then this is irrelevant
  • Rule 1: Service all web requests a) Make sure requests get to your ‘front door’ Request DNS Application Feature Global “100% Available” SLA Route53 Scalable Latency based routing Integrated http://aws.amazon.com/route53/sla Secure Data Details Supported from AWS global edge locations for fast and reliable domain name resolution Automatically scales based upon query volumes Supports resolution of endpoints based upon latency, enabling multiregion application delivery Integrates with other AWS services allowing Route 53 to front load balancers, S3 and EC2 Integrates with IAM giving fine grained control over DNS record access
  • Rule 1: Service all web requests a) Make sure requests get to your ‘front door’ b) Make sure you open the door when they arrive Request DNS Route53 Application Data
  • Rule 1: Service all web requests a) Make sure requests get to your ‘front door’ b) Make sure you open the door when they arrive Request Data Application DNS Region Availability Zone Elastic load balancing Multi-availability zone Multi-region Availability Zone Route53 Availability Zone Elastic Load Balancer Availability Zone Region
  • Rule 1: Service all web requests a) Make sure requests get to your ‘front door’ b) Make sure you open the door when they arrive c) Have the data to form a response Request Data Application DNS Region Availability Zone Availability Zone Route53 Availability Zone Elastic Load Balancer Availability Zone Region
  • Rule 1: Service all web requests a) Make sure requests get to your ‘front door’ b) Make sure you open the door when they arrive c) Have the data to form a response Request Application DNS Data Region Multi-AZ RDS Availability Zone (Master-slave) Inter-region replication Availability Zone Route53 Availability Zone Read-replicas Elastic Load Balancer Availability Zone Region
  • Rule 2: Service requests as fast as possible
  • Rule 2: Service requests as fast as possible a) Choose the fastest route Request Region A Route53 Region B
  • Rule 2: Service requests as fast as possible a) Choose the fastest route Request 16ms Region A Route53 92ms Region B
  • Rule 2: Service requests as fast as possible a) Choose the fastest route Request 16ms Region A Route53 92ms Region B
  • Rule 2: Service requests as fast as possible a) Choose the fastest route Request Region A DNS entry Route53 16ms Region A Region B
  • Rule 2: Service requests as fast as possible a) Choose the fastest route b) Offload your application servers CloudFront 3 Served from S3 World-wide content distribution network /images/* Easily distribute content to end users with low latency, high data transfer speeds, and no commitments. 2 London Served from EC2 *.php Paris 1 Single CNAME www.mysite.com NY
  • Rule 2: Service requests as fast as possible a) Choose the fastest route b) Offload your application servers Without CloudFront EC2 webservers/app servers loaded by user requests
  • Rule 2: Service requests as fast as possible a) Choose the fastest route b) Offload your application servers With CloudFront Load of user requests pushed into CloudFront, EC2 cluster can scale down Offload Scale Down
  • Rule 2: Service requests as fast as possible a) Choose the fastest route b) Offload your application servers CDN for CDN for Static Static & Content No CDN Dynamic Content Server Load Response Time Server Load Response Time Server Load Response Time Offload Scale Down
  • Rule 2: Service requests as fast as possible a) Choose the fastest route b) Offload your application servers c) Cache it if you can ElastiCache Memcached and redis compatible caching layer Serve frequently requested & slow changing data from scalable cache clusters Reduce load on database and other servers
  • Rule 2: Service requests as fast as possible Database Query Performance a) b) c) d) Choose the fastest route Offload your application servers Cache it if you can Single digit latencies where it matters Desired consistency, predictability Scale
  • Rule 2: Service requests as fast as possible Database Query Performance a) b) c) d) Choose the fastest route Offload your application servers Cache it if you can Single digit latencies where it matters Desired consistency, predictability Actual degraded performance with scale Scale
  • Rule 2: Service requests as fast as possible Database Query Performance a) b) c) d) Choose the fastest route Offload your application servers Cache it if you can Single digit latencies where it matters Desired consistency, predictability Management problems Data sharding Data caching Provisioning Cluster management Fault management Actual degraded performance with scale Scale
  • Rule 2: Service requests as fast as possible Database Query Performance a) b) c) d) Choose the fastest route Offload your application servers Cache it if you can Single digit latencies where it matters DynamoDB Dynamo DB Query Performance Low latency Large scale Zero admin Predictable performance Relational Database Query Performance Scale
  • Rule 2: Service requests as fast as possible Database Query Performance a) b) c) d) Choose the fastest route Offload your application servers Cache it if you can Single digit latencies where it matters DynamoDB Dynamo DB Query Performance Low latency Large scale Zero admin Predictable performance Average single-digit milliseconds server side latencies Runs on solid state drives, and is built to maintain consistent, fast latencies at any scale Scale
  • Rule 3: Handle requests at any scale a) Scale up Vertical Scaling From $0.02/hr Scale up with Elastic Compute Cloud (EC2) Basic unit of compute capacity Range of CPU, memory & local disk options 20 Instance types available, from micro through cluster compute to SSD backed
  • Rule 3: Handle requests at any scale a) Scale up b) Scale out as-create-auto-scaling-group MyGroup --launch-configuration MyConfig --availability-zones eu-west-1a --min-size 4 --max-size 200 Trigger auto-scaling policy Auto-scaling Automatic re-sizing of compute clusters based upon demand
  • Rule 3: Handle requests at any scale a) Scale up b) Scale out c) Dial it up Elastic Block Store DynamoDB Provisioned IOPS up to 4000 per EBS Provisioned read/write performance per volume table Predictable performance for Predictable high performance scaled via demanding workloads such as console or API databases
  • DynamoDB: over 500,000 writes per second Amazon EMR: more than 1 million writes per second “AWS gave us the flexibility to bring a massive amount of capacity online in a short period of time and allowed us to do so in an operationally straightforward way. AWS is now Shazam’s cloud provider of choice,” Jason Titus, CTO
  • Rule 4: Simplify architecture with services 30% On-Premise Infrastructure 70% Your Business Managing All of the “Undifferentiated Heavy Lifting”
  • Rule 4: Simplify architecture with services 30% On-Premise Infrastructure AWS Cloud-Based Infrastructure 70% Your Business Managing All of the “Undifferentiated Heavy Lifting” More Time to Focus on Your Business 70% Configuring Your Cloud Assets 30%
  • Rule 4: Simplify architecture with services Relational Database Service Use RDS for databases No need to install or manage database instances Scalable and fault tolerant configurations MySQL, PostgreSQL, Oracle and SQL Server DynamoDB Provisioned throughput NoSQL database Fast, predictable performance Fully distributed, fault tolerant architecture Use DynamoDB for high performance keyvalue DB
  • Rule 4: Simplify architecture with services Amazon SQS Reliable message queuing without additional software Reliable, highly scalable, queue service Processing results for storing messages as they travel Amazon SQS between instances 1 Processing task/processing 2 trigger Push inter-process workflows into the cloud with SWF Simple Workflow Task A Reliably coordinate processing steps across applications Task B 3 (Auto-scaling) Integrate AWS and non-AWS resources Manage distributed state in complex systems Task C
  • Rule 4: Simplify architecture with services Cloud Search Don’t install search software, use CloudSearch Document Server Elastic search engine based upon Amazon A9 search engine Fully managed service with Search Server sophisticated feature set Scales automatically Results Elastic MapReduce Elastic Hadoop cluster Integrates with S3 & DynamoDB Leverage Hive & Pig analytics scripts Integrates with instance types such as spot Process large volumes of data cost effectively with EMR
  • Rule 5: Automate operational management a) Everything is programmable Access everything via CLI, API or Console Compute Security Scaling CDN Backup DNS Database Storage Load Balancing Workflow Monitoring Networking Messaging Achieve the highest levels of automation sophistication with ease
  • Rule 5: Automate operational management a) Everything is programmable b) Think disposable, one click deployments Cloud Formation Automate creation of ‘stacks’ in a repeatable way Scripting framework for AWS resource creation Feature Platform support Details Support for AWS resources from EC2 to IAM Resource creation Creates AWS resources behind the scenes and reports on progress Declarative Specify stacks in JSON format and source control your environments Customizable Drive stack creation with paramaters
  • Rule 5: Automate operational management a) Everything is programmable b) Think disposable, one click deployments c) Design for failure, implement self healing Bootstrapping Auto-scaling Cloud Watch Customize instance startup Maintain capacity of instances Get instances to ask ‘who am I?’ question on startup and be configured dynamically upon being asnwered Using a minimum pool size will maintain capacity in the event of instance failures Know what’s going on, take automated actions Use CloudWatch standard and custom metrics to create alarms. Respond with automated administration actions
  • Rule 5: Automate operational management a) Everything is programmable b) Think disposable, one click deployments c) Design for failure, implement self healing
  • Rule 6: Leverage unique cloud properties a) Optimize costs with instance types Hi-Mem 4XL 68.4 GB 26 ECUs 8 virtual cores Cluster Compute 8XL 60.5 GB 88 ECUs 8 core 2 x Intel Xeon Hi-Mem 2XL 34.2 GB 13 ECUs 4 virtual cores Cluster Compute 4XL 23 GB 33.5 ECUs 8 Nehalem virtual cores Hi-Mem XL 17.1 GB 6.5 ECUs 2 virtual cores Extra Large 15 GB 8 ECUs 4 virtual cores Large 7.5 GB 4 ECUs 2 virtual cores Small 1.7 GB, 1 ECU 1 virtual core Micro 613 MB Up to 2 ECUs (for short bursts) Medium 3.75 GB 2 ECUs 1 virtual cores High-CPU Med 1.7 GB 5 ECUs 2 virtual cores Cluster GPU 4XL 22 GB 33.5 ECUs 8 Nehalem virtual cores 2 x NVIDIA Tesla “Fermi” M2050 GPUs High-CPU XL 7 GB 20 ECUs 8 virtual cores
  • Rule 6: Leverage unique cloud properties a) Optimize costs with instance types On-demand instances Reserved instances Spot instances Unix/Linux instances start at $0.02/hour 1- or 3-year terms Bid on unused EC2 capacity Pay as you go for compute power Pay low up-front fee, receive significant hourly discount Spot Price based on supply/demand, determined automatically Low cost and flexibility Low Cost / Predictability Cost / Large Scale, dynamic workload handling Pay only for what you use, no up-front commitments or long-term contracts Helps ensure compute capacity is available when needed Use Cases: Applications with short term, spiky, or unpredictable workloads; Application development or testing Use Cases: Use Cases: Applications with flexible start and end times Applications with steady state or predictable usage Applications only feasible at very low compute prices Applications that require reserved capacity, including disaster recovery
  • Rule 6: Leverage unique cloud properties a) Optimize costs with instance types 7000 6000 Spot 5000 4000 On Demand 3000 2000 Reserved Instances 1000 0
  • Rule 6: Leverage unique cloud properties a) Optimize costs with instance types b) Get insight fast with Elastic MapReduce Elastic MapReduce Feature Details Managed, elastic Hadoop cluster Scalable Use as many or as few compute instances running Hadoop as you want. Modify the number of instances while your job flow is running Integrates with S3 & DynamoDB Leverage Hive & Pig analytics scripts Integrates with instance types such as spot Integrated with other services Works seamlessly with S3 as origin and output. Integrates with DynamoDB Comprehensive Supports languages such as Hive and Pig for defining analytics, and allows complex definitions in Cascading, Java, Ruby, Perl, Python, PHP, R, or C++ Cost effective Monitoring Works with Spot instance types Monitor job flows from with the management console
  • Rule 6: Leverage unique cloud properties a) Optimize costs with instance types b) Get insight fast with Elastic MapReduce Input data S3 + DynamoDB Code Elastic MapReduce Name node Queries + BI Via JDBC, Pig, Hive Output S3 + SimpleDB HDFS Elastic cluster
  • Features powered by Amazon Elastic MapReduce: People Who Viewed this Also Viewed Review highlights Auto complete as you type on search Search spelling suggestions Top searches Ads 200 Elastic MapReduce jobs per day Processing 3TB of data
  • “With AWS, our developers can now do things they couldn’t before… …Our systems team can focus their energies on other challenges.” Dave Marin Search and data-mining engineer
  • What your users want… Fast, performant experience Always on, accessible anywhere Lots of new features all of the time Personalized and rich application
  • With AWS Elastic utility capacity Lots of new features all of the time ✔ Always on, accessible anywhere Personalized and rich application
  • With AWS Elastic utility capacity Lots of new features all of the time ✔ Highly available global coverage Personalized and rich application ✔
  • With AWS Elastic utility capacity Agility & automated operations ✔ ✔ Highly available global coverage Personalized and rich application ✔
  • With AWS Elastic utility capacity Agility & automated operations ✔ ✔ Highly available global coverage Cost effective storage, big data & analytics ✔ ✔
  • aws.amazon.com get started with the free tier
  • Thank you Kingsley Wood Business Development Manager