The
Feb. 2007 issue of acm queue has an interesting article titled Is
Your SOA (Service Oriented Architecture) DOA (Dead on Arrival)? It begins with a hypothetical story of
Marty the Software Manager who gets fired on a failed and over-promised SOA project.
Like any software project, a SOA project could go wrong due to a multitude of reasons: inadequate analysis of the problem space, wrong level of abstraction, over-reliance on vendor promises, lack of buy-in from stake holders and so on. It is important to keep in mind that SOA is just an architectural style and not a panacea and substitute for good old engineering principles. In fact distributed and shared nature of SOA systems heightens some of the traditional problem areas such as availability, versioning, recovery-on-failure etc.
A strong governance program, aided by software tools like
HP Systinet, can go a long to address some of these issues.
Information disclosed in this community becomes public.
Exercise caution when deciding to disclose your personal information.
HP reserves the right, but is not obligated to, edit or remove your comment if it contains personally identifiable information or other content HP deems unacceptable.
Opinions expressed are your personal opinions or those of the original authors, and not of HP.
Please see HP's web Terms of Use for more details.
