Easily compare ChinaCache and Imperva 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 | Imperva |
---|---|---|
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. | Imperva's CDN (formerly Incapsula) makes your websites and applications faster, more reliable and safer. A global network of servers provides content caching, load balancing and failover, while an enterprise-grade cloud web application firewall and DDoS protection safeguard your site from the latest threats. |
Products
Product | ChinaCache | Imperva |
---|---|---|
Dynamic content deliveryNon-cacheable content delivery. User login, shopping cart ... | Dynamic Content Acceleration | Content Delivery Network |
Small file deliveryStatic object delivery; caching of small files (file size <1 MB) | Static Content Acceleration | Content Caching |
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 | |
Video on demandDelivery of on demand video | Media Acceleration | |
Image OptimizationAutomatic image transformation/compression/optimization | Image Compression | |
DNSAuthoritative DNS for customer domain |
Name Server (NS) Protection
Name Server (NS) Protection is a secure proxy in front of your authoritative DNS
|
|
WAFWeb Application Firewall | Web Application Firewall | |
Anti-DDoSDDoS attack protection. Specific product(s) for this. | DDoS Protection | |
Private CDNDedicated edge resources & custom configs | ||
Edge ComputeRun your code on CDN edge servers |
Network
How many POP locations do ChinaCache and Imperva have in different parts of the world?
Region | ChinaCache | Imperva |
---|---|---|
North America | 8 | 12 |
Latin America | 1 | 5 |
Europe | 3 | 12 |
Russia & CIS | 0 | 0 |
Asia excl. China | 10 | 12 |
China | 400 | 0 |
Oceania | 0 | 3 |
Middle East | 1 | 3 |
Africa | 1 | 2 |
Pricing
Pricing & contract duration | ChinaCache | Imperva |
---|---|---|
Minimum contract term | 12 months | Unknown |
Minimum monthly costs | Unknown | Unknown |
Requests costsCustomers pay for client to CDN requests | None | Unknown |
Ingress costsCustomers pay for origin-to-CDN bytes transferred | Unknown | Unknown |
NA/EU traffic (low volume) | Unknown | Unknown |
APAC traffic (low volume) | Unknown | Unknown |
LATAM traffic (low volume) | Unknown | Unknown |
Features
Web acceleration | ChinaCache | Imperva |
---|---|---|
Instant setupSign up, configure, start testing. | ||
Change propagation delayHow fast do config changes propagate to all POPs? | <5 minutes | Instant |
Apex/root domain OK No performance degradation when using http(s)://domain.com | Non-Anycasted network | Anycasted network (regional) |
HTTP/2 | FAQ | |
HTTP/3 | ||
WebSockets | WebSockets docs | |
IPv6Do the edge servers have IPv6? | At customer request | IPv6 support |
Compression Reduce file size for faster delivery | Compress on the edge | |
Origin pull - protocolHTTP only or HTTPS possible too? | HTTP and HTTPS |
HTTP and HTTPS.
Can be IP address
|
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
|
Can configure specific other Host header.
Forward client request Host header is possible
|
Origin ShieldOne POP pulls from origin, other POPs pull from the shield POP | ||
Waiting RoomDuring peak traffic, route users to a virtual waiting room | Waiting Room | |
Push / uploadStore your content directly on CDN, no customer origin | ||
Cache control - CDN caching |
CDN can honor origin headers
Custom rules can be set by CDN support team
|
Granular control/override rules possible |
Cache control - client caching | Granular control/override rules possible | |
Serve Stale CDN serves cached but expired content in case origin is in trouble | ||
Purge Invalidate or delete cached objects on CDN | <3 minutes delay | Instant |
Purge - capabilities | Purge all, purge by directory | Purge all, by directory, by file extension, by tag(s) |
Analytics | Real time perf and security events dashboard | |
Log files | Logs are daily or hourly |
Available via UI, API, or full SIEM integration
Logs are not delayed
|
API | Purge, analytics, billing. Not configuration | Purge, analytics, configuration |
HTTPS & Content Protection | ChinaCache | Imperva |
---|---|---|
CDN domain HTTPSUse the CDN's domain, like cloudfront.net | Only for testing | CDN and SSL/TLS |
Customer domain HTTPSYour domain in the CDN's certificate | ||
Customer cert HTTPSYour certificate on the CDN | ||
Token authentication | Via authentication header | |
Geo blocking | ||
Hotlink protectionThird parties cannot deeplink to your content | ||
Basic authenticationUser logs in on the CDN to get content | Two Factor Authentication | |
IP white/blacklisting | IP address/ranges/subnets, self-service in UI |
Support
Customer support | ChinaCache | Imperva |
---|---|---|
Documentation | Yes, but not public. | Yes, public |
Humans | Different levels of support are available. | Imperva’s team of support engineers deliver technical assistance 24x7x365 via phone, email, or online via the self service portal |