Governance is indeed a key activity for any architectural approach. It is simply over emphasized when talking about SOA, IMO. Some vendors put their governance tools first when describing their offerrings, ahead of the tools to create services and provide service communication. That's a mistake, IMO.
Reducing redundancy is a reasonable goal. But redundancy in and of itself isn't always bad and at times is actually the right solution. -Rob --- In [email protected], "Adwait Ullal" <[EMAIL PROTECTED]> wrote: > > Rob: > > Strong governance is what will make SOA succeed ... frankly, do you > want each project each defining redundant services and the ones who > come along later scratch their heads to figure out which is the > right one? > > > - Adwait > > -- > Adwait Ullal > > e: mailto:[EMAIL PROTECTED] > w: http://www.adwait.com > l: http://www.linkedin.com/in/adwait > j: http://finance.groups.yahoo.com/group/AdwaitsDotNetJobs
