In our last couple API strategy workshops, we've had good discussions on a common question for API providers - do you need to offer an SDK (software dev kit) for your API?
In this context we defined an SDK as going beyond offering an API to include platform-specific code that developers use in their apps to invoke API operations, also including the source code, and documentation that developers might need. Here's what we came up with:
Reasons to consider an SDK:
Speed adoption on a specific platform - for example Objective C SDK for iPhone. Lots of...
We're excited to announce the general availability of Apigee Enterprise 3.8! Some highlights:
OAuth 2.0 – Apigee Enterprise 3.8 is Oauth 2.0, draft version 10, compliant. If you are running our OAuth 1.0a solution, you can migrate to OAuth 2.0.
Developer Connect - a Drupal-based portal you brand with your look-and-feel and use for publishing API documentation, content, and community management. Give your developers their own API testing console and other social publishing features such as blogs and forums. See more developer portal details here.
Key Manager Service - handle the complete lifecycle for API keys and security...
How to explore Facebook's new Places APIs in the Apigee Test Console:
Don't have a minute to watch the video? Start by viewing the checkins at the Cookie Jar.
If you rely on Twitter to see what your friends are having for lunch, waiting 24 seconds to get an update is fine. If you're a stock trader who could have lost a few thousand dollars or more while reading this post, 24 seconds is a very long time to learn that your favorite company just got acquired.
Real-time runs on APIs as much as it runs inside a web browser. This means that the "real-time web" isn't always "real-time"- a web service API is typically a request-response technology, requiring that the client makes a request of the server, waits...
We've seen an architectural pattern emerge over the last two years that deals with the expanding variety of computing devices and the exploding number of APIs used in modern applications. This pattern is API Virtualization - applying a virtual layer above the API itself to deal with the different concerns that come into play when delivering an API to different device and machine endpoints as well as across a range of different classes of business relationships.
One of the big shifts that has occurred...
One key point is that an API can be driven by a relatively small team.
Yet an API has a disproportionate impact on the business, and this impact scales with low marginal costs.
This can be an especially effective strategy for retailers that might live in world of thin margins, limited resources, and the constant pressure of the peak holiday...
Facebook and Twitter are cache assembly lines -- every web page and API request is served up by many calls to various caches at different levels - assembling the final result from many different chunks. At this scale there is almost no other way to deliver reasonable performance.
For APIs - what's the largest chunk of all? The entire API response.
APIs lend themselves nicely to caching responses because it is often easy to identify the cache...