What's the difference between THRON Multimedia Proxy and a WAN Accelerator?

Business Case:

KPI to be measured

Bookmark this resource Follow

Ask a question

Was this article helpful? 1 out of 1 found this helpful

Infrastructure upgrade costs and complexity can be a big challenge on enterprise organizations, this is why bandwidth optimization, especially within corporate networks, has become a key requirement and there are many solutions on the market that help you achieve this result, usually referred to as WAN Accelerators.
THRON tackles the challenge from a different perspective, there are some key differences between THRON Multimedia Proxy and WAN Accelerators.

First of all, what's a WAN Accelerator? A WAN accelerator is a device (usually an hardware device / appliance) that aims to reduce the amount of data that needs to be transferred across the network at transport level through caching, adopting data deduplication and compression techniques. In practice, a WAN accelerator caches for duplicate files (or parts of the files), so that it is sufficient to store them in a local cache rather than sending them back across the WAN. WAN accelerators barter the WAN's I/O with the appliance disk's I/O, improving the performance of data transfers in situations where delays are caused mainly by an insufficient bandwidth.

Up to this point it might seem that there's no difference in what the Multimedia Proxy does. The element that characterizes the difference between any WAN Accelerator and the Multimedia Proxy is THRON. THRON has a precise data structure and a strict logic when it comes to content delivery. A WAN accelerator operates on data transmission, there is no correlation with the type of message that data transmission is trying to convey. Multimedia Proxy on the other hand, since it has been specifically built for THRON, knows its data structure and is perfectly aware of how its delivery must be handled according to the content type or the target.

Let's make some examples:

A WAN accelerator, in case of live streaming, can not know which information are actually the same for any user, thus avoiding to re-send them, and this happens especially when the streaming is hooked to authenticated user sessions;
A WAN accelerator can not "explode" encrypted traffic unless it has access to THRON's proprietary certificates, hence it will systematically fail to accelerate encrypted connections (which are actually THRON's default connections), while Multimedia Proxy is capable of handling encrypted traffic natively.
Finally, we can say that a WAN Acceleration is not an alternative solution to THRON Multimedia Proxy because a WAN Accelerator aims to optimize traffic transmitted across the network while THRON Multimedia Proxy avoids that useless traffic is transmitted across the network.
Was this article helpful?
1 out of 1 found this helpful

Have any question?

Open a ticket