Welcome!

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

Related Topics: Microservices Expo, Industrial IoT

Microservices Expo: Article

Editorial: Who's in Charge Here?

If you're old enough, you probably remember the whole episode with Al Haig in the White House

If you're old enough, you probably remember the whole episode with Al Haig in the White House, saying "I'm in charge here" during the period when Reagan was shot. He wasn't really, but it's a good illustration of the concept of confusion, and how different people react to situations. How is this relevant to SOA and Web services? That's an excellent question.

As in a country, an organization implementing SOA needs governance and direction. A simple example may help shine a light on this subject. Let's suppose a division of a large company implements a new security service. Since it's only one division (let's suppose the company has some 50 divisions), they size the service to suit their needs only, and use a small server (maybe two for redundancy). Now, the service is successful, and other divisions start to use it, and so on. Pretty soon the service is up and down like an elevator, and when it is up, the response time is slow.

This illustrates why SOA and Web services need a governance model. Our hypothetical division implements the service for its needs, without considering the bigger picture. However, one of the goals of any SOA is reuse of services and reduction of redundancy, so any service that is successful needs to be designed for reuse. One of the key issues, of course is who pays for it. Why should that single division shoulder the burden of maintenance and equipment for the other 49 divisional needs?

Key concepts in the governance of SOA are cost and control. These two concepts go hand in hand - you can't expect control without expecting to bear the cost of the service. As services become more widespread and usage increases, organizations have to deal with scalability challenges, increased maintenance, and eventually with version-control issues.

Another key challenge is managing the reduction of complexity. Everyone is in favor of reducing the number of different ways to do the same task, as long as you don't touch MY way of doing things. One division of a large corporation surveyed its various applications and identified about 1,000 services. Then they did some comparisons and realized that because of redundancy, they could reduce the service count to fewer than 200. Over 80 percent of their software portfolio was redundant.

When things are that way, they are that way for reasons. Some have to do with specialized systems for special purposes - silos of useful functionality, but limited scope. It's not uncommon for organizations to have three or four or more systems for every real service - in telecommunications for example, it's often the case that they add a new billing system to account for new ways of doing business, rather than wait for changes to the old billing system. These are the problems SOA is designed to solve, but the key issue is governance. You may have heard the expression "You can have it fast, you can have it cheap, or you can have it quickly, but you can't have all three." Somewhere along the line the decision of whether we need it right now, or whether we will stick to a service interface and make changes has to be made. Fortunately, SOA allows us to put a façade in front of any new system to make it conform to the needs of the organization. In this fashion, it allows an organization to add new capabilities quickly, without compromising the overall integrity of the architecture. It also enables reduction of redundancy, without the pain of intermediate states of a system.

In order to achieve this nirvana - this heaven of software and services, there has to be order, and management and governance. The corporate equivalent of Al Haig must stand up, and say "I'm in charge here." However, in order for it to work, he must REALLY be in charge - and stick to his guns long enough to effect change.

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