Welcome!

Microservices Expo Authors: Stackify Blog, Aruna Ravichandran, Dalibor Siroky, Kevin Jackson, PagerDuty Blog

Related Topics: Microservices Expo

Microservices Expo: Article

Business Optimization Through SOA

The role of governance in unlocking SOA business value

Governance is the tail that wags the SOA dog. An organization that deploys Web Services without a solid governance program is headed for serious trouble in terms of reliability, security, and cost.

 While governance is a necessity for any IT endeavor, the open and potentially chaotic nature of SOA makes governance either a showstopper or a magic bullet for success, depending on how it's approached. This article will look at SOA governance from both a technological and business perspective, highlighting the need for a complete governance model - a closed loop that spans design time to runtime, policy definition, enforcement, and audit.

The Goal: Business Optimization through SOA
Encounters with today's endless discussions about Service Oriented Architecture bring to mind the old Hollywood phrase, "Cut to the chase." Forget the endless ruminations on containers, service buses, standards, and IDEs. What are we really talking about when we get granular with Web Services and their attendant minutia? We're talking about money.

SOA is about money, or at least, it should be. An SOA is a long-term technology initiative (it never really ends) that is meant to deliver a return on investment, whether you're investing hard dollars or equivalent resources. A non-profit with volunteer developers is just as much an investor in an SOA as General Motors.

In particular, SOA should be able to deliver on several of its well-hyped promises for business value, including a reduction in overall IT cost, business agility, and a faster application development and integration cycle. At the root of all these potential savings is the concept of software reuse. If a Web Service can be developed once, but reused many times across multiple consuming applications, then many cost reductions fall into place. The need to redevelop a comparable application drops off, and the cycle time for getting the new application up and running will be shorter if there's no development cycle to go through. Reuse also serves agility by enabling rapid extensions of systems into new uses based on dynamic shifts in strategic and operational requirements.

Getting There: A Path of SOA Governance
Reuse, the main driver of financial value from Web Services, is based on the highly flexible nature of Web Services. However, this flexibility is a double-edged phenomenon. The same openness and flexibility can also make Web Services chaotic and unreliable. How can you reach the financial results of reuse with such a potentially out-of-control mechanism?

Though it may seem counterintuitive, the path to the business benefits of SOA, to all that groovy openness and flexibility, leads right through a world of tight governance. The necessity of adopting strict but agile controls as a prerequisite for freedom is reminiscent of the classic Harry Truman line, "If you want to live like a Republican, you better vote for the Democrats." Only when you have a high level of confidence that your Web Services are well-managed, secure, and governed can you be confident that sharing them broadly won't cause more problems than the freedom is worth.

So, let's think old school IT governance and learn to govern our Web Services. SOA governance is a matter of getting your Web Services and overall SOA to behave in the way it's meant to, and preventing it from being misused. It's about control. If you design a Web Service for a specific purpose and set of consumers, you want to have an assurance (and the ability to audit) that it was only used for that purpose and consumer. And, you want it to be available, performing as intended, and secure. The transactions must have integrity, at least to the degree that you specify.

If you can't control your Web Service to this extent, you haven't governed it, and it will inevitably be misused, become unreliable and insecure. The risks of an ungoverned Web Service, and by extension an ungoverned SOA, include performance failures, security breaches, and breakdowns in data integrity. A low-performing, unreliable, and insecure SOA doesn't generate reuse or agility. It's just a costly pain in the neck. Let's not go there.

An SOA governance program delivers you from these risks. A good governance program will include provisions for the security and reliability of Web Services as well as sophisticated methods for controlling the reuse of Web Services. With governance in effect, you can exploit the reuse and agility potential of your Web Services. You can assign usage rights to Web Services to new consumers, confident that they're authorized and authenticated for use. You can meet security and reliability requirements set out for Web Services by the consumers you work with.

For example, if you develop a Web Service, and wish to extend it for reuse with a new business partner, you will likely want to be able to set, enforce, and monitor a service level for that Web Service. And, you'll probably want to establish, enforce, and monitor security policies that benefit both you and the partner, regarding the Web Service. Depending on your industry, you may need to encrypt or digitally sign the SOAP messages and establish an audit log of Web Service use and transactions for non-repudiation.

There are three main levers of SOA governance: policy definition, policy enforcement, and audit. To govern, you must be able to define the rules you expect to have followed. That's policy definition. And, to govern, you must be able to enforce the policies you define. It does little good to define policies if you can't enforce them. That would be like leaving a store unlocked and hoping that customers will have the decency to put money in the till on the honor system. Believe it or not, many IT governance programs rely to a degree on the honor system for policy enforcement. Your SOA doesn't have to be that way.

Finally, to satisfy various stakeholders that defined governance policies have in fact been enforced, you need a high-integrity audit record of what has gone on. Besides being able to audit the actual Web Service transactions, you also need to be able to show an audit log of the enforcement of the governance policies themselves. For instance, if you want to show a stakeholder that you specified that all SOAP message emanating from a specific Web Service must be encrypted, you have to be able to produce a bulletproof audit log of the establishment and enforcement of that policy.

Audit-worthiness is of interest to auditors of both the "capital A" and "small a" variety. There are auditors of various sorts in your company and its partners who need assurance that SOA governance is in place. There are also auditors (Capital A) who review your company's financial statements for the SEC and your internal controls for Sarbanes-Oxley.

It's only with these tight controls that the Web Service begins to have any reuse value. The challenge, of course, is to impose all this control without locking the whole SOA up so tight that it defeats its entire purpose. If you just wanted lockdown, you would have stayed with your existing systems. The trick, therefore, is to automate your SOA governance to the point that these controls are highly automated and seamlessly baked into the Web Service lifecycle itself. This is where the "loop" comes in.

Closing the Loop
Runtime SOA governance, the ability to define, enforce, and audit policies for Web Services at runtime, should be a benchmark of SOA maturity. Any serious enterprise SOA should be well governed at runtime. Of course, that itself is not always so easy, as Web Service endpoints and the "last mile" reaching from Enterprise Service Buses to the Web Services themselves can be out of the reach of many built-in ESB governance packages. Ditto for multi-vendor ESB to ESB mediation. However, assuming you've licked those challenges and adopted sound runtime SOA governance, you must still contend with the "loop."

The loop is the complete lifecycle for a Web Service from design time to runtime. The loop can either be "broken," meaning that you define policies at design time and hope they get enforced at runtime, or "closed," where definition, enforcement, and audit happen seamlessly in one solution. If you have two separate governance systems, one for design time and one for runtime, you might find yourself in a "define and hope" form of SOA governance, which is unsustainable and unreliable. Throw multiple platforms and enterprises into the mix and things can get downright out of control. "Define and hope," or loosely integrated design time and runtime governance systems, inhibit the realization of SOA business value.

The broken loop model of SOA governance carries with it a serious risk, which is the potential for a drop-off in governance between design time and runtime. Though this may not be a huge issue for a small organization, it can be a major problem in security and compliance terms for a large or complex operation. If the governance policies defined for a Web Service at design time can't be assured at runtime, and there's not an audit log, then the governance will be unsound. By extension, all of the reuse and agility you want from that Web Service will be very difficult to realize. At the very least, it will be quite costly to manually supervise the continuity of governance across the broken loop.

If you opt for a "closed loop" approach to SOA governance, you can define policies at design time and automatically enforce them at runtime. Closed loop SOA governance typically leverages the power of UDDI registry and a policy metadata repository that functions across the full life cycle of the Web Service. With a closed loop governance solution, your enforcement of defined policies will be seamlessly auditable from design time through runtime. With a closed loop approach, realizing the business value of SOA comes within reach. You have the ability to reuse Web Services and perform integrative acts of agility but stay confident that the governance policies you need to assure the integrity of your business remain in place.

Conclusion
SOA governance is a critical activity for an enterprise seeking to find the business return on its investment in Web Services. Though it may seem counterintuitive, the best way to find the financial upside in the openness and flexibility of Web Services is to implement tight governance. To work, though, the governance must not be overly restrictive of change. Otherwise, it would defeat the whole purpose of the SOA.

Best practices suggest that a comprehensive SOA governance solution should encompass both design time and runtime. Ideally, the solution should provide a "closed loop" approach that automates and connects the definition of governance policies at design time with their enforcement and audit at runtime. When the loop is closed, then the agility of SOA can take center stage with a minimum of governance overhead but a high level of confidence in reliability and security.

More Stories By Hugh Taylor

Hugh Taylor is the co-author of Understanding Enterprise SOA and Event-Driven Architecture: How SOA Enables the Real-Time Enterprise and the author of The Joy of SOX: Why Sarbanes Oxley and Service-Oriented Architecture May be the Best Thing that Ever Happened to You. He serves as Senior Director of Marketing at Mitratech, a Los Angeles based enterprise software company.

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.


@MicroservicesExpo Stories
How is DevOps going within your organization? If you need some help measuring just how well it is going, we have prepared a list of some key DevOps metrics to track. These metrics can help you understand how your team is doing over time. The word DevOps means different things to different people. Some say it a culture and every vendor in the industry claims that their tools help with DevOps. Depending on how you define DevOps, some of these metrics may matter more or less to you and your team.
For many of us laboring in the fields of digital transformation, 2017 was a year of high-intensity work and high-reward achievement. So we’re looking forward to a little breather over the end-of-year holiday season. But we’re going to have to get right back on the Continuous Delivery bullet train in 2018. Markets move too fast and customer expectations elevate too precipitously for businesses to rest on their laurels. Here’s a DevOps “to-do list” for 2018 that should be priorities for anyone w...
If testing environments are constantly unavailable and affected by outages, release timelines will be affected. You can use three metrics to measure stability events for specific environments and plan around events that will affect your critical path to release.
In a recent post, titled “10 Surprising Facts About Cloud Computing and What It Really Is”, Zac Johnson highlighted some interesting facts about cloud computing in the SMB marketplace: Cloud Computing is up to 40 times more cost-effective for an SMB, compared to running its own IT system. 94% of SMBs have experienced security benefits in the cloud that they didn’t have with their on-premises service
DevOps failure is a touchy subject with some, because DevOps is typically perceived as a way to avoid failure. As a result, when you fail in a DevOps practice, the situation can seem almost hopeless. However, just as a fail-fast business approach, or the “fail and adjust sooner” methodology of Agile often proves, DevOps failures are actually a step in the right direction. They’re the first step toward learning from failures and turning your DevOps practice into one that will lead you toward even...
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...
The goal of Microservices is to improve software delivery speed and increase system safety as scale increases. Microservices being modular these are faster to change and enables an evolutionary architecture where systems can change, as the business needs change. Microservices can scale elastically and by being service oriented can enable APIs natively. Microservices also reduce implementation and release cycle time and enables continuous delivery. This paper provides a logical overview of the Mi...
While walking around the office I happened upon a relatively new employee dragging emails from his inbox into folders. I asked why and was told, “I’m just answering emails and getting stuff off my desk.” An empty inbox may be emotionally satisfying to look at, but in practice, you should never do it. Here’s why. I recently wrote a piece arguing that from a mathematical perspective, Messy Desks Are Perfectly Optimized. While it validated the genius of my friends with messy desks, it also gener...
The next XaaS is CICDaaS. Why? Because CICD saves developers a huge amount of time. CD is an especially great option for projects that require multiple and frequent contributions to be integrated. But… securing CICD best practices is an emerging, essential, yet little understood practice for DevOps teams and their Cloud Service Providers. The only way to get CICD to work in a highly secure environment takes collaboration, patience and persistence. Building CICD in the cloud requires rigorous ar...
The enterprise data storage marketplace is poised to become a battlefield. No longer the quiet backwater of cloud computing services, the focus of this global transition is now going from compute to storage. An overview of recent storage market history is needed to understand why this transition is important. Before 2007 and the birth of the cloud computing market we are witnessing today, the on-premise model hosted in large local data centers dominated enterprise storage. Key marketplace play...
The cloud revolution in enterprises has very clearly crossed the phase of proof-of-concepts into a truly mainstream adoption. One of most popular enterprise-wide initiatives currently going on are “cloud migration” programs of some kind or another. Finding business value for these programs is not hard to fathom – they include hyperelasticity in infrastructure consumption, subscription based models, and agility derived from rapid speed of deployment of applications. These factors will continue to...
Some people are directors, managers, and administrators. Others are disrupters. Eddie Webb (@edwardawebb) is an IT Disrupter for Software Development Platforms at Liberty Mutual and was a presenter at the 2016 All Day DevOps conference. His talk, Organically DevOps: Building Quality and Security into the Software Supply Chain at Liberty Mutual, looked at Liberty Mutual's transformation to Continuous Integration, Continuous Delivery, and DevOps. For a large, heavily regulated industry, this task ...
Following a tradition dating back to 2002 at ZapThink and continuing at Intellyx since 2014, it’s time for Intellyx’s annual predictions for the coming year. If you’re a long-time fan, you know we have a twist to the typical annual prediction post: we actually critique our predictions from the previous year. To make things even more interesting, Charlie and I switch off, judging the other’s predictions. And now that he’s been with Intellyx for more than a year, this Cortex represents my first ...
"Grape Up leverages Cloud Native technologies and helps companies build software using microservices, and work the DevOps agile way. We've been doing digital innovation for the last 12 years," explained Daniel Heckman, of Grape Up in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
The Toyota Production System, a world-renowned production system is based on the "complete elimination of all waste". The "Toyota Way", grounded on continuous improvement dates to the 1860s. The methodology is widely proven to be successful yet there are still industries within and tangential to manufacturing struggling to adopt its core principles: Jidoka: a process should stop when an issue is identified prevents releasing defective products
Defining the term ‘monitoring’ is a difficult task considering the performance space has evolved significantly over the years. Lately, there has been a shift in the monitoring world, sparking a healthy debate regarding the definition and purpose of monitoring, through which a new term has emerged: observability. Some of that debate can be found in blogs by Charity Majors and Cindy Sridharan.
We seem to run this cycle with every new technology that comes along. A good idea with practical applications is born, then both marketers and over-excited users start to declare it is the solution for all or our problems. Compliments of Gartner, we know it generally as “The Hype Cycle”, but each iteration is a little different. 2018’s flavor will be serverless computing, and by 2018, I mean starting now, but going most of next year, you’ll be sick of it. We are already seeing people write such...
It’s “time to move on from DevOps and continuous delivery.” This was the provocative title of a recent article in ZDNet, in which Kelsey Hightower, staff developer advocate at Google Cloud Platform, suggested that “software shops should have put these concepts into action years ago.” Reading articles like this or listening to talks at most DevOps conferences might make you think that we’re entering a post-DevOps world. But vast numbers of organizations still struggle to start and drive transfo...
Let's do a visualization exercise. Imagine it's December 31, 2018, and you're ringing in the New Year with your friends and family. You think back on everything that you accomplished in the last year: your company's revenue is through the roof thanks to the success of your product, and you were promoted to Lead Developer. 2019 is poised to be an even bigger year for your company because you have the tools and insight to scale as quickly as demand requires. You're a happy human, and it's not just...
"Opsani helps the enterprise adopt containers, help them move their infrastructure into this modern world of DevOps, accelerate the delivery of new features into production, and really get them going on the container path," explained Ross Schibler, CEO of Opsani, and Peter Nickolov, CTO of Opsani, in this SYS-CON.tv interview at DevOps Summit at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.