The 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 by car, by rail, or by air. By car, we can use maps to plot the shortest, fastest route. By rail or air, it’s a more complicated equation: we must travel from our home to a hub, then travel by rail or train to another hub, then travel from that hub to our destination.

It can even be more complex: you might drive from your home to a train station, take one or more trains to an airport, take a connecting flight to a major airport hub, have a connecting flight at another air hub, get to your destination hub, and then have to reverse the entire process in order to reach your final business destination. All of these hub-related exchanges involve time and scheduling problems. Who hasn’t waited in an airport between connecting flights for inordinate spans of time? https://goo.gl/WdQTTj #DataIntegration #ML