Publication | Closed Access
What's in a Name? Distinguishing between SaaS and SOA
118
Citations
7
References
2008
Year
Software MaintenanceA A ServiceEngineeringSoftware EngineeringSoftware Architectural ModelsSoftware ArchitectureSoa GovernanceManagementSoftware Architecture ModelingWeb Service ModelingService-oriented Software EngineeringService-oriented ArchitectureInformation ManagementSoftware DesignService-oriented ComputingAlphabet SoupService-level AgreementSystem SoftwareMarketing Strategy
SaaS and SOA are often confused, but SaaS is a delivery model while SOA is a construction model, and Zachman's framework can clarify this distinction. The article proposes using Zachman's architectural model to illuminate the differences between SaaS and SOA, after briefly reviewing their concepts and architectural history. The authors apply the Zachman model to differentiate the two architectural approaches to building software. The intuitive use of the Zachman model effectively explains SaaS versus SOA differences even to non‑IT professionals.
Considerable confusion arises in distinguishing between software as a service (SaaS) and service-oriented architecture (SOA). Zachman's framework can help to try to make sense of the alphabet soup of Web services and utilities that form the basis for both SOA and SaaS. The difference between SaaS and SOA is that the former is a software-delivery model whereas the latter is a software-construction model. A better way to illuminate the differences between these two concepts is to use the well-known Zachman architectural model. In this article, we briefly examine the concepts of SaaS and SOA, followed by a brief history of software architectural models. We use the Zachman model to differentiate the two architectural approaches to building software. Because the Zachman model is so intuitive, the approach we take to describe the differences between SaaS and SOA works well even with non-IT professionals.
| Year | Citations | |
|---|---|---|
Page 1
Page 1