Easily compare ChinaCache and CacheFly for POP locations, products, pricing, features & support. We hope this helps you better understand the similarities and differences between these content delivery networks.
Company
Company | ChinaCache | CacheFly |
---|---|---|
Short profile | Founded in 1998, publicly traded on NASDAQ (CCIH), ChinaCache is the first CDN in China and generally considered to be one of the better CDNs for China delivery because of their network, knowledge and experience from working with (enterprise) multinational customers. The ChinaCache network and services are not limited to mainland China and ChinaCache has been growing steadily outside China in the past years. | Launched in 2002, CacheFly developed the world's first TCP-anycast based content delivery network. CacheFly has a focus on optimizing the CDN for throughput and has steadily built out the network to now have 50+ POPs on 6 continents. CacheFly provides a 100% uptime SLA and takes pride in acting as 'consultants to our customers'. |
Products
Product | ChinaCache | CacheFly |
---|---|---|
Dynamic content deliveryNon-cacheable content delivery. User login, shopping cart ... | Dynamic Content Acceleration | |
Small file deliveryStatic object delivery; caching of small files (file size <1 MB) | Static Content Acceleration | |
Large file deliveryStatic object delivery; caching of large files (file size >1 MB) | Download Acceleration | |
Live videoDelivery of live video. RTMP? Transcoding/transmuxing? | Media Acceleration | Ultra Low Latency Video Streaming |
Video on demandDelivery of on demand video | Media Acceleration | VoD |
Image OptimizationAutomatic image transformation/compression/optimization | Smart Image Optimization | |
DNSAuthoritative DNS for customer domain | ||
WAFWeb Application Firewall | ||
Anti-DDoSDDoS attack protection. Specific product(s) for this. | ||
Private CDNDedicated edge resources & custom configs | Fully custom solution | |
Edge ComputeRun your code on CDN edge servers | Custom solutions available for edge scripting |
Network
How many POP locations do ChinaCache and CacheFly have in different parts of the world?
Region | ChinaCache | CacheFly |
---|---|---|
North America | 8 | 17 |
Latin America | 1 | 18 |
Europe | 3 | 16 |
Russia & CIS | 0 | 0 |
Asia excl. China | 10 | 7 |
China | 400 | 2 |
Oceania | 0 | 3 |
Middle East | 1 | 5 |
Africa | 1 | 1 |
Pricing
Pricing & contract duration | ChinaCache | CacheFly |
---|---|---|
Minimum contract term | 12 months | 1 month |
Minimum monthly costs | Unknown | $0 (5 TB/m) |
Requests costsCustomers pay for client to CDN requests | None | No |
Ingress costsCustomers pay for origin-to-CDN bytes transferred | Unknown | No |
NA/EU traffic (low volume) | Unknown | $0.03 per GB |
APAC traffic (low volume) | Unknown | $0.03 per GB |
LATAM traffic (low volume) | Unknown | $0.03 per GB |
Features
Web acceleration | ChinaCache | CacheFly |
---|---|---|
Instant setupSign up, configure, start testing. | ||
Change propagation delayHow fast do config changes propagate to all POPs? | <5 minutes | 5 - 180s depending on the change |
Apex/root domain OK No performance degradation when using http(s)://domain.com | Non-Anycasted network |
Must purchase dedicated IP
Or use DNS provider that can do CNAME flattening
|
HTTP/2 | ||
HTTP/3 | ||
WebSockets | ||
IPv6Do the edge servers have IPv6? | At customer request | Custom enablement |
Compression Reduce file size for faster delivery | Resend from origin | |
Origin pull - protocolHTTP only or HTTPS possible too? | HTTP and HTTPS |
HTTP and HTTPS
Match client to edge request protocol is possible
|
Origin pull - Host headerUse client > edge value? Set specific value? |
Configure specific other Host header
CDN can also forward client request Host header to origin
|
Set specific Host header value or forward value from client to edge request. Support for AWS Origin Secret Key Header |
Origin ShieldOne POP pulls from origin, other POPs pull from the shield POP | ||
Waiting RoomDuring peak traffic, route users to a virtual waiting room | ||
Push / uploadStore your content directly on CDN, no customer origin | FTP or Cloud Storage can be enabled | |
Cache control - CDN caching |
CDN can honor origin headers
Custom rules can be set by CDN support team
|
Origin headers are honored. Can config caching overrides |
Cache control - client caching | Origin headers are forwarded to client. Can config overrides | |
Serve Stale CDN serves cached but expired content in case origin is in trouble | CacheFly support team can activate this edge behaviour | |
Purge Invalidate or delete cached objects on CDN | <3 minutes delay | Purge Speed |
Purge - capabilities | Purge all, purge by directory | Purge all and by directory, not by tag or header |
Analytics | Near real-time, lots of metrics | |
Log files | Logs are daily or hourly |
Pull via FTP or have pushed with Log Streaming to customer endpoint
Logs are 5 minutes delayed
|
API | Purge, analytics, billing. Not configuration | Purge, analytics, configuration |
HTTPS & Content Protection | ChinaCache | CacheFly |
---|---|---|
CDN domain HTTPSUse the CDN's domain, like cloudfront.net | Only for testing | Free |
Customer domain HTTPSYour domain in the CDN's certificate | ||
Customer cert HTTPSYour certificate on the CDN | Upload your own Certificate or Include Automatic Certificate | |
Token authentication | Self-service activation/configuration | |
Geo blocking | Self-service activation/configuration. Predefined and custom rules | |
Hotlink protectionThird parties cannot deeplink to your content | ||
Basic authenticationUser logs in on the CDN to get content | Available in a Custom/Private CDN scenario | |
IP white/blacklisting | Custom rules can be scripted (by support team at no extra charge) |
Support
Customer support | ChinaCache | CacheFly |
---|---|---|
Documentation | Yes, but not public. | Yes, public |
Humans | Different levels of support are available. | All customers get 24/7 email and phone support and a dedicated implementation/solutions engineer. Extra support ('Elite managed') available at a fee with SLA for support response time |