Microservices Expo Authors: Liz McMillan, Pat Romanski, Carmen Gonzalez, Elizabeth White, Jason Bloomberg

Related Topics: IBM Cloud, Microservices Expo, Recurring Revenue

IBM Cloud: Article

Eight Gates to Great SOA Governance

The key to instituting a successful governance process

While there's certainly no shortage of opinions on the future of SOA, the reality is that SOA is very much alive. The core principles of what SOA can do in terms of cost savings, increased productivity, and the virtual elimination of information and application silos won't go away. However, the term "SOA" will likely evolve into something else, as it becomes more and more a part of the computing landscape.

What the recent dialog has sparked is an opportunity to redefine SOA and rethink our approach to building, managing, and extending the infrastructure so that it's truly aligned with business goals. One of the most efficient and cost-effective ways to do this - as evidenced by hundreds of successful SOA deployments - is through governance.

Yet simply applying governance without a clear understanding of business goals is counter-productive. The key is to identify where, when, and at what points in the SOA journey that governance is most critical.

Based on the collective experience of organizations of all sizes, following all or part of the "eight gates" outlined below has proven to be key to instituting a successful governance process.

Serving as a blueprint to guide architects on the governance process, these gates are designed to complement each other while addressing the increasingly complex requirements associated with the software development lifecycle. You can equate the gates to a production line approach where the creation of a product begins with the most fundamental step and incrementally undergoes more detailed design and development before being deployed into production.

When it comes to building and deploying an SOA, following the recommendations outlined in these eight gates can be the difference between success and failure.

Gate One: Define the Business Requirements
During this stage, many organizations unknowingly create unrealistic expectations or confusion among their business and IT leaders. At gate one, the focus should be on determining business goals and requirements and clearly articulating how technology can support the execution of those goals.

Besides mapping out the business goals, related requirements and key performance indicators, it's imperative to build consensus among key stakeholders with agreed-on metrics and benchmarks that will validate and/or redirect the efforts at each stage.

Further - and while it may sound obvious to some - it's important to leave the acronyms and jargon behind and speak only in terms of business value and financial benefits such as return on investment, total cost of ownership, time to market, etc. Some of the most successful SOA project leaders hardly used the term SOA in their explanation to business leaders.

Gate Two: Build Consistency into the Solution Architecture
For larger organizations with various IT efforts underway, it's inevitable that different development teams will have different approaches to solving business challenges. While this can contribute to a library of best practices, it more often leads to confusion, redundant efforts, and increased costs associated with duplicate software licenses and allocation of staff. Not to mention the affects of increased complexity that reduces the infrastructure's reliability, stability, and interoperability.

Building on the lessons from gate one that focused on defining the business requirements, gate two is associated with clearly articulating and agreeing on the standards, policies, and best practices that must be adhered to as the services are being built. These standards include reference architectures, platform standards, software usage standards, and reuse policies.

More Stories By Jaimin Patel

Jaimin Patel is director of new business development at WebLayers and has more than 18 years of IT industry experience in various roles spanning IT management, software development, and product management. Prior to WebLayers, Jaimin was vice president of network systems and services for Fidelity Investment Systems where he ran multiple enterprise management departments and executed enterprise-wide CIO initiatives.

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
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...
"NetApp's vision is how we help organizations manage data - delivering the right data in the right place, in the right time, to the people who need it, and doing it agnostic to what the platform is," explained Josh Atwell, Developer Advocate for NetApp, in this SYS-CON.tv interview at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
The Jevons Paradox suggests that when technological advances increase efficiency of a resource, it results in an overall increase in consumption. Writing on the increased use of coal as a result of technological improvements, 19th-century economist William Stanley Jevons found that these improvements led to the development of new ways to utilize coal. In his session at 19th Cloud Expo, Mark Thiele, Chief Strategy Officer for Apcera, compared the Jevons Paradox to modern-day enterprise IT, examin...
In his session at 20th Cloud Expo, Mike Johnston, an infrastructure engineer at Supergiant.io, discussed how to use Kubernetes to set up 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. H...
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, will discuss why containers should be paired with new architectural practices such as microservices ra...
In his session at 20th Cloud Expo, Scott Davis, CTO of Embotics, discussed how automation can provide the dynamic management required to cost-effectively deliver microservices and container solutions at scale. He also discussed how flexible automation is the key to effectively bridging and seamlessly coordinating both IT and developer needs for component orchestration across disparate clouds – an increasingly important requirement at today’s multi-cloud enterprise.
The Software Defined Data Center (SDDC), which enables organizations to seamlessly run in a hybrid cloud model (public + private cloud), is here to stay. IDC estimates that the software-defined networking market will be valued at $3.7 billion by 2016. Security is a key component and benefit of the SDDC, and offers an opportunity to build security 'from the ground up' and weave it into the environment from day one. In his session at 16th Cloud Expo, Reuven Harrison, CTO and Co-Founder of Tufin, ...
DevOps is often described as a combination of technology and culture. Without both, DevOps isn't complete. However, applying the culture to outdated technology is a recipe for disaster; as response times grow and connections between teams are delayed by technology, the culture will die. A Nutanix Enterprise Cloud has many benefits that provide the needed base for a true DevOps paradigm. In their Day 3 Keynote at 20th Cloud Expo, Chris Brown, a Solutions Marketing Manager at Nutanix, and Mark Lav...
Many organizations are now looking to DevOps maturity models to gauge their DevOps adoption and compare their maturity to their peers. However, as enterprise organizations rush to adopt DevOps, moving past experimentation to embrace it at scale, they are in danger of falling into the trap that they have fallen into time and time again. Unfortunately, we've seen this movie before, and we know how it ends: badly.
TCP (Transmission Control Protocol) is a common and reliable transmission protocol on the Internet. TCP was introduced in the 70s by Stanford University for US Defense to establish connectivity between distributed systems to maintain a backup of defense information. At the time, TCP was introduced to communicate amongst a selected set of devices for a smaller dataset over shorter distances. As the Internet evolved, however, the number of applications and users, and the types of data accessed and...