Hi, i work for a retail company, we are starting to make someÃÂ internal software in. NET and of course using WCF to 'connect' applications, we have still a very long way to a SOA architecture but i am doing some deep researching on the path to SOA.
One thing i dont see a good solution is in how to implement some service registry, for human and software access, at this point of my research im not looking for a ESB or some robust and powerfull (and complex) middleware for services architecture, currently i want to publish services with associated documents for human acess and of course for client access, my initial requirement would be given a contract (Interface) determine a service endpoint based on parameters such as network response, debug/production, service quality, transaction support, etc. with this i start looking and of course first go to see UDDI, i use for research Windows Server 2003 and Windows Server 2008 and both gives me UDDI as a component of the OS, so i was happy to there, but i start read some microsoft documentation i began to doubt, the docs are poor for msdn standar, refersÃÂ some requirements in terms of Netscape navigator... supports API v2.0 of UDDI and frm 2005 there is v3....ÃÂ ÃÂ plus trying to use the UDDI wasnt very easy for an IT manager people, i have some gap between WCF services and the UDDI model, not easy to close... doing some more research i
View Complete Post