Welcome!

Microservices Expo Authors: Pat Romanski, AppDynamics Blog, Liz McMillan, Elizabeth White, Stackify Blog

Related Topics: Microservices Expo

Microservices Expo: Article

Exclusive SOA Web Services Journal Briefing – Thomas Erl On SOA

The Principles of Service-Orientation

With the unwavering prominence of service-oriented architecture (SOA) there is an increasing interest in understanding what exactly it means for something to be considered "service-oriented." Thomas Erl recently completed a lengthy research project for SOA Systems Inc. into the origins of SOA and the current state of service-orientation among all primary SOA technology platforms. This body of work contributed to the mainstream SOA methodology developed by SOA Systems and was also documented in Thomas's new book, Service-Oriented Architecture: Concepts, Technology, and Design. We caught up with Thomas (a previous contributor to WSJ) to ask him to share some of the insights he gained from his work with SOA and service-orientation.

There's no need to mention that SOA has become a major focal point of the IT industry and a primary consideration on numerous corporate agendas. Nor is there a need to get into how SOA has been so heavily promoted that the term has already reached hall-of-fame status as one of the most recognized acronyms in IT history.

What is more important than the term itself is the impact its perceived meaning continues to have on how automation solutions are constructed. Its popularity to date is largely the result of vendors advertising SOA support or capability as part of their product lines. Because SOA has been so vendor-driven, its meaning has been somewhat divergent, skewed by proprietary technology that is still identified with common characteristics that transcend proprietary boundaries.

These common characteristics are critical to defining and understanding an abstract technology architecture classified as "service-oriented." Viewing SOA in abstract is what establishes an agnostic reference point from which proprietary implementations can be measured and, ultimately, unified.

Vendor-Oriented Service-Orientation
Vendors and other organizations in the SOA space have published numerous papers, blueprints, and even frameworks. Most such documents serve the dual purpose of educating readers about SOA while marketing related products or services. This is nothing new. Past variations of client-server and distributed architecture models have varied significantly in both technology and design, depending mostly on who and what was used to implement them.

However, because a core expectation of SOA is its ability to harmonize and streamline diverse technical environments, preserving an abstract viewpoint is required to achieving its potential. This is because SOA, when elevated to an enterprise level, can be used to establish an ecosystem in which an agnostic, overarching framework transcends proprietary environments and constraints.

How the components and elements within this framework are shaped and standardized is of critical importance. This underlines the need for a design paradigm that is sufficiently generic so that it can be applied to solutions regardless of implementation, while remaining in alignment with where powerhouse vendors and organizations are currently taking the technology that is fueling the service-oriented computing platform.

Service-Orientation and Object-Orientation
Design paradigms have played an important role in the evolution of technology and application architecture. The most widely recognized paradigm for distributed business automation has been object-orientation. The system-wide implementation technology for object-oriented solutions has traditionally been proprietary, where, despite the use of the agnostic principles of object-orientation, objects or components are designed to function and interact by using technology and protocols specific to a computing and/or vendor platform.

Service-orientation owes much of its existence to object-orientation. Like traditional multitiered architectures, SOA is based on a model wherein solution logic is distributed. As with object-orientation, concepts such as encapsulation, abstraction, and reusability are fundamental to the design of distributed units of automation logic (services) within SOA. Key differences in these approaches are focused on how these units relate to each other and the scope at which the respective paradigms can be applied.

See Figure 1

Service-Orientation and the Separation of Concerns
I have yet to find a better means of explaining service-orientation than to reach back to that fundamental software engineering theory known as the "separation of concerns." This theory essentially proposes that larger problems be decomposed into a series of individually identifiable problems or "concerns." The logic required to address or solve the larger problem can then also be broken down into individual units of logic that address specific concerns.

Past design paradigms and development platforms have applied this theory in different ways. Component-based and object-oriented designs, for example, provide specific approaches for the decomposition of concerns and the design of corresponding solution logic. Service-orientation establishes a new and distinct means of realizing a separation of concerns. As a design paradigm, it is an evolution of past approaches, augmented and extended in support of the overall goals and characteristics of SOA.

See Figure 2

Common Service-Orientation Principles
Service-orientation began with a modest scope - a basic set of principles centered on an architectural model focused primarily on distinguishing services as reusable and discoverable resources. However, technology architecture in support of service-orientation is making significant strides, and extending its reach into key realms of enterprise computing.

Expectations are being raised surrounding a new era of business automation composed of services as adaptive, shared software assets that promise to infuse an enterprise with organization-level agility, federated interoperability, and vendor independence. These expectations have placed demands on what a distributed automation solution classified as "service-oriented" should be capable of, expanding the breadth of the service-oriented paradigm and adding to and further shaping its principles.

So far, eight common and fundamental principles have been identified. Note that these are classified as "common" in that they represent a cross-section of the most widely accepted design approaches and best practices promoted and practiced by the organizations most responsible for realizing the contemporary SOA movement.

Here then are the common principles of service-orientation:

  • services are loosely coupled
  • services share a formal contract
  • services abstract underlying logic
  • services are composable
  • services are reusable
  • services are autonomous
  • services are stateless
  • services are discoverable

More Stories By Thomas Erl

Thomas Erl is a best-selling IT author and founder of Arcitura Education Inc., a global provider of vendor-neutral educational services and certification that encompasses the Cloud Certified Professional (CCP) and SOA Certified Professional (SOACP) programs from CloudSchool.com™ and SOASchool.com® respectively. Thomas has been the world's top-selling service technology author for nearly a decade and is the series editor of the Prentice Hall Service Technology Series from Thomas Erl, as well as the editor of the Service Technology Magazine. With over 175,000 copies in print world-wide, his eight published books have become international bestsellers and have been formally endorsed by senior members of many major IT organizations and academic institutions. To learn more, visit: www.thomaserl.com

Comments (3)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


Microservices Articles
Skeuomorphism usually means retaining existing design cues in something new that doesn’t actually need them. However, the concept of skeuomorphism can be thought of as relating more broadly to applying existing patterns to new technologies that, in fact, cry out for new approaches. In his session at DevOps Summit, Gordon Haff, Senior Cloud Strategy Marketing and Evangelism Manager at Red Hat, discussed why containers should be paired with new architectural practices such as microservices rathe...
DevOps is under attack because developers don’t want to mess with infrastructure. They will happily own their code into production, but want to use platforms instead of raw automation. That’s changing the landscape that we understand as DevOps with both architecture concepts (CloudNative) and process redefinition (SRE). Rob Hirschfeld’s recent work in Kubernetes operations has led to the conclusion that containers and related platforms have changed the way we should be thinking about DevOps and...
With the rise of Docker, Kubernetes, and other container technologies, the growth of microservices has skyrocketed among dev teams looking to innovate on a faster release cycle. This has enabled teams to finally realize their DevOps goals to ship and iterate quickly in a continuous delivery model. Why containers are growing in popularity is no surprise — they’re extremely easy to spin up or down, but come with an unforeseen issue. However, without the right foresight, DevOps and IT teams may lo...
"There is a huge interest in Kubernetes. People are now starting to use Kubernetes and implement it," stated Sebastian Scheele, co-founder of Loodse, in this SYS-CON.tv interview at DevOps at 19th Cloud Expo, held November 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA.
In his session at 20th Cloud Expo, Mike Johnston, an infrastructure engineer at Supergiant.io, will discuss how to use Kubernetes to setup a SaaS infrastructure for your business. Mike Johnston is an infrastructure engineer at Supergiant.io with over 12 years of experience designing, deploying, and maintaining server and workstation infrastructure at all scales. He has experience with brick and mortar data centers as well as cloud providers like Digital Ocean, Amazon Web Services, and Rackspace....
Today most companies are adopting or evaluating container technology - Docker in particular - to speed up application deployment, drive down cost, ease management and make application delivery more flexible overall. As with most new architectures, this dream takes significant work to become a reality. Even when you do get your application componentized enough and packaged properly, there are still challenges for DevOps teams to making the shift to continuous delivery and achieving that reducti...
Modern software design has fundamentally changed how we manage applications, causing many to turn to containers as the new virtual machine for resource management. As container adoption grows beyond stateless applications to stateful workloads, the need for persistent storage is foundational - something customers routinely cite as a top pain point. In his session at @DevOpsSummit at 21st Cloud Expo, Bill Borsari, Head of Systems Engineering at Datera, explored how organizations can reap the bene...
Is advanced scheduling in Kubernetes achievable?Yes, however, how do you properly accommodate every real-life scenario that a Kubernetes user might encounter? How do you leverage advanced scheduling techniques to shape and describe each scenario in easy-to-use rules and configurations? In his session at @DevOpsSummit at 21st Cloud Expo, Oleg Chunikhin, CTO at Kublr, answered these questions and demonstrated techniques for implementing advanced scheduling. For example, using spot instances and co...
Docker is sweeping across startups and enterprises alike, changing the way we build and ship applications. It's the most prominent and widely known software container platform, and it's particularly useful for eliminating common challenges when collaborating on code (like the "it works on my machine" phenomenon that most devs know all too well). With Docker, you can run and manage apps side-by-side - in isolated containers - resulting in better compute density. It's something that many developer...
In his general session at 19th Cloud Expo, Manish Dixit, VP of Product and Engineering at Dice, discussed how Dice leverages data insights and tools to help both tech professionals and recruiters better understand how skills relate to each other and which skills are in high demand using interactive visualizations and salary indicator tools to maximize earning potential. Manish Dixit is VP of Product and Engineering at Dice. As the leader of the Product, Engineering and Data Sciences team at D...