Related link: http://www.oasis-open.org/news/oasis_news_02_03_05.php
My reaction to UDDI from a technical standpoint, which I’ve heard echoed by many is that it’s ludicrously complex for a spec that just defines a resource directory framework, and it reinvents wheels that no one in their right mind should be venturing to reinvent.
My reaction to UDDI from a commerce standpoint, which I’ve heard echoed by many is that the white pages/yellow pages analogy simply doesn’t fly. People in real life use these books as the most cursory index to find vendors, and in the end they use a lot of other, very specialized inquiries to determine whether a particular vendor is truly a compatible trade partner. Why do Web services consumers need an over-elaborated infrastructure for accessing all sorts of Web services details when in the end they’ll still have to pick up the phone and make the usual, specialized inquiries?
Clearly some people don’t share this skepticism, since progress has continued on UDDI, but honestly, this surprises me. I wonder who really does see the value in UDDI, and to what extent they have begun to realize the potential value. My bemused reaction to UDDI might just be an aspect of the general phenomenon I’ve noted that Web services have miraculously ceased to intersect my professional life. Perhaps we just don’t see what we don’t like. Well, if so, today is presumably a good day for folks with different tastes from mine.
Do you use UDDI in practice? Does UDDI 3.0 provide anything that makes the practical difference?