Cloudinary Blog

A Primer: Content Delivery Through a China CDN Partnered With Cloudinary

Akshay Ranganath
By Akshay Ranganath
Content Delivery Through a China CDN With Cloudinary

In February 2018, Cloudinary announced its support of content delivery through CDNs [content delivery networks] in China. With this offering, we announced the ability to support features like automatic format f_auto, DPR selection dpr_auto and authentication (using token and cookies). This post elaborates on the CDN options available to you and the related setup requirements.

Note
China CDN is an advanced solution and available for our Enterprise customers only.

Delivery of China-Destined Content Through a China CDN

As my colleague Maor Gariv explained, fast delivery of online content requires that CDN edge servers be close to viewers. For audiences in China, delivery must be through a local CDN. At the outset, you might need to procure an Internet Content Provider (ICP) license. Whether that requirement pertains to you is a legal question so consult with your legal team. Typically, an ICP license is required only if your business operates out of Mainland China and you want to host or cache content on servers there. For more details, see these two references:

Cloudinary and Its China CDNs

Cloudinary has partnered with China CDNs Akamai and ChinaCache to help our customers with content delivery in China. Akamai requires a valid ICP license. Also, even though that CDN supports HTTP traffic through its secure network, your traffic must be HTTPS based. On the other hand, ChinaCache offers a partnership whereby customers can leverage one of its subdomains for delivering status resources. Therefore, you can work with ChinaCache without an ICP license or if you’d like to deliver either of the following:

  • Traffic on a domain with a valid ICP license
  • HTTP traffic The simple decision tree below helps you decide which China CDN to opt for: Akamai or ChinaCache.

Image Source

Note

  • With a valid ICP, you can work with ChinaCache even though the setup involves a bit more paperwork. See the next section for details.
  • Both Akamai and ChinaCache require that you go through a validation process even with a valid ICP license, lengthening the integration time.

Differences Between Akamai and ChinaCache

Akamai and ChinaCache differ in two aspects: cache invalidation and contractual details.

Note
The following is a comparison between the two CDNs when working with Cloudinary for media delivery. This is not a comprehensive comparison between the 2 CDNs.

Cache Invalidation

Integrated with Cloudinary as one of its core CDNs, Akamai is available as a network choice for delivering media. If you delete or modify media assets, Cloudinary’s automated workflow seamlessly clears Akamai’s CDN cache. ChinaCache’s integration with Cloudinary yields a custom CDN for delivering your Cloudinary-hosted content. That means that, in case of asset updates or deletions, Cloudinary cannot automatically clear ChinaCache’s cache and that you must build a process to ensure that the changes are in place on ChinaCache. Cloudinary’s webhook notifications could help you set up the workflow.

Contract Requirements

Cloudinary can easily add domains with Akamai. As a customer, you only need to fulfill the formalities for account modifications or upgrades with no need for a separate contract to adopt Akamai as your China CDN. However, to enable Cloudinary to integrate with ChinaCache for content delivery, you must enter into a contract agreement with that vendor.

Time to Market

The biggest unknown for Cloudinary’s integration with a China CDN is how long it takes to obtain an ICP license. If you already have such a license and have no vendor preference, integration takes about a week, which is the time required for us to submit the license application to the CDN and for it to validate and whitelist the domain for delivery. If you don’t need an ICP license, you must first step through the procurement process with ChinaCache. This will involve some time to work on a new contract with ChinaCache. Once that’s complete, the integration at Cloudinary takes about five workdays, after which you must build the workflow for cache invalidation, which could take a few days to weeks. Overall, assume that a robust implementation of China delivery would take 15 to 30 calendar days. Again, that estimate does not include the time required for procuring an ICP license.

Conclusion

Now you have an idea of the two CDN options for delivering content in China through Cloudinary, the process of implementation, and the related schedules. Feel free to contact us with any questions and sign up for free. Our best wishes for a smooth sail in building a blazingly fast experience for your audience in China!

Recent Blog Posts

Amplify Your Jamstack With Video

By Alex Patterson
Amplify Your Jamstack With Cloudinary Video

As defined by Amazon Web Services (AWS), Amplify is a set of products and tools with which mobile and front-end web developers can build and deploy AWS-powered, secure, and scalable full-stack apps. Also, you can efficiently configure their back ends, connect them to your app with just a few lines of code, and deploy static web apps in only three steps. Historically, because of their performance issues, managing images and videos is a daunting challenge for developers. Even though you can easily load media to an S3 bucket with AWS Amplify, transforming, compressing, and responsively delivering them is labor intensive and time consuming.

Read more
Cloudinary Helps Move James Hardie’s Experience Online

While COVID has affected most businesses, it has been particularly hard on those that sell products for the physical ‘brick and mortar’ world. One company that literally fits that bill is our Australian customer James Hardie, the largest global manufacturer of fibre cement products used in both domestic and commercial construction. These are materials that its buyers ideally want to see up close, in detail. When customers have questions, they expect personal service.

Read more
How to Build an Enhanced Gravatar Service, Part 2

Part 1 of this post defines the capabilities of an enhanced Gravatar service, which I named Clavatar, and describes the following initial steps for building it:

This post, part 2 of the series, explains how to make Clavatar work like Gravatar and to develop Clavatar’s capabilities of enabling requests for various versions of the images related to user accounts.

Read more
How to Build an Enhanced Gravatar Service, Part 1

The advent of web development since 25 years ago has given birth to an abundance of online services that help developers build apps efficiently and smoothly. Gravatar is a shining example of such a service. Built by WordPress, Gravatar generates globally recognized avatars. Fun fact: 80 percent of Gravatar users first came across that service when reading a WordPress blog.

Read more