The Fairytale of UDDI Registry and Public Web Services
UDDI was proposed as a solution to publish and search services. UDDI defines data structures relevant to service discovery and a set of APIs to access them. The standard was supported by major software vendors such as IBM, Microsoft and SAP. Although UDDI was claimed to become successful in restricted and controlled environments (there are several implementations of UDDI servers available for the internal use these days), it has not prevailed in the domain of publicly available Web Services (you can read more about shutdown of IBM, Microsoft and SAP public UDDI registries and many articles discussing this topic as old as 2004, just to mention some of them for reference from pluralsight, techtarget or realworldsoa at inforworld).
We are frequently asked by users of seekda Web Services search engine if seekda develops or aims to develop a public UDDI registry. To be more specific what people really mean are UDDI APIs allowing to access seekda in a programmatic way. The short answer is that we are neither doing nor planning to do so in a short term. However at the same time we believe that we can learn a lot from the work done by UDDI designers and creators of public UDDI registries. We do not completely neglect the future possibility of implementing the standardized UDDI APIs (or ebXML registry APIs). Anyway at this stage we do not consider UDDI APIs as a very essential feature which would improve search for public Web Services and the exponential growth of Web of services.
Continue reading “The Fairytale of UDDI Registry and Public Web Services” »
