Timing-Out Slow-Performing External API Requests

API performance varies depending on many variables, including the response of the Internet (for example, resolve time and transfer time) and the timing for work that occurs on the remote server (connect time and processing time). My last post illustrated that calls to the World Bank Countries API sometimes exhibit abnormally slow performance. Unpredictable, though […]

Continue reading

How One Slow External API Can Bring Your Product Down

APIs receive a request from a user, gather data and/or perform some processing based on the request, then return the requested information (or other result) to the user. This sounds simple. But a lot can go wrong, and even when everything succeeds, the time it takes to complete the process can be highly variable. Greater […]

Continue reading

API Performance as a Function of Call Location

Some weeks ago, I created API monitors that call the World Bank’s Countries API from four different locations: Ireland, Oregon (U.S. West Coast), Tokyo, and Washington, D.C. (U.S. East Coast). All four monitors request the World Bank information for Brazil. Here’s a recent view of my API Science Dashboard for these monitors: Each monitor is […]

Continue reading

Creating a Multi-Step API Monitor

One of the unique features of the API Science platform is the capability to create multi-step API monitors, wherein multiple API calls are chained together into a single monitor. If your product requires multiple API calls in order to produce the result you deliver to your customer, you could create a collection of standard single-call […]

Continue reading