What’s Next for APIs: Performance Tuning

Kin Lane, July 13th, 2011

New RelicAs the Web API space heats up, it’s becoming more difficult to differentiate yourself and attract developers. And so it’s crucial that your API can perform well. Performance isn’t just about processing requests and delivering responses quickly. As Netflix experienced this year, understanding how users makes calls, why they make the calls they do, and what should be contained in your API payload is critical.

NetflixWith 37x growth in 13 months, the Netflix API has been a success. But did the number of calls on the API directly equal success? Or was it evidence of flaws in the API design? In other words, could the API be less chatty and structure its payloads in more optimal ways?

To figure this out, you need some performance analytics. There are several metering and analytics tools for API owners to employ these days. These can help you play API gatekeeper and traffic cop. But when it comes to performance analysis, it may be that you need something that will track a little deeper.

New Relic is a real-time performance analytics suite for web applications, but their tools can be just as easily applied to deeply analyze the operations of a RESTful API as a Web application.

In addition to offering a window into real-time API operations, New Relic can provide insight into how your change management process is affecting your performance, from version to version. Every time new code is written and released, New Relic can provide visibility into whether its performing optimally compared to earlier version.

Another area New Relic can be applied is to help gauge scalability. It can help you assess the performance of your API as you scale it up and down to meet the demands of your customers.

In addition to the necessary server-side plugins and web dashboard for API monitoring, New Relic provides its own RESTful API for accessing API metrics and dashboard elements. All of this can provide some unprecedented visibility into your API operations.

Tags: Metrics
Both comments and pings are currently closed.

3 Responses to “What’s Next for APIs: Performance Tuning”

July 21st, 2011
at 1:33 pm
Comment by: Website Traffic | What’s Next for APIs: Performance Tuning

[...] What’s Next for APIs: Performance Tuning Related Reading: RSS Feeds & Website Syndication- How to Attract The Search Engine Spiders and Increase Traffic to Your Website (Website) Hi-Traffic Suite How To Get Free Website Traffic and Increase Page Rank – (Step By Step Video Tutorial) developers, insight, payload, payloads, web application Leave a comment Trackback [...]

July 28th, 2011
at 8:16 am
Comment by: Always an Eye on Performance, Google Adds Partial Responses to Some APIs

[...] the next revision of their API. While we are on the discussion of API performance, do read up on a performance tuning article that we recently covered. Related ProgrammableWeb ResourcesLearn more Google APIs Discovery [...]

January 26th, 2012
at 8:19 am
Comment by: Cloud Assault: a Sledgehammer for Your APIs

[...] Assault is part of an API performance tuning trend we wrote about last July. Related ProgrammableWeb ResourcesLearn more Cloud Assault API [...]

Follow the PW team on Twitter

ProgrammableWeb
APIs, mashups and code. Because the world's your programmable oyster.

John Musser
Founder, ProgrammableWeb

Adam DuVander
Executive Editor, ProgrammableWeb. Author, Map Scripting 101. Lover, APIs.