Service-orientation has received a lot of attention since 20033 due to the benefits it promises. These include increased return on investment, organisational agility and interoperability as well as a better alignment between business and IT. It builds heavily on earlier design paradigms and enhances them with standardisation, loose coupling and business involvement.4 The paradigm lost momentum in 2009;5 since 2014, renewed interest can be observed under the Microservices moniker. In technology, different vendor SOA platforms have used different definitions of service-orientation. Some vendors promote different principles and tenets over others, but a fair amount of commonality exists.6
Service-orientation inherits a small number of principles from earlier paradigms including object-oriented programming, component-based software engineering and open distributed processing. It is commonly acknowledged that several service-orientation principles have their roots in the object-oriented design paradigm: the two are complementary paradigms and there will always be a need for both.7 Services also inherit a number of features of software components, including
Open Distributed Processing (ODP) combines the concepts of open systems and distributed computing, which are essential characteristics of service-orientation. The key features of ODP are all inherited by service-orientation, including federation, interoperability, heterogeneity, transparency and trading/broking.
Don Box was one of the first to provide a set of design guidelines referred to as his "four tenets of service-orientation", which he described primarily in relation to the Microsoft Indigo (subsequently Windows Communication Foundation) platform that was emerging at the time:
Other vendors and independent consultants have published their definitions of service-orientation and SOA, for instance, N. Josuttis in "SOA in Practice" and D: Krafzig et al. in "Enterprise SOA". An article in the December 2005 edition of the IBM System Journal8 entitled "Impact of service orientation at the business level"9 provided a study of how the service-orientation paradigm relates to fundamental componentization and the IBM Component Business Model (CBM).
Paul Allen defines service orientation as a (business) paradigm, with three main components: business architecture, Service-oriented architecture and software oriented management. Allen's book defines seven Service-Oriented Viewpoints (labelled SOV7): Allen, Paul (2006). Service Orientation Winning Strategies and Best Practices. Cambridge University Press. ISBN 978-0521843362.
Allen uses the viewpoints as starting point for stating questions during the design process.
Service-orientation has continued to receive increased recognition as an important part of the service-oriented computing landscape and a valid design approach to achieving service-oriented architecture.
Erl, Thomas. "SOA Principles". http://www.soaprinciples.com/p3.php ↩
"Service-Oriented Software Engineering". http://www.s-cube-network.eu/km/terms/s/service-oriented-software-engineering ↩
"Gartner's Hype Cycle Special Report for 2005" (PDF). http://www.gartner.com/resources/130100/130115/gartners_hype_c.pdf ↩
Erl, Thomas. "What Is SOA? - Introduction". http://www.whatissoa.com/p16.php ↩
"SOA is Dead; Long Live Services". Application Platform Strategies Blog. http://apsblog.burtongroup.com/2009/01/soa-is-dead-long-live-services.html ↩
Liebhart, Daniel. SOA goes real. Hanser, 2007, p. 22 ↩
"Elements of Service-Oriented Analysis and Design". www.ibm.com. 2 June 2004. http://www.ibm.com/developerworks/library/ws-soad1/index.html ↩
"IBM Journal of Research & Development". www.research.ibm.com. 23 October 2017. Archived from the original on 2006-03-12. https://archive.today/20060312002405/http://www.research.ibm.com/journal/sj/ ↩
"Impact of service orientation at the business level". www.research.ibm.com. 23 October 2017. Archived from the original on 2006-03-12. https://archive.today/20060312024514/http://www.research.ibm.com/journal/sj/444/cherbakov.html ↩