Azure Virtual WAN vs. Riverbed SteelHead

Azure Virtual WAN provides single functional interphase for routing, monitoring, connectivity and security operations. The connection of hubs in Azure virtual WAN makes it simple for us to use Microsoft as the pillar of our spoke connectivity. The platform provides us with robust connectivity features that allow for transitive connectivity across different spokes. However, you should always ensure you have understood your total cost of ownership to avoid potential price bombshells.

Incentivized

If you are dealing with large CAD files on a daily basis "remotely", Riverbed Steelhead makes your home office feel just like the office

Incentivized

• It offers a seamless experience while connecting Virtual networks and Workloads via Azure Hub.
• Lot of connectivity options present - site to site VPN/Express route etc.
• Very easy connectivity and migration with on-premise sites and Azure Hub.

Incentivized

• Effectively improves data throughput over VPN WAN connections.
• Seamless operation.
• Optimizes a variety of applications. Including, HTTPS, Citrix, Netapp SM and SV, Exchange, etc.

Incentivized

• Integrations are limited within Azure. It is difficult to carry out multi-cloud integrations.
• If you haven't understood your monthly cost you can receive price shocks.

Incentivized

• A reduction in price is always welcomed
• Simplify and streamline advanced features and add-on pieces for more detailed traffic analysis
• Getting granularity into traffic behavior becomes confusing and very expensive

Incentivized

As we were already using Azure as a cloud platform, it was easy setting up a Virtual WAN inside Azure as users/developers and DevOps engineers were familiar with the user interface and functioning as compared to going to some other portal for just the VWAN solution. The umbrella of features provided by Azure Virtual WAN made it the right choice for our infrastructure.

Incentivized

We tested Cisco eleven years ago in parallel with Riverbed in a PoC. The Cisco configuration was very complex and sticky based on the location. The Riverbed configuration is flexible based on the whole storage. A software client for devices like laptops or tablets is not available for Cisco WAAS, therefore we selected Riverbed based on a PoC.

Incentivized

• Automatic troubleshooting solves incidents without costing our operational time.
• We are able unify all our operational activities.

Incentivized

• Files now open a lot quicker, at near local speeds.
• We are able to respond to customers quicker as we can get access quicker.

Incentivized