Welcome!

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

Related Topics: Microservices Expo

Microservices Expo: Article

Technologists Are No Longer Speaking in Tongues

Standards and interoperability are important in all aspects of our work

Recently I had a chance to do some training in France. I participated in a week of coursework with classmates from all over the world. Some were from France, Spain, Holland, Sweden, and England; others were from even further - the United States and even India. To say the least, it was an eye-opening experience and dramatic evidence that standards and interoperability are important in all aspects of our work as technologists.

Early on in our journey to a service-oriented enterprise we began to realize that for services to work, truly work, they had to be standards based, and, more important, those standards had to trump implementation, so that the services would interoperate as well.

In our training class, English was the language standard for speaking as well as writing. This made sense, as English seemed to be the one language that the class all had in common. The question was posed, for example, since the training was in France, why not have a French version of the class. This seemed a reasonable question to me as well. The answer was that while we were in France, there were many participants who did not speak French. Also, given the international nature of the audience, the question could be posed for many other languages as well. For the purposes of cost containment and the ability to be flexible regarding the content (by only having to update content in one language, not a dozen), a single standard was needed.

This lesson has very similar applications in our work. Not everyone spoke English with equal facility - some were very fluent, while some could understand what was said but had less confidence in their own speaking abilities. Similarly the issues faced by various implementation differences from vendors resulted directly in the creation of the WSI board and its interoperability profile. In our analogy, the basic profile is sort of like a test of spoken and written English that allows users to gauge their ability to communicate successfully with other users. Which is all the basic profile does. It doesn't mean that every word is understood by both parties, merely that they can understand each other. Occasionally we still had to resort to pictures, pointing, or the odd written word to be adequately understood.

I've seen this happen recently due to simple differences in WSDL between the Apache Axis toolkit and one of the commercial ESB products. While the WSDL worked on one side, Apache, it refused to function as is on the bus. Sadly, the developers responsible for this electronic tower of Babel sat right next to one another, so there was no reason at all why they couldn't have communicated with each other and shared the WSDL early enough in the process so that when the integration work was scheduled to happen, it would have gone smoothly.

The coursework did show another amazing aspect of standards and interoperability - how successful people could be when they were able to communicate effectively. During the training exercises, I'd say the average participant spoke at least three languages (I do, but only if you count Latin). Yet we were able to do the work effectively and have very intense discussions around the subject matter, because we all shared one common standard.

In the same fashion, when you consider what the standards that we have now allow us to accomplish, it's pretty remarkable. Ten years ago we had major IT initiatives designed to allow systems to speak with one another (we called it EAI). Sadly, each of those initiatives was in its own language, so at large we still had chaos and no one lingua franca, and no Rosetta stone. Now, thanks to our standards around services, we have achieved interoperability and communication without the need for proprietary solutions and can accomplish the majority of EAI functionality via our existing platforms (with perhaps a few additions such as BPM). Fortunately for all of us, we are no longer speaking in tongues.

More Stories By Sean Rhody

Sean Rhody is the founding-editor (1999) and editor-in-chief of SOA World Magazine. He is a respected industry expert on SOA and Web Services and a consultant with a leading consulting services company. Most recently, Sean served as the tech chair of SOA World Conference & Expo 2007 East.

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.


Microservices Articles
At its core DevOps is all about collaboration. The lines of communication must be opened and it takes some effort to ensure that they stay that way. It’s easy to pay lip service to trends and talk about implementing new methodologies, but without action, real benefits cannot be realized. Success requires planning, advocates empowered to effect change, and, of course, the right tooling. To bring about a cultural shift it’s important to share challenges. In simple terms, ensuring that everyone k...
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...
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...
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...
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...
Kubernetes is a new and revolutionary open-sourced system for managing containers across multiple hosts in a cluster. Ansible is a simple IT automation tool for just about any requirement for reproducible environments. In his session at @DevOpsSummit at 18th Cloud Expo, Patrick Galbraith, a principal engineer at HPE, will discuss how to build a fully functional Kubernetes cluster on a number of virtual machines or bare-metal hosts. Also included will be a brief demonstration of running a Galer...
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...
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....
"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.
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...