SOA Process is Key Element of Runtime Governance

As we begin to consider the elements runtime governance, it will be necessary to give SOA process some serious thought. The first thing IT managers have to think about, as part of optimizing the SOA Lifecycle, is whether they have captured all the processes and services affected by those processes in the first place.

Next, of course, is policy and process enforcement: e.g., are the right policies and rules in place and operating? And can we enforce the various types of policy: security compliance, Sarbanes-Oxley, HIPAA and so on? Are we able to measure performance?

SOA Process Example

Consider the example of eBay. There are both buyers and sellers, and sellers have the expectation that they'll get paid on time. Just as, when they are delivering goods, there needs to be a level of trust in place with respect to the services. The same is true with SOA -- can it be trusted? Are the services in compliance? And so on.

Good SOA Process Requires Feedback Loop

And then, finally, there is the critical need for feedback. Is Operations getting the data it needs, for example? IT needs to receive this kind of evaluation information in order able to feed it back into the design time and deployment-time environment.

By taking these steps, services can be continually improved. In order to accomplish this goal of continuous improvement, the deployment on the network of a "SOA system of record" -- like the Systinet Registry -- is highly recommended.

For More Information

Learn more about how to enforce SOA process and policy. Register to watch the free webinar, Optimizing the SOA Lifecycle from Design Time to Runtime with Comprehensive SOA Governance from Progress Actional.