Welcome!

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

Related Topics: Microservices Expo

Microservices Expo: Article

SOA World Editorial — Ready, Fire, Aim

We all do it from time to time - forget something or do something incredibly stupid

We all do it from time to time - forget something, get it out of sequence - and experience that annoying feeling that we've just done something incredibly stupid. I usually arrive at the dry cleaners to pick up my clothes, only to realize I'd left the next batch behind. Fortunately, it's not a long drive. But it's usually because I'm in a rush, trying to accomplish multiple things. If I slowed down just a second, I might accomplish more.

Service-oriented architecture faces similar challenges. In particular, the concept of architecture seems to be the one that gets left behind, or thrown out with the bathwater. Yet it's really the architecture part of SOA that enables it to provide the highest return on investment from an implementation.

I've gone on and on about architecture - what it is, why it's important, how to do it - in numerous issues of SOAWorld Magazine. Yet in many cases I still see organizations with the same old problem: "Ready, Fire, Aim!"

This is partially due to the challenges of providing an ROI on technology that is in many cases considered pure infrastructure. It's an old problem. Remember when you didn't have Internet access on the job, or it was a slow dial-up? Making the case that Internet access was important to the employee base was difficult - especially if you had to justify a move from limited dial-up to universal broadband. Sure, we all thought it was a good idea, but what was the monetary value to the organization? It was much easier to quantize the costs than to enumerate the benefits and place a value on them. And yet, eventually, the overwhelming majority of organizations have moved to broadband.

SOA is very similar. It's nearly impossible to quantify the business benefit of an SOA migration. The benefits are clear in an environment with multiple applications and strong integration needs, but at the same time, it's still a challenge to pin a number to them. Will an SOA increase productivity? Will it reduce maintenance costs? How much? How long will it take to reduce those costs? Yes, the questions sound like you're being pecked to death by the accounting duck, but they are also real issues. Bottom line in today's economy is that an SOA migration needs clear ROI justification.

Which is a challenge. Instead, organizations are using the grassroots approach to SOA. New projects have to include SOA. Old applications that are being renovated are encouraged to adopt SOA aspects. And slowly, through the process of accretion, an SOA arises from the muck.

The challenge is that by building SOA a system at a time, we're concentrating on the wrong end of the process and ignoring the role of architecture. We're building the same old silo - perhaps a little more open, but not a whole lot better than the system as it existed before the introduction of an SOA element.

This is why architecture is important. Without it, services arise at all levels of granularity. Processes have to be cobbled together haphazardly. Service rationalization and consolidation does not take place, so duplicate or nearly duplicate services exist long after they should have been rationalized to a single service. The retirement of redundant systems is delayed long after it could be accomplished.

Although it's rare to be able to fund a complete SOA overhaul, a best practice that should be followed is to set up an SOA Governance and Architecture group. The group doesn't need to boil the ocean in order to solve every problem, but as systems are reworked or introduced they can be the coordination point for rationalizing the enterprise to a set of identified services. They can also serve as the mediator in various negotiations around design and guide the IT organization as to how best to achieve an SOA given multiple options.

In the same way that I need someone to remind me to take my dry cleaning with me, we all need to have Architecture as part of SOA. Now where did I put that cleaning ticket?

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