Cloud services enterprise architecture part 2

We’ve developed the EA further from my last post – adding an output service of software development consulting, and adding the following input services:

Messaging services:
-IM
-SMS
-Tweets (down with the kids!)

Work management services:
- Task management
- Workflow
- Timesheets

Mind mapping services:
- Mind mapping

Business continuity services:
- Backup

Legal services
- Legal advice

Software development services:
- Application platform
- Database platform
- IDE (Integrated Development Environment)
- Test management
- Architecture
- Requirements

Here’s the latest picture: now to find the right providers for each of these services!

Interesting posts on the "Principles of Cloud Oriented Architecture", and "Cloud Computing Bill of Rights"

I’ve been reading James Urquhart’s blog The Wisdom of Clouds for some time now – a leading thinker in the emergent space of Cloud-based architecture.

In particular, the following recent posts are especially worth reading:

Update: the Cloud Computing Bill of Rights

The Principles of Cloud Oriented Architecture

Generally I agree with James that, since the world is now coasting towards a single common, shared Cloud Oriented Architecture that a set of common principles, rights and responsibilities can and should be drafted (but I would ask by whom?). As with any technological advance, the social and legal effects cannot be thought through soon enough before the impact of the change is felt. The question of jurisdiction will always be hardest – which authorities govern and legislate for data and other services in the (international and potentially off-planet) Cloud? Technology moves ever more quickly than the human population can keep up.

In some ways this “Bill of Rights” reminds me of a political manifesto – there will be diametrically opposing views on privacy and security for example from the governments of many countries, and so the practical question is *how* such a BoR would ever come to realised.

However, another way to look at the BoR is as a requirements spec trying to solve 3 discrete technical problems:

Namely:

• Providing clear ownership of data and avoiding Cloud services providers ever “owning” their customers’ data.
• Providing clear accountability (=measurable!) for Cloud service levels
• Providing clear ownership of (patented?) intellectual property underlying a Cloud service

James has brought us all a long way by articulating these vulnerabilities in today’s Cloud services model – however I personally think that it’s more likely that these issues will be addressed successfully (and cheaper!) using technology rather than by the law.

An alternative Microsoft-based Cloud Services Architecture

Just had a read of my friend Matt Smith’s blog post from a couple of weeks ago, which covers very similar ground to my last post on the cloud services I’ve started using. Matt is a Microsoft fanboy – he even once proposed SharePoint as a viable alternative to a girlfriend in a presentation – these things come back to haunt you, you know! – and so is pretty keen on MS’ Mesh services (must take a closer look at these) – I’m mostly using Google at the moment. Compare and contrast at http://blog.mattsmith.co.nz/Lists/Posts/Post.aspx?ID=40.