Why OpenAPI Matters

Ever since the Internet was created, the problem of connecting available services with consumers who need those services has been ubiquitous. Developers knew that “surely someone must have solved this problem, but where do I find their solution?” An important development was the invention of APIs (Application Programming Interfaces). APIs enable an outside application to utilize the […]

Continue reading

Diving into OpenAPI 3.1

In the past decade API’s have proliferated. Companies sought increased efficiency through automated business-to-business transaction processing using APIs; web-based companies created APIs to enable developers to integrate their data products into new processes; and new companies were created that pulled data from multiple external APIs and fused it into their own processing to produce unique web products that offered potential audiences a view of meshed data that wasn’t available elsewhere. The pandemic accelerated this trend, as people working from home were no longer able to easily and securely connect to the corporate intranet to accomplish their tasks. As the number of available APIs mushroomed, problems arose…

Continue reading

Why Does Tail Latency Matter?

It’s a complicated question, actually: latency versus throughput. Throughput is how many responses you can give to your varied customers in a certain amount of time. Latency is the amount of time it took for an individual customer to receive the response to their request. If your product is going to succeed, obviously you need […]

Continue reading

Five Ways to Help Your Developers Analyze API Outages

When your product relies on APIs (external or internal), it is critical that you monitor those APIs in order to know when something goes awry that affects your customer’s perception of your product’s current status. There are many ways an API can be down and or adversely affect your product. An external API may simply […]

Continue reading

The Effect of Global Location on CURL Call Metric Patterns

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: The conclusion from studying […]

Continue reading

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 reading

Analyzing API Performance Hour-of-Day Statistics

A recent post analyzed API performance by hour of day over a one-week period. The average performance of calls to the API was fairly consistent, except for calls made in the last hour of the day (the hour before Midnight Universal Time). This plot presents the analysis results: The question is: why was average performance […]

Continue reading

Analyzing 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 reading

A 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 reading