George Crump


Upcoming Events

Cloud Connect
Santa Clara
Feb 13-16, 2012

Cloud Connect brings together the entire cloud eco-system to better understand the transformation we're experiencing and promises to be the defining event of the cloud computing industry. Learn about the latest cloud technologies and platforms from thought leaders in Cloud Connect’s comprehensive conference.

Register Now!

More Events »

Subscribe to Newsletter

  • Keep up with all of the latest news and analysis on the fast-moving IT industry with Network Computing newsletters.
Sign Up

Will Cloud ISVs Determine Cloud Storage Winners?

Cloud storage providers are all actively pursuing Independent Software Developers (ISVs) to support their cloud at the back-end. The idea is to make cloud storage a simple option to your storage application of choice, making the use of cloud storage skyrocket. The provider with the most ISVs in their pockets wins. Will that strategy work?

In the past I've said for cloud storage to be successful, it needs to be seamless. Users can't even know that they are using the cloud. It just happens. This is the concept behind ISVs doing the integration work. For example, if you are using a backup application and you want to be able to move a copy of that data to the cloud for disaster recovery purposes, selecting a cloud-target is as simple as clicking the check box.

The strategy seems sound, as long as the cloud storage provider can get the ISV to support only their cloud or at least make their cloud the preferred target of the ISV's application. To date, many of the larger cloud-storage-enablement announcements say thst there is support for three or four cloud providers. This means that the cloud-storage providers still have to communicate directly to the storage manager so that when that list of choices presents itself, they know why they should pick one provider over another. The key to making this strategy work is for cloud storage providers to capture the smaller ISVs. There are thousands of them, to integrate their application into the provider's storage. It would be logical for a smaller ISV to want to allocate the development resources one time and pick one cloud provider.

What is going to sway these smaller ISVs? I don't think it's all about additional profits. Most cloud providers are pretty close in the amount of revenue-sharing that they can provide. The decision points are really going to be around the strength of the cloud storage API. What capabilities can it bring to their application for example, and of course, how easy is it to integrate into their application? Another area is going to be company stability. The reality is that we have been sharing storage across public networks for some time, yet perception is that cloud storage is something new and that most of the companies involved are either new entities or they are new at providing this kind of service. Cloud providers are going to need to provide sustainability. Finally, the last thing an ISV wants to hear about is how the cloud service is down for one reason or another. Many of them fear, and justifiably so, that if they provide a cloud extension to their application and it becomes unavailable that they, the ISV, are going to get the first call. Also most small ISVs (and large ones) build their following on great customer service.

The takeaway is that cloud providers do need to go after the ISV market, but get BOTH the ISV and the eventual user of that ISV's application to understand the benefits of their particular cloud offering. ISV integration is a good strategy, but you still have to have a superior offering.

Related Reading


More cloud-storage Insights



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

Network Computing encourages readers to engage in spirited, healthy debate, including taking us to task. However, Network Computing 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. Network Computing 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.
 

Research and Reports

Hypervisor Derby
August 2011

Network Computing: August 2011

TechWeb Careers