SOA: Difference between revisions
Jump to navigation
Jump to search
imported>Ro Thorpe mNo edit summary |
imported>Ro Thorpe |
||
| Line 6: | Line 6: | ||
==Two views on same topic== | ==Two views on same topic== | ||
Often the term SOA is overloaded with varying interpretations. Service Oriented Architecture has become a term which has steadily been allocated with ever more ‘meaning’. From a set of (technical) architectural principles <ref>Erl, T. (2005): Service-Oriented Architecture. Concepts, Technology, and Design. Prentice Hall, Professional Technical Reference (PTR), Upper Saddle River. ISBN: 0-13-185858-0. Page 54.</ref><ref>Gartner Research by Genovese, Y. (2006): Most benefits of service oriented architecture for business applications are longer term. Gartner Research, publication date 9-2-2006. ID number G00137562</ref> | Often the term SOA is overloaded with varying interpretations. Service Oriented Architecture has become a term which has steadily been allocated with ever more ‘meaning’. From a set of (technical) architectural principles,<ref>Erl, T. (2005): Service-Oriented Architecture. Concepts, Technology, and Design. Prentice Hall, Professional Technical Reference (PTR), Upper Saddle River. ISBN: 0-13-185858-0. Page 54.</ref><ref>Gartner Research by Genovese, Y. (2006): Most benefits of service oriented architecture for business applications are longer term. Gartner Research, publication date 9-2-2006. ID number G00137562</ref> it has been deemed a design approach,<ref>Gartner Research by Natis, Y.V. , Schulte, R.W. (2003): Introduction to SOA. Gartner Research, publication date 14-4-2003. ID number SPA-19-5971</ref> a product according to various vendors,<ref>See for example the blog of Eric Roch (2007): SOA Product Evaluation. http://blogs.ittoolbox.com/eai/business/archives/soa-product-evaluation-13930</ref> a strategy,<ref>Jayashetty, S., Kumar, P.M. (2006): Adopting Service Oriented Architecture increases the flexibility of your enterprise. Infosys Viewpoint, | ||
march 2006.</ref> | march 2006.</ref> a business IT alignment approach<ref>Allen, P., Higgins, S., McRae, P., Schlamann, H. (2006): Service Orientation, Winning Strategies and Best Practices. Cambridge University Press, Cambridge, UK. ISBN-13 978-0-521-84336-2. p3.</ref> or even a paradigm.<ref>Bieberstein, N. , Bose, S. , Walker L. , Lynch A. (2005): Impact of Service-oriented architecture on enterprise systems, organizational structures, and individuals. IBM Systems journal, vol. 44, no. 4, 2005. p691.</ref> | ||
Service Orientation is proposed as a coordinating paradigm. Strikingly enough no explicit definition of Service Orientation as a paradigm has been encountered in the literature. Often Service Orientation and SOA are mixed up. One of the reasons is the growing hype around this term and the many commercial interests trying to join in with their interpretation of the hype. | Service Orientation is proposed as a coordinating paradigm. Strikingly enough no explicit definition of Service Orientation as a paradigm has been encountered in the literature. Often Service Orientation and SOA are mixed up. One of the reasons is the growing hype around this term and the many commercial interests trying to join in with their interpretation of the hype. | ||
Revision as of 11:53, 7 September 2010
Service Oriented Architecture (SOA) and Service Orientation (SO) are two intertwined concepts.[1] Service Oriented Architecture is a computer system's architectural style for creating and using business processes, packaged as services, throughout their lifecycle. Service Orientation is the organizational paradigm, focused at obtaining and creating a better alignment between IS and the business processes and structure of an enterprise. When discussing SOA and SO, the notion of Business Process Management should be taken into account.
The concepts are still evolving and other sources may use different definitions.
Two views on same topic
Often the term SOA is overloaded with varying interpretations. Service Oriented Architecture has become a term which has steadily been allocated with ever more ‘meaning’. From a set of (technical) architectural principles,[2][3] it has been deemed a design approach,[4] a product according to various vendors,[5] a strategy,[6] a business IT alignment approach[7] or even a paradigm.[8]
Service Orientation is proposed as a coordinating paradigm. Strikingly enough no explicit definition of Service Orientation as a paradigm has been encountered in the literature. Often Service Orientation and SOA are mixed up. One of the reasons is the growing hype around this term and the many commercial interests trying to join in with their interpretation of the hype.
Service Oriented Architecture
References & Citations
- ↑ Erl, Thomas (2006): Why we should focus on service-orientation more than SOA. http://searchsoa.techtarget.com/news/interview/0,289202,sid26_gci1189356,00.html
- ↑ Erl, T. (2005): Service-Oriented Architecture. Concepts, Technology, and Design. Prentice Hall, Professional Technical Reference (PTR), Upper Saddle River. ISBN: 0-13-185858-0. Page 54.
- ↑ Gartner Research by Genovese, Y. (2006): Most benefits of service oriented architecture for business applications are longer term. Gartner Research, publication date 9-2-2006. ID number G00137562
- ↑ Gartner Research by Natis, Y.V. , Schulte, R.W. (2003): Introduction to SOA. Gartner Research, publication date 14-4-2003. ID number SPA-19-5971
- ↑ See for example the blog of Eric Roch (2007): SOA Product Evaluation. http://blogs.ittoolbox.com/eai/business/archives/soa-product-evaluation-13930
- ↑ Jayashetty, S., Kumar, P.M. (2006): Adopting Service Oriented Architecture increases the flexibility of your enterprise. Infosys Viewpoint, march 2006.
- ↑ Allen, P., Higgins, S., McRae, P., Schlamann, H. (2006): Service Orientation, Winning Strategies and Best Practices. Cambridge University Press, Cambridge, UK. ISBN-13 978-0-521-84336-2. p3.
- ↑ Bieberstein, N. , Bose, S. , Walker L. , Lynch A. (2005): Impact of Service-oriented architecture on enterprise systems, organizational structures, and individuals. IBM Systems journal, vol. 44, no. 4, 2005. p691.