We all know that the simplest CDN architecture is generally as follows:
1
Normal
Usually, CDN edge nodes go directly to the origin site to obtain content. There are hundreds of CDN edge nodes around the world, and there are countless servers in the nodes. If there is no cache in the CDN and people from all over the world visit at the same time, the origin site will crash because it cannot handle too many requests.
2
therefore
Therefore, the editor will talk about the parent layer in this issue. The parent layer, also known as the middle layer or the upper layer, is a scenario in which the protection of the origin site is considered from the CDN side. If it feels familiar, it means your memory is not bad. The previous Tips (2) also introduced a similar scheme for protecting the source station, CDN shield, which is a scenario where the source station is protected from the source station side.
3
possible
Perhaps, some officials will raise such a question, since CDN shield can protect the origin site, why introduce the concept of parent layer? Isn't this superfluous? From two aspects: First, CDN shield provides storage services, similar to the customer's secondary source site, and will incur a certain storage fee. If the customer uses Aspera as the upload method, additional charges will be charged. About Aspera, the real artifact, I will talk about it when I have time in the future. When using the parent layer, there will be no charge, at least most of the CDN providers I know so far do this. Furthermore, CDNs are all about providing end-to-end services and protection, so isn’t it just the right thing to do? Whether it is front-end or back-end, CDN can escort the origin site.
4
if
If many edge nodes are compared to children, the parent layer, as the name suggests, is the father. Although this will be a bit ridiculous, which family will raise hundreds of children? However, please believe the editor's judgment, CDN has indeed done it, and it has done a pretty good job. The father not only fulfilled the children's wishes, but also took on the children's homework. Looking ahead, when the edge node receives a large number of requests, it will go to the parent layer first. If the parent layer does not hit, it will converge back to the source. Looking back, the origin site only receives requests from the parent layer, which greatly reduces the pressure on the origin site. The origin site can spend more resources to do other things, and the overall CDN performance is improved.
This issue of Tips is here, see you in the next issue~
We all know that the simplest CDN architecture is generally as follows:
1
Normal
Usually, CDN edge nodes go directly to the origin site to obtain content. There are hundreds of CDN edge nodes around the world, and there are countless servers in the nodes. If there is no cache in the CDN and people from all over the world visit at the same time, the origin site will crash because it cannot handle too many requests.
2
therefore
Therefore, the editor will talk about the parent layer in this issue. The parent layer, also known as the middle layer or the upper layer, is a scenario in which the protection of the origin site is considered from the CDN side. If it feels familiar, it means your memory is not bad. The previous Tips (2) also introduced a similar scheme for protecting the source station, CDN shield, which is a scenario where the source station is protected from the source station side.
3
possible
Perhaps, some officials will raise such a question, since CDN shield can protect the origin site, why introduce the concept of parent layer? Isn't this superfluous? From two aspects: First, CDN shield provides storage services, similar to the customer's secondary source site, and will incur a certain storage fee. If the customer uses Aspera as the upload method, additional charges will be charged. About Aspera, the real artifact, I will talk about it when I have time in the future. When using the parent layer, there will be no charge, at least most of the CDN providers I know so far do this. Furthermore, CDNs are all about providing end-to-end services and protection, so isn’t it just the right thing to do? Whether it is front-end or back-end, CDN can escort the origin site.
4
if
If many edge nodes are compared to children, the parent layer, as the name suggests, is the father. Although this will be a bit ridiculous, which family will raise hundreds of children? However, please believe the editor's judgment, CDN has indeed done it, and it has done a pretty good job. The father not only fulfilled the children's wishes, but also took on the children's homework. Looking ahead, when the edge node receives a large number of requests, it will go to the parent layer first. If the parent layer does not hit, it will converge back to the source. Looking back, the origin site only receives requests from the parent layer, which greatly reduces the pressure on the origin site. The origin site can spend more resources to do other things, and the overall CDN performance is improved.
This issue of Tips is here, see you in the next issue~