Commentary

George Crump
 

In The Cloud, Architectures Matter

There is a common statement that I hear when talking with members of the cloud community, that the user should not be concerned with what is the architecture of the cloud. I disagree -- details matter.

There is a common statement that I hear when talking with members of the cloud community, that the user should not be concerned with what is the architecture of the cloud. I disagree -- details matter.Actually, this idea that the user shouldn't care about how things are done is seen throughout the industry. Deduplication vendors would have you believe that it doesn't matter where deduplication happens, storage vendors would have you believe that how their thin provision works doesn't matter, but where you hear this propaganda the most is in the cloud and, in particular, regarding cloud storage.

Just like I want to know what brand of tires are on my car, I want to know what architecture the cloud storage provider is built on. Why does this matter? Don't you sign up for an SLA? As I often have to remind people, the SLA is only as good as the paper it is written on. Sure, if the service goes down and suffers an outage and they violate their SLA, you might be able to sue or get free service as a form of compensation, but the fact remains you still went down and couldn't get to potentially important information when you needed to.


More Storage Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Most users would have rather not had the service go down in the first place as opposed to getting free service or winning a legal battle. How do you make sure that happens? Understand and investigate the architecture. Make sure that someone else, some other provider, is using that type of architecture, that it works and has proven itself to be reliable over the test of time (which, admittedly, given the maturity of cloud storage, may be brief).

This doesn't preclude you from looking at cloud startups like ParaScale or Cleversafe. Their architectures are available to a wide variety of providers. It also means that you should look for architectures built on more traditional storage architectures, comparing the two types and weighing cost vs. reliability. Obviously, the provider has a role to play in this availability as well, and its capabilities and track record has to be understood.

I would scrutinize very closely those providers that do not share the details of their architecture. What if this cloud that you are writing to is a bunch of very loosely coupled NAS boxes? How will they scale and manage that? How will they insure reliability? Conversely, what if the cloud is based on very high-end storage? Sure, the reliability is there, but can the provider be competitive from a price point as the data ages? In cloud storage you are looking for that delicate balance between cost effectiveness and reliability.

I'm not sure who originally said that the devil is in the details, but even an old saying like that applies to a new technology like cloud computing.

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.


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