July 06, 2008   Sign In |  About ebizQ |  Contact Us |  Join ebizQ Gold Club
Open Source Syndicate This
Print this article    Email this article    Talk Back!    Write to Editor
SOA Governance 101
04/17/2008
By Dave Rosenberg, CEO, Mulesource
SOA represents a brave new world of system design. The business benefits - increased reuse, reduced time to market, and lower total costs of ownership - are often touted by vendors and analysts alike. A major challenge remains that the technical aspects of SOA - WSDLs, schemas, and the like - are often much easier to articulate and implement than the organizational and process methodologies associated with how you actually achieve SOA.

Structure and governance help to guide the people, processes and applications that make SOA successful. As with any emerging society, the participants within an SOA environment need a common governance framework that provides the rules of engagement, in order for everyone to reap the associated benefits.

ADVERTISEMENT
Our Popular Webinars
BPM for Financial Services
Roundtable Discussion: Open Source Market Update
Evolving Security Architectures and SOA for Better Business Collaboration
Getting Started with BPM
Roundtable Discussion: MDM's Role as a Critical Enabler for SOA
More Webinars

As we talk with IT organizations, too often we see them making the same mistakes, pushing forward with the technical aspects of SOA without considering the governance implications. Here are the most common mistakes we run into, and some tips on how you might avoid them:

Mistake 1: Decentralizing common artifacts

When common artifacts such as WSDLs, schemas or configs are scattered in various locations, organizations waste time searching for interfaces and schemas. This is because they lack a central authority for the published service interface, which discourages discovery and reuse across an enterprise.

Solution: A centralized authority

Creating a centralized repository or registry allows others to more easily reuse artifacts and utilize an authority for what services, schemas, and applications are available. It also enables an organization to track not just what is available during design-time, but also what services are running in production. More often, an organization must mandate the use of a registry or repository otherwise it will be ignored and no SOA benefits will be realized.

Mistake 2: Reinventing the wheel

In the typical decentralized IT organization, services and applications are often written again and again to perform the same function. As a result, many different versions of the same artifact are built and integrated, increasing development times and creating a huge maintenance cost burden.

Solution: Collaborate and recycle

The way to avoid falling into this trap is simple. Share requirements and collaborate on building artifacts. Reuse applications, services, and artifacts whenever possible and use a centralized repository or registry to store information, discover existing services, and collaborate on new ones.

Page 1

More Top Stories
Is SOA Management Primed for More Consolidation? Gold Club Protected
AMR Research: The Future of the SOA Market Gold Club Protected
So What the Heck is a Service Anyway? Gold Club Protected
Is Governance the Silver Bullet of Agility? Gold Club Protected
Doing Risk Management Right Gold Club Protected
Understanding SOA Service Life-Cycle Management Gold Club Protected
More Top Stories
Related News
Microsoft and Micro Focus Invest in Enterprise Application Modernization
Oracle Unveils BEA's Role in Product Strategy for Next-Generation Middleware
AmberPoint Launches Systems Integrator Partner Program
More News
Subscribe to our Newsletters
ebizQ Weekly Gold Club Update
Live Webinar Updates
Updates from ebizQ Partners
ebizQ SOA Update
ebizQ BPM Update
ebizQ Security Update
ebizQ BI Update
ebizQ Open Source Software Update
Virtual Show Newsletter
ebizQ Web 2.0 and the Enterprise
Your E-mail Address:
Changing Tires on a Moving Car
Case studies and solutions for governing the continuous evolution of complex SOA systems

Date: Jul 15, 2008
Time: 12:00 PM ET
(16:00 GMT)

REGISTER TODAY!
Roundtable Discussion: MDM's Role as a Critical Enabler for SOA
Date: Jul 16, 2008
Time: 12:00 PM ET
(16:00 GMT)

REGISTER TODAY!
Archived Webinars | Upcoming Webinars
  Three Keys To BI Success: Information Management, Production, And Delivery
If your organization is like the majority of mid-sized to large enterprises, it runs like a wide and disparate set of business intelligence (BI)...Learn More
ebizQ also recommends
 Optimal Service-Parts Management: Part One
 The Geek Gap: Do Suits Care?
 Collaboration and Social Media <i>Taking Stock of Today's Experiences and Tomorrow's Opportunities</i>
 BPM Done Right
 Mitigate Risk with Security Assessments
More White Papers

Marketing Solutions | Feedback | About ebizQ | Unsubscribe | Privacy Policy | Site Map

Live Chat