Registry is hot, hot, hot
A few days ago, my blogmate Britton reported on Sun's new registry, which will be incorporated into the Java Enterprise System 4 server middleware stack, to be released this fall.
Today, both SOA Software and Systinet announced new offerings employing UDDI, which is becoming the most commonly accepted registry standard.
What's all the hubbub about registries? Most companies still only have a handful of Web services in operation, and therefore don't need this capability yet. As the number of Web services grow, and companies begin to look at orchestrating these services into a service-oriented architecture, a registry becomes vital for storing and discovering available services, and linking them to policies.
The latest Evans Data Web services/SOA survey shows that at this time, few companies (15%) have implemented working registries for their Web services, but this number is expected to more than quadruple over the next 18 months. That's huge stuff.
SOA Software's Service Manager v 3.0 is built around an enterprise-class UDDIv3 registry. Service Manager version 3.0 adds registry-based dashboard functionality, service endpoint discovery, auto-management, extensive real-time charting and a JSR168 portal framework for the user interface. The SOA Software Service Manager uses a central UDDIv3 registry as a policy store to abstract developers from the complexity of implementing enterprise security and management policies. SOA Software says its UDDIv3-compliant registry is the first product to integrate service discovery with policy and performance management.
Systinet announced it is shipping Systinet Registry 6.0, and Systinet Policy Manager, a new product that offers an extensible, standards-based policy framework for achieving quality and consistency of SOA services. Systinet also announced the expansion of the Systinet product family to include SOA contract management and impact management solutions, coupled with information management capabilities to store and administer key SOA assets.