UDDI

Fowler on Registries: Something wiki this way comes

Object expert, refactoring maven and all around software process guru Martin Fowler took a look at the notion of registries recently, particularly the notion of automated registry service look up. Martin Fowler is an eminent technologist - and like the old broker E.F. Hutton, when Martin Fowlder talks, people listen. Continued »

HP builds ‘culture of governance’ for SOA

HP solidifies leadership in SOA governance with Systinet 3.0, which now covers services lifecycle, business process, and IT service management, writes analyst Dana Gardner in his blog this week.

“The newest market leading Systinet UDDI registry forms the cockpit for managing not only services, but with the newly added Business Process Execution Language (BPEL) support, takes the helm for business processes, too,” Gardner writes. “HP plans to further push the envelope on a master management value even further into IT operations and IT Service Management, as well as a PPM role with the registry.”

The addition of a configuration management database (CMDB) sets the stage for a wider “culture of governance” to emerge in enterprises, Kelly Emo, SOA product marketing manager at HP Software, tells Gardner. 

Gardner also points to a comprehensive assessment of HP’s governance products and strategies by fellow analyst Brad Shimmin posted on the Current Analysis Website.

In SOA provides a test for QA, HP finds, SearchSOA covered HPs expansion of governance to cover quality assurance. And in an earlier article, HP integrates design and runtime SOA governance, SearchSOA covered the design time / runtime integration in Systinet.

What is SOA quality?

I was talking with Wayne Ariola, Parasoft’s vice president of strategy and corporate development, last week about the concept of SOA quality. Parasoft’s been using the term “SOA quality” as part of the latest rollout of its SOAtest product, which now is able to query UDDI registries so that WSDL verification tests can be performed at the time they’re published.

Quality is a key element in software development and it should go without saying that the more business that gets pumped through Web services, the more important it will be to have a good QA process in place for those services. Noting that “lack of central visibility” is normal in the classic software development lifecyle, Ariola listed what he thinks are key elements in that SOA quality process.

1. SOA necessitates centralization, a role played by the registry/repository. He argued that stovepipes become inevitable without it.

2. A health check needs to be performed to make sure the asset meets the requirements. Among the potential requirements, he highlighted defining the asset’s consistency and the boundaries for its reuse.

3. You need a convenient way to emulate the service. Taking down a component could cause unintended chaos once it’s being leveraged in multiple places. Testing and changes are best handled in the virtual arena in order to avoid that trap.

4. If a component or service is going to reused, the testing expectations need to be made readily available so that different orchestration scenarios can be vetted. In general the testing environment should be as open and accessible as possible.
5. Make sure you fully and accurately define your SLAs, future users of that service will need to understand the true behavior expectations behind it.

6. Be prepared to do some sort of compliance monitoring in order to make sure your services are being properly used.

REST-based SOA registry tilts at status quo

Last week WSO2 released a REST-based SOA registry, joining Mulesource, which released a REST-based SOA registry in January. Together they’re doing something we haven’t seen a lot of in the SOA space over the past few years: they’re innovating.

So much energy has been poured into establishing standards, building out distinct product markets and fleshing out platforms that it’s been a while since we’ve seen much in the way of innovation. Early in this decade the ESB, the services registry, Web services management software and XML networking hardware pushed the IT envelope. They gave users a way to combine applications in a whole new way. Suddenly component assembly was on the table and loosely coupled, autonomous, stateless, composable, reusable services moved from theory to reality.

The REST-based registry isn’t likely to create that sort of paradigm shift, but it does shake up a marketplace that may be getting a bit complacent. Both of these releases are open source and both try to support the service-oriented concept of discoverability without using the UDDI standard. You might be asking, isn’t SOA supposed to be standards-based? Well, yes, it is, but that doesn’t mean that UDDI has to be one of those standards. REST is built on the HTTP standard. It also opens up the question of how can we better enable the princples of service orientation?

I’m not implying WSO2 and Mulesource have found a better way to build a registry, UDDI may still be the gold standard as far as that’s concerned, but they have opened up the subject for debate by attacking discoverability in a new way. They also might be setting the table for the next wave of innovation in SOA. Going back to a December podcast with Forrester Research’s John Rymer, the area of dynamic business applications begs for real-time innovation. Perhaps Microsoft’s Oslo initiative will break ground in model-driven design. IBM may be unveiling its REST-based Project Zero this spring.

Wherever the innovation comes from, we need to remember that it will come. We’ve been conditioned to think of SOA as a set of products and standards that popped up seven years ago, but what it really entails is an approach to technology that will allow you to best incorporate the next wave of innovation … and the one after that … and the one after that. These REST-based registries may be the precursors of advances to come.