KeynoteGreg Brail

Let’s talk about APIs

The first public APIs

Yahoo, EBay, Amazon, Google

Twitter and its API launches

Knowledge of APIs and their benefits begin to spread

The first “year of the API”

APIs are powering major consumer brands

Netflix, Nike, Nintendo, Walgreens…

A Really Short History of APIs

2004

2006

2011

2009

What Did We Learn From All That?

•Developer experience matters•And your own employees are developers too

What have we learned?

•Public APIs aren’t for everyone•But customer, internal and partner APIs are

What have we learned?

•OAuth and JSON are enterprise-ready •and Internet-scale

What have we learned?

•REST was a PhD dissertation•it has had an amazing amount of impact…•but don’t forget about developers and end users

What have we learned?

•First Generation– Didn’t matter as long as it’s HTTP

•Second Generation– “Pragmatic REST” uses REST concepts and JSON

•Third Generation– Design your user experience for each device– Customize an API for it

Simple API Evolution

The API is not the destination

What Have we Learned?

Let’s Talk About Apigee

Let’s build some hardware for XML

Sonoa ServiceNet appliance

Apigee “free”, Analytics

Developer community features

Apigee Console

We are now “Apigee”

UserGrid, 4th Gen Platform

Apigee

2004

2007

2008

2009

2010

2011

2012

The API proxy is not the destination

What We’ve Learned

•Edge•Insights•Exchange•and more…

Today

•Flexible rate plans•Multi-currency billing•Integrated with Apigee

Monetization

•Structure of API stored inside Apigee•Auto-generated docs•Foundational

API Modeling

•Volos•Argo•Trireme•Usergrid•Others

Apigee Open Source

•Apache Incubator•Years as open source•Members in 170+ cities

Usergrid

•Build with a great community•Run on Apigee•Pick from 45,968 packages•Add Apigee features

Node.js support

Introducing Volos

•Node.js modules•MIT License•Integrates with Apigee

•OAuth 2.0•Quota•Cache•Apigee back-end•Redis back-end•More to come…

Volos

Thank You