If the testing is automated using the API Science platform, then a second dimension is added: an historical view of the uptime and availability of all APIs that affect the product’s performance. If you have configured automated API monitoring using your API Science account, and you’ve created an API Science API key, then you can access the historical data for any of your API monitors and create whatever view you require of the status of the APIs that affect your product’s viability.
The effect of distance from the queried resource is often underestimated by start-up companies. A study of performance timings for a simple query to the World Bank’s Countries API revealed that a request for a small set of data from different locations around the globe produces very different results.
The effect of distance between the client and the server that is providing the response is far greater than a developer or start-up manager might think. For example, the response time for someone in Tokyo querying a Washington DC API is about 10 times the response time for someone in DC querying that same API. This is why the major Internet companies create data centers across the globe that replicate (though with some delay) what’s happening at their central Silicon Valley data centers.
The upcoming sequence of blog posts will illustrate how you can implement this.