Easily compare Tata Communications 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 | Tata Communications | Imperva |
|---|---|---|
| Short profile | Tata Communications is a full service, carrier grade, global CDN that has been in operation since their acquisition of BitGravity in 2012. The CDN rides on Tata’s global infrastructure which is the largest Tier 1 network in the world. Tata’s ownership of the network and peering relationships enable it to be very competitive when it comes to price. | 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 | Tata Communications | Imperva |
|---|---|---|
| Dynamic content deliveryNon-cacheable content delivery. User login, shopping cart ... | Dynamic Site Acceleration | Content Delivery Network |
| Small file deliveryStatic object delivery; caching of small files (file size <1 MB) | Whole Site Acceleration | Content Caching |
| Large file deliveryStatic object delivery; caching of large files (file size >1 MB) | Large Object Rapid Delivery | |
| Live videoDelivery of live video. RTMP? Transcoding/transmuxing? | Live Streaming | |
| Video on demandDelivery of on demand video | Video On Demand | |
| Image OptimizationAutomatic image transformation/compression/optimization | Image Compression | |
| DNSAuthoritative DNS for customer domain |
Name Server (NS) Protection
|
|
| WAFWeb Application Firewall | CDN Security | Web Application Firewall |
| Anti-DDoSDDoS attack protection. Specific product(s) for this. | CDN Security | DDoS Protection |
| Private CDNDedicated edge resources & custom configs | ||
| Edge ComputeRun your code on CDN edge servers |
Network
How many POP locations do Tata Communications and Imperva have in different parts of the world?
| Region | Tata Communications | Imperva |
|---|---|---|
| North America | 8 | 12 |
| Latin America | 0 | 5 |
| Europe | 4 | 12 |
| Russia & CIS | 0 | 0 |
| Asia excl. China | 10 | 12 |
| China | 0 | 0 |
| Oceania | 1 | 3 |
| Middle East | 1 | 3 |
| Africa | 0 | 2 |
Pricing
| Pricing & contract duration | Tata Communications | Imperva |
|---|---|---|
| Minimum contract term | Unknown | Unknown |
| Minimum monthly costs | Unknown | Unknown |
| Requests costsCustomers pay for client to CDN requests | Unknown | 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 | Tata Communications | Imperva |
|---|---|---|
| Instant setupSign up, configure, start testing. | ||
| Change propagation delayHow fast do config changes propagate to all POPs? | <10 minutes | Instant |
| Apex/root domain OK |
Global Anycasted network
|
Anycasted network (regional) |
| HTTP/2 | End of 2017 | FAQ |
| HTTP/3 | ||
| WebSockets | WebSockets docs | |
| IPv6Do the edge servers have IPv6? | IPv6 support | |
| Compression |
Resend from origin
|
Compress on the edge |
| Origin pull - protocolHTTP only or HTTPS possible too? | HTTP and HTTPS |
HTTP and HTTPS.
|
| Origin pull - Host headerUse client > edge value? Set specific value? | Can't configure specific other Host header |
Can configure specific other Host header.
|
| Origin ShieldOne POP pulls from origin, other POPs pull from the shield POP |
Tiered architecture, not single POP shield
|
|
| 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 | Full and granular control | Granular control/override rules possible |
| Cache control - client caching | Full and granular control | Granular control/override rules possible |
| Serve Stale |
||
| Purge |
No longer than 2 mins, often much faster | Instant |
| Purge - capabilities | Purge all, purge by directory, not by tag or header | Purge all, by directory, by file extension, by tag(s) |
| Analytics |
Many metrics in the UI
|
Real time perf and security events dashboard |
| Log files |
Refreshed every 24h. Available via FTP
|
Available via UI, API, or full SIEM integration
|
| API | Purge, configuration. Not analytics | Purge, analytics, configuration |
| HTTPS & Content Protection | Tata Communications | Imperva |
|---|---|---|
| CDN domain HTTPSUse the CDN's domain, like cloudfront.net | CDN and SSL/TLS | |
| Customer domain HTTPSYour domain in the CDN's certificate | ||
| Customer cert HTTPSYour certificate on the CDN |
SNI. Pricing is custom.
|
|
| Token authentication | Via authentication header | |
| Geo blocking | ||
| Hotlink protectionThird parties cannot deeplink to your content | Their support team is needed | |
| Basic authenticationUser logs in on the CDN to get content | Two Factor Authentication | |
| IP white/blacklisting |
White or black listing. IP addresses and CIDR blocks
|
IP address/ranges/subnets, self-service in UI |
Support
| Customer support | Tata Communications | Imperva |
|---|---|---|
| Documentation | Some documentation, not public | Yes, public |
| Humans | All customers get 24/7 email and phone support. | Imperva’s team of support engineers deliver technical assistance 24x7x365 via phone, email, or online via the self service portal |