Commentary

John Foley
Editor, InformationWeek  

InformationWeek Releases Storage-As-A-Service RFI

The storage-as-a-service market continues to grow and change, with new players introducing products and services that give businesses an alternative to do-it-yourself, on-premises data storage. In preparation for a full-blown analysis of the market, InformationWeek is releasing a Request for Information aimed at storage-as-a-service vendors.

The storage-as-a-service market continues to grow and change, with new players introducing products and services that give businesses an alternative to do-it-yourself, on-premises data storage. In preparation for a full-blown analysis of the market, InformationWeek is releasing a Request for Information aimed at storage-as-a-service vendors.This is a formal call for participation to storage-as-a-service vendors. The RFI describes a hypothetical mid-sized company called DIY Marketing Services, which is growing despite the recession as client companies turn to DIY for outsourced marketing services. The company requires 100 TB of storage to start, with expectations that data volume could triple or quadruple within a year.

The RFI provides an overview of DIY's business, describes its existing IT infrastructure and technology goals, and requests detailed information on vendors' service offerings, pricing, and service level agreements. We ask that vendors RSVP to let us know that they plan to participate by March 30, and the deadline for returning completed RFIs is April 6. InformationWeek plans to publish our analysis of the completed RFIs and the overall storage-as-a-service market in May.


More Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

We brought in IT consultant Jon Toigo of Toigo Partners to help draft the RFI and analyze the results. Storage-as-a-service vendors interested in participating can submit a completed RFI directly to Jon at jtoigo@toigopartners.com.

The RFI, titled "Storage As A Service," can be downloaded here. Registration is required.


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.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links