I'm always being asked lately.Tencent Cloud CDNIs it possible to fight or not? Is the domestic node stable? This problem I really can not use “okay”, “good” such a piece of soup words to muddle through. After all, these days, whoever hangs a CDN business is not for psychological comfort, to be a real loading speed and cost optimization.
I have a few projects at hand, from the daily PV hundreds of thousands of content station to the real-time requirements of the SaaS background, have used the Tencent cloud CDN, some pits have stepped on, some surprises have been encountered. Today I'll break open the rubbed, and talk to you about my real experience of the use of the first half of the year, without a filter, and not for anyone to stand.
Let's start with the most intuitive feeling: if you are a major user in the country, Tencent Cloud CDN coverage breadth is indeed the basic solid. The kind of “North Unicom South Telecom” of the old calendar, in which it can not be experienced. I once had a whim to use a distributed monitoring tool to ping a test page I tied to the Tencent Cloud CDN, from Harbin to Haikou, from Shanghai to Urumqi, the latency performance is more balanced than I expected.
Of course, there is absolutely no such myth as “as fast as the whole country”, part of the Northwest occasionally fluctuates slightly, but in the mainstream urban agglomeration, you can hardly find obvious shortcomings. Behind this is its more than 2,800 domestic acceleration nodes in support, quantitative change does cause qualitative change.
But more nodes will be all right? Don't believe this nonsense, CDN is essentially an “operation and maintenance intensive” service.
Configuration policy is the soul. At first, I also made a mistake, the domain name is connected to the default cache rules, and found that some dynamic interfaces are also blindly cached, making a mess of user data. Later I figured out the doorway, its cache configuration system is actually very fine, so fine that you can use the URI suffix, path directory, and even query strings (although it is usually not recommended to cache the content with query strings) to do differentiated rules.
For example, for our site's static resources, I usually set it up this way, directly in the console to match, but the principle is this:
I found that, for images, CSS/JS and other static resources, pulling the cache time full (for example, one year) and adding the “immutable” logo is a major performance optimization tool for modern browsers. This means that when the user visits for the second time, the browser will not send HTTP requests to ask the CDN “if the file has changed”, and directly load the local disk, the speed is a qualitative leap. Tencent cloud CDN console, this rule can be easily matched through the “file suffix”, which is the basic operation.
A little more advanced is that, for frequently updated static resources, such as the front-end packaged with hash fingerprints `bundle.[hash].js`, I even dare to set a more aggressive caching strategy, because the file content changes, the file name changes, essentially a new resource. This set of play to run, can not be separated from the CDN to return to the source of the link of strong protection. Tencent Cloud's multi-source backup and slice back to the source (Range back to the source) function I rely on. My source station set up two servers, a main one standby, once the main machine in the middle of the night, CDN instantly cut to the standby machine, monitoring did not have time to alarm, switching on the completion of the end-user completely senseless. These days, even the CDN have to “defense teammates” (referring to their own unreliable source station), there is no point in disaster recovery capabilities really can not.
When it comes to returning to the source, you have to mention the cost. Tencent cloud CDN billing model is the peak of the bandwidth and the flow of two, which depends on your business curve. One of my video resource station, the traffic curve is like a roller coaster, the peak and trough can be ten times worse, with bandwidth billing on the blood loss. After I cut to traffic billing, the average monthly bill dropped about 15%, but if you are a smooth business, perhaps bandwidth billing is more cost-effective. It has a “change billing method” function in the background, which can be switched on a monthly basis, which is more flexible. My suggestion is to use traffic billing for the first month, and look at the bandwidth monitoring graph in the console, if the curve fluctuates a lot like an ECG, then stick to traffic billing; if it's a smooth straight line, then cut the bandwidth billing decisively, and save a little bit is a little bit.
Security, Tencent cloud CDN integrated basic protection (anti-CC attack, anti-brush) for the general small and medium-sized sites enough. I have a station was once crawler crazy crawling commodity page, directly in the CDN layer configuration of a frequency limit rules, a single IP every 5 seconds more than 20 requests on the pop-up verification code, instantly quiet. Configuration interface is in Chinese, the description is also clear, unlike some foreign service providers, hidden deep not to mention the terminology is also mysterious.
Of course, it's not perfect. Let me complain a little bit: although the console is full-featured, the entrance of some advanced functions is a bit deep, such as “QUIC protocol” acceleration, which is quite obvious for mobile enhancement, but it is not enabled by default, and you have to open it manually in the “Advanced Configuration” of the domain name management. The "QUIC protocol" acceleration is quite obvious for mobile enhancement. Also, its real-time log push, although it supports second delay delivery to the COS (object storage) or CLS (logging service), but the initial configuration for newcomers, the steps are a little cumbersome, the first time I get it also took a little time. However, once matched, the logs are used to do accurate analysis and anomaly detection, is really fragrant.
Oh yes, a reminder, if you are using Vue, React, these front-end frameworks to do the single page application (SPA), must remember to match the “404 back to the source” or “error page redirection” rule. Because the routing of SPA is controlled by the front-end, the user directly accesses a deep path, there is no such file on the CDN, if you don't do anything about it, it will really return 404. The correct approach is to let all the “file does not exist” request, are back to your `index.html`. I've seen several teams step into this pit.
As for the price.Tencent Cloud CDNIt is in the middle of the domestic market, not the cheapest but certainly not the most expensive. It has frequent campaigns, with large vouchers for new users and ongoing discount packages for existing users. My strategy is to buy a “traffic resource package” or “bandwidth package” during the business stabilization period, which can save you another amount of money compared to the volume. This is a common practice, and it's pretty much the same for all of them.
On balance, Tencent Cloud CDN is a “solid honor student” image for me. It may not be as extreme as some niche service providers in a single point (for example, some specifically for video optimization to the bone), but it is in the acceleration performance, node coverage, comprehensiveness, console ease of use and cost, to take a good balance. You are not too easy to find its fatal shortcomings, which for the vast majority of enterprises and developers seeking stability, is precisely the most important. It makes CDN from a need to carefully wait for the “technical work”, become more like a reliable, worry-free “infrastructure”.
Finally, I'd like to share a personal tip: Don't “set it and forget it” with any CDN. Regularly look at the monitoring report, analyze the hit rate, bandwidth/traffic consumption of the Top URL, you may find that some of the old images are still frequently accessed, or there is a sudden burst of pages worth doing more refined caching strategy. Tools are dead, people are alive, the Tencent Cloud CDN these features play to understand, it is your business to speed up the tool; if you throw it there regardless, it is also an ordinary traffic pipe. Well, the experience shared here, specifically how to choose, but also depends on your own business ruler.
