Light Reading Mobile – Telecom News, Analysis, Events, and Research

5:40 PM -- Interesting observation from Jesse Robbins, CEO of Opscode Inc. and a former IT lead at Amazon Web Services LLC:

"One of the reasons Amazon is successful with EC2 is because Amazon is very comfortable with low margins," Robbins says. "If there's one thing Jeff [Bezos] likes, it's a business with low margins that other people would be crazy to get into."

That could be another worry for carriers as they try to keep up with the cloud services craze.

We've already heard Randy Bias, CEO of Cloudscaling, say everybody would be best off building clouds out of ordinary, cheap gear, the way Amazon does. (If you haven't heard him say that, click on the video below.) Now there's the suggestion that clouds themselves might get chased into commodity territory, too.

A lot of doubt surrounds Bias' theory, and of course it's easy to take the most famous cloud name and unfairly compare it to everything. But I think Amazon exemplifies the kind of challenge carriers are facing with the cloud. It's a space where they're not making the rules. Worst case, the new cloud providers like Amazon become what the telcos ought to have become.

Opscode, of course, thinks it can help. The company's open-source framework, Chef, helps automate the process of configuring cloud services; think of it like programming a robot to change the oil on any car, regardless of make or model. Opscode makes its money on the Hosted Chef, which went live Tuesday after a year of Google-like beta; the service matches these recipes (their word, so don't roll your eyes at me) with the exact hardware in your cloud, which Opscode is continually polling.

What all that means is lowered opex, in the form of employing fewer people. But it also means faster turn-up of services, something that telcos are going to have to be on the ball about.

Useful? Possibly. Opscode has only one carrier customer, but it's KT Corp., which is no slouch.

{videoembed|207676}

— Craig Matsumoto, West Coast Editor, Light Reading

5:40 PM Carriers getting into cloud services are going to have to be wary of Amazon's true superpower
June 14, 2011 | Craig Matsumoto |


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.
 
Related Videos
White Papers SPONSORED CONTENT
Featured