Editing Web Services Discovery (section)

==History of UDDI==
UDDI was written in August 2000, at a time when the authors had a vision of a world in which consumers of web services would be linked up with providers through a public or private dynamic brokerage system. In this vision, anyone needing a service, such as credit card [[authentication]], would go to their service broker and select a service supporting the desired SOAP (or other) service interface, and meeting other criteria. In such a world, the publicly operated UDDI node or broker would be critical for everyone. For the consumer, public or open brokers would only return services listed for public discovery by others, while for a service producer, getting a good placement in the brokerage—by relying on metadata of authoritative index categories—would be critical for effective placement.

UDDI was included in the [[Web Services Interoperability]] (WS-I) standard as a central pillar of web services infrastructure, and the UDDI specifications supported a publicly accessible Universal Business Registry in which a naming system was built around the UDDI-driven service broker.

UDDI has not been as widely adopted as its designers had hoped.<ref>[https://www.innoq.com/blog/st/2010/03/uddi-r.i.p./] UDDI R.I.P</ref> [[IBM]], [[Microsoft]], and [[SAP (company)|SAP]] announced they were closing their public UDDI nodes in January 2006.<ref>{{Cite web|url=http://soa.sys-con.com/node/164624|title=Microsoft, IBM, SAP To Discontinue UDDI Web Services Registry Effort &#124; Microservices Expo|website=soa.sys-con.com}}</ref> The group defining UDDI, the OASIS Universal Description, Discovery, and Integration (UDDI) Specification Technical Committee voted to complete its work in late 2007 and has been closed.<ref>[http://lists.oasis-open.org/archives/uddi-spec/200807/msg00000.html] Message announcing closure of Technical Committee</ref>
In September 2010, Microsoft announced they were removing UDDI services from future versions of the [[Windows Server]] operating system. Instead, this capability would be moved to [[BizTalk Server]].<ref>{{Cite web|url=https://docs.microsoft.com/en-us/windows/win32/win7appqual/removal-of-uddi-services-from-server-os|title=Removal of UDDI Services from Server Operating System - Win32 apps|website=docs.microsoft.com|date=27 April 2021 }}</ref>  In 2013, Microsoft further announced the deprecation of UDDI Services in BizTalk Server.<ref>{{Cite web|url=https://docs.microsoft.com/en-us/biztalk/install-and-config-guides/what-s-new-in-biztalk-server-2013-and-2013-r2|title=What's New in BizTalk Server 2013 and 2013 R2 - BizTalk Server|website=docs.microsoft.com|date=24 May 2022 }}</ref> In 2016, Microsoft removed UDDI Services from BizTalk Server.<ref>{{Cite web|url=https://docs.microsoft.com/en-us/biztalk/install-and-config-guides/what-s-new-in-biztalk-server-2016|title=What's New in BizTalk Server 2016 - BizTalk Server|website=docs.microsoft.com|date=7 July 2021 }}</ref>

UDDI systems are most commonly found inside companies, where they are used to dynamically bind client systems to implementations.<ref>{{Cite thesis|url=https://etheses.bham.ac.uk/id/eprint/6350/|title=Value- and debt-aware selection and composition in cloud-based service-oriented architectures using real options|first=Esra Fawaz Ahmad|last=Alzaghoul|date=December 18, 2015|publisher=University of Birmingham |type=d_ph |via=etheses.bham.ac.uk}}</ref> However, much of the search [[metadata]] permitted in UDDI is not used for this relatively simple role.