NPR API Usage and Metrics
Download as PPT, PDF6 likes1,903 views
These slides demonstrate some of the usage and metrics of the NPR API. In addition to the flow of an NPR story from creation to distribution, I also tried to provide a reasonable sampling of the more popular or interesting implementations.
1 of 53
Downloaded 49 times
![Questions? Daniel Jacobson [email_address] Twitter: @daniel_jacobson To see the API: http:// www.npr.org/api To follow the API development: http:// www.npr.org /blogs/inside](https://image.slidesharecdn.com/npruses-100407210643-phpapp01/85/NPR-API-Usage-and-Metrics-53-320.jpg)
Ad
Recommended
NPR Presentation at Wolfram Data Summit 2010
NPR Presentation at Wolfram Data Summit 2010Daniel Jacobson A modified version of my OSCON presentation focused on data, content, and workflow, in addition to distribution strategies.
NPR - NewMediaDays2010 - Flexible Content
NPR - NewMediaDays2010 - Flexible Contentzachbrand Flexible content presentation from NewMediaDays 2010 showing how NPR philosophy of COPE has driven audience and improved efficiency.
Andrew Mager, Spotify
Andrew Mager, SpotifyMashery This document discusses how to build a developer community from scratch. It recommends (1) assuming users know nothing about APIs and explaining concepts like REST and HTTP, (2) being clear about what is supported and not supported, (3) explaining authentication, (4) highlighting integrations, (5) being open about upcoming projects and feedback, (6) maintaining an internal FAQ, (7) using social media focused on developers, (8) providing code demos, (9) having an excellent developer website, and (10) showcasing examples of apps built with the API.
"A Large Company Content Marketing Journey"
"A Large Company Content Marketing Journey"Content Marketing Institute Content Marketing World 2011
"A Large Company Content Marketing Journey"
Todd Wheatland, Head of Global Marketing, Kelly Services
Content marketing can be challenging for a large, business-to-business company that has a long history of traditional marketing. In this session, Todd will discuss how Kelly Services is managing to develop valuable and compelling content, focusing on:
• How to conceptualize and communicate the content mission
• How to convert possible detractors into rabid supporters
• How to tap into existing channels for story creation
• How to identify “low hanging fruit” and “early wins”
• How to optimize existing tools and avoid turf wars
• How to balance creativity with replicability–and move quickly
OpenID Adoption UX Summit
OpenID Adoption UX SummitDaniel Jacobson These slides are from the OpenID UX Summit at Sears in Chicago. We discuss the newly formed Adoption Committee for OpenID, NPR's identity sharing strategy, Sears' OpenID case study, PBS' case study, and the goal towards a federated public media identity.
Successful content with a metrics driven approach
Successful content with a metrics driven approachKevin Nichols We hear all the time that ‘content is king.’ But if this really is the case, how do we prove it? And how do we continue to improve content and our solutions around it?
For organizations that publish content, metrics and key performance indicators (KPI’s) must prove the worth of content practices and solutions to management teams and decision makers. But ROI is not just about more products being sold, conversions of customers or operational efficiencies gained. In this webinar, learn how to access the appropriate metrics, analytics and KPI’s necessary to make your content useful and intelligent.
How to Get Started with a Cross Functional Approach to Content Management - T...
How to Get Started with a Cross Functional Approach to Content Management - T...Lasselle-Ramsay This presentation will allow you to discover the powerful ways that DITA/XML can deliver content to multiple outputs.
(Almost) Four Years On: Metrics, ROI, and Other Stories from a Mature DITA CM...
(Almost) Four Years On: Metrics, ROI, and Other Stories from a Mature DITA CM...Keith Schengili-Roberts The document summarizes the experience of implementing a DITA content management system (CMS) at AMD's graphics division over almost four years. Key points include:
1) Productivity increased 2.3-3x through content reuse, automation, and fewer formatting issues in localization. Output increased while staff decreased.
2) Localization costs dropped to less than half of pre-CMS levels due to greater content reuse and streamlined processes.
3) Tracking metadata allows comprehensive measurement of productivity, including topics created/modified, translation auto-matches, and topic reuse rates. This data aligns with product release cycles.
W2E NY 2010 NPR Everywhere
W2E NY 2010 NPR Everywherezachbrand As the media leader who first brought a public content API to the market in 2008, NPR continues to innovate and learn about what it means to have flexible content. Our philosophy assumes that to maintain relevancy in an online world media companies need to be adroit at delivering content to multiple channels and disparate platforms. This in turn has lead us to keep a strategic focus on our API development. This positions us not just to meet our distribution needs, but has also helped drive business opportunity and allows for effective design and user experience whether in a browser or on a mobile device. This presentation will share our lessons learned and key metrics around successful creation and use of flexible content – from technology needs to business, editorial and design opportunities in an increasingly fragmented online product landscape.
NPR: Digital Distribution Strategy: OSCON2010
NPR: Digital Distribution Strategy: OSCON2010Daniel Jacobson When launching the API at OSCON in 2008, NPR targeted four audiences: the open source community; NPR member stations; NPR partners and vendors; and finally our internal developers and product managers. In its short two-year life, the NPR API has grown tremendously, from only a few hundred thousand requests per month to more than 60M. The API, furthermore, has enabled tremendous growth for NPR in the mobile space while facilitating more than 100% growth in total page views in the last year.
NPR's Digital Distribution and Mobile Strategy
NPR's Digital Distribution and Mobile StrategyDaniel Jacobson The NPR API has been the great enabler to achieve rapid development in the mobile space. That is, because we have our rich and powerful API, our mobile team is free to pursue the development of their mobile products without being encumbered by limited internal development resources. The touch-point between the mobile product and our content is fixed which means the mobile team can focus on design and usability for the specific platform.
Kqed And The Npr Api
Kqed And The Npr ApiKevin Cooke A talk on how KQED is using the NPR API to consume and share content, given at Hacks & Hackers on 5/22/10
Web2expo 2011u
Web2expo 2011uzachbrand Presentation from Web2.0 Expo NY 2011.
Good architecture of systems and flexibility of content has also allowed NPR to have the freedom and agility to quickly deploy solid user experience and elegant design to multiple platforms. This presentation will cover how NPR improved the code inside its API to be more efficient, while meeting new and evolving product needs
Michael Yoch (NPR) - The NPR API: Powering "Radio" in a Multiplatform World
Michael Yoch (NPR) - The NPR API: Powering "Radio" in a Multiplatform WorldRadiocamp 2011 NPR produces and distributes radio and digital content to over 900 stations reaching 92% of the US population. With the rise of broadband and internet-connected devices, NPR is developing an API to make its content flexible and accessible across multiple platforms. The API allows NPR, stations, and other partners to build many products like mobile apps, websites, and widgets to engage audiences on any device in new ways. By breaking content into modular pieces with metadata, the API powers everything NPR publishes and enables broad reach through both traditional and emerging technologies.
NPR API: Create Once Publish Everywhere
NPR API: Create Once Publish Everywherezachbrand The document discusses NPR's content management strategy of creating content once and publishing it everywhere (COPE) using their API. It outlines the benefits of this approach, including improved development efficiencies, enabling new digital experiences and business opportunities. It also shares lessons learned, such as the need for flexible content structures, clear examples over documentation, and ensuring technology and content teams are aligned. Upcoming improvements to the API are also mentioned, such as image cropping and new output formats.
API Business Models
API Business ModelsJohn Musser What's a good API business model? If you have an API, or you plan to have an open API, or just want to use APIs in your web or mobile app, what models make sense? See 20 different API business models. This comprehensive survey of the gamut of today's options covering anything from paid to getting paid to indirect.
Open API Ecosystem Overview: December 2010
Open API Ecosystem Overview: December 2010John Musser The document summarizes the state of open APIs in 2010. Some key points include:
- Open APIs have grown rapidly in recent years, with over 2,400 APIs listed by 2010 compared to just 105 in 2000. Growth has accelerated.
- Successful APIs have a business model baked in, are easy to adopt, and provide good developer support. Common models include pay-per-use, affiliate marketing, and software as a service.
- REST has become more popular than SOAP due to its simplicity. JSON is also growing as an alternative to XML.
- Major tech companies are increasingly dependent on APIs, with billions of API calls per day powering services like Facebook and Amazon.
Mashery Npr Open Content
Mashery Npr Open ContentSt. Louis Public Radio NPR provides a comprehensive API that allows access to over 250,000 stories and 400,000 audio files from NPR.org. The API sees significant usage, with nearly 1,000 registrants, over 4.3 million requests, and 200,000 page views to the technical documentation site. However, some content is excluded due to rights restrictions. Future enhancements may include the ability to post content, additional output formats, and more member station and external content.
Open APIs and the Semantic Web 2011
Open APIs and the Semantic Web 2011John Musser 1. The document discusses the state of the market for open APIs and semantic web technologies. It notes that REST has become the dominant API design approach over SOAP. JSON support is growing and has surpassed XML for new APIs.
2. While there are over 3,300 APIs tracked, semantic API adoption remains low with only 1% of APIs supporting RDF. The growth of invisible APIs and APIs as products is also discussed.
3. Key trends include the rise of APIs as core products and business models, with some companies abandoning websites in favor of monetizing their APIs. Developer ecosystem cultivation and support is also cited as important for API success.
API Strategy Evolution at Netflix
API Strategy Evolution at NetflixMichael Hart Developing an API strategy should be considered a journey, not a project with a predetermined outcome. This presentation describes Netflix's journey to discover a winning API strategy as well as future directions for the API.
Your API is So 2006 - MoDevEast 2011
Your API is So 2006 - MoDevEast 2011Delyn Simons This document discusses the growth of APIs since 2006 and trends in their development and use. It notes that the number of APIs listed on ProgrammableWeb has grown significantly since 2006. REST has become the dominant API design pattern over SOAP, and JSON support is rising dramatically. The document advocates that API providers think like platforms by dropping SOAP, using push notifications to engage developers, providing interactive documentation, and focusing on internal and partner usage to achieve mainstream success.
APIs
APIsChris Castiglione APIs. What are they? Why should you care? This is a part of my Programming For Non-Programmers Workshop series.
API Product Opportunity Responsibility Nicolas Sierro 2015.pptx
API Product Opportunity Responsibility Nicolas Sierro 2015.pptxBlockchainizator The document discusses the history and evolution of APIs, including early examples from Salesforce, eBay, and Amazon in the late 1990s-early 2000s. It notes that APIs allow companies to unlock the business potential of their data and services by making them available to external developers and partners. Successful API strategies treat the API as a product in its own right, with clear business models, pricing, and onboarding support for developers. The growth of APIs has accelerated in recent years, driven by trends like mobile, cloud computing and the desire to build platforms.
Open APIs - State of the Market 2011
Open APIs - State of the Market 2011John Musser This document summarizes key trends in the open API market based on data from ProgrammableWeb.com. It finds that the growth of APIs is accelerating, with over 3,200 APIs currently listed. The most competitive categories have dozens of APIs. It also discusses the rise of simplicity in APIs, with REST and JSON becoming increasingly dominant. Finally, it explores business models for APIs, noting some companies are focusing exclusively on their API as the product rather than accompanying websites.
YES, APIs Make You Special
YES, APIs Make You Specialduvander Creating web applications today is very different than just a few years ago. The cause of this shift also enabled the move toward a more mobile future. There are now thousands of APIs that allow developers to focus on the part of the technology that is specific to the application. Social login, infrastructure services and many specialized datasets make up the core of today's web and mobile apps. In this talk, Adam DuVander traces the brief and impactful history of APIs. He also shares some tips to take full advantage of the trend in your own projects and businesses.
Open APIs: State of the Market, May 2010
Open APIs: State of the Market, May 2010John Musser Overview of the open API marketplace based on data from ProgrammableWeb.com. Presentation by John Musser at Glue Conference, May 2010.
APIs for Internal Audiences - Netflix - App Dev Conference
APIs for Internal Audiences - Netflix - App Dev ConferenceDaniel Jacobson API programs, typically thought of as a public program to see what public developer communities can build with a company's data, are becoming more and more critical to the success of mobile and device strategies. This presentation takes a look at Netflix's and NPR's strategies that lead to tremendous growth and discusses how Netflix plans to take this internal API strategy to the next level.
The future-of-netflix-api
The future-of-netflix-apiDaniel Jacobson This presentation demonstrates the great successes of the Netflix API to date. After some introspection, however, there is an opportunity to better prepare the API for the future. This presentation also offers a few ideas on how the Netflix API architecture may change over time.
Netflix Edge Engineering Open House Presentations - June 9, 2016
Netflix Edge Engineering Open House Presentations - June 9, 2016Daniel Jacobson Netflix's Edge Engineering team is responsible for handling all device traffic for to support the user experience, including sign-up, discovery and the triggering of the playback experience. Developing and maintaining this set of massive scale services is no small task and its success is the difference between millions of happy streamers or millions of missed opportunities.
This video captures the presentations delivered at the first ever Edge Engineering Open House at Netflix. This video covers the primary aspects of our charter, including the evolution of our API and Playback services as well as building a robust developer experience for the internal consumers of our APIs.
Top 10 Lessons Learned from the Netflix API - OSCON 2014
Top 10 Lessons Learned from the Netflix API - OSCON 2014Daniel Jacobson The document discusses lessons learned from Netflix's API strategy over time. It notes that Netflix started with a focus on growing a community of public developers but now prioritizes ensuring subscribers can stream. It also discusses separating concerns between API providers and consumers, embracing differences in audiences, being pragmatic over dogmatic in API decisions, enabling fast iteration, planning for failures, and scaling infrastructure to match growth.
Ad
More Related Content
Similar to NPR API Usage and Metrics (20)
W2E NY 2010 NPR Everywhere
W2E NY 2010 NPR Everywherezachbrand As the media leader who first brought a public content API to the market in 2008, NPR continues to innovate and learn about what it means to have flexible content. Our philosophy assumes that to maintain relevancy in an online world media companies need to be adroit at delivering content to multiple channels and disparate platforms. This in turn has lead us to keep a strategic focus on our API development. This positions us not just to meet our distribution needs, but has also helped drive business opportunity and allows for effective design and user experience whether in a browser or on a mobile device. This presentation will share our lessons learned and key metrics around successful creation and use of flexible content – from technology needs to business, editorial and design opportunities in an increasingly fragmented online product landscape.
NPR: Digital Distribution Strategy: OSCON2010
NPR: Digital Distribution Strategy: OSCON2010Daniel Jacobson When launching the API at OSCON in 2008, NPR targeted four audiences: the open source community; NPR member stations; NPR partners and vendors; and finally our internal developers and product managers. In its short two-year life, the NPR API has grown tremendously, from only a few hundred thousand requests per month to more than 60M. The API, furthermore, has enabled tremendous growth for NPR in the mobile space while facilitating more than 100% growth in total page views in the last year.
NPR's Digital Distribution and Mobile Strategy
NPR's Digital Distribution and Mobile StrategyDaniel Jacobson The NPR API has been the great enabler to achieve rapid development in the mobile space. That is, because we have our rich and powerful API, our mobile team is free to pursue the development of their mobile products without being encumbered by limited internal development resources. The touch-point between the mobile product and our content is fixed which means the mobile team can focus on design and usability for the specific platform.
Kqed And The Npr Api
Kqed And The Npr ApiKevin Cooke A talk on how KQED is using the NPR API to consume and share content, given at Hacks & Hackers on 5/22/10
Web2expo 2011u
Web2expo 2011uzachbrand Presentation from Web2.0 Expo NY 2011.
Good architecture of systems and flexibility of content has also allowed NPR to have the freedom and agility to quickly deploy solid user experience and elegant design to multiple platforms. This presentation will cover how NPR improved the code inside its API to be more efficient, while meeting new and evolving product needs
Michael Yoch (NPR) - The NPR API: Powering "Radio" in a Multiplatform World
Michael Yoch (NPR) - The NPR API: Powering "Radio" in a Multiplatform WorldRadiocamp 2011 NPR produces and distributes radio and digital content to over 900 stations reaching 92% of the US population. With the rise of broadband and internet-connected devices, NPR is developing an API to make its content flexible and accessible across multiple platforms. The API allows NPR, stations, and other partners to build many products like mobile apps, websites, and widgets to engage audiences on any device in new ways. By breaking content into modular pieces with metadata, the API powers everything NPR publishes and enables broad reach through both traditional and emerging technologies.
NPR API: Create Once Publish Everywhere
NPR API: Create Once Publish Everywherezachbrand The document discusses NPR's content management strategy of creating content once and publishing it everywhere (COPE) using their API. It outlines the benefits of this approach, including improved development efficiencies, enabling new digital experiences and business opportunities. It also shares lessons learned, such as the need for flexible content structures, clear examples over documentation, and ensuring technology and content teams are aligned. Upcoming improvements to the API are also mentioned, such as image cropping and new output formats.
API Business Models
API Business ModelsJohn Musser What's a good API business model? If you have an API, or you plan to have an open API, or just want to use APIs in your web or mobile app, what models make sense? See 20 different API business models. This comprehensive survey of the gamut of today's options covering anything from paid to getting paid to indirect.
Open API Ecosystem Overview: December 2010
Open API Ecosystem Overview: December 2010John Musser The document summarizes the state of open APIs in 2010. Some key points include:
- Open APIs have grown rapidly in recent years, with over 2,400 APIs listed by 2010 compared to just 105 in 2000. Growth has accelerated.
- Successful APIs have a business model baked in, are easy to adopt, and provide good developer support. Common models include pay-per-use, affiliate marketing, and software as a service.
- REST has become more popular than SOAP due to its simplicity. JSON is also growing as an alternative to XML.
- Major tech companies are increasingly dependent on APIs, with billions of API calls per day powering services like Facebook and Amazon.
Mashery Npr Open Content
Mashery Npr Open ContentSt. Louis Public Radio NPR provides a comprehensive API that allows access to over 250,000 stories and 400,000 audio files from NPR.org. The API sees significant usage, with nearly 1,000 registrants, over 4.3 million requests, and 200,000 page views to the technical documentation site. However, some content is excluded due to rights restrictions. Future enhancements may include the ability to post content, additional output formats, and more member station and external content.
Open APIs and the Semantic Web 2011
Open APIs and the Semantic Web 2011John Musser 1. The document discusses the state of the market for open APIs and semantic web technologies. It notes that REST has become the dominant API design approach over SOAP. JSON support is growing and has surpassed XML for new APIs.
2. While there are over 3,300 APIs tracked, semantic API adoption remains low with only 1% of APIs supporting RDF. The growth of invisible APIs and APIs as products is also discussed.
3. Key trends include the rise of APIs as core products and business models, with some companies abandoning websites in favor of monetizing their APIs. Developer ecosystem cultivation and support is also cited as important for API success.
API Strategy Evolution at Netflix
API Strategy Evolution at NetflixMichael Hart Developing an API strategy should be considered a journey, not a project with a predetermined outcome. This presentation describes Netflix's journey to discover a winning API strategy as well as future directions for the API.
Your API is So 2006 - MoDevEast 2011
Your API is So 2006 - MoDevEast 2011Delyn Simons This document discusses the growth of APIs since 2006 and trends in their development and use. It notes that the number of APIs listed on ProgrammableWeb has grown significantly since 2006. REST has become the dominant API design pattern over SOAP, and JSON support is rising dramatically. The document advocates that API providers think like platforms by dropping SOAP, using push notifications to engage developers, providing interactive documentation, and focusing on internal and partner usage to achieve mainstream success.
APIs
APIsChris Castiglione APIs. What are they? Why should you care? This is a part of my Programming For Non-Programmers Workshop series.
API Product Opportunity Responsibility Nicolas Sierro 2015.pptx
API Product Opportunity Responsibility Nicolas Sierro 2015.pptxBlockchainizator The document discusses the history and evolution of APIs, including early examples from Salesforce, eBay, and Amazon in the late 1990s-early 2000s. It notes that APIs allow companies to unlock the business potential of their data and services by making them available to external developers and partners. Successful API strategies treat the API as a product in its own right, with clear business models, pricing, and onboarding support for developers. The growth of APIs has accelerated in recent years, driven by trends like mobile, cloud computing and the desire to build platforms.
Open APIs - State of the Market 2011
Open APIs - State of the Market 2011John Musser This document summarizes key trends in the open API market based on data from ProgrammableWeb.com. It finds that the growth of APIs is accelerating, with over 3,200 APIs currently listed. The most competitive categories have dozens of APIs. It also discusses the rise of simplicity in APIs, with REST and JSON becoming increasingly dominant. Finally, it explores business models for APIs, noting some companies are focusing exclusively on their API as the product rather than accompanying websites.
YES, APIs Make You Special
YES, APIs Make You Specialduvander Creating web applications today is very different than just a few years ago. The cause of this shift also enabled the move toward a more mobile future. There are now thousands of APIs that allow developers to focus on the part of the technology that is specific to the application. Social login, infrastructure services and many specialized datasets make up the core of today's web and mobile apps. In this talk, Adam DuVander traces the brief and impactful history of APIs. He also shares some tips to take full advantage of the trend in your own projects and businesses.
Open APIs: State of the Market, May 2010
Open APIs: State of the Market, May 2010John Musser Overview of the open API marketplace based on data from ProgrammableWeb.com. Presentation by John Musser at Glue Conference, May 2010.
APIs for Internal Audiences - Netflix - App Dev Conference
APIs for Internal Audiences - Netflix - App Dev ConferenceDaniel Jacobson API programs, typically thought of as a public program to see what public developer communities can build with a company's data, are becoming more and more critical to the success of mobile and device strategies. This presentation takes a look at Netflix's and NPR's strategies that lead to tremendous growth and discusses how Netflix plans to take this internal API strategy to the next level.
The future-of-netflix-api
The future-of-netflix-apiDaniel Jacobson This presentation demonstrates the great successes of the Netflix API to date. After some introspection, however, there is an opportunity to better prepare the API for the future. This presentation also offers a few ideas on how the Netflix API architecture may change over time.
More from Daniel Jacobson (20)
Netflix Edge Engineering Open House Presentations - June 9, 2016
Netflix Edge Engineering Open House Presentations - June 9, 2016Daniel Jacobson Netflix's Edge Engineering team is responsible for handling all device traffic for to support the user experience, including sign-up, discovery and the triggering of the playback experience. Developing and maintaining this set of massive scale services is no small task and its success is the difference between millions of happy streamers or millions of missed opportunities.
This video captures the presentations delivered at the first ever Edge Engineering Open House at Netflix. This video covers the primary aspects of our charter, including the evolution of our API and Playback services as well as building a robust developer experience for the internal consumers of our APIs.
Top 10 Lessons Learned from the Netflix API - OSCON 2014
Top 10 Lessons Learned from the Netflix API - OSCON 2014Daniel Jacobson The document discusses lessons learned from Netflix's API strategy over time. It notes that Netflix started with a focus on growing a community of public developers but now prioritizes ensuring subscribers can stream. It also discusses separating concerns between API providers and consumers, embracing differences in audiences, being pragmatic over dogmatic in API decisions, enabling fast iteration, planning for failures, and scaling infrastructure to match growth.
Maintaining the Netflix Front Door - Presentation at Intuit Meetup
Maintaining the Netflix Front Door - Presentation at Intuit MeetupDaniel Jacobson This presentation goes into detail on the key principles behind the Netflix API, including design, resiliency, scaling, and deployment. Among other things, I discuss our migration from our REST API to what we call our Experienced-Based API design. It also shares several of our open source efforts such as Zuul, Scryer, Hystrix, RxJava and the Simian Army.
Netflix API - Separation of Concerns
Netflix API - Separation of ConcernsDaniel Jacobson Most API providers focus on solving all three of the key challenges for APIs: data gathering, data formatting and data delivery. All three of these functions are critical for the success of an API, however, not all should be solved by the API provider. Rather, the API consumers have a strong, vested interest in the formatting and delivery. As a result, API design should be addressed based on the true separation of concerns between the needs of the API provider and the various API consumers.
This presentation goes into the separation of concerns. It also goes into depth in how Netflix has solved for this problem through a very different approach to API design.
This presentation was given at the following API Meetup in SF:
http://www.meetup.com/API-Meetup/events/171255242/
Maintaining the Front Door to Netflix : The Netflix API
Maintaining the Front Door to Netflix : The Netflix APIDaniel Jacobson This presentation was given to the engineering organization at Zendesk. In this presentation, I talk about the challenges that the Netflix API faces in supporting the 1000+ different device types, millions of users, and billions of transactions. The topics range from resiliency, scale, API design, failure injection, continuous delivery, and more.
Why API? - Business of APIs Conference
Why API? - Business of APIs ConferenceDaniel Jacobson Many API programs get launched without a clear understanding as to WHY the API should exist. Rather, many are focused on WHAT the API consists of and HOW it should be targeted, implemented and leveraged. This presentation focuses on establishing the need for a clear WHY proposition behind the decision. The HOW and then WHAT will follow from that.
This presentation also uses the history of the Netflix API to demonstrate the power, utility and importance of knowing WHY you are building an API.
Scaling the Netflix API - OSCON
Scaling the Netflix API - OSCONDaniel Jacobson The term "scale" for engineering often is used to discuss systems and their ability to grow with the needs of its users. This is clearly an important aspect of scaling, but there are many other areas in which an engineering organization needs to scale to be successful in the long term. This presentation discusses some of those other areas and details how Netflix (and specifically the API team) addresses them.
Scaling the Netflix API - From Atlassian Dev Den
Scaling the Netflix API - From Atlassian Dev DenDaniel Jacobson The term "scale" for engineering often is used to discuss systems and their ability to grow with the needs of its users. This is clearly an important aspect of scaling, but there are many other areas in which an engineering organization needs to scale to be successful in the long term. This presentation discusses some of those other areas and details how Netflix (and specifically the API team) addresses them.
Scaling the Netflix API
Scaling the Netflix APIDaniel Jacobson The term "scale" for engineering often is used to discuss systems and their ability to grow with the needs of its users. This is clearly an important aspect of scaling, but there are many other areas in which an engineering organization needs to scale to be successful in the long term. This presentation discusses some of those other areas and details how Netflix (and specifically the API team) addresses them.
Netflix API: Keynote at Disney Tech Conference
Netflix API: Keynote at Disney Tech ConferenceDaniel Jacobson This document discusses the evolution of Netflix's API architecture over time. It begins by explaining Netflix's initial "one-size-fits-all" REST API model and how requests grew exponentially as more devices were supported. This led Netflix to move away from resource-based APIs to experience-based APIs tailored for specific devices and use cases. Key aspects of the new design included reducing "chattiness", handling variability across devices, and supporting innovation at different rates. The document also discusses Netflix's approach to versioning APIs and making them more resilient through techniques like circuit breakers and fallbacks.
Netflix API
Netflix APIDaniel Jacobson Daniel Jacobson is the Director of Engineering at Netflix API. He discussed techniques for scaling the Netflix API, including moving from a resource-based API to an experience-based API model to improve efficiency. Netflix uses cloud deployment techniques like autoscaling and canary releases for development and testing. Resiliency is ensured through techniques like circuit breakers and fallbacks.
API Revolutions : Netflix's API Redesign
API Revolutions : Netflix's API RedesignDaniel Jacobson Revolutions have a common pattern in technology and this is no different for the API space. This presentation discusses that pattern and goes through various API revolutions. It also uses Netflix as an example of how some revolutions evolved and where things may be headed.
Set Your Content Free! : Case Studies from Netflix and NPR
Set Your Content Free! : Case Studies from Netflix and NPRDaniel Jacobson Last Friday (February 8th), I spoke at the Intelligent Content Conference 2013. When Scott Abel (aka The Content Wrangler) first contacted me to speak at the event, he asked me to speak about my content management and distribution experiences from both NPR and Netflix. The two experiences seemed to him to be an interesting blend for the conference. These are the slides from that presentation.
I have applied comments to every slide in this presentation to include the context that I otherwise provided verbally during the talk.
Netflix API - Presentation to PayPal
Netflix API - Presentation to PayPalDaniel Jacobson I gave this presentation to the engineering team at PayPal. This presentation discusses the history and future of the Netflix API. It also goes into API design principles as well as concepts behind system scalability and resiliency.
Techniques for Scaling the Netflix API - QCon SF
Techniques for Scaling the Netflix API - QCon SFDaniel Jacobson This presentation was from QCon SF 2011. In these slides I discuss various techniques that we use to scale the API. I also discuss in more detail our effort around redesigning the API.
Netflix API : BAPI 2011 Presentation : SF
Netflix API : BAPI 2011 Presentation : SFDaniel Jacobson This is my presentation from the Business of APIs Conference in SF, held by Mashery (http://www.apiconference.com).
This talk talks briefly about the history of the Netflix API, then goes into three main categories of scaling:
1. Using the cloud to scale in size and internationally
2. Using Webkit to scale application development in parallel to the flexibility afforded by the API
3. Redesigning the API to improve performance and to downscale the infrastructure as the system scales
When viewing these slides, please note that they are almost entirely image-based, so I have added notes for each slide to detail the talking points.
Redesigning the Netflix API - OSCON
Redesigning the Netflix API - OSCONDaniel Jacobson The Netflix API was originally launched 3 years ago to expose Netflix metadata and services to developers and build applications. It now handles over 1 billion requests per day from over 20,000 developers and 13,000 applications. However, Netflix has undergone many business changes and the API needs to be redesigned to focus on its core streaming business and support international growth. The new design will build a scalable data distribution pipeline to deliver customized, optimized metadata and services to each streaming client and platform. It will use wrappers and response handlers to customize the response for each device and isolate problems. This will allow faster development and reduce the need for versioning across many client types and interfaces.
History and Future of the Netflix API - Mashery Evolution of Distribution
History and Future of the Netflix API - Mashery Evolution of DistributionDaniel Jacobson Presentation on the history and future of the Netflix API. This presentation walks through how the API was formed, why it needs a redesign and some of the principles that will be applied in the redesign effort.
This presentation was given at the Mashery Evolution of Distribution session in San Francisco on June 2, 2011.
Presentation to ESPN about the Netflix API
Presentation to ESPN about the Netflix APIDaniel Jacobson This is a presentation that I gave to ESPN's Digital Media team about the trajectory of the Netflix API. I also discussed Netflix's device implementation strategy and how it enables rapid development and robust A/B testing.
NPR : Examples of COPE
NPR : Examples of COPEDaniel Jacobson This presentation shows the same NPR story displayed in a wide range of platforms. The content, through the principles of COPE, is pushed out to all of these destinations through the NPR API. Each destination, meanwhile, uses the appropriate content for that presentation layer.
Ad
Recently uploaded (20)
Into The Box Conference Keynote Day 1 (ITB2025)
Into The Box Conference Keynote Day 1 (ITB2025)Ortus Solutions, Corp This is the keynote of the Into the Box conference, highlighting the release of the BoxLang JVM language, its key enhancements, and its vision for the future.
#StandardsGoals for 2025: Standards & certification roundup - Tech Forum 2025
#StandardsGoals for 2025: Standards & certification roundup - Tech Forum 2025BookNet Canada Book industry standards are evolving rapidly. In the first part of this session, we’ll share an overview of key developments from 2024 and the early months of 2025. Then, BookNet’s resident standards expert, Tom Richardson, and CEO, Lauren Stewart, have a forward-looking conversation about what’s next.
Link to recording, transcript, and accompanying resource: https://bnctechforum.ca/sessions/standardsgoals-for-2025-standards-certification-roundup/
Presented by BookNet Canada on May 6, 2025 with support from the Department of Canadian Heritage.
AI and Data Privacy in 2025: Global Trends
AI and Data Privacy in 2025: Global TrendsInData Labs In this infographic, we explore how businesses can implement effective governance frameworks to address AI data privacy. Understanding it is crucial for developing effective strategies that ensure compliance, safeguard customer trust, and leverage AI responsibly. Equip yourself with insights that can drive informed decision-making and position your organization for success in the future of data privacy.
This infographic contains:
-AI and data privacy: Key findings
-Statistics on AI data privacy in the today’s world
-Tips on how to overcome data privacy challenges
-Benefits of AI data security investments.
Keep up-to-date on how AI is reshaping privacy standards and what this entails for both individuals and organizations.
Rusty Waters: Elevating Lakehouses Beyond Spark
Rusty Waters: Elevating Lakehouses Beyond Sparkcarlyakerly1 Spark is a powerhouse for large datasets, but when it comes to smaller data workloads, its overhead can sometimes slow things down. What if you could achieve high performance and efficiency without the need for Spark?
At S&P Global Commodity Insights, having a complete view of global energy and commodities markets enables customers to make data-driven decisions with confidence and create long-term, sustainable value. 🌍
Explore delta-rs + CDC and how these open-source innovations power lightweight, high-performance data applications beyond Spark! 🚀
TrustArc Webinar: Consumer Expectations vs Corporate Realities on Data Broker...
TrustArc Webinar: Consumer Expectations vs Corporate Realities on Data Broker...TrustArc Most consumers believe they’re making informed decisions about their personal data—adjusting privacy settings, blocking trackers, and opting out where they can. However, our new research reveals that while awareness is high, taking meaningful action is still lacking. On the corporate side, many organizations report strong policies for managing third-party data and consumer consent yet fall short when it comes to consistency, accountability and transparency.
This session will explore the research findings from TrustArc’s Privacy Pulse Survey, examining consumer attitudes toward personal data collection and practical suggestions for corporate practices around purchasing third-party data.
Attendees will learn:
- Consumer awareness around data brokers and what consumers are doing to limit data collection
- How businesses assess third-party vendors and their consent management operations
- Where business preparedness needs improvement
- What these trends mean for the future of privacy governance and public trust
This discussion is essential for privacy, risk, and compliance professionals who want to ground their strategies in current data and prepare for what’s next in the privacy landscape.
How analogue intelligence complements AI
How analogue intelligence complements AIPaul Rowe
Artificial Intelligence is providing benefits in many areas of work within the heritage sector, from image analysis, to ideas generation, and new research tools. However, it is more critical than ever for people, with analogue intelligence, to ensure the integrity and ethical use of AI. Including real people can improve the use of AI by identifying potential biases, cross-checking results, refining workflows, and providing contextual relevance to AI-driven results.
News about the impact of AI often paints a rosy picture. In practice, there are many potential pitfalls. This presentation discusses these issues and looks at the role of analogue intelligence and analogue interfaces in providing the best results to our audiences. How do we deal with factually incorrect results? How do we get content generated that better reflects the diversity of our communities? What roles are there for physical, in-person experiences in the digital world?
Heap, Types of Heap, Insertion and Deletion
Heap, Types of Heap, Insertion and DeletionJaydeep Kale This pdf will explain what is heap, its type, insertion and deletion in heap and Heap sort
Special Meetup Edition - TDX Bengaluru Meetup #52.pptx
Special Meetup Edition - TDX Bengaluru Meetup #52.pptxshyamraj55 We’re bringing the TDX energy to our community with 2 power-packed sessions:
🛠️ Workshop: MuleSoft for Agentforce
Explore the new version of our hands-on workshop featuring the latest Topic Center and API Catalog updates.
📄 Talk: Power Up Document Processing
Dive into smart automation with MuleSoft IDP, NLP, and Einstein AI for intelligent document workflows.
Drupalcamp Finland – Measuring Front-end Energy Consumption
Drupalcamp Finland – Measuring Front-end Energy ConsumptionExove How to measure web front-end energy consumption using Firefox Profiler. Presented in DrupalCamp Finland on April 25th, 2025.
Big Data Analytics Quick Research Guide by Arthur Morgan
Big Data Analytics Quick Research Guide by Arthur MorganArthur Morgan This is a Quick Research Guide (QRG).
QRGs include the following:
- A brief, high-level overview of the QRG topic.
- A milestone timeline for the QRG topic.
- Links to various free online resource materials to provide a deeper dive into the QRG topic.
- Conclusion and a recommendation for at least two books available in the SJPL system on the QRG topic.
QRGs planned for the series:
- Artificial Intelligence QRG
- Quantum Computing QRG
- Big Data Analytics QRG
- Spacecraft Guidance, Navigation & Control QRG (coming 2026)
- UK Home Computing & The Birth of ARM QRG (coming 2027)
Any questions or comments?
- Please contact Arthur Morgan at [email protected].
100% human made.
Build Your Own Copilot & Agents For Devs
Build Your Own Copilot & Agents For DevsBrian McKeiver May 2nd, 2025 talk at StirTrek 2025 Conference.
tecnologias de las primeras civilizaciones.pdf
tecnologias de las primeras civilizaciones.pdffjgm517 descaripcion detallada del avance de las tecnologias en mesopotamia, egipto, roma y grecia.
What is Model Context Protocol(MCP) - The new technology for communication bw...
What is Model Context Protocol(MCP) - The new technology for communication bw...Vishnu Singh Chundawat The MCP (Model Context Protocol) is a framework designed to manage context and interaction within complex systems. This SlideShare presentation will provide a detailed overview of the MCP Model, its applications, and how it plays a crucial role in improving communication and decision-making in distributed systems. We will explore the key concepts behind the protocol, including the importance of context, data management, and how this model enhances system adaptability and responsiveness. Ideal for software developers, system architects, and IT professionals, this presentation will offer valuable insights into how the MCP Model can streamline workflows, improve efficiency, and create more intuitive systems for a wide range of use cases.
HCL Nomad Web – Best Practices and Managing Multiuser Environments
HCL Nomad Web – Best Practices and Managing Multiuser Environmentspanagenda Webinar Recording: https://www.panagenda.com/webinars/hcl-nomad-web-best-practices-and-managing-multiuser-environments/
HCL Nomad Web is heralded as the next generation of the HCL Notes client, offering numerous advantages such as eliminating the need for packaging, distribution, and installation. Nomad Web client upgrades will be installed “automatically” in the background. This significantly reduces the administrative footprint compared to traditional HCL Notes clients. However, troubleshooting issues in Nomad Web present unique challenges compared to the Notes client.
Join Christoph and Marc as they demonstrate how to simplify the troubleshooting process in HCL Nomad Web, ensuring a smoother and more efficient user experience.
In this webinar, we will explore effective strategies for diagnosing and resolving common problems in HCL Nomad Web, including
- Accessing the console
- Locating and interpreting log files
- Accessing the data folder within the browser’s cache (using OPFS)
- Understand the difference between single- and multi-user scenarios
- Utilizing Client Clocking
The Evolution of Meme Coins A New Era for Digital Currency ppt.pdf
The Evolution of Meme Coins A New Era for Digital Currency ppt.pdfAbi john Analyze the growth of meme coins from mere online jokes to potential assets in the digital economy. Explore the community, culture, and utility as they elevate themselves to a new era in cryptocurrency.
Enhancing ICU Intelligence: How Our Functional Testing Enabled a Healthcare I...
Enhancing ICU Intelligence: How Our Functional Testing Enabled a Healthcare I...Impelsys Inc. Impelsys provided a robust testing solution, leveraging a risk-based and requirement-mapped approach to validate ICU Connect and CritiXpert. A well-defined test suite was developed to assess data communication, clinical data collection, transformation, and visualization across integrated devices.
Quantum Computing Quick Research Guide by Arthur Morgan
Quantum Computing Quick Research Guide by Arthur MorganArthur Morgan This is a Quick Research Guide (QRG).
QRGs include the following:
- A brief, high-level overview of the QRG topic.
- A milestone timeline for the QRG topic.
- Links to various free online resource materials to provide a deeper dive into the QRG topic.
- Conclusion and a recommendation for at least two books available in the SJPL system on the QRG topic.
QRGs planned for the series:
- Artificial Intelligence QRG
- Quantum Computing QRG
- Big Data Analytics QRG
- Spacecraft Guidance, Navigation & Control QRG (coming 2026)
- UK Home Computing & The Birth of ARM QRG (coming 2027)
Any questions or comments?
- Please contact Arthur Morgan at [email protected].
100% human made.
IEDM 2024 Tutorial2_Advances in CMOS Technologies and Future Directions for C...
IEDM 2024 Tutorial2_Advances in CMOS Technologies and Future Directions for C...organizerofv IEDM 2024 Tutorial2
What is Model Context Protocol(MCP) - The new technology for communication bw...
What is Model Context Protocol(MCP) - The new technology for communication bw...Vishnu Singh Chundawat
Ad
NPR API Usage and Metrics
- 1. NPR API Usage By Daniel Jacobson National Public Radio April 13, 2010
- 2. The following slides demonstrate some of the usage and metrics of the NPR API. In addition to the flow of an NPR story from creation to distribution, I also tried to provide a reasonable sampling of the more popular or interesting implementations.
- 3. Lifecycle of an NPR story From CMS to API to Presentation Layers
- 4. NPR CMS
- 5. NPR API
- 6. NPR.org
- 10. NPR Mobile Site
- 11. NPR Addict iPhone App
- 12. NPR Android App
- 13. KPCC.org
- 14. WBUR.org
- 15. KQED.org
- 17. iGoogle Gadget
- 18. NewsMap
- 21. MPR.org
- 22. Diane Rehm Show
- 23. KPCC Story Selection CMS Tool
- 24. WBUR Growth : With NPR API Content
- 25. Station Ingest
- 27. KLCC Displaying N3 Stories from NPR API
- 28. WBUR Displaying N3 Story from NPR API
- 29. Other Usage
- 30. NPR : Mix Your Own Podcast
- 31. NPR Symbian App
- 32. Yahoo! Widget
- 33. Chumby Widget
- 34. NPR and Google Maps Mashup (open sourced)
- 35. Niels Mayer Podcast Timeline
- 36. TetonCode – Story Counts by Topic
- 37. Solr Search with NPR API
- 38. Twitter Mashups
- 39. reverbiage.com
- 40. Audio Player for UNIX (KDE)
- 42. Code Libraries
- 43. Code Libraries Perl Module
- 44. Drupal Module
- 45. Code Libraries Ruby Code Wrapper
- 46. Code Libraries Python Library
- 47. Metrics
- 48. NPR API : Requests per Month
- 49. NPR API : Stories Requested per Month
- 50. NPR API : Total Output Format Distribution 0.01% Atom 0.1% JSON 1.5% HTML 2.6% JavaScript 1.6% PodcastRSS 0.7% MediaRSS 5.8% RSS 86.3% NPRML
- 51. NPR API : Output Format Distribution per Month
- 52. NPR API : Non-NPRML Output Format Growth
- 53. Questions? Daniel Jacobson [email_address] Twitter: @daniel_jacobson To see the API: http:// www.npr.org/api To follow the API development: http:// www.npr.org /blogs/inside