Channels ▼
RSS

Database

Programming For The Public Cloud?


Clouds today come in two basic flavors: the private cloud (wholly behind the firewall) and the public cloud, which runs on remote hosts. The private cloud currently enjoys IT management’s attention, because taking lots of individual servers, putting them into a pool, and parceling out their capabilities as needed has tremendous advantages for the data center. Of these, none is more prominent that the ability to scale up resources when projects demand and back down again when the need declines.

Private clouds require little changes in programming. Instances of virtual machines are spun up from an administrative console and the application is migrated to this home in the clouds from which, by and large, it works as expected.

The public cloud — whose leading hosts include Amazon, Google, Microsoft — is a different thing altogether. Code cannot be migrated simply to these hosts and expected to work correctly. It won’t. Google’s App Engine, for example, allows only a select list of core Java classes to run on its platform. If your code relies on a proscribed class, your app will not run.

Moreover, each platform uses its own unique datastore, which does not run at all like traditional relational DBMSs. (Microsoft Azure does offer a "cloudified" version of its SQL Server database product as an option.) So, if you plan to run applications in the public cloud, you’ll either have to invest considerable effort porting existing code or writing new apps from scratch. Doing so will reveal a second problem: No two platforms use the same API. So, from the get go, you are coding to a proprietary platform &mdash with all the constraints that implies.

This problem is widely acknowledged, but efforts to provide a universal API, such as the Simple Cloud API, have garnered little enthusiasm from the cloud hosts. This situation puts IT organizations in a bind. If considering using the public cloud, therefore, run extensive pilots before committing to a platform. Know your platform’s limitations and costs intimately before making it the basis of an important app. You’re likely to be residing there a long time.

— Andrew Binstock is the Executive Editor of Dr. Dobb's. He can be reached at alb@drdobbs.com.


Related Reading


More 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

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's 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 or spam. Dr. Dobb's 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.
 

Video