If you treat Cloud resources like physical resources, then you've given up much of the flexibility the Cloud promises.

Have we really solved the coupling problem by moving to REST?

The marketplace is responsible for defining Cloud Service Models.

A backup is only as good as your ability to restore your data from the backup.

Combining  SSL and encrypted volumes can secure your Cloud data in motion and at rest, but it plug all the holes.

Not all software development project tasks must be done in a sequence. With Agile requirements prioritization you can complete the deliverables and tasks in order of importance.

With hypermedia-based discovery, any client can determine what any resource can do for it simply by following hyperlinks. The API is the bookmark, which never changes.

Never expect requirements to be fixed -- even for agnostic Services. Digital ink never dries. The same should go for your code.

Achieving reusable code that actually meets the requirements for reuse is far more difficult than it sounds.

We haven't yet seen any type of cyber attack that changes the game. Some kind of coordinated effort that causes unexpected, appalling damage. In other words, we haven't had our Cyber-9/11 yet.