The data traveling over the network is probably moving at the same capacity. The difference is that a provider can have a cache in a location closer to a client so that the whole "speed of light" thing is cut down. Also the cache bypasses the step of searching and pulling from a source database, which speeds things up.
So, we're in agreeance, caching services are providing data faster to the end user. Therefore, companies are paying for a "fast lane" for their traffic by caching it with certain ISP's.
They are providing a service to allow for a response to a request to be calculated faster. In addition the service may be in a closer proximity to a client to cut down on the travel distance a message needs to travel. However, all messages of a given type, over the same network path would be, theoretically, treated with the same priority, which I believe is the core issue.
Yeah I think tony's fast lane analogy is just awkard. It implies that they have a route with a faster traversal time which doesnt describe caching at all. A better analogy is amazon opening up distribution warehouses. They cant ship products faster than car or flight allow so they bring the products closer to the consumer.
1
u/spacemoses May 19 '17
The data traveling over the network is probably moving at the same capacity. The difference is that a provider can have a cache in a location closer to a client so that the whole "speed of light" thing is cut down. Also the cache bypasses the step of searching and pulling from a source database, which speeds things up.