Ads by TechWords

See your link here
Receive the latest technology news and information.
Application/Web Development
Web Services/SOA
Computerworld Daily News (First Look and Wrap-Up)
Computerworld Blogs Newsletter
The Weekly Top 10
Cloud Computing
View all newsletters




Privacy Policy
 

Is Your SOA Governance Strategy a Disaster Waiting to Happen?

December 15, 2005 12:00 PM ET

Computerworld - As the service-oriented architecture (SOA) environment and marketplace matures, and the topic of SOA governance has moved to the forefront, I have noticed that industry discussion is increasingly centered on the topic of repositories and registries. What role should a repository and/or a registry play in an SOA initiative?

There are those that say "a registry is all you need," while others, including Ron Schmelzer and Jason Bloomberg at ZapThink LLC, argue that a repository with asset management and governance capabilities is just as important as the downstream registry. Before I explore this latter point of view, however, let's define those two terms within SOA.

A registry specifies the set of available deployed services (think of the Windows registry, which is used to manage the list of installed programs and some of their configuration settings), while a repository manages services and their artifacts (work products such as requirements documents, models, test plans and usage guides) through their full architectural, development and deployment life cycles. A repository may store those artifacts directly, or more likely, it may simply reference where those artifacts reside, such as in version-control repositories, requirements management tools and automated test tools.

Repositories are also used to manage the supporting software assets that make up the service implementation -- the myriad components, adapters, legacy application programming interfaces (API), SQL queries and other software elements that support the operations expressed by a Web service's Web Services Description Language document.

With these definitions, it becomes clear why a repository is just as important, if not more important, than a registry. A well-designed repository is where everything comes together on the architectural/development side of SOA, where new services can be proposed and managed through their development life cycle, then exposed to downstream application developers directly within their integrated development environments.

This production/distribution/consumption model is core to SOA, and applies not only to deployed services (the purview of a registry) but also to services under development or architectural review. Certainly, at some point, those produced services will be deployed and exposed through some form of registry function (be it Universal Description, Discovery and Integration, an enterprise service bus's native registry/proxy service, a repository's search and notification APIs or even Lightweight Directory Access Protocol), but thinking that you have solved your service management and governance problem by deploying a registry is like thinking that you've avoided an iceberg by avoiding the part you can see. The registry is 10% of the solution, and the bulk of our needs are "underwater" and invisible to



Jump to comments

Web Services

Additional Resources

Xerox
By using solid ink technology only from Xerox, you could save up to 65% by printing color for the cost of black and white. Enter for a chance to WIN a PhaserTM 8860 network color printer!
Microsoft
Save time and mitigate security risk. Deploy it now.
Sybase
In this white paper, IDC analyzes the role of next-generation mobile enterprise platforms as organizations seek a more strategic deployment of mobile solutions.

Learn the important issues you must consider before starting your next mobility initiative. Get your mobility white paper from IDC now, compliments of Sybase.

White Papers & Webcasts

Maximizing website Return on Information with high-quality search
Download this whitepaper explaining how an investment in site search can boost your earnings while reducing customer service costs.  

Red Hat Continues to Redefine SOA: SIMPLE. OPEN. AFFORDABLE.
SOA enables enterprises to accelerate business execution while driving higher quality and customer satisfaction.  

Open Source Middleware Reference Architecture
A roadmap of open source software capabilities across a diverse set of application requirements.  

Understanding the Business Benefits of an Open Source SOA Platform
Address the serious business challenges that SOA helps to overcome.  

Enterprise Acceleration
Best practices to help IT developers become more productive.  

The Commercialization of ITIL: Lessons Learned
Register for this event today!