Mark, what exact problem do you mean? And how the level of decentralization of Service Registry (or, if you prefer, database of available services) relates to this problem?

I understand that articles like this one irritate technical people (including myself) because 90% of the content is just noise and nonsense. But, I still don't understand your point.

Are you against using the service registry for governance? Or are you against centralized registry? Or is it just UDDI you don't like?

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.

Radovan

On 5/23/06, Mark Baker <[EMAIL PROTECTED]> wrote:
Anne - all that you describe there is trivially-decentralizable, so I
maintain, if you do it with UDDI you've got a new problem to deal
with.


On 5/22/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
> Don't pidgeon-hole registry and repository into a system used only for
> discovery.
>
> Registries provide a conduit for multiple runtime systems to share
> management and control information (e.g., policies, SLAs, heuristics, etc).
> Repositories support metadata management, policy management, contract
> management, dependency management, impact analysis, and lots of other
> SDLC/governance activities.
>
> Anne
>
> On 5/22/06, Mark Baker <[EMAIL PROTECTED]> wrote:
> >
> > > This is where a UDDI Registry/Repository comes into its own,
> >
> > Ouch!
> >
> > No, the problem is that if you change implementations and stuff
> > breaks, then you're not loosely coupled.  "Become more loosely
> > coupled" is the answer to that problem.
> >
> > If you centralize trivially-decentralizable functionality like
> > discovery to solve a loose coupling problem, then you've now got two
> > problems.
> >
> > Mark.
> >
> >
> >
> >
> >
> >
> >
> > Yahoo! Groups Links

> >
> >
> >
> >
> >
> >
> >
> >
>
>





SPONSORED LINKS
Computer software Computer aided design software Computer job
Soa Service-oriented architecture


YAHOO! GROUPS LINKS






--
Radovan Janecek
http://radovanjanecek.net/blog

SPONSORED LINKS
Computer software Computer aided design software Computer job
Soa Service-oriented architecture


YAHOO! GROUPS LINKS




Reply via email to