To cope with the complicated network environment and fix various network problems in internet businesses, Tencent Cloud deploys high-performance cache nodes globally based on the existing network structure to create a new virtual network architecture, so you can store your business content on the edge servers closer to your users according to your cache policies, shortening the distance between users and content, reducing the access latency, and improving the availability.
To better distinguish between the acceleration services, Tencent Cloud provides different products for different acceleration types:
Comparison Item | CDN | ECDN |
Use case | Static website resource acceleration, file download acceleration, and audio/video on demand website | Ecommerce, in-game payment, financial website, and online education |
Coverage | Chinese mainland Outside the Chinese mainland Global |
|
Billing Mode | Billed by traffic hourly Traffic packages available for users in the Chinese mainland. For more information, see Billing Overview of CDN |
Billed by number of requests and excessive traffic For more information, see Billing Overview of ECDN |
Acceleration method | Static content is accelerated, and dynamic content is pulled from the origin server | Dynamic acceleration and dynamic/static acceleration are supported |
Resource reserve | More than 2,800 nodes in over 70 countries/regions, with a total reserved bandwidth of over 150 Tbps |
When connecting a domain name to be accelerated to Tencent Cloud, you can select either of the two products in the CDN console:
Note that the two acceleration types use different acceleration policies and billing standards. For more information, see Billing Overview of CDN and Billing Overview of ECDN respectively.
A user in Shenzhen accesses an origin server in Beijing whose address is 1.1.1.1
through cdntest.com
.
cdntest.com
for access, the local DNS resolves the configured CNAME record value cdntest.com.cdn.dnsv1.com
, and the request is sent to Tencent's proprietary DNS scheduling system and assigned to the optimal CDN edge server close to the user whose IP is 2.2.2.2
.2.2.2.2
. If the content has been cached on it, the user's requested content will be returned, and the process ends.1.1.1.1
, and the requested content will be decided by the configured host header.2.2.2.2
gets the resource from the origin server, it will be cached on the edge server according to the custom cache policies and returned to the user. Then, the request will end.cdntest.com
again, the Tencent DNS scheduling system will preferentially schedule the request to the CDN edge server whose IP is 2.2.2.2
, as it already caches the corresponding content. In this way, the user can directly get the content from the edge server without requesting it from the origin server.cdntest.com
, then cdntest.com
is the acceleration domain name..cdn.dnsv1.com
or .dsa.dnsv1.com
, such as cdntest.com.cdn.dnsv1.com
and cdntest.com.dsa.dnsv1.com
, which needs to be resolved in the DNSPod console.1.1.1.1
, which is the origin address.1.1.1.1
, the actually requested address is originhost.com
, that is, originhost.com
is the host header. Generally, the acceleration domain name and the host header domain name should be the same, which can be adjusted based on your business needs.Configuration Item | Description | Use Position |
---|---|---|
Acceleration domain name | Domain name to be connected to CDN, which is the actual domain name accessed by end users | Create a Domain Name > Domain Configuration |
Origin address/origin domain name | IP address (domain name) of the origin server. If the requested content is not on the CDN node, this address (domain name) will be accessed to get the requested content. Origin server: server that provides a service, which can process and respond to user requests. End users access your business at the origin address. An origin address can be a domain name or IP address. The origin address cannot be the same as the acceleration domain name. |
Create a Domain Name > Origin Configuration |
Host header | Server content actually requested during origin-pull of the CDN node. | Create a Domain Name > Origin Configuration |
CNAME domain name | After your acceleration domain name is connected, the system will automatically assign a CNAME domain name suffixed with .cdn.dnsv1.com or .dsa.dnsv1.com .After your acceleration domain names are mapped to the CNAME domain name, Tencent Cloud will dynamically change the IP address pointed to by the CNAME record and update all your acceleration domain names, eliminating your need to manually change the IP addresses pointed to them. |
Configure CNAME |
Note:The above data is for reference only. Data fluctuations in complicated network environments are normal.
Note:The above data is for reference only. Data fluctuations in complicated network environments are normal.
Note:The above data is for reference only. Data fluctuations in complicated network environments are normal.
Note:The above data is for reference only. Data fluctuations in complicated network environments are normal.
If you are a new user and activate the service in the CDN console, both CDN and ECDN will be activated, but the unused service will not incur fees. For more information, see Configuring CDN from Scratch.
If CDN is activated but ECDN is not, when you add a domain name for dynamic/static acceleration or dynamic acceleration for the first time, the system will automatically activate ECDN for you as shown below:
If you already activated ECDN in the original ECDN console, you can submit a ticket for migrating your account. After successful migration, you can use ECDN in the CDN console.
Note:
- Dynamic/Static acceleration: it is applicable to business scenarios where dynamic and static data is integrated, such as various website homepages.
- Dynamic acceleration: it is applicable to scenarios such as account login, order transaction, API call, and real-time query.
Fees generated by an ECDN domain name will be billed according to the billing overview of ECDN.
If your business has additional requirements for security, you can purchase an additional security service based on CDN, i.e., SCDN. For more information, see Secure Content Delivery Network.
End User Location | Acceleration Effect | Selected Acceleration Region |
---|---|---|
Chinese mainland | Access requests from global users will be scheduled to the cache nodes in the Chinese mainland for service | Chinese mainland |
Outside Chinese mainland (including Hong Kong, Macao and Taiwan (China)) | Access requests from global users will be scheduled to cache nodes outside the Chinese mainland for service | Outside Chinese mainland |
Global | Access requests from global users will be scheduled to the nearest node for service | Global |
CDN and ECDN both have globally deployed edge servers to route end users to the nodes nearest to them in their respective regions based on your choice. Note that the billing standards vary by acceleration region. For more information, see Billing Overview.
Note:If you have purchased a traffic package, check whether the regions where it is available match your needed acceleration region.
This tutorial describes how to quickly configure CDN/ECDN and the relevant parameters. Click Configuring CDN from Scratch to view it.
Was this page helpful?