3

I have been tasked with building a registry/directory of the WCF web services in my organization. My first thought was about using UDDI. However, UDDI doesn't seem to enjoy particularly good press, with some claiming it is dead - see What are some good alternatives to a UDDI registry?

Considering the following:

  • this registry is strictly for business purposes, i.e. we want a list of web services and document their functionality web service
  • discovery is not required, i.e. clients will continue to be pre-configured and any changes to any service will be manually propagated
  • it should be possible to automate publishing to the registry, e.g. as part of the service deployment process

Are there are any good alternatives worth considering?

Community
  • 1
  • 1
Fabio
  • 730
  • 3
  • 10

2 Answers2

1
  • UDDI
  • ebXML
  • WS-Discovery
  • mDNS

If you're in Java-land, JAXR is another location

spy
  • 3,199
  • 1
  • 18
  • 26
0

I would just use a custom SharePoint list.

John Saunders
  • 160,644
  • 26
  • 247
  • 397
  • that only works if you have sharepoint available and you're commited to a specific version, can you know where the farm is, and you know the id of the list and the columns it contains. That's a lot of things you need to know ahead of item. The point of dynamic discovery is that you need to know at least as possible to figure out where the service is. – spy Jun 19 '15 at 10:59
  • Yeah, pity that dynamic discovery didn't become more popular. And SharePoint Foundations is free.And you only need a single URL to find the list and read the metadata _and_ the data. – John Saunders Jun 19 '15 at 13:48