A perhaps more useful implementation of UDDI involves installing an internal UDDI site at a large organization such as a telecom. A telecom could easily have hundreds of internal and external Web Services available to a large audience. By using UDDI, the corporations IT department takes advantage of a standard that many people are familiar with. In this situation, a new developer or consultant in the organization knows almost immediately where to find information about the services available in the organization.
If the repository is kept up to date, it could save an IT department money by reducing training and documentation costs.
Imagine that you’re a consultant at a large corporation and you’ve been charged with bringing data on legacy systems, such as an IBM mainframe, to the public Web site.
Instead of hunting down an administrator, finding documentation, or having to create your own documentation, you simply go to the internal UDDI site. You search for the type of Web Service you’re looking for, connect your Web page to this Web Service, and then deploy your new Web application.
Remember that a UDDI site only works if the people creating and using Web Services keep it up to date. All the advantages of UDDI are lost if users are not disciplined about disseminating the information.