Click here to close now.

Welcome!

@MicroservicesE Blog Authors: Sematext Blog, Lori MacVittie, Ian Goldsmith, Liz McMillan, Pat Romanski

Related Topics: @MicroservicesE Blog

@MicroservicesE Blog: 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) View Comments

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.


Most Recent Comments
erl 10/29/05 06:17:48 AM EDT

{{{ 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." }}}

I'd not heard this one before. Useful phrase.

queZZtion 10/29/05 05:36:51 AM EDT

||| technology architecture in support of service-orientation is making significant strides, and extending its reach into key realms of enterprise computing |||

The age of SOA will last much longer than the age of client/server. How long though?

Short&Sweet 10/29/05 05:32:53 AM EDT

Erl's book on this subject, Service-Oriented Architecture: Concepts, Technology, and Design has 792 pages - helpful to have this boiled down to just 3 pages here!

@MicroservicesExpo Stories
T-Mobile has been transforming the wireless industry with its “Uncarrier” initiatives. Today as T-Mobile’s IT organization works to transform itself in a like manner, technical foundations built over the last couple of years are now key to their drive for more Agile delivery practices. In his session at DevOps Summit, Martin Krienke, Sr Development Manager at T-Mobile, will discuss where they started their Continuous Delivery journey, where they are today, and where they are going in an effort ...
I’ve been thinking a bit about microservices (μServices) recently. My immediate reaction is to think: “Isn’t this just yet another new term for the same stuff, Web Services->SOA->APIs->Microservices?” Followed shortly by the thought, “well yes it is, but there are some important differences/distinguishing factors.” Microservices is an evolutionary paradigm born out of the need for simplicity (i.e., get away from the ESB) and alignment with agile (think DevOps) and scalable (think Containerizati...

Let's just nip the conflation of these terms in the bud, shall we?

"MIcro" is big these days. Both microservices and microsegmentation are having and will continue to have an impact on data center architecture, but not necessarily for the same reasons. There's a growing trend in which folks - particularly those with a network background - conflate the two and use them to mean the same thing.

They are not.

One is about the application. The other, the network. T...

The release of Kibana 4.x has had an impact on monitoring and other related activities.  In this post we’re going to get specific and show you how to add Node.js monitoring to the Kibana 4 server app.  Why Node.js?  Because Kibana 4 now comes with a little Node.js server app that sits between the Kibana UI and the […]
Containers Expo Blog covers the world of containers, as this lightweight alternative to virtual machines enables developers to work with identical dev environments and stacks. Containers Expo Blog offers top articles, news stories, and blog posts from the world's well-known experts and guarantees better exposure for its authors than any other publication. Bookmark Containers Expo Blog ▸ Here Follow new article posts on Twitter at @ContainersExpo
There are 182 billion emails sent every day, generating a lot of data about how recipients and ISPs respond. Many marketers take a more-is-better approach to stats, preferring to have the ability to slice and dice their email lists based numerous arbitrary stats. However, fundamentally what really matters is whether or not sending an email to a particular recipient will generate value. Data Scientists can design high-level insights such as engagement prediction models and content clusters that a...
In today's application economy, enterprise organizations realize that it's their applications that are the heart and soul of their business. If their application users have a bad experience, their revenue and reputation are at stake. In his session at 15th Cloud Expo, Anand Akela, Senior Director of Product Marketing for Application Performance Management at CA Technologies, discussed how a user-centric Application Performance Management solution can help inspire your users with every applicati...
As enterprises engage with Big Data technologies to develop applications needed to meet operational demands, new computation fabrics are continually being introduced. To leverage these new innovations, organizations are sacrificing market opportunities to gain expertise in learning new systems. In his session at Big Data Expo, Supreet Oberoi, Vice President of Field Engineering at Concurrent, Inc., discussed how to leverage existing infrastructure and investments and future-proof them against e...
Once the decision has been made to move part or all of a workload to the cloud, a methodology for selecting that workload needs to be established. How do you move to the cloud? What does the discovery, assessment and planning look like? What workloads make sense? Which cloud model makes sense for each workload? What are the considerations for how to select the right cloud model? And how does that fit in with the overall IT transformation?
You use an agile process; your goal is to make your organization more agile. But what about your data infrastructure? The truth is, today's databases are anything but agile - they are effectively static repositories that are cumbersome to work with, difficult to change, and cannot keep pace with application demands. Performance suffers as a result, and it takes far longer than it should to deliver new features and capabilities needed to make your organization competitive. As your application an...
17th Cloud Expo, taking place Nov 3-5, 2015, at the Santa Clara Convention Center in Santa Clara, CA, will feature technical sessions from a rock star conference faculty and the leading industry players in the world. Cloud computing is now being embraced by a majority of enterprises of all sizes. Yesterday's debate about public vs. private has transformed into the reality of hybrid cloud: a recent survey shows that 74% of enterprises have a hybrid cloud strategy. Meanwhile, 94% of enterprises a...
SYS-CON Events announced today that SUSE, a pioneer in open source software, will exhibit at SYS-CON's DevOps Summit 2015 New York, which will take place June 9-11, 2015, at the Javits Center in New York City, NY. SUSE provides reliable, interoperable Linux, cloud infrastructure and storage solutions that give enterprises greater control and flexibility. More than 20 years of engineering excellence, exceptional service and an unrivaled partner ecosystem power the products and support that help ...
Virtualization is everywhere. Enormous and highly profitable companies have been built on nothing but virtualization. And nowhere has virtualization made more of an impact than in Cloud Computing, the rampant and unprecedented adoption of which has been the direct result of the wide availability of virtualization software and techniques that enabled it. But does the cloud actually require virtualization?
There’s a lot of discussion around managing outages in production via the likes of DevOps principles and the corresponding software development lifecycles that does enable higher quality output from development, however, one cannot lay all blame for “bugs” and failures at the feet of those responsible for coding and development. As developers incorporate features and benefits of these paradigm shift, there is a learning curve and a point of not-knowing-what-is-not-known. Sometimes, the only way ...
Right off the bat, Newman advises that we should "think of microservices as a specific approach for SOA in the same way that XP or Scrum are specific approaches for Agile Software development". These analogies are very interesting because my expectation was that microservices is a pattern. So I might infer that microservices is a set of process techniques as opposed to an architectural approach. Yet in the book, Newman clearly includes some elements of concept model and architecture as well as p...
How can you compare one technology or tool to its competitors? Usually, there is no objective comparison available. So how do you know which is better? Eclipse or IntelliJ IDEA? Java EE or Spring? C# or Java? All you can usually find is a holy war and biased comparisons on vendor sites. But luckily, sometimes, you can find a fair comparison. How does this come to be? By having it co-authored by the stakeholders. The binary repository comparison matrix is one of those rare resources. It is edite...
As the world moves from DevOps to NoOps, application deployment to the cloud ought to become a lot simpler. However, applications have been architected with a much tighter coupling than it needs to be which makes deployment in different environments and migration between them harder. The microservices architecture, which is the basis of many new age distributed systems such as OpenStack, Netflix and so on is at the heart of CloudFoundry – a complete developer-oriented Platform as a Service (PaaS...
There is no question that the cloud is where businesses want to host data. Until recently hypervisor virtualization was the most widely used method in cloud computing. Recently virtual containers have been gaining in popularity, and for good reason. In the debate between virtual machines and containers, the latter have been seen as the new kid on the block – and like other emerging technology have had some initial shortcomings. However, the container space has evolved drastically since coming on...
The widespread success of cloud computing is driving the DevOps revolution in enterprise IT. Now as never before, development teams must communicate and collaborate in a dynamic, 24/7/365 environment. There is no time to wait for long development cycles that produce software that is obsolete at launch. DevOps may be disruptive, but it is essential. The DevOps Summit at Cloud Expo – to be held June 3-5, 2015, at the Javits Center in New York City – will expand the DevOps community, enable a wide...
Cloud Expo, Inc. has announced today that Andi Mann returns to DevOps Summit 2015 as Conference Chair. The 4th International DevOps Summit will take place on June 9-11, 2015, at the Javits Center in New York City. "DevOps is set to be one of the most profound disruptions to hit IT in decades," said Andi Mann. "It is a natural extension of cloud computing, and I have seen both firsthand and in independent research the fantastic results DevOps delivers. So I am excited to help the great team at ...