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

Partner news: Cloudinary-Getty Images Integration

Supported by intelligent automation, Cloudinary serves as an effective conduit between media asset management and delivery so you can take maximum advantage of assets, compress workflows, and build and coordinate engaging and inspiring customer experiences. Through Cloudinary’s Digital Asset Management (DAM) solution, which employs the company’s innovative image and video APIs, creative and marketing teams can benefit from them, as well as from many AI-powered and automated capabilities. As a result, you can transform, optimize, and deliver media at scale on an intuitive UI.

Read more
Why Audio in Video Matters

Many content creators and consumers tend to regard video as visuals, but that’s only part of the experience. Immersive video content includes strong audio. Just like in a movie, the audio for video content comprises many components: the narrator or subjects, the background music that sets the mood and draws viewers in, sound effects, and so forth.

Read more

For Developers: the HTML <picture> Element Explained

By Amarachi Amaechi
For Developers: the HTML <picture> Element Explained

We all know the good ol', tireless <img> element, which has been a long-time go-to for inserting graphics into webpages. Time doesn’t stop, however, and neither do technological advancements. So, let’s get you up to speed with the element’s modern alternative: the <picture> element.

Read more