Dark Reading 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.


08:29 AM
George Crump
George Crump

Data Center Revolution Or Evolution

I recently read a claim by one major supplier of Fiber Channel over Ethernet (FCoE) technology that it would be the dominant infrastructure in use in data centers in two to three years! Are you kidding me? Other than impossible that is just not the speed at which the data center moves. The data center evolves, it does not revolt.

I recently read a claim by one major supplier of Fiber Channel over Ethernet (FCoE) technology that it would be the dominant infrastructure in use in data centers in two to three years! Are you kidding me? Other than impossible that is just not the speed at which the data center moves. The data center evolves, it does not revolt.There is a constant stream of technologies that claim to have the ability to revolutionize the data center. Currently we have FCoE, Solid State Disk (SSD) and a laundry list of capacity reduction technologies. Technological shift takes years. For example SANs, despite all their advantages over direct attached storage, took five to six years to become commonplace. 3PAR was alone on the thin provisioning soap box for years before it became a must have capability. Data Domain had to try 15 different explanations of deduplication before it became a household (or data center) name.

Technology has to get past the hype phase and into the "understood phase" before it really becomes practical in data center use. Usually this is about two years after the storage industry thinks we have reached full adoption. For example deduplication, despite all the hype, is still only deployed in about 30% of all data centers and is still primarily used in the backup process. Just now companies like Data Domain, Ocarina Networks and Permabit are putting systems in place that address deduplication in the higher tiers of storage.

SSDs similarly have hurdles to jump, while clearly systems vendors like EMC and NetApp as well as SSD specific systems providers like Texas Memory and Violin Memory are seeing dramatic increases in their business. The technology needs to become more price competitive and easier to provide data management on. Companies like Storspeed and Nexenta are addressing the data placement issue by providing systems that have the intelligence to move data between SSD and mechanical drives automatically. This is critical for wide scale deployment since any empty space on SSD is 15X more expensive than empty space on mechanical drives.

FCoE is no different. As we discuss in our article "Planning for FCoE" the technology is becoming mature and there is a need to begin working it slowly into your data center as opposed to the forced path to premature migration. FCoE migration should be done gradually, not overnight and certainly most data centers will not be finished with the FCoE conversion in the next 3 years.

Technology should evolve into your data center. There is almost always a need that a technology like SSD, FCoE or deduplication can address right now. Implement it for those needs and where it can be easily cost justified. This approach allows you to solve today's problem now, then puts you in a place to better understand how to use the technology as it matures and becomes more cost effective.

Track us on Twitter: http://twitter.com/storageswiss

Subscribe to our RSS feed.

George Crump is founder of Storage Switzerland, an analyst firm focused on the virtualization and storage marketplaces. It provides strategic consulting and analysis to storage users, suppliers, and integrators. An industry veteran of more than 25 years, Crump has held engineering and sales positions at various IT industry manufacturers and integrators. Prior to Storage Switzerland, he was CTO at one of the nation's largest integrators.

Comment  | 
Print  | 
More Insights
Oldest First  |  Newest First  |  Threaded View
How SolarWinds Busted Up Our Assumptions About Code Signing
Dr. Jethro Beekman, Technical Director,  3/3/2021
'ObliqueRAT' Now Hides Behind Images on Compromised Websites
Jai Vijayan, Contributing Writer,  3/2/2021
Attackers Turn Struggling Software Projects Into Trojan Horses
Robert Lemos, Contributing Writer,  2/26/2021
Register for Dark Reading Newsletters
White Papers
Cartoon Contest
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2021-03-05
The Blog module in Kentico CMS 5.5 R2 build 5.5.3996 allows SQL injection via the tagname parameter.
PUBLISHED: 2021-03-05
Deutsche Post Mailoptimizer 4.3 before 2020-11-09 allows Directory Traversal via a crafted ZIP archive to the Upload feature or the MO Connect component. This can lead to remote code execution.
PUBLISHED: 2021-03-05
ssh-agent in OpenSSH before 8.5 has a double free that may be relevant in a few less-common scenarios, such as unconstrained agent-socket access on a legacy operating system, or the forwarding of an agent to an attacker-controlled host.
PUBLISHED: 2021-03-05
The npm package ansi_up converts ANSI escape codes into HTML. In ansi_up v4, ANSI escape codes can be used to create HTML hyperlinks. Due to insufficient URL sanitization, this feature is affected by a cross-site scripting (XSS) vulnerability. This issue is fixed in v5.0.0.
PUBLISHED: 2021-03-05
A flaw was found in newlib in versions prior to 4.0.0. Improper overflow validation in the memory allocation functions mEMALIGn, pvALLOc, nano_memalign, nano_valloc, nano_pvalloc could case an integer overflow, leading to an allocation of a small buffer and then to a heap-based buffer overflow.