Your Current Language Is:

Dyn Research: The API Usage Of Managed DNS Customers

By

Chief Revenue Officer

If you are a Dyn power user, you are probably quite familiar with our API. For those of you that are not as well-versed, an API is a set of programming instructions and standards that is open to the public so that developers can integrate with a software.

In Dyn’s case, our API is easy-to-use and allows users to manage their DNS zones, in addition to automating everyday processes. The APIs are built to support an array of common programming runtimes and languages (e.g. PHP, Perl, Java, C#, Ruby on Rails, etc.).

We encourage Dyn Managed DNS users and partners to use our API and I have been interested in just how much it is used. The research team looked into how many monthly requests the API gets and out of those, the percentage that are SOAP versus REST.

We have close to 500 customers who use our API and have experienced tremendous growth in the number of API requests per month over the course of the last two years. We have grown from serving 7.3 million monthly API requests in January 2012 to 38.1 million API requests in September 2013, a 420% growth over a mere 20 months.

API Requests

SOAP vs. REST

SOAP API requests currently form 3.3% of our total API requests. As you can see, over those 20 months, we had not seen much of an increase in SOAP API requests, while the entire growth has been via REST API requests.
REST vs SOAP

Kyle York is the Chief Revenue Officer for Dyn, a cloud-based Internet Performance company that helps companies monitor, control, and optimize online infrastructure for an exceptional end-user experience. Follow Kyle on Twitter: @kyork20 and @Dyn.

Related Posts