Common Misconceptions about Service-Oriented Architecture

Abstract

You don't have to look far to become aware of the effect that service-oriented architecture (SOA) is having on software systems. Vendors are aggressively marketing hardware, software, tools, and services that support SOA implementation within organizations as diverse as the Department of Defense, banks, federal agencies, manufacturing companies, and health care providers. Even more significantly, customers are embracing SOA as a way to successfully achieve business agility and interoperability among systems. However, our experience from working with current and potential adopters of SOA is that they often have a variety of misconceptions that lead them to oversimplify the effort required to implement SOA. Chief among these misconceptions is the belief that simply by adopting an SOA strategy for the enterprise, an organization has established a well-crafted architecture that will help the organization achieve its many IT goals. In reality, SOA is not an architecture, but an architectural pattern from which an infinite number of architectures can be derived - both good and bad. In this experience report, we discuss at a high level this and several other misconceptions about SOA derived from our experiences

DOI: 10.1109/ICCBSS.2007.9

Extracted Key Phrases

05010020072008200920102011201220132014201520162017
Citations per Year

399 Citations

Semantic Scholar estimates that this publication has 399 citations based on the available data.

See our FAQ for additional information.

Cite this paper

@article{Lewis2007CommonMA, title={Common Misconceptions about Service-Oriented Architecture}, author={Grace A. Lewis and Edwin J. Morris and Soumya Simanta and Lutz Wrage}, journal={2007 Sixth International IEEE Conference on Commercial-off-the-Shelf (COTS)-Based Software Systems (ICCBSS'07)}, year={2007}, pages={123-130} }