Earlier this week, Greg speculated that Twitter might have benefited from digging deeper into API metrics and usage patterns, so we thought it would be a good time to put him on the spot with a tech talk he recorded on API visibility a couple weeks ago.
We'd like to run a short series on product and technical requirements you might consider for an API roadmap or strategy. We’ll base this on trends we see in talking to hundreds of product and engineering managers that are either opening or consuming APIs (or aggregating and publishing large numbers of RSS feeds.)
Instead of talking about your APIs functionality, this is about what's *around* the API features and data. Many APIs start out as just raw naked back end features. And there is often a big gap between a raw feature and a full-fledged service, which is your API...
Greg Brail, our CTO, took advantage of a break from O'Reilly Velocity and a new Flip HD ultra to record a series of four short whiteboard talks on issues many face when opening an API - visibility, security, traffic management, and more. Here is the first clip and you can preview all of these and more API case studies on our Apigee youtube channel,