Enterprise Storage Strategies

Stephen Foskett

Subscribe to Stephen Foskett: eMailAlertsEmail Alerts
Get Stephen Foskett: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Related Topics: Cloud Computing, VMware Journal, Rackspace Journal, Citrix Virtualization Journal, EMC Journal, Memopal, SaaS Journal, SEO Journal, Azure Cloud on Ulitzer, Enterprise IT: Moving CapEx to OpEx , Java Developer Magazine, Cloud Hosting & Service Providers Journal, Cloud Backup and Recovery Journal, Green Storage Journal, Microsoft Developer, Google App Engine

Blog Feed Post

Cloud Storage Flavors: Platform/Infrastructure and Service/Product

Take a look at the various data storage offerings called "cloud" and your head will start to ache

Take a look at the various data storage offerings called "cloud" and your head will start to ache. How can so many things all bear the "cloud storage" name and yet be so totally different? The answer is obvious to long-time industry observers: Each provider has tailored their offering to make it distinct in the market, and each supports different use cases

Infrastructure versus Platform

Although I am not one to tilt at windmills, especially when it comes to arguing the "rightness" of cloud-based marketing, I sometimes do hit upon a set of terminology that makes sense to me. Wading through the mess of "as-a-service" or "XaaS" names posted by my friend Greg Schulz the other day, it occurred to me that drawing a line between a platform and its underlying infrastructure is quite useful indeed. As Jeff Darcy points out, one can use this distinction to help make sense of the cloud storage landscape:

  • Cloud infrastructure resembles physical infrastructure in many technical ways. Consider Amazon's EBS or the 3PAR, NetApp, and new Symantec storage systems: They are highly scalable and can be used to support multi-tenancy in a service-based model but are also commonly used for very conventional purposes. Indeed, cloud cynics and skeptics would be forgiven for thinking of them as yesterday's fish wrapped in today's newspaper, since the technologies involved have changed very little from the pre-cloud era.
  • Cloud platforms resemble Internet applications and are thus much harder for infrastructure-focused folk to grasp. Offerings like Amazon S3 are a playground for programmers with REST-ish HTTP API access, but appliations expecting conventional blocks or files are left out in the cold. Cloud storage platforms are as different from SAN, NAS, and CAS as Google App Engine or Microsoft Azure is from VMware ESX or Citrix Xen.

When we encounter new beasts, we humans try to group them with more familiar things. Thus, a Pteropus becomes a flying fox, anime becomes a cartoon, and baseball is called rounders for adults. But these groupings often deceive us, hiding both the qualities and novelty of the item in question. Cloud compute and storage platforms are composed of conventional hardware, to be sure, but their uniqueness and value lies in how these building blocks are used.

Cloud storage platforms present a wholly new approach to data storage, with programmable access, integrated metadata, and the possibility of policy-based action. Last year, I called for a real revolution in storage, and today I recognize many of these elements being put into practice with cloud platforms. This is the reason I redirected my career and have devoted my time to evangelizing cloud systems in the enterprise IT community. Infrastructure has little strategic value any longer, so IT must move up the stack.

Service versus Product

Go-to-market approaches also vary among cloud storage products. Simply put, some are offered as services and others as products. Since the value proposition for cloud storage is so strongly rooted in the service provider concept (including multi-tenancy, scalability, high utilization, commodity hardware, and distribution of data), observers are often confused when they encounter a cloud product rather than a service.

Even the nomenclature can get confusing, with many referring to all cloud offerings as "services" regardless of the sales approach used. Many products are sold as "enabling cloud services" or "a foundation for SaaS", and the development of internal or hybrid cloud service providers is a hot topic in IT circles. Although many go-to-market approaches exist, it is fair to say that service-orientation is a hallmark of cloud products.

Enter the Cloud Storage Matrix

Applying these simple labels to the cloud storage market reveals a simple matrix of offerings. Some are clearly conventional SAN or NAS infrastructure products that can be leveraged as a foundation for cloud services. Others are true cloud platforms sold as a product for service providers. Then there is the storage capacity offered on a service basis by hosting providers, including the elastic block storage (EBS) included with Amazon's EC2 cloud compute infrastructure service. Finally, we have the true cloud storage platform services: Amazon S3, Nirvanix SDN, and Rackspace Cloud Files.

EMC's Atmos is an unusual beast indeed. It easily falls into all four quadrants, being sold as both a product and service and used as both a platform and infrastructure. Only EMC can tell if this "all things to all people" approach is working, but it will take some serious resources to make it a success. It certainly confounds the issue for those of us who are trying to bring clarity to the world of cloud storage!

Building Bridges

One thorny issue for cloud storage has been the unconventional HTTP-based access method required by true cloud platforms. This has been something of a chicken-and-egg quandry for businesses developing cloud storage offerings: Conventional block and file protocols enable accessibility and promote usage but also limit the impact of the platform. As Steve Duplessie points out, cloud storage offerings must include real strategic value rather than being sold simply as cheap rental space.

One way to build a bridge between today's world of SAN and NAS and the future of programmable storage platforms is to include both access methods. This is the reason that Nirvanix rolled out its bridge to the SDN, CloudNAS, last year. Conventional applications can read and write to the Nirvanix cloud storage service as if they were accessing a local file system. CloudNAS handles the translation between POSIX filesystem calls on a UNIX or Windows server and RESTful HTTP calls to the cloud. It also includes caching and encryption to address the two most common concerns about cloud storage, performance and security.

Although conventional access methods and product offerings offer an onramp to the cloud, the real revolution will not come until applications are able to seamlessly access stored objects. This is why cross-platform programming libraries like the Zend Simple Cloud API and CloudLoop for Java are so interesting: They bridge a new breed of applications to the cloud storage platforms already offered. Cloud storage is moving up and to the right, adopting both the platform and service orientations that are the hallmarks of the Internet age.

Read the original blog entry...

More Stories By Stephen Foskett

Stephen Foskett has provided vendor-independent end user consulting on storage topics for over 10 years. He has been a storage columnist and has authored numerous articles for industry publications. Stephen is a popular presenter at industry events and recently received Microsoft’s MVP award for contributions to the enterprise storage community. As the director of consulting for Nirvanix, Foskett provides strategic consulting to assist Fortune 500 companies in developing strategies for service-based tiered and cloud storage. He holds a bachelor of science in Society/Technology Studies, from Worcester Polytechnic Institute.