Silicon Valley Code Camp : October 5th and 6th 2013
Jonathan LeBlanc is an Emmy award winning software engineer, author of the O’Reilly book "Programming Social Applications", and the Head of Global Developer Evangelism at PayPal. Specializing in identity and security, hardware to web interconnectivity, data mining techniques, as well as open source initiatives around social engagement, Jonathan works on the development of emerging initiatives towards building a more user-centric web.
One of the largest issues in API architecture development is that the task is often driven by the pragmatic indoctrination of a specification into a product rather than designing around the speed and ease of development, usually due to a separation between the engineering teams and their core developer user base.
Extending upon the ideas of API design around developer accelerated development delivered in the PayPal keynote, we will take a deeper look into some of the great techniques delivered to us through the RESTful specification, applying them to developer API consumption practices with the intention of creating efficient best practices for rapid development.
Within this talk we will explore what we have learned through reconstructing our API backbone at PayPal for our developer community, including:
- API automation practices for code reduction and application longevity
- Open security standards that promote developer integration ease and maintain strict security practices
- RESTful API architecture best practices for developer centric accelerated development
Constructing a successful and simple API is the lifeblood of your developer community, and REST is a simple standard through which this can be accomplished. As we construct our API and need to secure the system to authenticate and track applications making requests, the open standard of OAuth 2 provides us with a secure and open source method of doing just this.
In this talk, we will explore REST and OAuth 2 as standards for building out a secure API infrastructure, exploring many of the architectural decisions that PayPal took in choosing variations in the REST standard and specific implementations of OAuth 2.