Welcome!

Microservices Expo Authors: Liz McMillan, Flint Brenton, Jason Bloomberg, Elizabeth White, Yeshim Deniz

Related Topics: Microservices Expo

Microservices Expo: Article

Pragmatic SOA Interoperability

Architecture, not new middleware

A well-planned Web Service interoperability environment begins by clearly defining who your Web Service consumers are now and in the future. There was a time not so long ago when you could count on a fairly homogenous consumer population. This was about the same time that you were happy just to be able to get a Web Service running in the first place and finding a consumer who could actually interact with your Web Service was cause for celebration. Those days have changed however and Web Services interoperability, once a "fancy" addition to your SOA design, is now a key and indispensable requirement in most SOA scenarios.

Today, SOA architects must contend with complex scenarios that assume a variety of Web Service consumers or in many cases are asked to create Web Services that are generic enough to be interoperable with just about any known consumer. If you're serious about implementing SOA in your worldwide enterprise you'll have to forget about the luxury of being able to dictate the configuration of all of your consumers and instead build fully interoperable Web Services. Most robust Internet Web Service APIs, familiar to all of us such as Amazon.com, eBay, or Salesforce.com, have learned this lesson already with very successful results. Those companies know that Web Service interoperability lies in the architecture approach and not in the implementation of new middleware.

What Makes Interoperability So Challenging?

Standards Proliferation and Complexity
The interaction between Web Services and consumers is rooted on a set of standards developed by standards organization committees at OASIS, W3C, and WS-I. These standards such as XML Schema, SOAP, WSDL, and WS-* protocols are intended to provide a technology-agnostic level of abstraction over the service implementation which should theoretically guarantee interoperability. However, it's not the standards themselves, but their implementation by individual Web Service technology vendors that must be interoperable. In a perfect world, every vendor would implement Web Services standards in exactly the same way, which would guarantee interoperability out-of-the-box. As you must know, that's just too good to be true. In the real world, every vendor implements these standards sometimes with just slight variations and other times entirely different versions. In many other cases vendors choose which aspects of a standard to implement, or maybe even choose not to implement a given standard at all. This proliferation and complexity is most obvious when we look at the WS-* protocols.

When this article was written, up to four different WS-Addressing versions were in use. Three versions of the specification are named by their release date: the March 2003 version, the March 2004 version, and the August 2004 version, developed before the specification moved to W3C. The fourth version, 1.0, was completed in May 2006 and developed after the specification went under the W3C umbrella. And if that's not confusing enough, after moving to W3C, the specification split into multiple parts: a core specification and two other specifications that describe bindings for SOAP and WSDL.

There are also different WS-* protocols that address very similar scenarios such as WS-Eventing and WS-Notifications, WS-MessageDelivery and WS-Addressing or WS-Reliability and WS-ReliableMessaging. Committees from OASIS and W3C are working to unify those overlapped protocols into a single set of standards. Vendors can and often implement different versions of the same WS-* protocol or implement one of multiple similar standards such as WS-ReliableMessaging instead of WS-Reliability.

Although the combination of SOAP and WS-* protocols provide a solution for some of the most interesting challenges in distributed computing, the complexity of this approach makes it impractical and nearly impossible to implement in real-world interoperability scenarios. Just a small subset of the over 100 WS-* standards specifications available today have been implemented by vendors. One last, but certainly not least, challenge involved in using SOAP and WS-* protocols is that they can also limit the service availability to clients such as script applications or Web browsers that don't support that generation of SOAP messages.

Best Practice: Use WS-I Profiles
Some WS-* protocols have a WS-I profile available that contains some of the principles and a subset of features of the protocols that should be implemented to guarantee interoperability. Making the services compatible with a WS-I profile (is this one exists) is a standard and globally accepted approach to interoperability. However for some protocols, a WS-I profile isn't available or doesn't address the interoperability requirements.

Best Practice: Implement Multi-Binding Services
To support multiple versions of the same WS-* protocol it's recommended to design the services with multiple bindings per specific versions of the protocol. This approach segments the different types of interactions at the binding level improving aspects like versioning, management, etc. The code in Listings 1 and 2 illustrates a sample Microsoft Windows Communication Foundation (WCF) Service configured to support multiple types of interactions using bindings. Specifically, this service supports secure and reliable interactions as well as basic SOAP interactions using two different bindings.

Best Practice: Exposes SOAP and REST Interfaces
Resource State Transfer (REST) provides a simpler alternative to the use of SOAP and the WS-* protocols for some scenarios. The fact that REST is based on XML messages over HTTP makes it accessible to most of the client technologies on the market including browsers and script languages. Some services can expose both SOAP and REST interfaces and offer a broader set of options to consumers. The example in Listing 3 illustrates that approach using Oracle Application Server.

Aligning Code and Contract
When designing a service you must first consider where to start. Do you create your code first or your contract first? Or do you give them each equal importance by creating them in parallel. However, even if you were extremely diligent in developing perfect synergy between your code and your contract you would still find that the limitations of the basic standards themselves, such as XSD and WSDL, could easily do you in. For example, the XML Schema model presents severe limitations in terms of composability compared with most programming languages data structures. This is often reflected in non-optimal translations between XML Schema structures and programming data structures. Similarly, WSDL 1.0 and 2.0 are both too abstract for describing services that can be interpreted by Web Services frameworks in a consistent way.

There's a lot of debate in the Web Service community around whether to use a contract-first versus a code-first approach to develop Web Services. One of the common arguments in favor of a contract-first approach is that it facilitates interoperability. Whether that's arguably true, the reality is that just a few mortals know WSDL and XSD well enough to design solid service contracts. Given the complexities of both standards developers often end up designing non-optimal WSDLs and XSDs that are translated into poor service implementations. On the other hand, a code-first approach is more familiar to developers but can produce contracts that aren't interoperable.

Best Practice Recommendation
Some of the most successful Web Service implementations have been designed using a hybrid approach that combines the agility of a code-first approach with the flexibility of a XSD/WSDL-first approach. Following these technique developers can leverage their existing skills on a particular development platform to guarantee an optimal service implementation while the WSDL-XSD experts verify that the contract is suited to meeting the interoperability needs. Figure 1 illustrates this approach.

Multi-Transport Services
SOAP, WSDL, and the different WS-* protocols are transport-agnostic specifications. Theoretically it's possible to host the same service using multiple transports such as HTTP, TCP, JMS, etc. Although this feature is supported by some of the Web Services technology frameworks on the market such as Windows Communication Foundation (WCF) or Apache Axis, only HTTP has been adopted widely enough to be considered for interoperability scenarios. Another factor to consider when implementing multi-transport services in real-world scenarios is that certain transports require a specific behavior of the service. For instance, a Web Service that uses JMS as a transport probably implements one-way, long-running, and asynchronous operations. That behavior is fundamentally different from a Web Service that uses HTTP as a transport on which it makes sense to implement atomic operations using different multiple exchange patterns. Hosting the same Web Services using JMS and HTTP makes little or no sense in most of the scenarios.


More Stories By Jesus Rodriguez

Jesus Rodriguez is a co-founder and CEO of KidoZen, an enterprise mobile-first platform as a service redefining the future of enterprise mobile solutions. He is also the co-founder to Tellago, an award-winning professional services firm focused on big enterprise software trends. Under his leadership, KidoZen and Tellago have been recognized as an innovator in the areas of enterprise software and solutions achieving important awards like the Inc 500, Stevie Awards’ American and International Business Awards.

A software scientist by background, Jesus is an internationally recognized speaker and author with contributions that include hundreds of articles and sessions at industry conferences. He serves as an advisor to several software companies such as Microsoft and Oracle, sits at the board of different technology companies. Jesus is a prolific blogger on all subjects related to software technology and entrepreneurship. You can gain valuable insight on business and software technology through his blogs at http://jrodthoughts.com and http://weblogs.asp.net/gsusx .

More Stories By Javier Mariscal

Javier Mariscal is the President and Founder of TwoConnect, Inc, a highly renowned consulting and systems integration company based in Miami, Florida with subsidiary offices in New York City, and San Francisco. After nearly 15 years, Javier is still mostly responsible for guaranteeing that TwoConnect’s innovative integration solutions deliver real and immediate results to its clients. As an author and frequent speaker on SOA and related technologies, Javier constantly reaffirms the need for “practical SOA” which focuses not on pushing a brand or a platform but on delivering immediate business rewards. Under his leadership, TwoConnect has been the first to market with multiple SOA related products and solutions such as the Web Services Enhancements 3.0 Adapter for Microsoft BizTalk Server and the SQL Server Service Broker Enhancements, both currently in production at companies worldwide. In 2006, TwoConnect announced a new line of products and services under its AdapterWorx brand, which has been hugely successful in accelerating its SOA solutions delivered. Following the success of AdapterWorx and a banner year in 2006 in general, Javier was nominated for Entrepreneur of the Year by Hispanic Business Magazine.

Comments (0)

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.


@MicroservicesExpo Stories
All organizations that did not originate this moment have a pre-existing culture as well as legacy technology and processes that can be more or less amenable to DevOps implementation. That organizational culture is influenced by the personalities and management styles of Executive Management, the wider culture in which the organization is situated, and the personalities of key team members at all levels of the organization. This culture and entrenched interests usually throw a wrench in the work...
Don’t go chasing waterfall … development, that is. According to a recent post by Madison Moore on Medium featuring insights from several software delivery industry leaders, waterfall is – while still popular – not the best way to win in the marketplace. With methodologies like Agile, DevOps and Continuous Delivery becoming ever more prominent over the past 15 years or so, waterfall is old news. Or, is it? Moore cites a recent study by Gartner: “According to Gartner’s IT Key Metrics Data report, ...
Many organizations are now looking to DevOps maturity models to gauge their DevOps adoption and compare their maturity to their peers. However, as enterprise organizations rush to adopt DevOps, moving past experimentation to embrace it at scale, they are in danger of falling into the trap that they have fallen into time and time again. Unfortunately, we've seen this movie before, and we know how it ends: badly.
In his session at Cloud Expo, Alan Winters, U.S. Head of Business Development at MobiDev, presented a success story of an entrepreneur who has both suffered through and benefited from offshore development across multiple businesses: The smart choice, or how to select the right offshore development partner Warning signs, or how to minimize chances of making the wrong choice Collaboration, or how to establish the most effective work processes Budget control, or how to maximize project result...
In his keynote at 19th Cloud Expo, Sheng Liang, co-founder and CEO of Rancher Labs, discussed the technological advances and new business opportunities created by the rapid adoption of containers. With the success of Amazon Web Services (AWS) and various open source technologies used to build private clouds, cloud computing has become an essential component of IT strategy. However, users continue to face challenges in implementing clouds, as older technologies evolve and newer ones like Docker c...
For organizations that have amassed large sums of software complexity, taking a microservices approach is the first step toward DevOps and continuous improvement / development. Integrating system-level analysis with microservices makes it easier to change and add functionality to applications at any time without the increase of risk. Before you start big transformation projects or a cloud migration, make sure these changes won’t take down your entire organization.
Without a clear strategy for cost control and an architecture designed with cloud services in mind, costs and operational performance can quickly get out of control. To avoid multiple architectural redesigns requires extensive thought and planning. Boundary (now part of BMC) launched a new public-facing multi-tenant high resolution monitoring service on Amazon AWS two years ago, facing challenges and learning best practices in the early days of the new service.
You often hear the two titles of "DevOps" and "Immutable Infrastructure" used independently. In his session at DevOps Summit, John Willis, Technical Evangelist for Docker, covered the union between the two topics and why this is important. He provided an overview of Immutable Infrastructure then showed how an Immutable Continuous Delivery pipeline can be applied as a best practice for "DevOps." He ended the session with some interesting case study examples.
Both SaaS vendors and SaaS buyers are going “all-in” to hyperscale IaaS platforms such as AWS, which is disrupting the SaaS value proposition. Why should the enterprise SaaS consumer pay for the SaaS service if their data is resident in adjacent AWS S3 buckets? If both SaaS sellers and buyers are using the same cloud tools, automation and pay-per-transaction model offered by IaaS platforms, then why not host the “shrink-wrapped” software in the customers’ cloud? Further, serverless computing, cl...
"We view the cloud not as a specific technology but as a way of doing business and that way of doing business is transforming the way software, infrastructure and services are being delivered to business," explained Matthew Rosen, CEO and Director at Fusion, in this SYS-CON.tv interview at 18th Cloud Expo (http://www.CloudComputingExpo.com), held June 7-9 at the Javits Center in New York City, NY.
Without lifecycle traceability and visibility across the tool chain, stakeholders from Planning-to-Ops have limited insight and answers to who, what, when, why and how across the DevOps lifecycle. This impacts the ability to deliver high quality software at the needed velocity to drive positive business outcomes. In his general session at @DevOpsSummit at 19th Cloud Expo, Eric Robertson, General Manager at CollabNet, will discuss how customers are able to achieve a level of transparency that e...
We all know that end users experience the internet primarily with mobile devices. From an app development perspective, we know that successfully responding to the needs of mobile customers depends on rapid DevOps – failing fast, in short, until the right solution evolves in your customers' relationship to your business. Whether you’re decomposing an SOA monolith, or developing a new application cloud natively, it’s not a question of using microservices - not doing so will be a path to eventual ...
"DivvyCloud as a company set out to help customers automate solutions to the most common cloud problems," noted Jeremy Snyder, VP of Business Development at DivvyCloud, in this SYS-CON.tv interview at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
We all know that end users experience the Internet primarily with mobile devices. From an app development perspective, we know that successfully responding to the needs of mobile customers depends on rapid DevOps – failing fast, in short, until the right solution evolves in your customers' relationship to your business. Whether you’re decomposing an SOA monolith, or developing a new application cloud natively, it’s not a question of using microservices – not doing so will be a path to eventual b...
"This all sounds great. But it's just not realistic." This is what a group of five senior IT executives told me during a workshop I held not long ago. We were working through an exercise on the organizational characteristics necessary to successfully execute a digital transformation, and the group was doing their ‘readout.' The executives loved everything we discussed and agreed that if such an environment existed, it would make transformation much easier. They just didn't believe it was reali...
"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.
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 a lot of 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 reduction in cost ...
Your homes and cars can be automated and self-serviced. Why can't your storage? From simply asking questions to analyze and troubleshoot your infrastructure, to provisioning storage with snapshots, recovery and replication, your wildest sci-fi dream has come true. In his session at @DevOpsSummit at 20th Cloud Expo, Dan Florea, Director of Product Management at Tintri, provided a ChatOps demo where you can talk to your storage and manage it from anywhere, through Slack and similar services with...
"I focus on what we are calling CAST Highlight, which is our SaaS application portfolio analysis tool. It is an extremely lightweight tool that can integrate with pretty much any build process right now," explained Andrew Siegmund, Application Migration Specialist for CAST, 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.
Explosive growth in connected devices. Enormous amounts of data for collection and analysis. Critical use of data for split-second decision making and actionable information. All three are factors in making the Internet of Things a reality. Yet, any one factor would have an IT organization pondering its infrastructure strategy. How should your organization enhance its IT framework to enable an Internet of Things implementation? In his session at @ThingsExpo, James Kirkland, Red Hat's Chief Archi...