Virtualization stretches the servers, enables scaling up of IT resources on demand and provides a cost-effective alternative to power-hungry data centres. Given all those benefits, it makes sense to use virtualization for networks too. Virtual network components seem to be a logical advancement for the otherwise hardware-based network architecture incumbent in most companies at the time of this writing.
Virtual servers, however, is a rather budding technology and their use is best applied for specific scenarios. As such, virtual servers require the same kind of support, vigilance in terms of security and load balance requirements. For instance, virtual servers still need a robust firewall protection along with a host of other security measures.
You can manage servers but what happens when you consider going for a complete virtual networking model? Is it beneficial for companies? Does the technology hold good for businesses with medium to high level networking demands?
Virtual networking is a viable option only in some cases. Network elements have a heavy dependence on Input-output protocols with a heavy emphasis on data transfer, migration and storage. More often than not, dedicated servers with full-time networking components are required to support such networks.
For one, virtual appliances will make the use of routers, switches and firewalls a resource intensive need in terms of CPU cycles in heavy usage – resources that you could use for good elsewhere. If you did use virtual appliances, you would have to commission extra provisions for your servers in terms of capacity, RAM and performance (which lead to increased costs).
Virtualization solutions require the use of hypervisor software. The hypervisor software also virtualizes all aspects of network interfaces. This is in turn uses up even more CPU cycles. We didn’t even begin talking about the loads of data that passes between the various virtual machines that has to be copied, transferred or stored – all of which contributes to more latency. If your network isn’t robust enough, this load can even make your network go belly-up.
It isn’t all that depressing though. Virtual networks are a perfect solution for any kind of intensive CPU processing without any dependence on dedicated hardware such as using it for web application firewalls (WAF), complex load balancers, etc.
As we can see, there’s still a long way to go for virtual networking to happen -- it is a viable alternative for hardware intensive networking architecture.
The full blown potential of virtual networking is yet to be unleashed. What do you think?