My previous post used CURL component metrics to illustrate performance in calling the World Bank Countries API (located in Washington, D.C.) from Oregon. The curl resolve, connect, processing, and transfer times for calls from Oregon over a period of one week were plotted and analyzed. Here is the plotted Oregon data…
Continue readingGlobal Monitoring
Using CURL Component Data to Illustrate API Call Performance Patterns
My last post analyzed performance component results produced by the curl Internet data transfer utility in an effort to understand what typically causes slow API call performance. Four instances of unusually slow but successful calls to the World Bank Countries API were studied. In three instances (calls from Oregon, Ireland, and Japan), curl’s Processing Time […]
Continue readingAnalyzing the Causes of Slow API Call Performance
In recent posts I’ve been analyzing the data for a week of API monitoring from four different locations around the globe (Washington, DC, Oregon, Ireland, and Japan). The hourly performance for calls over the week looks like this: Since the World Bank Countries API that’s being called is located in Washington, DC, it’s not surprising […]
Continue readingAnalyzing API Performance by Day of Week
My last post showed how the API Science API can be utilized to create a graphical analysis of API performance binned by hour of day. In this post, we use data extracted from the API Science API to analyze the performance of an API by day of week. This type of analysis would be useful […]
Continue readingAnalyzing API Performance Binned by Hour of Day
Performance data from the API Science API can be analyzed in many different ways. For example, a recent post presents A Graphical View of API Performance Based on Call Location. The analysis uses cURL statistics to compare the performance of monitors that call the World Bank Countries API from various locations around the globe over […]
Continue readingAnalyzing API Call Performance from Different Global Locations Based on cURL Metrics
My previous post presented “A Graphical View of API Performance Based on Call Location.” In that post, we analyzed the performance of a week of calls to the World Bank Countries API (which is served from Washington DC) from four different locations around the globe: Washington DC USA, Oregon USA, Ireland, and Tokyo Japan. The […]
Continue readingA Graphical View of API Performance Based on Call Location
The performance of APIs is dependent on both the processing time from when the API receives a request and delivers a response, and the time it takes for the request and response data packets to traverse the Internet distance between the calling system and the system that hosts the API. The timings for calls to […]
Continue readingHow to Use Your API Science One-Month Free Trial (Part 2)
Part 1 of this series introduced the API Science platform and described the basics of how you can utilize your free one-month trial to monitor and evaluate the internal and external APIs that are critical for your platform to be fully functional. Once you have signed up and reviewed what API Science offers, the sensible […]
Continue readingHow to Use Your API Science One-Month Free Trial (Part 1)
API Science provides new users with a free one month trial. In this post I’ll outline ways you can utilize your free trial to explore the features API Science offers. APIs are an essential component of almost every modern online product. If your product is an app, then you’re providing your customers with information of […]
Continue readingThe Effect of “Internet Distance” on Perceived API Performance
Everyone knows that when we travel, the physical distance we must traverse is a determinate factor in how long it will take for us to reach our destination. We travel highways by car, or go by rail, or fly. By car, we can use maps to plot the shortest, fastest route. By rail or flying, […]
Continue reading