Hybrid Networking is Available NOW: Why wait for (Windows) 2016 and a New (Azure) Stack?
As customers start moving to the cloud two of the first considerations – and the source of many questions – are networking and security. “How do I connect my data centers to the cloud?” “How do I connect various cloud data centers/zones/regions to each other?” “How do I secure applications in the cloud?” “Can I use my existing firewalls/vulnerability scanners/intrusion detection/compliance/configuration management tools or should I use something different?” Often, security in the cloud is one of the biggest inhibitors to cloud adoption so to overcome these trust issues most cloud providers must provide higher levels of security & compliance than customers usually achieve in house.
Complicating matters further, moving to the cloud is often accompanied by new use cases and applications. Big data, internet of things, microservices…those nice, simple three tier web apps we all used as examples in the past are way too simplistic to model the needs of the network today and new network and security tools are needed to deal with this new complexity. But do your new tools necessarily need to be different in the cloud from those you use on-premises? If you are adopting a hybrid cloud model – whether that means on-premises + public cloud or multiple cloud providers or something in between – I would surmise that in an ideal world you would want to use a common set of tools across each. I have heard from numerous customers that networking was the thing they struggled with the most as they started using other public clouds, with some even saying they had to redo their public cloud networks multiple times before they got it correct.
To learn more and to read the entire article at its source, please refer to the following page, Hybrid Networking is Available NOW: Why wait for (Windows) 2016 and a New (Azure) Stack?- VMware vCloud Blog