Designing a Cloud Interface: Four Guidelines

| | Comments (0) | TrackBacks (0)

My critique of both a recent CACM article and one of the author's blog entries, regarding Cloud vs. Grid interfaces, was quite long, and I've been told, meandering.

Here is a pithy summary of my position:

1. The greatest leverage in system architecting is at the interfaces. The greatest dangers are also at the interfaces. [1]

2. When the components of a system are highly independent, operationally and managerially, the architecture of the system __is__ the interfaces. [1]

3. For networked applications, there are many different styles of interface, including APIs, to message exchange contracts, to hypermedia. These drive very different emergent properties in the resulting system.

4. Loosely coupled systems are assisted by the projection of both object state AND available state transitions. Hypermedia is a suitably general model to enable this.

[1] This is just a paraphrase of Maier & Rechtin regarding key heuristics for systems architecture. For a summary, see this paper.

0 TrackBacks

Listed below are links to blogs that reference this entry: Designing a Cloud Interface: Four Guidelines.

TrackBack URL for this entry: http://www.stucharlton.com/blog/mt-tb.cgi/110

Leave a comment

About this Entry

This page contains a single entry by Stu published on September 19, 2008 7:59 AM.

VMWorld and Interop was the previous entry in this blog.

The roots of our current economic failures is the next entry in this blog.

Find recent content on the main index or look in the archives to find all content.

About Me
(C) 2003-2008 Stuart Charlton

Blogroll on Bloglines

Disclaimer: All opinions expressed in this blog are my own, and are not necessarily shared by my employer or any other organization I am affiliated with.