The majority of large enterprises are using cloud platforms now but few have shifted this use from their DevOps team over to central IT — but will in the next 1-2 years. When you do, you should quickly get your networking team involved as most of the Dev-to-Cloud connections that have been put in place by your developers may not meet your corporate security or WAN performance standards. This is a key finding in the latest report from myself and Andre Kindness that is now available to clients at Forrester.com.
As you no doubt know by now, from reading our research, cloud use is not an isolated activity. Most applications built in the cloud are native hybrid, meaning they connect to something outside the cloud. Most commonly these applications reach back into your corporate data center to talk to systems of record, such as databases, CRM or ERP systems or other key corporate resources. The connections established most often by these developers are public links secured with SSL or VPN constructs. These are easy to establish by the developers but are often set up without the QoS or security controls your networking teams have established for other corporate WAN links. So if you want consistency in your WAN policies, it’s time to get the networking experts involved.
Carrier Ethernet aims to provide users with a wide-area service to connect sites, in the same way that asynchronous transfer mode (ATM), Frame Relay, and X.25 services from carriers have done in the past. While end user demand for carrier Ethernet services in Asia is relatively small, it’s growing year over year and is having an impact on service providers’ bottom lines: Carrier Ethernet services currently account for 8% to 10% of service providers’ total connectivity revenues in the region.