Justin.tv and AWS Kyle Vogt - VP of Engineering

Kyle Vogt - VP of Engineering

Brief Intro Justin’s 24/7 “Lifecast” starts March 2007 Live Flash video and interactive chat Network for cool live broadcasts Hot-shot Hot Everything recorded and browse-able

Justin’s 24/7 “Lifecast” starts March 2007

Live Flash video and interactive chat

Network for cool live broadcasts

Everything recorded and browse-able

Police Raid Prank Hands up! SF Police! Who was stabbed?

Justin.tv (the business) VC funded in July 6M hits / month 300 broadcasters 7 full-time employees Lots of AWS

VC funded in July

6M hits / month

300 broadcasters

7 full-time employees

Lots of AWS

Growing quickly... Page views up 300% in a month.

Architecture Phase I - March 2007 Vitalstream CDN running FMS 1 broadcaster (Justin) Adequate capacity Expensive. 60% of connections failed!

Phase I - March 2007

Vitalstream CDN running FMS

1 broadcaster (Justin)

Adequate capacity

Architecture Phase II - May 2007 Stream splitter + Wowza 1 broadcaster (Justin) 1,000 streams Servers crashed every 2 hours! Limited capacity.

Phase II - May 2007

Stream splitter + Wowza

1 broadcaster (Justin)

1,000 streams

Architecture Phase III - July 2007 Python Media Server 1,000 broadcasters 100,000 streams More sleep for me. Reliable and scalable.

Phase III - July 2007

Python Media Server

1,000 broadcasters

100,000 streams

AWS By the Numbers 3,170,680 minutes of archived video 50 GB new archive video / day 250 mbps average live bandwidth 1,700 mbps peak live bandwidth 10 to 100 EC2 instances

Financial Comparison 125kbps video stream Provider Cost per user / hour Incremental Savings Time Investment Hardware Cost CDN $0.135 n/a Very Little None Amazon Web Services $0.0074 18x Some None Datacenter $0.0017 4x Lots $$$$$

Bad things Temptation to de-scale to save a buck DB and Memcached outside EC2 Using S3 where a CDN is better ... not much else

Temptation to de-scale to save a buck

DB and Memcached outside EC2

Using S3 where a CDN is better

... not much else

Good things Scaling your website in seconds Serving big objects from EC2 / S3 Using source control and deployment tools Thinking about scaling ahead of time Letting Amazon do the hard work

Scaling your website in seconds

Serving big objects from EC2 / S3

Using source control and deployment tools

Thinking about scaling ahead of time

Letting Amazon do the hard work

Thanks.