Subscribe / Unsubscribe Enewsletters | Login | Register

Pencil Banner

6 key network considerations to take into account before migrating to the cloud

Nick Kephart, senior director of product marketing, ThousandEyes | June 3, 2016
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.

This vendor-written tech primer has been edited by Executive Networks Media to eliminate product promotion, but readers should note it will likely favor the submitter’s approach.

As organizations shift more workloads to the cloud they increasingly rely on networks and infrastructure they don't own or directly manage. Yet this infrastructure is just as critical as when applications and services were hosted in the data center. Being able to explore these networks in advance to identify choke points and routing issues 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 you should take into account before shifting to the cloud:

1. Baseline performance before deployment - Getting a baseline measure of network performance when moving to the cloud 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.

Before cloud computing, the network was essentially under an organization’s control. And it’s not that networks are necessarily less complex, it’s just that network teams had access to all the network data, like packets, flows and device level information to monitor performance and security. And when issues arose, teams had the ability to troubleshoot and triage problems.

Traditional monitoring approaches worked in a world where the network was managed and contained, and boundaries well defined. However, these data sources are no longer available for monitoring the performance of the cloud network, where devices can’t be directly instrumented or polled. Visibility into cloud and third-party networks can only come from data sources such as synthetic and end user monitoring. These techniques can provide quality of experience metrics that network teams can rely upon to test configurations and baseline performance before moving to the cloud.

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.

But how do you know what the ideal configurations are before deploying? Time to have a look at your new data sources. The first in your arsenal is derived from a technique you may already be using to monitor application experience in terms of page load and user transaction timings. Synthetic monitoring can be used to gain insight into infrastructure and network performance as well as your application. What’s great about synthetic monitoring is that it works in cloud environments and across the Internet in addition to your data center for in-depth information about how each portion of the network is performing.


1  2  3  Next Page 

Sign up for CIO Asia eNewsletters.