Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><strong>Public UDDI is indeed dead, but it managed to survive in private registries inside enterprises.</strong></p> <blockquote> <p>A UDDI registry's functional purpose is the representation of data and metadata about Web services. A registry, either for use on a public network or within an organization's internal infrastructure, offers a standards-based mechanism to classify, catalog, and manage Web services, so that they can be discovered and consumed by other applications. </p> <ul> <li><a href="http://uddi.org/pubs/uddi-tech-wp.pdf" rel="noreferrer">http://uddi.org/pubs/uddi-tech-wp.pdf</a></li> </ul> </blockquote> <p>This isn't bad for a definition and purpose, unfortunately it was applied at the web level. </p> <p>UDDI was supposed to be the "yellow pages" of web services. If you wanted to find a web service providing a certain functionality, you would look it up inside the UDDI. </p> <p>The idea was to use a standard (universal) mechanism for online interaction between SOA businesses components. You then dynamically looked up services, connected to them and do business automatically. And the decision for choosing between similar services was supposed to happen based on the metadata found in the UBR (all of it inside a very complex model which discouraged adoption) with no way of checking if the service actually did what you were expecting it to do.</p> <p>But bringing every interaction to a common ground was impossible because businesses are highly heterogeneous. And businesses still revolves around people, human activity and human decisions. </p> <p>Business are conducted between partners that choose to make business with each other only after thorough analysis and negotiation, before finally striking a business deal and agree on all terms and conditions. Only then their infrastructures are connected. And at this point the UDDI definition does start to make sense, because within the enterprise UDDI allows you to:</p> <ul> <li>relocate services without any of the clients failing;</li> <li>supports load balancing;</li> <li>improves efficiency by reducing manual interventions within the infrastructure;</li> <li>manage redundancy (if one service fails the clients will search for another service providing the same functionality);</li> <li>etc</li> </ul> <p>.. but all of this within a confined set of predetermined services who's functionality is well established and agreed upon.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload