Network Computing is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Identifying Cloud Migraines Before Migration

The move to cloud shows no signs of slowing, with Gartner predicting the worldwide public cloud services market to grow 17.3 percent in 2019. So, as organizations shift more to the cloud, it means they will increasingly rely on networks and infrastructure they don't own and directly manage. Yet this infrastructure is just as critical to consume and deliver the applications and services as when it was in the data center.

Being able to explore these networks to identify choke points and routing issues in advance helps to inform better network investment and configuration decisions. It is essential for a successful cloud deployment as well as ensuring an optimized environment on an ongoing basis.

There are six key network considerations IT managers should take into account before shifting to the cloud. They are:

1. Baseline performance before deployment: Getting a baseline measure of network performance when moving to the cloud, first and foremost, requires adopting a different set of data points than organizations have typically used in the past. The move to IaaS, SaaS, or any cloud service for that matter, means organizations are beholden to those providers as well as third-party service provider networks through which the application or service traffic traverses.

2. See and understand bottlenecks in your infrastructure: It's possible that, based on existing configurations and routing policies, certain offices and sites are not optimized to consume applications or services over the Internet. For example, a branch office in India may have issues accessing Salesforce because of transcontinental latency and a bandwidth constrained MPLS circuit. Similarly, a branch in Austin may have better and more reliable access to applications being served from El Paso rather than San Antonio.

 3. Map out real traffic paths: Having visibility into specific areas of a distributed network that are problematic, as well as pertinent details that can help determine a root cause, results in more tangible and actionable information for the network you own and those of your providers. To achieve a complete picture of how traffic is traversing the cloud network, it is essential to combine synthetic tests with ping and traceroute functionality. Now network teams can not only test the reachability of an endpoint or host through the cloud but also use that data to determine the route or path of a packet through a distributed network while measuring transit delays.

4. Collaborate with SaaS and Cloud providers: So, when it comes time to work with your SaaS, ISP, and cloud providers, it helps to share this information, related visualizations, and diagnostic information in an easily consumable way. That way, when a trouble ticket is generated, it is dealt with much more quickly by the vendor or provider. Knowing exactly where a problem exists, and the related cause analysis empowers teams to take immediate action and enable the responsible party to take immediate action as well.

5. Get things right before deployment: With detailed visualizations and hop-by-hop metrics, it becomes possible to try out a routing change, plan for a new data center or test a rollout of a new application or SaaS service. Synthetic testing layered with contextual data and a detailed visual network topology allows teams to test performance and gain insight into initial infrastructure configurations, plan changes and understand their impact on cloud applications to get things right before deployment.

6. Continually monitor the performance of your network and its impact on applications: The same techniques and data sources teams are used to baseline performance and achieve optimal cloud configurations can also be used on an ongoing basis to ensure continued performance. Active monitoring with additional layered information allows organizations to constantly keep an eye on performance degradation to optimize end-user experiences across their network. 

This virtuous cycle of better performance becomes even more important in the future as organizations increasingly rely on the Internet for their critical operations. Growing levels of software-based automation will only increase the number of different network paths traversed and the resulting end user experience. Accurate insights into the entire cloud network enable organizations to troubleshoot and solve their cloud performance problems, alleviating potential cloud migraines and ensuring the business runs smoothly…and painlessly.