Most consider cloud computing to be this magical technology that will solve all of world's IT problems. The reality is that you're still doing computing. You're still storing stuff, still processing stuff, still placing information in databases. This means -- Dare I say it? -- you need to put some architectural forethought around cloud computing.
The lack of an architecture -- typically, the lack of a SOA -- is a recipe for failure in the world of cloud computing. An architecture provides the structure necessary to mesh your existing enterprise IT assets with the emerging world of cloud computing. Most who leverage clouds, PaaS, IaaS, or SaaS, understand the dilemma and quickly turn to basic architecture and planning...only to find that those 'in the know' are nowhere to be found.
Good SOA architects are a rare species. Many who claim to have mad SOA skills come up short. The trend is to leverage whatever the next magical and hyped technology is in the hopes that no one will notice that the existing architecture is a huge mess, and the addition of cloud computing resources will just make it messier.
Making matters worse are the numbers of SOA technology vendors who have falsely position their technology as "cloud computing technology," when they should be focused on SOA leading to successful cloud computing. There is a huge difference. This vendor hype has just added to confusion around both the concepts of cloud computing and SOA, and the end users are once again looking to toss technology at problems that really need better architectural thinking.
Clearly, we don't have enough SOA A list players to go around as cloud computing explodes.