Commentary

Charles Babcock
InformationWeek  

Avoid Trap Of Proprietary Cloud Tooling: Use Simple API

What's the first thing you should do if you're thinking of developing software for cloud computing? At ZendCon, Zend Technologies user group yesterday, three members of a five member panel answered the same way: adopt Simple Cloud API, the open source cloud services interface.

What's the first thing you should do if you're thinking of developing software for cloud computing? At ZendCon, Zend Technologies user group yesterday, three members of a five member panel answered the same way: adopt Simple Cloud API, the open source cloud services interface.Simple API for Cloud Application Services was announced Sept. 22 as an open source project for cross cloud operations. If you adopt Simple API, your application will be able to call the same service from different clouds. If you need storage in the cloud, build the Simple API for storage services into your application and you will be able to use storage in either Amazon EC2 or Nirvanix Storage Delivery Network. Amazon doesn't provide support for Simple API the way Nirvanix does, but the Eucalyptus open source code project has generated an open source version of its S3 storage API that can stand in.

The panel Tuesday was called Developing On the Cloud, and Wil Sinclair, Zend's cloud strategist, said the tooling you use to build cloud software -- the applications you need to interoperate with cloud services -- will have a big impact on what you can do. If you start out by using a proprietary cloud's tools and develop software to work with it, your investment will tend to work only with that cloud and will have limited value. If you adopt the Simple API for Cloud Application Services, it will work with all clouds that support it, he told a crowd of about 150 PHP developers yesterday at the San Jose Conference Center. Sinclair leads the Zend effort to win adherents to Simple API so his views are predictable. The same can be said, I guess, for two other panel members, IBM's Doug Tidwell and Microsoft's Vijay Rajagopalan, whose firms both endorse Simple API. Zend, as the maker of PHP scripting language and tools, is the host of the Simple API project. PHP is frequently used in Web applications. It's likely to be frequently used in cloud applications.


More Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

IBM and Microsoft might prefer to set standards that others follow, but in this case they are in favor of following standards. They're behind the leaders in cloud computing. Standards open the door to playing catch-up. Amazon.com, VMware and more specialized outfits, such as Engine Yard and Rackspace, have a jump on other vendors.

Microsoft is about to launch its Azure cloud at its Professional Developer's Conference in Los Angeles Nov. 16.

Andi Gutmans, CEO of Zend, said during a keynote at the conference that Microsoft is interested in getting as many developers as possible to use Azure. Microsoft isn't just interested in Visual Studio and .Net developers. It wants Eclipse-based tools and the developers who use them to work in Azure as well. One way it can do so is to provide an API to Eclipse that let's PHP programmers inside Eclipse reach services in Azure and it is likely to do so.

Microsoft's interest in and cooperation with open source PHP is well known. For other languages, there's still a question mark. We'll know that Simple API is opening things up for sure if we see Microsoft provide Eclipse with an API for Java tool users that enables them to work with Azure as well.


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