Apigee: Secure Protection for APIs and Mashups

14 Oct, 2009, by appsheriff || Topics: Script

apigee

There are Google analytics to help our website, but it is difficult to manage the app against a burst of traffic and whether any API we are using, slowing down it. It is very difficult to keep track of all of thousands of APIs in the web. Apigee functions similar to what google analytics do for the web. Apigee can help you understand API usage, protect your apps and back end from misuse and to control traffic flow.

Apigee is a website that can provides you analytics and throttling for APIs. It can be considered as a cross between “Google Analytics for APIs” and an API circuit-breaker that will keep your app from any traffic spike on your API.

Apigee is brought to you by Sonoa Systems, and built on the same industrial-strength API management platform used by insurance, leading financial services and media companies. It is in beta version now. Sonoa has built the service around its massively, scalable API router. According to the general manager of apigee, they see API like the dark matter of the Internet.

Web developer can know which of the API’s is messing up the mashup or website with the help of easy to understand charts and graphs provided by apigee. If your website is a mashup of several APIs, Apigee would monitor each one for error rates, response time and number of requests being put through which is just to make sure the developer is not hitting the limit. Big sites with popular APIs have a different problem. They set limits so that their servers do not crash, but sometimes one or two heavy users may cause a meltdown. Apigee lets sites throttle API limits with simple sliders and hence, once the limits are hit, any particular API user cannot exceed limit.

The Apigee succeeded in doing this is because it is, in fact, creating a proxy for each API. Proxies are created using Sonoa’s API routers, and the API calls are routed through Apigee. Either the API provider or consumer can set one up a proxy. As you can not drop a Javascript beacon in an API like you can on a Website, this is the only-method by which the broad usage of APIs can be calculated.

The drawback of using Apigee is that it introduces latency into the whole system. Though this latency is only 200 to 300 milliseconds for most apps, it is a huge value for real-time apps like Twitter.

Bookmark and Share

Leave a Reply