Monday, September 23, 2013

BYOD

It may sound like an acronym on an invite to a bad wedding but it's not... BYOD stands for Bring Your Own Device and it's really not all that exciting.  BYOD is a buzzword, a trend and one cannot ignore the implications behind it. 

It just may be that your employer may someday ask you to bring your own device to work.  For people who work at TURNkey IT, each person gets a mobile phone allowance.  In essence, each person is being encouraged to bring his/her own device and use it for work purposes.  People use their tablets, cell phones and notebook computers for work all of the time. 

The implications on a network are not to be ignored.  On average, each person has 2.2 devices to account for.  Therefore if you have an office of 10 people, it is likely that the wireless infrastructure must support 22 devices.  If you're in a Starbucks with 50 other people, it is likely that their access points are tethered to over 100 devices (or many more).

Users are changing the way they use the internet.  No longer is it just to send a quick email or respond to a text. People are tending to stream music, movies and use bandwidth like never before.  Smartphones, tablets and phablets (phones nearly as large as tablets) are most entertaining when using large chunks of bandwidth.

A single T1 line and a Linksys WRT54G router simply don't cut the mustard any more...  It will be more commonplace to see the demand for 100M fiber connections in the near future and likely increasing to gigabit connections by 2016.

Bandwidth aggregators or link / load balancers help people take multiple ISP connections and put them together.  Now you can have redundancy and total aggregate bandwidth.

Whatever may come of it, technology is very cool and life requires you now to BYOD.  Look around you the next time you're in public, you'll see device after device texting, taking selfies, and generally staying tethered to something.  Google glass thinks we should be even more connected.

We'll see how it all shakes out.

For now,

David Kolssak

No comments:

Post a Comment