Part of the cloud computing movement has been the rise of a cloud computing derivation called private clouds. You can think of private clouds as a collection of systems that provide sharable storage, database, and processing services, such as cloud computing providers Amazon and Force.com, but reside within firewalls and within datacenters.
Private clouds are getting attention today due to the popularity of cloud computing, and the need for some organizations to keep their computing resources within their datacenters but move to a more sharable computing infrastructure that should increase efficiency and cost effectiveness. However, as I look at the emerging patterns of use, I see a lot of crossover from SOA, and that's not a bad thing.
[ See related news: "Battle brewing over next-generation private clouds." ]
Private clouds, albeit different from enterprise to enterprise, have a few common patterns. Private clouds offer shareable resources, or the ability to reuse storage, database, transactional, and business process management services. Moreover, they typically have governance frameworks surrounding them, as well as many other features that make them look like the core components -- or at last the first instances -- of an SOA.
What's interesting here is that they can repackage an existing concept that many are pushing back on these days, as something new and exciting, but they are basically the same SOA concepts. Heck, we did that with SOA, which was based on existing architectural patterns, so why not private clouds and cloud computing? Perhaps it's all in the marketing.