Getting Developers hooked on your API by Nicolas Garnier at Codemotion DubaiCodemotion Dubai
Hypermedia, REST, SOAP... It's not a matter of 'why' anymore but rather of 'how'. Still, once your API is all set up, getting developers to use it is a real challenge. A challenge you should be ready to rise to as your API can eventually be its own channel for product adoption. How to make sure developers know about your API, that they use it efficiently and finally, that they love using it.
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.
Getting Developers hooked on your API by Nicolas Garnier at Codemotion DubaiCodemotion Dubai
Hypermedia, REST, SOAP... It's not a matter of 'why' anymore but rather of 'how'. Still, once your API is all set up, getting developers to use it is a real challenge. A challenge you should be ready to rise to as your API can eventually be its own channel for product adoption. How to make sure developers know about your API, that they use it efficiently and finally, that they love using it.
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.
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.
Just a few years back, lack of a standard way to document, govern or describe a contract for the APIs acted as a deterrent to API adoption within the enterprise. WSDL 2.0 and WADL provided early support, but they couldn’t truly capture the essence of RESTful APIs. Recently we have seen the emergence of several description languages. New ways to describe and document APIs have emerged such as Swagger, RAML, API Blueprint and others, each taking a slightly different approach.