
Amidst all the SOA-related activity that is currently underway, there still remains a significant amount of confusion as to what exactly constitutes a service-oriented architecture. Some qualify an SOA project by the fact that Web services technologies are being used, while others classify SOA as a Web-centric variation of object-oriented design.
What has become more clear than the actual meaning of SOA is the strategic vision that has emerged around it. This vision is comprised of a set of goals and benefits that most stakeholders fully expect to see realized when they support and commit to SOA initiatives. However, because the "SOA" acronym has been used to brand products, technologies, and even projects without a clear understanding of its meaning, many of these expectations have been and will continue to remain unfulfilled. For example, the common (and dangerous) assumption that a solution is service-oriented solely because it uses Web services has led to much disappointment. There is, in fact, a wealth of information out there that communicates the meaning of SOA in detail. The only problem is that this information is fragmented - distributed across marketing literature, technology specifications, media reports, and independent research efforts.
Great start! Anyone else care to give it a go?
In all seriousness, after doing some cursory navigation around these two sites, I can say without a doubt, that there is a wealth of information here fit for any development geek to sink his/her teeth into. As things progress, I'm sure I will be coming back to it for reference material as the technical verbiage in class intensifies and I begin to lose what little remaining confidence I have that I have the slightest clue what is going on.
5 comments:
You've got to be kidding!!!!!
Why don't my comment show on your site? Aren't they good enough?
Finally got there - I'll send via post office in the future - quicker!
mu
I think the DL has the EMIS guru!
Post a Comment