Welcome!

Microservices Expo Authors: Dalibor Siroky, Elizabeth White, Pat Romanski, John Katrick, Liz McMillan

Related Topics: Microservices Expo

Microservices Expo: Article

Service-Oriented Process: Thinking About Processes Before Services

Approaching SOA from this "Service-Oriented Process" perspective simplifies and clarifies many of the troublesome issues

When people are first exposed to a new technology, their first urge is to apply yesterday's approaches, theories, and concepts to that new technology. It is only natural, of course, to think of new technologies the way that one traditionally thought of the old technology that it might be replacing, because there is simply no experience yet with how the new technology can be best applied. Every technology goes through this "horseless carriage" phase of technology adoption, so named because when the automobile first came out, people inappropriately applied their knowledge of how to build and use horse carriages to automobiles. However, at some point, some smart individuals or groups realize that the new technology doesn't need to follow the same path as the old one, and the true benefits of the technology can finally be realized. This is when the market for that product really takes off.

Today, we're in the horseless carriage phase for Services and (Service-Oriented Architectures (SOA). The traditional mindset that needs changing is the view that Web Services are an extension of the component object model. To many developers, Web Services are simply "another interface to a compiled object." As a result, they apply their traditional component object design methods, deployment technologies, scalability and reliability approaches, and even terminology. The result: point-to-point implementations of Web Services that are every bit as brittle, tightly coupled, synchronous, and fine-grained as their object-oriented predecessors. In essence, these developers are taking a "bottom-up" view of SOA where the service implementation is the center of the world. As these developers are quickly realizing, thinking of SOA as connected to a particular object model (.NET or J2EE, for example) or implementation approach (application servers vs. messaging middleware, for example) makes meeting the basic principles of SOA a challenge.

Instead of thinking of SOA as a collection of interfaces to software functionality that must somehow be made to connect to other such interfaces, enterprises should approach SOA as enabling a fundamentally process-driven architecture that leverages distributed processes in addition to distributed services. We all understand distributed services-it's distributed computing based on the notion that service interfaces should be standardized and service descriptors and registries should be used to allow for runtime binding. However, distributed processes are all about the creation of business processes that in turn depend on other business processes that may be defined anywhere in the organization. Those business processes then at some point depend on atomic services to fulfill the activities required by their process flow.

Approaching SOA from this "Service-Oriented Process" perspective simplifies and clarifies many of the troublesome issues relating to distributed computing and SOA. Integration goes from being a troublesome chore that must be accomplished through implementing increasing layers of complicated and expensive technologies to a side effect of process execution. In fact, it's difficult to create a Service-Oriented Process that does not provide the fundamental benefits of application and business integration. The mere act of orchestrating and choreographing a Service-oriented business process accomplishes the task of most integration goals.

What is Service-Oriented Process?

While SOA provide a homogeneous and loosely coupled infrastructure for service description and invocation, they don't offer a specific approach to connecting the IT capabilities to the business requirements as we have discussed in earlier ZapFlashes. Since the main rationale for implementing SOA is to obtain quantifiable efficiencies and ROI, companies need to somehow connect the business requirements established by management with the services and capabilities deployed with SOA. For this to happen, SOA must be able to support reliable, durable and at times complex business processes. The application of business process to SOA is known as Service-Oriented Process.

Upcoming ZapThink Training Events

SOA TRAINING & CERT.
Sep. 14-17, 2009
LZA: Washington, DC

Sep. 21-24, 2009
LZA: Chicago, IL

Oct. 5-8, 2009
LZA: Omaha, NE

Oct. 26-29, 2009
LZA: Boston, MA

Nov. 2-5, 2009
LZA: Dubai, UAE

Nov. 9-12, 2009
LZA: Singapore

Nov. 17-20, 2009
LZA: Zurich, Switzerland

Dec. 8-11, 2009
LZA: London, UK

Jan. 11-14, 2010
LZA: Sydney

Mar. 16-19, 2010
LZA: Frankfurt, Germany

 

SOA/CLOUD GOVERNANCE
Sep. 30-Oct. 1, 2009
SOA Governance: DC

Oct. 13-14, 2009
SOA & Cloud Governance @ IASA: New York, NY

Dec. 14-15, 2009
SOA Governance: London

Jan. 18-19, 2010
SOA Governance: Sydney

 

PRACTICAL SOA
Oct. 2, 2009
Practical SOA & EA DC: Cost-Effective Legacy Enablement and Data Management

 

ZAPFORUM EVENTS
Oct. 1, 2009 - Wash. DC
ZapForum DC

Nov. 11, 2009 - Singapore
ZapForum Singapore

Dec. 10, 2009 - London, UK
ZapForum London

Jan. 13, 2010 - Sydney
ZapForum Sydney

Mar. 18, 2010 - Frankfurt
ZapForum Frankfurt

 

VIRTUAL TRAINING
Online LZA Boot Camp

Online Renewal of Existing LZA Credential

 

Individual, atomic Services are not particularly interesting. A business comprised of hundreds of discrete Services isn't particularly efficient. What is more interesting is the composition of multiple SOA into a coherent business process that meets business requirements. In order for this composition to occur, we need a way of composing atomic, fine-grained SOA into coarse-grained business services.Of course, in order to perform this composition, we need to apply business process techniques to SOA.

Business process methodologies are not particularly new. However, what is unique about SOA-based SOA, is that in an SOA, a process is a service. Individual services can be composed into a process flow that itself can be described as a service using the same SOA standards. The ability for services to be consumed by processes that can then be described as services is a very potent notion that shouldn't be overlooked. The services that are consumed by a process might be services local to an enterprise or available at a remote location. In this regard, a Service-Oriented Process exhibits the location independence as well as implementation independence features of loose coupling. A business process description (or flow model) can be published as a Web Service, described via WSDL and interacted with using SOAP. As a result, it becomes impossible to distinguish whether an invoked service is an atomic service or a service composed with business process. Users simply invoke the Service, which has been either specified statically, or determined dynamically through the use of a service registry.

Integration as a Side-Effect of Distributed Processes

In effect, many forward-looking integration efforts have tried to achieve some of the goals that business process approaches promise. Whenever multiple applications or organizations are expected to behave as if they were part of a cohesive and well-integrated architecture, many dimensions of business process come into play. A goal of many large organizations is that the various applications, repositories, and even roles or organizations appear to be well aggregated and integrated even though they are discrete entities that may be distributed across many departments and other enterprises. The different groups involved in the ultimate objective need to be part of the same overall business objective, and the primary way to make sure that all the various components and resources operate in synch is by coordinating them through formalized business process. The problems of integration can thus be reconceived as a part of the general problem of representing an executing business process.

ZapThink Take

It's quite possible that a few years from now, companies won't be spending so much of their time and money on integration middleware and approaches anymore. Instead, it will be the responsibility of every application that participates in a process to provide the necessary layers of integration. The enterprise architecture will provide integration capabilities, because it will be process driven. Enterprises will then be able to focus on more important aspects of their business: modeling their business requirements and processes, and building the IT systems that meet those goals.

More Stories By Ron Schmelzer

Ron Schmelzer is founder and senior analyst of ZapThink. A well-known expert in the field of XML and XML-based standards and initiatives, Ron has been featured in and written for periodicals and has spoken on the subject of XML at numerous industry conferences.

@MicroservicesExpo Stories
How is DevOps going within your organization? If you need some help measuring just how well it is going, we have prepared a list of some key DevOps metrics to track. These metrics can help you understand how your team is doing over time. The word DevOps means different things to different people. Some say it a culture and every vendor in the industry claims that their tools help with DevOps. Depending on how you define DevOps, some of these metrics may matter more or less to you and your team.
For many of us laboring in the fields of digital transformation, 2017 was a year of high-intensity work and high-reward achievement. So we’re looking forward to a little breather over the end-of-year holiday season. But we’re going to have to get right back on the Continuous Delivery bullet train in 2018. Markets move too fast and customer expectations elevate too precipitously for businesses to rest on their laurels. Here’s a DevOps “to-do list” for 2018 that should be priorities for anyone w...
If testing environments are constantly unavailable and affected by outages, release timelines will be affected. You can use three metrics to measure stability events for specific environments and plan around events that will affect your critical path to release.
In a recent post, titled “10 Surprising Facts About Cloud Computing and What It Really Is”, Zac Johnson highlighted some interesting facts about cloud computing in the SMB marketplace: Cloud Computing is up to 40 times more cost-effective for an SMB, compared to running its own IT system. 94% of SMBs have experienced security benefits in the cloud that they didn’t have with their on-premises service
DevOps failure is a touchy subject with some, because DevOps is typically perceived as a way to avoid failure. As a result, when you fail in a DevOps practice, the situation can seem almost hopeless. However, just as a fail-fast business approach, or the “fail and adjust sooner” methodology of Agile often proves, DevOps failures are actually a step in the right direction. They’re the first step toward learning from failures and turning your DevOps practice into one that will lead you toward even...
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...
While walking around the office I happened upon a relatively new employee dragging emails from his inbox into folders. I asked why and was told, “I’m just answering emails and getting stuff off my desk.” An empty inbox may be emotionally satisfying to look at, but in practice, you should never do it. Here’s why. I recently wrote a piece arguing that from a mathematical perspective, Messy Desks Are Perfectly Optimized. While it validated the genius of my friends with messy desks, it also gener...
The goal of Microservices is to improve software delivery speed and increase system safety as scale increases. Microservices being modular these are faster to change and enables an evolutionary architecture where systems can change, as the business needs change. Microservices can scale elastically and by being service oriented can enable APIs natively. Microservices also reduce implementation and release cycle time and enables continuous delivery. This paper provides a logical overview of the Mi...
The next XaaS is CICDaaS. Why? Because CICD saves developers a huge amount of time. CD is an especially great option for projects that require multiple and frequent contributions to be integrated. But… securing CICD best practices is an emerging, essential, yet little understood practice for DevOps teams and their Cloud Service Providers. The only way to get CICD to work in a highly secure environment takes collaboration, patience and persistence. Building CICD in the cloud requires rigorous ar...
The enterprise data storage marketplace is poised to become a battlefield. No longer the quiet backwater of cloud computing services, the focus of this global transition is now going from compute to storage. An overview of recent storage market history is needed to understand why this transition is important. Before 2007 and the birth of the cloud computing market we are witnessing today, the on-premise model hosted in large local data centers dominated enterprise storage. Key marketplace play...
The cloud revolution in enterprises has very clearly crossed the phase of proof-of-concepts into a truly mainstream adoption. One of most popular enterprise-wide initiatives currently going on are “cloud migration” programs of some kind or another. Finding business value for these programs is not hard to fathom – they include hyperelasticity in infrastructure consumption, subscription based models, and agility derived from rapid speed of deployment of applications. These factors will continue to...
Some people are directors, managers, and administrators. Others are disrupters. Eddie Webb (@edwardawebb) is an IT Disrupter for Software Development Platforms at Liberty Mutual and was a presenter at the 2016 All Day DevOps conference. His talk, Organically DevOps: Building Quality and Security into the Software Supply Chain at Liberty Mutual, looked at Liberty Mutual's transformation to Continuous Integration, Continuous Delivery, and DevOps. For a large, heavily regulated industry, this task ...
Following a tradition dating back to 2002 at ZapThink and continuing at Intellyx since 2014, it’s time for Intellyx’s annual predictions for the coming year. If you’re a long-time fan, you know we have a twist to the typical annual prediction post: we actually critique our predictions from the previous year. To make things even more interesting, Charlie and I switch off, judging the other’s predictions. And now that he’s been with Intellyx for more than a year, this Cortex represents my first ...
"Grape Up leverages Cloud Native technologies and helps companies build software using microservices, and work the DevOps agile way. We've been doing digital innovation for the last 12 years," explained Daniel Heckman, of Grape Up in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
The Toyota Production System, a world-renowned production system is based on the "complete elimination of all waste". The "Toyota Way", grounded on continuous improvement dates to the 1860s. The methodology is widely proven to be successful yet there are still industries within and tangential to manufacturing struggling to adopt its core principles: Jidoka: a process should stop when an issue is identified prevents releasing defective products
We seem to run this cycle with every new technology that comes along. A good idea with practical applications is born, then both marketers and over-excited users start to declare it is the solution for all or our problems. Compliments of Gartner, we know it generally as “The Hype Cycle”, but each iteration is a little different. 2018’s flavor will be serverless computing, and by 2018, I mean starting now, but going most of next year, you’ll be sick of it. We are already seeing people write such...
Defining the term ‘monitoring’ is a difficult task considering the performance space has evolved significantly over the years. Lately, there has been a shift in the monitoring world, sparking a healthy debate regarding the definition and purpose of monitoring, through which a new term has emerged: observability. Some of that debate can be found in blogs by Charity Majors and Cindy Sridharan.
It’s “time to move on from DevOps and continuous delivery.” This was the provocative title of a recent article in ZDNet, in which Kelsey Hightower, staff developer advocate at Google Cloud Platform, suggested that “software shops should have put these concepts into action years ago.” Reading articles like this or listening to talks at most DevOps conferences might make you think that we’re entering a post-DevOps world. But vast numbers of organizations still struggle to start and drive transfo...
Let's do a visualization exercise. Imagine it's December 31, 2018, and you're ringing in the New Year with your friends and family. You think back on everything that you accomplished in the last year: your company's revenue is through the roof thanks to the success of your product, and you were promoted to Lead Developer. 2019 is poised to be an even bigger year for your company because you have the tools and insight to scale as quickly as demand requires. You're a happy human, and it's not just...
"Opsani helps the enterprise adopt containers, help them move their infrastructure into this modern world of DevOps, accelerate the delivery of new features into production, and really get them going on the container path," explained Ross Schibler, CEO of Opsani, and Peter Nickolov, CTO of Opsani, in this SYS-CON.tv interview at DevOps Summit at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.