Recently in Business Strategy Category

In the first quarter of 2010, we created a 4-phased Cloud Storage Maturity Model which still makes complete sense in 2012. The market is finding the way forward, following the blueprint we described almost to a T.

With our cloud storage maturity model in mind, here are some thoughts on the trends we're seeing this year. What we're describing is the State of Cloud Storage in 2012:

• The rise of a new application delivery architecture

We think this year everyone will figure out that cloud storage is not just cheap storage via the web, but the delivery of a new application architecture, whereby applications are fully contained on a variety of devices (smartphones, tablets and PCs) and the backend is a cloud data store with REST APIs. 

• The consumerization of everything

Enterprises as well as large institutions will seek alternatives to allowing their employees to use consumer tools like DropBox as well as alternatives to tools like box that still store data (albeit encrypted) in a public cloud (i.e. Amazon S3). This trend, aptly named the "consumerization of IT" is creating many alternatives that provide more security, and integration with key corporate support tools.  Cloud Storage is a key enabler of the consumer tools that have found favor with early and wide adoption, so look for the successful entrants with enterprise class security to be based on cloud technologies, and stored behind private firewalls so that the solutions will be as attractive to end users as the consumer tools, but that IT can control the security of their confidential corporate data and compliance initiatives.

• Disintermediation of services
  

The disintermediation of telcos and device manufacturers will continue, with the most cogent example being Apple delivering text messaging "off network" via iCloud.   Already, with devices using WiFi, from multiple suppliers, a storage cloud is a key enabler of these services.

• Manageability

Storage cloud manageability will grow as a requirement as the storage clouds get larger.  Storage clouds will become a delivery vehicle for highly complex management schemes focused on storage tiering. Let's talk ITIL in the Cloud.

Ladies and gentlemen, fellow citizens of the Cloud, the enterprise is ready for cloud storage. Let us know what you think.

Let's discuss the rapid adoption of "App Stores", and the types of applications that are being enabled for a variety of devices, primarily tablets and smartphones. While these applications are each written to deliver unique capabilities and take advantage of the platform they are designed for, as well as being written for different platforms (for example, Android apps are developed in JAVA, Apple IOS apps in Objective C) they share a common enabling technology: REST API access to a storage cloud.  

This approach is rapidly enabling new applications, which differ from older approaches like client server, virtual desktop and Web browser enabled applications in very important ways.  The backend infrastructure ( a REST API storage cloud) is a simple, massively scalable server-based solution, that can reside within the enterprise data center (a private cloud), or at an IT Service Provider (either a hosted private cloud or a public cloud). It is easy to scale, easy to manage, and by providing a consistent storage backend, it allows developers to focus on their applications and associated business logic versus worrying about the backend architecture. This provides for a "separation of concerns" in that Web, Windows, MAC, Android or IOS applications can be substantially different, but they all use the same REST API of the storage cloud they depend on. As your application use and portfolio grows, you simply scale the storage cloud, versus having to make significant changes to the server infrastructure, as is the case with client server, virtual desktop or Web browser enabled applications.

The disruptive wave is coming fast, and you will see it bringing new capabilities and applications for that large screen in your automobile (watch for car makers offering applications in App Stores), a touch screen on your refrigerator, as well as enterprise applications that will support tablets and smart phones.  Think about estimating at a job site with an application on a tablet, or estimating a property insurance damage claim with a tablet, the application is on the tablet, and the data could reside in multiple storage clouds.

Expect to see more enterprise applications taking advantage of this low cost, and easy way to deliver the kind of applications their employees and partners need.

Enterprises are increasingly looking to on-premise private storage clouds as a cost-effective way to share information.  Why?  A cloud behind the firewall enables users to easily access, share and collaborate without compromising data security, integrity and availability.  But there are still a few points every enterprise needs to consider before making the decision.

1. Consider your security needs.  How private is a private cloud?  How confidential is the data that you may ultimately store in the cloud?  Do you want the cloud behind your firewall, and if so, how will you access it?  Will you open a port and depend on a user id and password for access control, or will you also require that your cloud is accessed via a VPN?  Remember, today an employee can decide to email a confidential file to someone outside of the firewall, so what do you really accomplish with a "private cloud"?  If the cloud is available thru a port, can you monitor the cloud and shut it down when (not if) it comes under attack?  If the data being stored cannot be compromised then it cannot be on a network, at all.
   
   
2. Make sure you have adequate internal resources.  Do you have the scale, expertise and data center space to host your own private storage cloud and will you save money versus public, multi tenant storage clouds?  Assuming that your analysis of number (1) above suggests that a private cloud is a desirable approach, then our experience is that you can host your own cloud for an identified operational cost that is at least as low as the public provider.  Now, if it forces you to accelerate capital consumption in order to build out a data center, it may be a poor decision.  But all those sorts of things being equal, you can do it.  The intangible costs, like unanticipated headaches, dilution of focus on your scarce resources, and or a poor choice of cloud infrastructure can quickly turn a winner into a loser.
   
   
3. Identify a use case before starting.  A common mistake that we see is the extraordinary focus on the technology as opposed to a focus on your cloud storage use case and the business case that surrounds the use case.  The project should start with an analysis of the use case and its resulting impact on the business, and operate on the assumption you can source a cloud of appropriate size, scalability and costs.
   
   
4. Research technology solutions that are most appropriate for your use case. When you take the use case approach, you will quickly understand that a private cloud is not just a storage infrastructure; but rather an ecosystem of cloud storage clients, backup and archive solutions, special purpose data movers, management and support, that, when combined with a cloud storage infrastructure gives you a complete solution.  Once again, a use case focus will flush this out, versus a platform technology led process.
   
   
5. Integrate cloud storage with your overall cloud computing strategy.  A storage cloud is simply one layer of a cloud computing stack.  How does this cloud fit within your cloud computing stack?  Does the way in which you integrate it support the other cloud computing decisions you have made?  Evaluation of the cloud storage solution and how it will interact with, support and/or be the infrastructure associated with your overall computing cloud is a critical part of your overall evaluation.  You may also choose to use a service provider hosted "private cloud" to solve issues associated with your deployment, and not ever deploy the storage part of a compute cloud within your own data center.   

And finally, you may want to check out our FREE TOOLKIT >>
CLOUD STORAGE: A BUSINESS MODEL for THE ENTERPRISE

After looking at this snippet I decided to read the full paper from Appirio.  It actually says that 68% of "cloud adopters" expect to have the majority of their data and applications in the cloud within three years. 

What we are not told is the actual % of cloud adopters amongst medium and large enterprises. So, 68% of some subset of medium and large enterprises are racing to the cloud - not bad - but not the marketplace as a whole either.

Since "cloud adopters" are also early adopters, it comes as no surprise that they are rapidly moving to the cloud and will be done in three years.  They are also doing it because they intuitively understand that the cloud is the right thing to do, and they know that even if it is at best a break even proposition today, they will be the first to arrive at the true benefits.  Or, perhaps, they are solving something more problematic than others may be enduring, like poorly designed home grown applications, legacy application that are ready to cycle out, lack of capital for data center expansion, or any other of the many drivers that sends you to the cloud for a solution.

 Also, cloud adoption is slowed primarily by security concerns, and two concurrent activities are solving this problem on a daily basis.  One, IT organizations are winding up their early evaluations and figuring out what they can immediately live with in a cloud solution.  Second, improved security solutions are racing to market to solve these concerns associated with cloud based solutions, so more and more cloud capabilities are now deemed secure.  This trend will continue until security is no longer the blanket excuse for not becoming cloudy, and instead wide spread adoption will be governed by capacity, conversion capability, business case process and analysis, and the orderly march to the next generation of computing infrastructure.

I have a golden rule of IT technology adoption:  It always happens, and it always happens slower than the industry pundits suggest.  Cloud computing is no different.  As a matter of fact, it is very supportive of my golden rule of IT Technology, and is behaving in the usual, predictable fashion. Every time someone tries to convince me otherwise, I think about IBM, the mainframe, and the many occasions it was pronounced dead.  I went to that funeral twenty years ago and it is still growing strong.  How about the AS/400? Same story.  

Now is an exciting time to be in information technology.  What excites me about cloud computing is that it is an approach to computing service delivery that is driving significant technology investment and the promise of significant returns.  And, it is being delivered in the crucible of the open market, not by government edict, or with central planning, but with the chaos and creative destruction that only capitalism can provide.

Dan Decasper co-founded Cirtas with the vision of enabling the enterprise to utilize cloud storage as if it were a local array.

CloudStorageStrategy.com asked him a few questions about "Cloud Storage Controllers" and what the technology means for the enterprise. 

Note: Cirtas is a Mezeo Ready Solution Partner.

What was the original idea behind Cirtas?
Cirtas' co-founders previously built a WAN optimization company that was acquired by Citrix.  Together, they saw the coming of the cloud and recognized that broad scale adoption of cloud storage would require a "catalyst" technology to make the experience seamless and high performing.  They had the expertise to develop such technology and founded Cirtas to address the market need.

What is a Cloud Storage Controller?
A Cloud Storage Controller (CSC) is analogous to the array controllers found in enterprise storage systems, except instead of providing data protection, security, advanced virtualization features, and performance for an array of locally attached disk drives, a Cloud Storage Controller provides these capabilities on top of public cloud storage.  The net result is that public cloud storage can be utilized by the enterprise as if it were a local storage array - quickly, easily and for any application.

Who uses them Cloud Storage Controllers? Why do they need them?
Cloud Storage Controllers are used by mid-to-large enterprise - typically organizations with 10TB to several petabytes of data that are looking to reduce their overall cost of storage and simplify their storage environment.

These types of customers need Cloud Storage Controllers because leveraging public cloud storage services is simply not feasible without them.  The sheer number of applications running in a typical enterprise precludes them from being re-written to cloud APIs, and other concerns such as security and performance must be overcome.  Cloud Storage Controllers address all these concerns in a very robust way, allowing cloud storage to be used like local storage - but with superior economics and simplicity.

What benefits does a CSC offer?
A Cloud Storage Controller offers three main benefits:

1) It creates a seamless and highly robust connection to cloud storage, while requiring no changes to applications running in the data center.  Applications are able to access the cloud using standard block and file access protocols on what appears to be a standard logical volume.  The magic of the Cloud Storage Controller is in presenting a standard storage interface to servers and applications on the SAN, while connecting to the cloud over the WAN, and requiring nothing of the user to make this happen.

2) It accelerates the performance of applications using cloud storage through advanced WAN acceleration techniques including caching, deduplication, compression, and protocol optimization.  These techniques make cloud storage perform like local storage - even over relatively limited Internet connections (e.g. a DS3 at 45Mbps).  Furthermore, these same techniques help customers reduce their cloud storage service fees (and total cost of ownership) since they are not storing as much data in the cloud or moving as much data back and forth to it.

3) The Cloud Storage Controller provides the same features and capabilities expected of local storage arrays, such as thin provisioning, automated storage tiering, volume management, snapshots, and more.  These capabilities enhance the native functionality of the cloud, making it easier to use and providing superior data protection capabilities.

What applications/data sets make sense for the cloud?
Any Tier 2 or Tier 3 application or data set makes sense for the cloud through a Cloud Storage Controller.  The applications that don't yet make sense are highly mission critical or performance sensitive applications like large databases, ERP systems, and data warehousing.  Applications that make perfect sense are home directories, unstructured content storage, SAN offload, archiving, backup/tape replacement, and large-scale data collection (e.g. log storage)

What are your impressions of the cloud storage market today, and where it's going?  
It's an exciting time to be in the cloud storage market.  There's so much potential and things are just getting going.  Cloud storage has been very successful for web applications, and in conjunction with cloud computing.  However, it hasn't yet transcended into a tool for the mainstream enterprise.  At Cirtas we've got an opportunity to change that and we're seeing tremendous traction.  When we started two years ago, IT managers were aware of the cloud, but were fairly uneducated about it.  Today there are increasing numbers of cloud storage initiatives being driven from the CIO level, along with much more recognition of the technology among the media and analyst community as a potential game changer.  So these days it's much easier to engage with customers.  Keep an eye on the statistics published by cloud storage providers - you'll be amazed at the growth rates you see them achieve.

Our Enterprise Cloud Storage ROI Model identifies the key enterprise business drivers for cloud storage, and provides a model that helps organizations quantitatively evaluate if implementing a private storage cloud is the best option for them.

The ROI model and paper may be downloaded here >>

In addition to reducing the cost of storage, the Enterprise Cloud Storage ROI Model examines other areas of opportunity, including:

• in-house backup
• thin provisioning
• risk management
• productivity gains
• the ability to manage large file transmissions
• workstation storage upgrades and
  
• sharing information versus emailing information

The good news is that implementing a private storage cloud can provide cost savings while maintaining control behind the firewall. This ROI model helps you evaluate multiple use case options so that you can make the right decision for your organization.

Download the Enterprise Cloud Storage ROI Model >>

Just read David Linthicum's post, A way out of the private cloud dead end. 

We discussed the advent of hybrid cloud in our earlier post on a maturity model for cloud storage. While it is important that technology providers are beginning to grapple with the requirements to move seamlessly from a private cloud to a public cloud, the assumption here is that the workload owner is willing to utilize a public cloud multi-tenant solution for their workload.  I'm not sure we're there yet.

It is unclear to me that the marketplace and especially the higher end enterprises  (who retain and own significant IT resources and data centers) are yet willing to embrace public multi-tenant clouds.  I know they'll eventually do so as the security solutions and their early experiences improve confidence in the public cloud.  Certainly there are non proprietary workloads that will be used for the earliest testing.  However, this is still a very nascent market, and you should expect that we have several years of work ahead of us to build out a fully functioning hybrid model that provides appropriate security and control.

I strongly agree that the level of activity is reminiscent of the late nineties.  The majors are trying to build out their cloud stacks, and they are doing that with internal development and by buying smaller companies focused on individual layers of the stack, or even a feature on the layer.  I looked at some "gee whiz" numbers from various research organizations, and saw that IDC postulates that more than one third of all digital information created on an annual basis will reside in, or at least pass through, the cloud at some point in its life cycle. 

Amazing!

On July 19, 2010, Rackspace led the announcement of OpenStack, with a goal of creating an open source cloud software solution for use on industry-standard hardware.  The initial releases contemplate solutions for both cloud compute and object storage.  While these are the first two releases, they are separate offerings.  Remember, cloud storage is not just the storage target for cloud computing, it is one potential storage target for cloud computing, and is in and of itself a stand alone cloud offering of programmable storage.

Now, I have purposely used a term from the clothing industry, "off the rack", to spend a moment looking at a framework for evaluating the opportunities this may present.  With dress shirts, you can buy off the rack, semi custom, or custom, each with a unique value proposition based on fit, choice and cost.   Interestingly enough, this may be a good lens through which to consider the possibilities of OpenStack, and in particular, OpenStack Object Storage.

Rackspace has made no secret of its motivations for leading this initiative, and its desire to focus on "fanatical" service as it's key differentiator versus the fundamental technology on which the service is based.  Fair enough, and so the question becomes, is the rapidly emerging and immature cloud marketplace already "mature" enough to seek homeostasis?  (Homeostasis is the property of a system, either open or closed, that regulates its internal environment and tends to maintain a stable, constant condition.)  Have enough models and innovations, from startups, academia, open source movements and large tech companies, been tested in the marketplace to the extent that we can already race to the common denominator?  Perhaps now is a good time to start, as long as you are willing to acknowledge that the desired results are a good ways off.

Before we jump off into "Off the Rack" software, a quick look back at open source is helpful.  For more reading on the open source software industry a good introduction is The Cathedral and the Bazaar. Six things are particularly interesting: 

1. An open source alternative can emerge as a follow on to a successful commercial technology and can become pervasive versus the commercial offerings it succeeded (LINUX versus UNIX is the reference case here).
   
2. A second result of this approach can also end up with a big success, although in more of a niche than a pervasive replace for the earlier commercial offerings (MySQL versus Oracle, IBM and Microsoft in the relational data base space).  
   
3. An open source effort can also emerge earlier in a technology cycle and come of age as a pervasive solution (Apache Web Server comes to mind here).
   
4. Open source generally requires very careful cultivation of the community of developers, with active interest by academia (and partnering with NASA is part of the formula here).  Commercially sponsored open source efforts are becoming more common, although it as of yet has not been proven as the typical "breeding ground" for most great open source successes.  Eucalyptus, with its roots at University of California Santa Barbara, seems to be a more traditional route.
   
5. Open source is not necessarily reflective of rapid commercial opportunities for success.  Eucalyptus is obviously beginning to maneuver towards a repeat of the commercialization model.  OpenStack is taking the approach most favored by other open source successes like Apache.  A couple of good reads here are this article from BusinessWeek and this. See also Derrick Harris' post over at GigaOm.
   
6. There are also hundreds of thousands of open source projects that had mixed success or languished altogether. A quick look at  SourceForge (an open source project hosting site) shows nearly a quarter million hosted projects. How many of these have languished or had little impact on the market.
   

So, the first issue is that there will exist for some time to come a real question as to the adoption potential of OpenStack.   I believe that adoption is driven by applicability to need.  In a moment we will address a serious issue which OpenStack Object Storage must overcome to be successful, at best, and at worst, will confine it to a niche market.  My views are very much directed at the Object Storage offering, versus the compute offering, which I believe exists in a different space and as a different type of solution.  With this backdrop, let's have a look at the cloud storage marketplace today, and use the analogy of off the rack, semi custom and custom:

• Off the Rack:  implement as is, one size fits all, each with unique approaches for performance, scalability, bit integrity, may or may not provide geo services.
• Semi Custom:  Select from storage types (DAS, SAN, NAS, JBOD), shared or distributed file systems and object systems, mix and match storage for different SLA and cost/usage patterns on the same infrastructure, multiple APIs, meta data and catalog abstracted from storage layer, geo services.
• Custom:  Generally a service only offering and not available as deployable infrastructure, specifics will vary widely based on service provider offering strategy.
  

Infrastructure	Type	Comments
Eucalyptus	Off the Rack	Limited S3 APIs
OpenStack	Off the Rack	CloudFiles APIs
Scality	Off the Rack	S3 APIs
Mezeo	Semi Custom	Mezeo Cloud Storage Platform API and Interoperability API
NetApp	Off the Rack	Bycast APIs, NetApp storage
EMC Atmos	Off the Rack	Atmos ReST APIs, EMC storage
Service	Type	Comments
Amazon S3	Custom	S3 APIs
Microsoft Azure	Custom	Windows centric
Rackspace	Off the Rack	Is the basis for OpenStack
Nirvanix	Custom	SOAP APIs, multi node
Google	Custom	Offers S3 APIs
AT&T Synaptic	Off the Rack	Based on EMC Atmos
OpSource, SoftLayer, Layered Tech and others	Custom	Based on Mezeo

As you can see from the summary above, there exist as many views of what constitutes either a cloud storage service or a desirable cloud storage deployable infrastructure as there are service providers and vendors.  Note that a semi custom infrastructure results in a "custom" service as implemented.  "Off the rack" results in very similar services by those who utilize the same infrastructure unless they make their own major additions.  Any offering can be differentiated by service, and the degree and quality of service is critical to customer satisfaction and plays a strong role in value creation.

The OpenStack announcement as it regards Object Store and its approach to cloud storage seems to view cloud storage infrastructure as highly akin to an operating system (or at least a "hypervisor") and more similar to a selection of LINUX or Windows than that of an application or middleware layer.  While I agree that cloud compute is very close to this model, cloud storage is a service oriented architecture, with programmability for new applications that can tolerate Internet latency because of Web Services (like ReST APIs). The industry constantly overlooks this key point as it is consumed with the low cost, pay for use and thin provisioning capabilities of this storage tier.  Solutions for thin provisioning and low cost have been available far longer than cloud storage. Further, pay for use is more of a business decision than a technology. 

In the earliest days of cloud storage, there existed initial confusion that cloud storage was defined by cost, scalability, pay for use, and thin provisioning only and not programmable access (usually via ReST APIs).  ParaScale paid a huge price for not understanding that cloud storage requires Web services (like ReST API) access.  Now, with OpenStack Object Store, we see a follow on case of this same perspective, but with basic APIs for Put, Get and List.   Yes, it provides for Internet access via ReST APIs, but the focus continues to be primarily cost based versus new application enablement based.  It could be argued that the open source approach will provide for the appropriate additions of "advanced services" to be added.  However, even the use of the platform by NASA is more focused on cost of storage than on advanced functionality because NASA stores much more data than almost any institution or enterprise in the world.

I think Savio Rodrigues states this view very well in his post:

"Select products based on business needs, not license alone: It's also interesting to note that very few enterprises are in NASA's position with regards to size of IT investment and skills in-house. While NASA engineers were ready and willing to contribute new features into the Eucalyptus open source community, few companies have the skills or governance to consider allowing their developers to contribute to open source projects.  Summary trend number 7 from the 2010 Eclipse survey results highlighted this issue.

To suggest that NASA's buying or IT decision making patterns represents much more than the top 1 percent of IT buyers would be a stretch."

The overwhelming majority of enterprises would rather pay a vendor to deliver, maintain, support and enhance their private cloud software infrastructure than place that burden on internal IT staff. Whether the enterprise is paying for a closed source commercial product, a commercial product based on an open core product, or a subscription to an open source product, the product selection decision will be made based on business requirements much broader than 'is the product open source or not?' "

Keep in mind that cloud storage is a stand alone service associated with application delivery over the Internet and also associated with low cost, pay for use, scalable storage resources.  Social media applications and many Web based applications exploit these capabilities; for example publishing a file to a URL and significant tagging of files.

This view of cloud storage as nothing more than cost and volume-based ignores its extraordinary importance as a service-oriented architecture for new application enablement.  I believe both views are equally important and need to be equally served.  Will OpenStack, with its pervasive cost focus, be able to drive its community to this additional view of needed contributions of advanced services for cloud storage?  Lydia Leong of Gartner Group provides an interesting view of the open source community issues associated with this in her post:

"At the same time, open sourcing is not necessarily a way to software success. Rackspace has a whole host of new challenges that it will have to meet. First, it must ensure that the roadmap of the new project aligns sufficiently with its own needs, since it has decided that it will use the project's public codebase for its own service. Second, it now has to manage and just as importantly, lead, an open-source community, getting useful commits from outside contributors and managing the commit process. (Rackspace and NASA have formed a board for governance of the project, on which they have multiple seats but are in the minority.) Third, as with all such things, there are potential code-quality issues, the impact of which become significantly magnified when running operations at massive scale."

One last comment on this business of vendor lock in and cloud storage APIs (another focus of the OpenStack announcement).  I would submit that while a specific set of APIs has the potential to create vendor lock in, this is a much smaller problem than what is experienced in other technologies.  If you are really worried about it, you probably have never actually written a ReST API call.  It is written in many languages, and we have seen cases where applications that run on S3 run unchanged on Mezeo.  Others need very minor modifications, and still others are excited to take advantage of some of the unique Mezeo services.  It just is not a problem, and this is much more related to FUD (fear, uncertainty and doubt) and marketing zealotry than it is associated with technological reality.  The APIs of choice will shake out, and it is far too early to say if it will be S3, OpenStack, CDMI or a combination of all of these, and others, as yet unforeseen. 

At Mezeo, we have never believed there will be one winner, and instead focused on architecture to enable easy and effective delivery of whichever APIs stand the test of time. The Mezeo Cloud Storage Platform API enables advanced services and programmatic access to Mezeo enabled storage clouds.   The Mezeo Interoperability API enables seamless interoperability of applications developed for Amazon S3, Google and Eucalyptus based storage clouds.

The interesting view that seems to be missing here is that marketplace competition by service providers already serves to drive down the price of cloud storage, so a commoditized stack embraced by most is unlikely to yield extraordinary incremental savings.  At the same time, while the competitive market conspires to drive cloud storage costs ever lower, the need to differentiate, and deliver solutions as well as a programmable storage to enable multiple new and exciting types of applications will rapidly replace the pure cost and scale focus of current cloud storage offerings.  Sometimes, the "new" application is simply enabling it in the cloud, to produce the same result at a lower cost!  This requires significant cloud storage functionality in order to make this easy and productive.  Amazon continues to prove this with their many additions and capabilities which differentiate their service.  Mezeo sees much the same view on the part of our customers.  The focus is on what cloud storage can do, what problems will it solve, what business opportunities does it create, what new applications can it enable and all of these views assume it will be competitively priced.

Cloud storage represents significant opportunities for institutions, the enterprise (see my recent post on the business case for enterprise cloud storage) and for the IT service provider.  Cloud storage is substantially different from cloud compute, and requires that you understand this difference in order to effectively evaluate the impact of this announcement, as well as your next steps.

There is no doubt that every enterprise has devoted some time and energy to evaluating how cloud technologies can best be put to work in their ongoing pursuit of cost reduction and to a lesser extent for potential improved service levels particularly around rapid provisioning of compute and storage resources.  Mezeo has recently begun to work with various enterprises, and I want to share some of the opportunities that appear to align strongly with these two goals.

In terms of cost, most enterprises are experiencing continued and significant growth in unstructured data.  As they look at the cost of this growth, it is more than just physical storage, data center occupancy, bandwidth utilization and power and the accompanying management demands; it is also the backup and disaster recovery requirements and the ability to quickly satisfy users who need more storage in order to execute whatever tasks and jobs they have.  Against this backdrop, the drumbeat of Amazon S3 and other public storage clouds advertises storage at costs that are generally below the internal "advertised" cost of the typical Fortune 500 company.  What gives?

First, cents/GB/month is only the tip of the iceberg, and bandwidth along with access charges gives a more realistic cost appraisal.  Next, real and legitimate concerns about data security exist (will someone gain unauthorized access, by accident or via an attack, to company data stored in a multi-tenant public storage cloud?).  Also, data integrity concerns are well founded (will the bits I store be returned, and will they be backed up and appropriate DR measures taken?).  Finally, can I absolutely trust the service provider to execute to the extent deemed necessary, and if they do, can they really save me any real money versus the assumed risk profile?  Private cloud computing is an appropriate strategy for addressing these issues.  

Not all unstructured data is a candidate for the latency of cloud storage as delivered from an IT service provider via the Internet.  So, while some tiers of data may be appropriate for a cloud storage service, it is a subset of the enterprise unstructured data requirement and not a lower cost panacea.  Hopefully, CIOs can easily make this case with their peers in senior management, although it may sometimes seem like they are making an excuse for keeping control and not exploiting new technologies.

Question one surrounds the cost proposition, and our analysis suggests that, even at sub petabyte initial cloud sizes, the enterprise can deliver economics for in-house cloud storage that compare very favorably.  In fact, it may even be lower than what is available from a service provider.  The Mezeo team comes from both a hosting and a cloud storage background, and this just reinforces our view that the cost proposition for private cloud storage has favorable economics.  However, if you are being forced to allocate capital for data center build outs, or you are otherwise CAPEX constrained, the hosted public cloud economics can be quite appealing.  Since businesses require positive margins, this further drives up the cost of cloud storage as hosted at a public service provider.

The case for improved user satisfaction is similar, regardless of public versus private, because the cloud gives users the capabilities they want.  First, with rapid provisioning of pay-as-you-go low cost cloud storage, the end user gets what they need when they need it via a frictionless interface.   Second, several benefits drive end user demand for cloud storage; including: avoidance of workstation storage upgrades, one solution for file sharing and collaboration, new capabilities and applications that exploit file search, tagging and publishing to a public URL, and the ability to access your storage anytime, anywhere and on any device.  Third, the solution is also ideal for implementing a workstation backup solution with sync.  It is not hard to see why end users would find all of these capabilities appealing.

Cloud storage clients, gateways and edge devices are also beginning to appear, and can solve many different issues.  For example, a client gives the end user access to multiple cloud storage accounts at multiple providers.  Why not replace that tape backup operation at a remote location with an iSCSI interface directly to a storage cloud, for a scheduled backup without local user intervention (get rid of the tape backup of your local file server, forever)?  Speaking of file servers, multiple solutions for replacing or even displacing file servers are coming to the market.  The savings from removing an entire layer of infrastructure are quite compelling.

New applications, including use of social media, may require file publishing.  Cloud storage allows you to store training videos, and make them easily available at every end user in the company.  Tagging and search offers new application capabilities, and new opportunities to support existing compliance requirements.  Secure file sharing, versus file publishing, may be a significant requirement as you work with customers and business partners.  Partner, customer and employee portals can reach new levels of capability with API accessible cloud storage, as the availability and the management of information is delivered via the cloud.

Our observation is that the early adopters have begun the move to cloud storage.  Why?  Simply, enterprise private cloud storage allows you to gain many of the benefits and set aside the security and data integrity concerns of public cloud storage.  At the same time, data tiering and private and public could solutions will drive "hybrid" cloud approaches that will allow the enterprise to exploit the best of both worlds.  In an upcoming post, we will offer up some tools to examine the cost and the benefits of cloud storage for the enterprise. 

It is a little difficult to discuss an article like What's a Hybrid Cloud and Where Can I get One? without at least agreeing upon some sort of definition.  We've already heard many of these definitions, but I'm not sure they're good enough.  Note: we did try to define the term hybrid earlier, as part of our Cloud Storage Maturity Model.

Well, what is it? 

First, let's look at the textbook definition of the word hybrid:

A hybrid is the combination of two or more different things, aimed at achieving a particular objective or goal.

A "hybrid car" has both an electric motor and an internal combustion engine, and the combination of the two serves to propel your automobile while providing a more efficient use of fuel.  So, a hybrid cloud is a combination of a public and a private cloud, aimed at providing a common cloud computing experience.

But for what purpose?  Hybrid computing clouds provide cloud computing that delivers the appropriate offerings with provisioning, pay-as-you-go for relatively limitless capacity, and improved security, and some would say at a lower cost than an internal cloud. Hybrid clouds can and do offer the opportunity to provide baseline processing within your own facilities, and use service providers for peak requirements.  By doing this, they can lower the cost versus private cloud computing. 

I've seen some hybrid cloud definitions that include edge or gateway devices, but I do not think that is definitive for hybrid cloud.  Now, with this definition, we can sort out what a hybrid cloud actually delivers.  In general, the argument that a multi-tenant public cloud is lower cost (on an absolute cost basis) than a private cloud is hogwash, in my experience.  I have seen examples of all of these, and in the case of a large enterprise, they may very well run private clouds for their own use that cost less than what they can buy the resources for on an open market basis.  (Now, before the switchboards light up with capex versus opex and idle resource arguments, I want to assure you that even taking these issues into account, the theory holds water).  This still begs the question as to what purpose does hybrid cloud serve?

In its most general case, the business value of hybrid cloud lies in its ability to bridge the gap between baseline computing and peak computing, assuming all things are equal or if not equal, at least acceptable (in terms of security and other incremental costs associated with hybrid cloud).  Otherwise, why go to the trouble?

There are other examples that are associated with backup and disaster recovery versus cost that also can be of high value with a hybrid approach, particularly if you only have one data center.  I store my backup locally, in case I need to do a speedy recovery.  I store an encrypted copy remotely, at a service provider, for DR purposes.  Voila!  Low cost, secure, multiple requirements solved.  Hybrid, it's a beautiful thing.

The hybrid cloud can also allow you to "bridge the gap" if you are in a data center bind, i.e. out of space or between build-outs.  This is a special case of bridging the gap.

Where can you get this, now? 

This is exactly our game plan (at Mezeo), and working with backup and archive providers, as well as Mezeo-based cloud storage service providers, and Mezeo private storage clouds for the enterprise, we deliver this solution today - in a matter of days and weeks, not months!