SOA or SOS? Rationale for a Semantic Service-Oriented Infrastructure

by Arun K. Majumdar

Service-oriented architecture (SOA) is the new sword for business process management (BPM), promising to cut through the old problems of enterprise application integration (EAI) and clear the path for interoperability among heterogeneous systems. Unfortunately, there is a growing and chaotic panoply of choices, recommendations, suggestions, standards, vendor positions, and approaches that mystify and muddy the core issues. SOA solutions, which are supposed to be the ultimate weapon for solving the problems, have exacerbated the situation with buzzwords. If we mix and match vendor solutions, techniques, and architectures without a principled understanding of all the issues, we may end up with a poorly constructed house of cards that can be blown away by the next gust of wind.

Password Protected Cutter Consortium clients, please log in:


This document is available to Cutter Consortium Resource Center clients only. Retrieve your password.
If you would like further information about how to become a client, please contact us at +1 781 648 8700 or sales@cutter.com, or you can Request Guest Access.
SOA or SOS? Rationale for a Semantic Service-Oriented InfrastructureSun Jan 01 16:57:03 CST 2006

Become a Member

Research and inquiry privileges, plus regular strategy meetings with Cutter's Business & Enterprise Architecture experts are just some of the perks! Talk to Cutter today about trial membership, including access to research, webinars, podcasts, white papers and more.

Request trial membership