Welcome!

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

Related Topics: Microservices Expo

Microservices Expo: Article

SOA Web Services Editorial — Development Blues

Nothing is more enlightening for a technologist than to observe development in progress

Nothing is more enlightening for a technologist than to observe development in progress. We're faced constantly with a bewildering array of choices and tools. We see specifications on paper that then become something completely different when we actually get to see them implemented in actual software that we then configure to meet our needs, or at least we hope.

I've been spending some time working with a team doing an SOA proof-of-concept test and it's reminded me of what an open book the world of SOA is, and how few pages have really been written in it. The migration of ideas to specifications, and then their transformation within software is a strange process.

Given that SOA has so many optional parts, it's not hard to understand how difficult it is for a vendor to put together a product that actually guides developers in the development process. In what may be the biggest irony of SOA, the technology that we use to enable interoperability is really a set of standalone software, distinct and separate from one another.

If you think about it, there is a logical progression of development for SOA, but because so much of SOA is about enabling communications with existing software rather than creating new services from scratch, there is no one typical development path. This is unfortunate, because the current situation is very similar to a least-common denominator approach, one where each aspect of development is distinct and isolated. You have one console for creating UDDI registry entries, another tool for creating WSDL and other documents, yet another tool for the actual coding of a service, and still another, different place for defining security entitlements. None of which are aware of one another. This makes development a fragmented, disjointed process.

Some may argue that it has to be this way for a toolset to support the broadest range of capabilities. I would agree, but I also think it's possible to create an SOA-focused development tool in the same way that folks like Borland created a Java editor that understood the environments in which it was used. In the same way that code editors today can understand the differences between BEA WebLogic and IBM WebSphere, there is a need for a development environment that understands the various standards as well as the concrete implementations of those standards and how to interface with them to make a development process seamless.

I am well aware this is not as trivial as it sounds. Just keeping an environment in synch with the various levels of specifications is not trivial. Supporting the latest is never enough - think about what would happen if the actual deployment environment is behind in revisions and needs a previous version. Now add to that differing implementations of standards by various vendors and you can begin to imagine the scope and depth of this problem. A good number of vendors have shied away from even contemplating a solution to the issue, preferring to believe there is no solution.

That's a problem, and an opportunity. SOA is too complex to be implemented piecemeal by cobbling together a set of tools. There is a strong need for a product to manage the complexity and variety of the process in a structured fashion. While XML editors such as XML Spy are very good at what they do, what's really needed is a more structured approach to creating services that removes the need to edit XML at all in favor of a more integrated approach that allows the developer to see into the whole process. Simple services are easy enough, but once we start to build complex, composite services that use things like WS Transactions or WS Orchestration, there needs to be a holistic view of the entire process, including the documents and descriptions that go along with service deployment.

This issue focuses on development tools, techniques and practices. We'll show you how to do SOA now, and let you think about how it should be done better in the future.

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