Merely putting SOA into your proposal or as a stated capability is no longer going to be a “deal clincher” or a key “business differentiator”. The counterview I hear practitioners in SOA will say is that SOA is not just the standardized service practices but is also how the services can be identified that are differentiating. But that’s the rub. If SOA treats every requirement or design as a service problem, where is the difference?
The ability to transform business is the most exciting feature of the Cloud phenomenon, but users currently see it “through a glass darkly,” and perhaps with a measure of faith and hope. More needs to be done to develop understanding of the business impact of Cloud Computing, and we should focus on this, as well as on the technical possibilities.
A new technical report and a Quick Reference Guide exploring the synergies and identifying integration points between Frameworx and TOGAF® has been published by The Open Group and TM Forum.
When Cloud reaches its fully adopted level, it will influence application architectures by driving them to be more componentized and service-oriented to support agility, commoditization and choice.
At The Open Group’s TOGAF® Camps, I enjoy watching people really delve into topics such as these, and get excited about sharing their own experiences and learn from others’. It’s rewarding to know that people take away new or refined ideas from these sessions that they will apply to their own enterprises.