Web Services Governance is a Marriage of Two Technologies

Web services governance in this scenario (see diagram) is shared by both parties: the registry (or system of record) and the SOA management solution. What's elegant about this marriage of technologies is that there's a nice overlap of capabilities. There are no hard lines that would demand inconvenient handoffs -- leaving the customer flailing about for support.

The Need for Web Services Governance Technology

An example which demonstrates the need to rely on the joint capabilities of a registry and a SOA management system simultaneously would be a case where a company has a new policy indicating that "all customer data must be encrypted". This policy is certainly something that would need to be set up in design-time and architectural time Because it's an architectural idea. But it's also something that needs to be facilitated in production -- to ensure it's being executed. And if it's not happening, IT needs to be able to acquire feedback, as discussed in a previous tutorial.

Web Services Governance Technology Reduces Risk

If a network is hosting a service that IT previously didn't know about -- a service that is trafficking unsecured customer data, then the company is likely in violation of industry or government regulations -- which instantly puts the organization at risk: of fines, revenue loss, prosecution and more. Service-related feedback (whether manually or automatically discovered), entered into the design- and runtime environments, allows the Systinet Registry and Actional SOA management tools to deliver the flexibility everyone desires from SOA, but with minimized risk.

For More Information

Learn more about why using a SOA registry and SOA management together is an ideal Web services governance solution. Download the free webinar, Optimizing the SOA Lifecycle from Design Time to Runtime with Comprehensive Governance.