Why do we charge for data transfer out but not for in?

0

Out of curiosity, what are the motivations (some of them might be obvious but I don't want assume too much and leave out other points) to charge for transfer out only? Is it possible there are some technological implications as well?

AWS
已提問 4 年前檢視次數 198 次
1 個回答
0
已接受的答案

In the early days of the Internet (think 25 years ago), there were effectively three kinds of networks:

  1. Content providers / Hosters: Would host content to be accessed, e.g. websites
  2. Content consumers (eyeball networks): Home or company networks were end-users would reside that consume this content.
  3. ISPs (today called transit provider) connecting the two above together.

Keep in mind that at this time content would primarily flow into one direction. This pre-dates concepts like Peer-to-Peer or platforms like Youtube, where users upload masses of content every minute. But it is also the time, when ADSL was invented. Keep in mind that the "A" in ADSL stands for "Asymmetric" because the target group of that product (home users and small businesses) was expected to download more than they would upload.

The rest of the links - and especially the ones connecting content providers to other networks - were symmetric. While these links were heavily used by content providers in the outbound direction (to send out all this content), they were barely utilized in the inbound direction. ISPs would charge per bidirectional capacity (at 95th percentile) and therefore it would make sense to charge content providers only for outgoing traffic.

This principle just stuck throughout the industry since then and never changed, despite so many other things around the Internet changing.

A good summary of this can also be found here: https://medium.com/google-cloud/why-ingress-traffic-to-the-cloud-is-free-79dc217b916

profile pictureAWS
專家
已回答 4 年前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南