On 5/23/06, Radovan Janecek <[EMAIL PROTECTED]> wrote:
> Are you against using the service registry for governance? Or are you against centralized registry? Or is it just UDDI you don't like?
I don't like UDDI for other (Web-related) reasons, but what I was
taking issue with in this case was the practice of gathering what is
originally decentralized information, and maintaining copies of that
information in some central location (the registry). It doesn't
actually *fix* the problem mentioned (brittle software components),
nor even make it easier to solve, since no new information has been
created by this process. It just makes it more difficult to maintain
the copied information, for all the usual reasons.
> For example, I'm using (centralized) Bugzilla (database of bugs) at Systinet for 'testing governance'. Of course, the Bugzilla itself would give me no value if I hadn't processes and discipline around it. If I had huge engineering organization that would mandate decentralized solution, I would be able to do it somehow - but so what? The same applies to the Registry - instead of bugs you govern service descriptions, service lifecycle, visibility, consumer-provider relationships, policies, and stuff like that.
Right, but that example isn't very applicable to the situation in the
article. If you said that you kept a centralized database of all
comments in your code (separate from your the code itself) then that
would be more analogous... and of course we'd all laugh you off the
list 8-)
Mark.
SPONSORED LINKS
| Computer software | Computer aided design software | Computer job |
| Soa | Service-oriented architecture |
YAHOO! GROUPS LINKS
- Visit your group "service-orientated-architecture" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
