Justin.tv - AWS The Start-Up Project

Slide 1: Justin.tv and AWS Kyle Vogt - VP of Engineering

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

Slide 3: Police Raid Prank Hands up! SF Police! Who was stabbed?

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

Slide 5: Growing quickly... Page views up 300% in a month.

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

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

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

Slide 9: 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

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

Slide 11: 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

Slide 12: 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

Slide 13: Thanks.