Welcome!

Related Topics: Microservices Expo

Microservices Expo: Article

SOA Governance Best Practices – Architectural, Organizational, and SDLC Implications

Taking the management of services to the next level

Influencing SOA Behavior
Determining and shaping the behavior patterns that will sustain an SOA effort through time is often the work of change management specialists. However, it is easier to conceptualize the role of behavior in SOA if we examine the intersection of major influences on organizational and individual behavior. Some of these influences are the following:

  • Corporate culture
  • Major decision-making processes
  • Budgeting processes
  • Incentives and penalty structures
  • Compensation linkages to corporate goals and mantras
  • Portfolio management processes
  • Architecture process (definition, acquisition, implementation)
  • Architecture practice (solutions development)
  • Corporate performance metrics, such as return on invested capital (ROIC), revenue and market share growth, cost controls, etc.
  • Promotion and advancement criteria
All of these factors influence behavior of organizations and individuals within an enterprise. In the context of an SOA, however, there are a few key factors that determine how effective an SOA can be without fundamental changes to the organization and processes of an organization. To understand these essential factors, we must locate the "center of gravity" of an SOA. Understanding certain key organizational and process relationships will help with the organization of SOA governance, the design of SOA governance processes, as well as understanding the behavior and incentive models that may be required in order to implement SOA governance. For example, the relationship of the budgeting process to project execution and implementation helps determine how effectively budgeting oversight impacts the resulting architecture of IT systems. Without proper budget-to-project alignment, teams will be inclined to build project-centric services that don't necessarily fit the broader needs of the organization's SOA. The relationship of the acquisition/procurement process to enterprise architecture is another key relationship that has a tremendous impact on the resulting architecture of an organization. Does the acquisition process reflect the goals and standards of the EA organization? If not, how can it be changed to better reflect it?

Another critical relationship is the relationship of EA to project or solution architecture - in other words, connecting architecture via governance to downstream activities (more on this in the next section of this article). If there is a disconnection between enterprise architecture and the architecture that is designed at the project level, then there is the possibility of a disjointed architecture.

These important relationships all point to how sociopolitical forces and organizational forces converge to either facilitate or hinder SOA governance. There are no easy answers to these challenges. However, understanding how these organizational tensions either help or hinder SOA governance will point to a path to implementing appropriate organizational institutions and processes to achieve SOA governance objectives.

Production/Distribution/Consumption: Separation of Concerns Within SOA Governance
SOA, in conjunction with other loosely coupled architectural approaches, forces IT organizations to recognize that teams producing services are not likely to be the consumers of those services. Unlike traditional application development, SOA is built upon the premise that a set of services can be employed within a wide range of applications. In other words, SOAs depend upon the separation of the production and consumption concerns within the IT organization, and a distribution vehicle that allows service producers and consumers to communicate and collaborate with each other. Let's define these production, distribution, and consumption concerns with a bit more detail:

  • Production: Identification of and governance over the development and maintenance of existing and newly defined candidate reusable services
  • Distribution: Publication of those services for widespread dissemination to potential service consumers
  • Consumption: Discovery of and governance over the appropriate use of services within application development projects
While it may be technically feasible to execute the responsibilities within these concerns through manually defined and managed procedures, the reality is that for IT organizations of any size to build out a successful SOA, both political/organizational issues such as those discussed in the previous section, and appropriate tooling such as a services repository/registry that automates both service governance and service distribution are essential. The following sections of this article highlight how a services repository/registry can be employed to support key best practices within the production/distribution/consumption life cycle inherent within SOA.

Production Best Practice: Pragmatic Service Definition
Services within an SOA cannot be developed in a "bottom-up," ad hoc manner. Bottom-up development of services is inherently driven by immediate project needs - how do I solve this specific problem with a specific implementation (often driven by the influence of existing applications and their behaviors masquerading as true business requirements). What happens when an organization defines and implements its services with this mindset? The service layer simply becomes YALOT (yet another layer of technology) - more spaghetti code of a different form that didn't improve our business process flexibility, but simply implemented a monolithic application in a different technology.

However services also cannot be defined solely in a "top-down" manner. Top-down business process analysis left to its own devices leads to either "analysis paralysis" - continual refinement of a model hoping to reach perfection (which never comes), or "Big-Bang" projects - trying to define and implement everything at once, usually with disastrous consequences (most typically a combination of "death march" projects and cost and schedule overruns).

Ultimately, what organizations need to make progress in SOA is to develop a coarse-grained business model driven by key business processes (not all of them, but only a representative set of high-priority processes to begin with). Architects and business analysts should collaborate to build this model using those processes to extract and define a normalized set of functions, then grouping those functions together based on behavioral affinity (read components and interfaces for those of you who are UML centric) as a strawman set of initial target service definitions.

At this point, we have a useful framework for the "real work" - detailed analysis, design, and implementation of the services we need for our current set of prioritized projects. Based on business process (and project) prioritization, we identify the needed services from our business reference model and formalize the service definition for these prioritized services. Ideally, each service should be driven by the requirements extracted from at least two separate processes - designing a service based on a single use case is very likely to result in a fragile and narrowly defined service that will not be flexible enough to meet our next set of prioritized projects. Our formalization efforts are likely to result in modifications to our business architecture - which is just fine! We can iteratively enhance our architecture as we make progress towards service implementation.

Production Best Practice:
Recommended Service SDLC Governance/Review Checkpoints
Now that we have our first set of services defined, we need to build and deliver them. Developing services within an SOA (i.e., for purposes of reuse across multiple applications) usually requires more of the production team than a single-use component, module, or object. In order for a service to be considered reusable, it must be maintainable, discoverable, and consumable. Maintainability introduces such concepts as version control (which we will address in more detail later in this article), models and other design documentation, and requirements traceability (why was the asset implemented in this way from a technical and business perspective). Discoverability forces us to consider how we help potential consumers of this asset find the asset in a timely fashion - via keywords, domain taxonomies, and mapping to models, for example. Consumability involves looking at the asset from the point of view of the downstream project planning to use the asset: Is there a user guide, a well-documented API, sample client code, and other artifact available to help the user rapidly understand how to apply this asset to the project at hand? Are dependencies on other assets (and to prior versions of this asset) specified and easily navigated?

More Stories By Brent Carlson

Brent Carlson is vice president of technology and cofounder of LogicLibrary, a provider of software development asset (SDA) management tools. He is the coauthor of two books: San Francisco Design Patterns: Blueprints for Business Software (with James Carey and Tim Graser) and Framework Process Patterns: Lessons Learned Developing Application Frameworks (with James Carey). He also holds 16 software patents, with eight more currently under evaluation.

More Stories By Eric Marks

Eric Marks is founder, president, and CEO of AgilePath Corporation, a service-oriented architecture (SOA) and Web services consulting firm based in Newburyport, MA. Marks is a software and technology veteran with 18 years of experience with firms including PricewaterhouseCoopers, Cambridge Technology Partners, Novell, Electronic Data Systems, StreamServe, Ontos, and Square D/Schneider Electric.

Comments (2) View Comments

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.


Most Recent Comments
robertmorschel 10/10/12 03:57:00 AM EDT

In my experience SOA needs to begin with a single, skilled team that can define evolving standards and processes in an agile manner, before being let loose on the enterprise; and even then, only if the enterprise has an established and effective centralised governance function that would be able to enforce SOA policies across multiple teams.

Robert

Gary Smith - SOA Network Architect 02/22/06 11:51:19 AM EST

Excellent. This puts governance into perspective.
All the hype around SOA appliances and governance shouldn't have you running out and putting these devices on your network until you understand what governance is all about.

GES

Latest Stories
Cognitive Computing is becoming the foundation for a new generation of solutions that have the potential to transform business. Unlike traditional approaches to building solutions, a cognitive computing approach allows the data to help determine the way applications are designed. This contrasts with conventional software development that begins with defining logic based on the current way a business operates. In her session at 18th Cloud Expo, Judith S. Hurwitz, President and CEO of Hurwitz & ...
As someone who has been dedicated to automation and Application Release Automation (ARA) technology for almost six years now, one of the most common questions I get asked regards Platform-as-a-Service (PaaS). Specifically, people want to know whether release automation is still needed when a PaaS is in place, and why. Isn't that what a PaaS provides? A solution to the deployment and runtime challenges of an application? Why would anyone using a PaaS then need an automation engine with workflow ...
SYS-CON Events announced today that Catchpoint Systems, Inc., a provider of innovative web and infrastructure monitoring solutions, has been named “Silver Sponsor” of SYS-CON's DevOps Summit at 18th Cloud Expo New York, which will take place June 7-9, 2016, at the Javits Center in New York City, NY. Catchpoint is a leading Digital Performance Analytics company that provides unparalleled insight into customer-critical services to help consistently deliver an amazing customer experience. Designed...
The cloud competition for database hosts is fierce. How do you evaluate a cloud provider for your database platform? In his session at 18th Cloud Expo, Chris Presley, a Solutions Architect at Pythian, will give users a checklist of considerations when choosing a provider. Chris Presley is a Solutions Architect at Pythian. He loves order – making him a premier Microsoft SQL Server expert. Not only has he programmed and administered SQL Server, but he has also shared his expertise and passion w...
With the proliferation of both SQL and NoSQL databases, organizations can now target specific fit-for-purpose database tools for their different application needs regarding scalability, ease of use, ACID support, etc. Platform as a Service offerings make this even easier now, enabling developers to roll out their own database infrastructure in minutes with minimal management overhead. However, this same amount of flexibility also comes with the challenges of picking the right tool, on the right ...
SYS-CON Events announced today that FalconStor Software® Inc., a 15-year innovator of software-defined storage solutions, will exhibit at SYS-CON's 18th International Cloud Expo®, which will take place on June 7-9, 2016, at the Javits Center in New York City, NY. FalconStor Software®, Inc. (NASDAQ: FALC) is a leading software-defined storage company offering a converged, hardware-agnostic, software-defined storage and data services platform. Its flagship solution FreeStor®, utilizes a horizonta...
SYS-CON Events announced today that Interoute, owner-operator of one of Europe's largest networks and a global cloud services platform, has been named “Bronze Sponsor” of SYS-CON's 18th Cloud Expo, which will take place on June 7-9, 2015 at the Javits Center in New York, New York. Interoute is the owner-operator of one of Europe's largest networks and a global cloud services platform which encompasses 12 data centers, 14 virtual data centers and 31 colocation centers, with connections to 195 ad...
SYS-CON Events announced today that (ISC)²® (“ISC-squared”) will exhibit at SYS-CON's 18th International Cloud Expo®, which will take place on June 7-9, 2016, at the Javits Center in New York City, NY. Two leading non-profits focused on cloud and information security, (ISC)² and Cloud Security Alliance (CSA), developed the Certified Cloud Security Professional (CCSP) certification to address the increased demand for cloud security expertise due to rapid growth in cloud. Recently named “The Next...
The Art of DevOps provides a fun overview to help teams understand DevOps. Written in the style of the famous 6th century Chinese manuscript “The Art of War,” this eBook describes DevOps in the form of a mission to continuously deliver assets to the operational battlegrounds safely, securely, and quickly. It’s a fun read with valuable insights.
SYS-CON Events announced today that Alert Logic, Inc., the leading provider of Security-as-a-Service solutions for the cloud, will exhibit at SYS-CON's 18th International Cloud Expo®, which will take place on June 7-9, 2016, at the Javits Center in New York City, NY. Alert Logic, Inc., provides Security-as-a-Service for on-premises, cloud, and hybrid infrastructures, delivering deep security insight and continuous protection for customers at a lower cost than traditional security solutions. Ful...
The Quantified Economy represents the total global addressable market (TAM) for IoT that, according to a recent IDC report, will grow to an unprecedented $1.3 trillion by 2019. With this the third wave of the Internet-global proliferation of connected devices, appliances and sensors is poised to take off in 2016. In his session at @ThingsExpo, David McLauchlan, CEO and co-founder of Buddy Platform, will discuss how the ability to access and analyze the massive volume of streaming data from mil...
Join us at Cloud Expo | @ThingsExpo 2016 – June 7-9 at the Javits Center in New York City and November 1-3 at the Santa Clara Convention Center in Santa Clara, CA – and deliver your unique message in a way that is striking and unforgettable by taking advantage of SYS-CON's unmatched high-impact, result-driven event / media packages.
SYS-CON Events announced today that Commvault, a global leader in enterprise data protection and information management, has been named “Bronze Sponsor” of SYS-CON's 18th International Cloud Expo, which will take place on June 7–9, 2016, at the Javits Center in New York City, NY, and the 19th International Cloud Expo, which will take place on November 1–3, 2016, at the Santa Clara Convention Center in Santa Clara, CA. Commvault is a leading provider of data protection and information management...
WebSocket is effectively a persistent and fat pipe that is compatible with a standard web infrastructure; a "TCP for the Web." If you think of WebSocket in this light, there are other more hugely interesting applications of WebSocket than just simply sending data to a browser. In his session at 18th Cloud Expo, Frank Greco, Director of Technology for Kaazing Corporation, will compare other modern web connectivity methods such as HTTP/2, HTTP Streaming, Server-Sent Events and new W3C event APIs ...
With an estimated 50 billion devices connected to the Internet by 2020, several industries will begin to expand their capabilities for retaining end point data at the edge to better utilize the range of data types and sheer volume of M2M data generated by the Internet of Things. In his session at @ThingsExpo, Don DeLoach, CEO and President of Infobright, will discuss the infrastructures businesses will need to implement to handle this explosion of data by providing specific use cases for filte...