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

Related Topics: Microservices Expo

Microservices Expo: Article

SOA Web Services Journal - U Don't Deploy It

Few years ago the whole paradigm was associated with with three concepts - SOAP, WSDL, and UDDI

A few years ago, when Web services started out as a buzzword in the enterprise, the whole paradigm was associated with (and still is) associated with three concepts - SOAP, WSDL, and UDDI. Now, when enterprises are putting Web services into production, you will most likely see two out of the three stakes being driven into the ground, but I have yet to see any real adoption of the "dynamic" part of any Web services implementation. Web services are taking root as a very feasible platform for achieving service orientation (not the only platform, mind you), but none of the clients that I have interacted with have any plan to adopt a UDDI-based service registry in the near or long term.

W3C defines a Web service as "a software system identified by a URI, whose public interfaces and bindings are defined and described using XML. Its definition can be discovered by other software systems. These systems may then interact with the Web service in a manner prescribed in its definition using XML-based messages conveyed over Internet protocols." Ironically, the definition does not mention WSDL as the mandated standard for defining and describing the Web service, SOAP as the XML-based message format, or UDDI as the means of "discovering the definition." The only things mandated by the definition is the usage of XML. However, as we know, the standard Web Services Architecture specification assumes SOA, WSDL, and UDDI. The definition and protocol aspects are definitely standardized and being deployed in enterprise applications. However, the discovery aspect still remains a pie in the sky as far as its actual application in the enterprise is concerned.

Web services is a platform for achieving SOA. In order to have reusable services, a component/service repository is a very valuable artifact. However, a public repository that can be used by multiple parties to locate universally available services across distributed locations is still a bit of an overkill in the industry today. UDDI is not necessary for categorizing services. Dynamic discovery and binding are very interesting concepts, until they are actually applied to the way businesses today, and in the foreseeable future, will interact with other businesses.

While the conceptualization, development, deployment, and maintenance of ubiquitous yellow pages is inherently complex, I don't think that is the crux of the problem. The bottom line is that you actually need a viable business model to apply the technology too. Think of our evolution from RPC to CORBA, to RMI (in Java) to Web services. Dynamic invocation has always had the "coolness" factor to it, but has never really found a home in prevalent business models. A few years back when all of us were drinking the Kool-Aid and dreaming about public marketplaces where participants of all levels could participate in a transaction, the whole concept of multi-party, multi-transactional architectures didn't really take off. This was not a failing in technology. It was a failing in the application of viable technology to a non-existent business model. How could parties conducting serious trade put their trust in companies who were here today, but may be gone tomorrow?

UDDI seems to in a similar situation. We have a long way to go before transactions, based on a random search, can be conducted without a formally established trust relationship between two parties. In the end, transactions are conducted between a consumer and a supplier, and these two parties establish relationships well in advance before exchanging goods.

On a different note, if you are a looking for a good book that discusses Web services from several perspectives, check out Perspectives on Web Services by Zimmerman, Tomlinson, and Peuser. A review is available on my blog http://ajitsagar.javadevelopersjournal.com.

More Stories By Ajit Sagar

Ajit Sagar is Associate VP, Digital Transformation Practice at Infosys Limited. A seasoned IT executive with 20+ years experience across various facts of the industry including consulting, business development, architecture and design he is architecture consulting and delivery lead for Infosys's Digital Transformation practice. He was also the Founding Editor of XML Journal and Chief Editor of Java Developer's Journal.

Comments (1)

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...