<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
	>

<channel>
	<title>GigaOM &#187; Netflix API</title>
	<atom:link href="http://gigaom.com/tag/netflix-api/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com</link>
	<description></description>
	<lastBuildDate>Thu, 23 May 2013 09:49:22 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
<cloud domain='gigaom.com' port='80' path='/?rsscloud=notify' registerProcedure='' protocol='http-post' />
<image>
		<url>http://0.gravatar.com/blavatar/0db8f6557d022075dbbf010c54d46d93?s=96&#038;d=http%3A%2F%2Fs2.wp.com%2Fi%2Fbuttonw-com.png</url>
		<title>GigaOM &#187; Netflix API</title>
		<link>http://gigaom.com</link>
	</image>
	<atom:link rel="search" type="application/opensearchdescription+xml" href="http://gigaom.com/osd.xml" title="GigaOM" />
	<atom:link rel='hub' href='http://gigaom.com/?pushpress=hub'/>
		<item>
		<title>Holy moly: Netflix clocks 42B API requests per month</title>
		<link>http://gigaom.com/2012/05/15/netflix-42-billion-api-requests/</link>
		<comments>http://gigaom.com/2012/05/15/netflix-42-billion-api-requests/#comments</comments>
		<pubDate>Tue, 15 May 2012 23:11:10 +0000</pubDate>
		<dc:creator>Janko Roettgers</dc:creator>
				<category><![CDATA[Daniel Jacobson]]></category>
		<category><![CDATA[Netflix]]></category>
		<category><![CDATA[Netflix API]]></category>

		<guid isPermaLink="false">http://gigaom.com/?p=521883</guid>
		<description><![CDATA[Netflix saw close to 42 billion API requests in January. The company originally released its API with third-party developers and their quirky mashups in mind, but these days, most of these requests come from Netflix's own apps on mobile and connected devices. <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=gigaom.com&#038;blog=14960843&#038;post=521883&#038;subd=gigaom2&#038;ref=&#038;feed=1" width="1" height="1" />]]></description>
				<content:encoded><![CDATA[<p><a href="http://gigaom2.files.wordpress.com/2012/05/42.jpg"><img  title="42" src="http://gigaom2.files.wordpress.com/2012/05/42.jpg?w=300&#038;h=194" alt="" width="300" height="194" class="size-medium wp-image-521903 alignleft" /></a><strong>Updated.</strong> Netflix clocked close to 42 billion API requests <del>per day</del> in January, according to the company’s director of engineering Daniel Jacobson, who revealed the number as part of a presentation he recently gave to the Paypal engineering team. <a href="http://www.slideshare.net/danieljacobson/netflix-api-presentation-to-paypal-12931138">In his slides</a>, Jacobson pointed out that the number of API requests has grown 70-fold in just two years, from 600 million in January of 2010 to 41.7 billion in January of 2012.</p>
<p><a href="http://gigaom2.files.wordpress.com/2012/05/netflix-api-42-billion.jpg"><img  title="netflix api 42 billion" src="http://gigaom2.files.wordpress.com/2012/05/netflix-api-42-billion.jpg?w=708" alt=""   class="aligncenter size-full wp-image-521884" /></a></p>
<p>Providing an API that is resilient enough to handle these kinds of demands is not a small feat, and Jacobson’s slides reveal some of the principles behind the architecture used for the task. However, there’s an even bigger story to this: The sole reason that Netflix’s API has gotten so popular in the last two years is that the company’s service is seeing huge amounts of traffic from connected devices.</p>
<p>Netflix originally built its API with third-party developers in mind, which used it to build websites and apps to manage one’s DVD queue and similar things. However, <a href="http://gigaom.com/video/netflix-ui-innovation/">the Netflix engineering team eventually realized</a> that it could use the very same API to bring Netflix to devices like the Roku, the PS3 and the Xbox. To see how much of an impact that decision had, check out where API requests came from in 2008:</p>
<p><a href="http://gigaom2.files.wordpress.com/2012/05/netflix-api-requests-2008.jpg"><img  title="netflix api requests 2008" src="http://gigaom2.files.wordpress.com/2012/05/netflix-api-requests-2008.jpg?w=708" alt=""   class="aligncenter size-full wp-image-521889" /></a></p>
<p>Compare that with API requests in 2011:</p>
<p><a href="http://gigaom2.files.wordpress.com/2012/05/netflix-api-requests-2011.jpg"><img  title="netflix api requests 2011" src="http://gigaom2.files.wordpress.com/2012/05/netflix-api-requests-2011.jpg?w=708" alt=""   class="aligncenter size-full wp-image-521890" /></a></p>
<p>Guess which segment Netflix is focusing on these days? Exactly:</p>
<p><a href="http://gigaom2.files.wordpress.com/2012/05/netflix-api-emphasis.jpg"><img  title="netflix api emphasis" src="http://gigaom2.files.wordpress.com/2012/05/netflix-api-emphasis.jpg?w=708" alt=""   class="aligncenter size-full wp-image-521891" /></a></p>
<p>Check out Jacobson’s entire presentation below:</p>
<div id="__ss_12931138" style="width: 425px;"><strong style="display: block; margin: 12px 0 4px;"><a title="Netflix API - Presentation to PayPal" href="http://www.slideshare.net/danieljacobson/netflix-api-presentation-to-paypal-12931138" target="_blank">Netflix API &#8211; Presentation to PayPal</a></strong> <iframe src="http://www.slideshare.net/slideshow/embed_code/12931138?rel=0" frameborder="0" marginwidth="0" marginheight="0" scrolling="no" width="425" height="355"></iframe></p>
<div style="padding: 5px 0 12px;">View more presentations from <a href="http://www.slideshare.net/danieljacobson" target="_blank">Daniel Jacobson</a></div>
<div style="padding: 5px 0 12px;"><em>Image <a href="http://creativecommons.org/licenses/by/2.0/">courtesy of</a> Flickr user <a href="http://www.flickr.com/photos/pagedooley/6061815931/in/photostream/">kevin dooley.</a></em></div>
</div>
<br />  <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=gigaom.com&#038;blog=14960843&#038;post=521883&#038;subd=gigaom2&#038;ref=&#038;feed=1" width="1" height="1" /><p><a href="http://pubads.g.doubleclick.net/gampad/jump?iu=/1008864/GigaOM_RSS_300x250&#038;sz=300x250&#038;c=976840"><img src="http://pubads.g.doubleclick.net/gampad/ad?iu=/1008864/GigaOM_RSS_300x250&#038;sz=300x250&#038;c=976840" /></a></p><p><strong>Related research and analysis from GigaOM Pro:</strong><br />Subscriber content. <a href="http://pro.gigaom.com/?utm_source=video&utm_medium=editorial&utm_campaign=auto3&utm_term=521883+netflix-42-billion-api-requests&utm_content=jroettgers">Sign up for a free trial</a>.</p><ul><li><a href="http://pro.gigaom.com/2011/09/what-amazons-new-kindle-line-means-for-apple-netflix-and-online-media/?utm_source=video&utm_medium=editorial&utm_campaign=auto3&utm_term=521883+netflix-42-billion-api-requests&utm_content=jroettgers">What Amazon&#8217;s new Kindle line means for Apple, Netflix and online media</a></li><li><a href="http://pro.gigaom.com/2012/12/connected-consumer-2013-how-2012-laid-the-groundwork-for-change/?utm_source=video&utm_medium=editorial&utm_campaign=auto3&utm_term=521883+netflix-42-billion-api-requests&utm_content=jroettgers">How consumer media will change in 2013</a></li><li><a href="http://pro.gigaom.com/2012/04/connected-consumer-q1-controversy-courtrooms-and-the-cloud/?utm_source=video&utm_medium=editorial&utm_campaign=auto3&utm_term=521883+netflix-42-billion-api-requests&utm_content=jroettgers">Controversy, courtrooms and the cloud in Q1</a></li></ul>]]></content:encoded>
			<wfw:commentRss>http://gigaom.com/2012/05/15/netflix-42-billion-api-requests/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
	
		<media:thumbnail url="http://gigaom2.files.wordpress.com/2012/05/42.jpg?w=150" />
		<media:content url="http://gigaom2.files.wordpress.com/2012/05/42.jpg?w=150" medium="image">
			<media:title type="html">42</media:title>
		</media:content>

		<media:content url="http://0.gravatar.com/avatar/08bc62ecf138202f06b74dfa01376e74?s=96&#38;d=retro&#38;r=PG" medium="image">
			<media:title type="html">jroettgers</media:title>
		</media:content>

		<media:content url="http://gigaom2.files.wordpress.com/2012/05/42.jpg?w=300" medium="image">
			<media:title type="html">42</media:title>
		</media:content>

		<media:content url="http://gigaom2.files.wordpress.com/2012/05/netflix-api-42-billion.jpg" medium="image">
			<media:title type="html">netflix api 42 billion</media:title>
		</media:content>

		<media:content url="http://gigaom2.files.wordpress.com/2012/05/netflix-api-requests-2008.jpg" medium="image">
			<media:title type="html">netflix api requests 2008</media:title>
		</media:content>

		<media:content url="http://gigaom2.files.wordpress.com/2012/05/netflix-api-requests-2011.jpg" medium="image">
			<media:title type="html">netflix api requests 2011</media:title>
		</media:content>

		<media:content url="http://gigaom2.files.wordpress.com/2012/05/netflix-api-emphasis.jpg" medium="image">
			<media:title type="html">netflix api emphasis</media:title>
		</media:content>
	</item>
	</channel>
</rss>
