On SOCK(net): Coping with the WAN Problem

On SOCK(net): Coping with the WAN Problem

Technology? That’s easy. Getting it into users’ hands? Not so much. Many enterprise tech teams run into problems when deploy a new solution to a geographically dispersed and “fluidly federated” teams. In the SOCK(net) podcast, “The WAN Problem,” Yadin and Tony discuss the issues — and the right things to do! — with ExtremeLabs’ Tom Henderson and a hands-on-guy, Precyse’s Chris Lewis.

The rate at which the computer industry is innovating far outpaces the ability of most Fortune 2000 companies. At Druva, we talk to a lot of teams within companies who are focused on supporting end users in a BYOD, or what I like to refer to as a “fluidly federated” network environment.

Our clients tell us that choosing a new technology or SaaS solution is the easy part. The hard part often is the deployment of the solution over a geographically-dispersed user base. Users can be located anywhere — across the entire country or spread across multiple countries.

When everyone works in an office with acceptable pipes, the IT folks in charge of deployment don’t have to think about connectivity. But with so many locations, that isn’t always the case.  We work with them to best approach a national or global deployment when parts of the company have limited bandwidth — what we refer to as the “WAN problem.”

In this episode of the SOCK(net) podcast, Yadin and Tony bring on special guests Tom Henderson, principal researcher at ExtremeLabs, and Chris Lewis, lead applications engineer at Precyse Solutions (which works with healthcare organizations to most organize clinical data). They discuss the (real world) best ways to tackle the problem faced by many enterprise tech teams when trying to deploy a new solution to a geographically dispersed teams.

Among the issues discussed:

  • How common it is to support users with limited bandwidth
  • How to work with global telecom companies to make sure you’re getting the bandwidth you’re paying for
  • The stakeholders to include in the conversation — and whom you should “forget” to invite to the meeting
  • And most importantly: the two things that you should never, ever do.

Want to learn more? Listen to the podcast… and hey, sign up for updates, via SoundCloud and iTunes!

https://itunes.apple.com/us/podcast/sock-net-tech-podcast/id1028450860?mt=2

https://soundcloud.com/sock-net/episode-2-the-wan-problem

See also:

Yadin-headshot

Yadin Porter de León

Yadin has spent the last decade in the technology and services field, working with local and global firms focusing on the complex service and product needs of companies within today’s compliance and regulatory landscape. At Druva, Yadin works with our most critical accounts as a technical account manager for the US Western region and takes care of key stakeholders to continually unlock value and strengthen relationships.

Tony-headshot

Tony Piscopo

Tony has been working in a Architecture and Engineering role for the last 15 years for both large enterprises and education. During the last 7 years he held the role of endpoint backup subject matter expert for Pfizer. At Druva, Tony works with our most critical accounts as a Technical Account Manager for the US Eastern region and takes care of key stakeholders to continually unlock value and strengthen relationships.

0 Comments

Leave a reply

Your email address will not be published. Required fields are marked *

*