| Bandwidth Control |
| Optimize the Use of Bandwidth in the Face of Bandwidth-Hungry, Audio-Video Streaming Applications |
| With the arrival of Web 2.0, audio & video streaming applications have become very popular. It is not just limited to YouTube and Hulu—every major website is incorporating streaming technology to promote its products and services. |
| |
| |
| 40% - 50% of the corporate bandwidth is consumed
by streaming applications these days |
|
| Web 2.0 is Degrading the Performance of Business Applications |
| As bandwidth need has gone up, so has the cost of providing bandwidth for corporations. Many organizations report that annual bandwidth costs have been growing over 30% per year. Bandwidth-hungry streaming can significantly degrade the performance and quality of other applications, such as business-related VoIP calls or online demos. |
Click to Enlarge  |
 |
Zscaler can save real dollars by allocating proper bandwidth to web applications,
while taking advantage of Web 2.0 streaming applications. |
|
| Bandwidth Control by Protocol is Ineffective |
| Traditionally bandwidth has been controlled by protocol. For example, allow 10% bandwidth for FTP, 60% bandwidth for HTTP and 15% for SMTP. Today, over 80% of the Internet-bound traffic from a corporation is HTTP or HTTPS. Allocating 80% of the total bandwidth to HTTP is not helpful if half a dozen streaming applications can consume most of that at the expense of, for example, Salesforce.com or a financial application. |
| Control Bandwidth by Web Applications |
| Zscaler solves bandwidth abuse or misuse problems by providing policy-based control for each major Internet application. For a location with many sales employees, a company can define a policy to allocate at least 20% of the bandwidth for Salesforce.com and 15% of the bandwidth for online meeting applications such as WebEx. |
- Application-based: Tailor bandwidth policy based on applications, such as Salesforce.com or NetSuite, and large files.
- Time-based: Create policies to limit use based on time of day; for example, provide only 15% bandwidth to large files between 8am and 5pm.
- Location-based: Customize policies by location or internet gateway; locations with more sales people may have one policy, whereas locations with largely engineers will have another.
|
| Zscaler Saves MPLS Bandwidth |
| Many enterprises backhaul Internet traffic from various locations around the globe to a couple of central gateways at the headquarters, where URL filtering is performed. This is often done by purchasing multi-packet label switching (MPLS) networks. Backhauling traffic creates latency and costs money. Zscaler’s distributed architecture with dozens of cloud nodes deployed around the globe eliminates the need to backhaul traffic, hence reducing latency and bandwidth costs. |
| To learn more about Comprehensive Managed Access, also read: URL Filtering and Web 2.0 Control |
| To request more information, please click here. |
| |
