Updated. Netflix (s NFLX) clocked close to 42 billion API requests
per day 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 (s EBAY) engineering team. In his slides, 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.
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.
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, the Netflix engineering team eventually realized that it could use the very same API to bring Netflix to devices like the Roku, the PS3 (s SNE) and the Xbox. (s MSFT) To see how much of an impact that decision had, check out where API requests came from in 2008:
Compare that with API requests in 2011:
Guess which segment Netflix is focusing on these days? Exactly:
Check out Jacobson’s entire presentation below: