Commentary

Cutting Through Buzzword Bull At Interop

After a couple of days in Las Vegas hearing all about 'cloud' this and 'fabric' that, a translation is in order.

Cloud and fabric are the two main themes at Interop 2011, a UBM TechWeb event, and like every IT term that attains buzzword status, these two are overused and ill-defined. So after a couple of days here in Las Vegas, allow me to translate.

According to the generous definitions slung by everyone from keynote speakers to show floor hawkers, "cloud" means any software or virtual machine not running on your local network. Some of these offerings might once have been known as websites, remote displays, or timeshare applications, but cloud suits the zeitgeist, so that's how people are reframing their products.


More Cloud Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

Thus, streaming an application display from a remote server to a tablet is now an example of the cloud at work. Running enterprise applications on internal, virtualized servers is now a private cloud, and mixing on-premises applications with an online, public/shared service is a hybrid cloud.

While all of these examples share elements of a rigorous cloud definition--that is, a shared, virtualized application or server, sized according to need, priced according to usage, and provisioned by end users--they also differ in so many ways that lumping them under the "cloud" obfuscates things.

So when Interop attendees hear the word, they must resist the temptation to equate the touted product with their idealization of a cloud service. That caveat aside, the popularity of utility, cloud-based applications is showing up on the show floor.

Whether it's the ability of virtualized security appliances like Vyatta's to be provisioned using the CloudStack framework or the plethora of WAN optimization products like those from Blue Coat and Riverbed, the cloud, however loosely defined, is changing the product landscape.

"Fabric," meantime, is the nom de guerre for any network equipment that provides:
(a) a high density of 10-Gigabit or greater ports,
(b) sub-five-microsecond latency between ports,
(c) scalable aggregation requiring no more than two tiers between server and core,
(d) data and storage network convergence, i.e., FCoE, and
(e) the ability to manage and apply network policy to virtual ports as if they were physical.

Within these broad criteria, almost every major vendor at Interop is touting a fabric architecture. Alcatel-Lucent leads with its Best of Interop category-winning data center switching architecture. Cisco has Fabric Path (though it has chosen to emphasize its wireless LAN technologies this week). Extreme Networks is showcasing its BlackDiamond X8 192-port-by-40-Gigabit core switch. And Juniper puts hardware to its much-hyped Qfabric architecture.

While they differ in implementation details, which vendors can't resist highlighting to the disparagement of their competitors, they seem to be taking different paths to the same destination: a high-speed, low-latency, converged network designed for virtualized applications. Although vendors love to highlight raw specifications like the number of 10-Gig ports per chassis or maximum number of ports in a low-latency switch mesh, unless you're running a Google-scale data center, these differences are less important than how each vendor's design and management software handle virtual network ports and traffic.

But don't take my word for it. Check out the highlights on Interop TV and see the latest products for yourself.

Kurt Marko is a contributor for InformationWeek.


Yes, you can stay safe in the cloud. In this Tech Center report, we explain the risks and guide you in setting appropriate cloud security policies, processes, and controls. Download the report now. (Free with registration.)

Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
Subscribe to RSS

Resource Links