Comments on The Grey Lines: Service Reuse and Agility

Edwin, Good questions. Reuse should be pretty eas...

2010-02-25T11:10:24.112-05:00

Edwin,
Good questions. Reuse should be pretty easy assuming you are tracking usage via your governance implementation. Agility is a bit more difficult.

First thing is to define what agility means to your org. Is it an IT measurement for how fast it can respond to changes or how fast it can make changes and/or implement new stuff? Or is it defined as how responsive the

good tips,i've never find my self designing servic...

2010-02-25T05:29:10.692-05:00

good tips,i've never find my self designing services,but i am much more involved on SOA Governance measurement and metrics development and one of the measures that was identified was percentage of service reuse and agility. what are the measures that one can look at when measuring service reuse and agility.

Edwin

Aloha to you Aloha!!,Global types are a pretty big...

2009-03-31T19:16:00.000-04:00

Aloha to you Aloha!!,
Global types are a pretty big subject which are probably needing another post all together.

Where as the low level primitive types will cause you grief at the technology level, global types will cause you grief at the service and business level.

It's amazing with all the SOA talk that has gone on, the area of XML schema design has received very little

The concept around basic datatypes ( string boolea...

2009-03-31T13:09:00.000-04:00

The concept around basic datatypes ( string boolean etc) is fine. But we are using Global data Types which are consistent with the organisation. Do you have any experience with that? Was curious if you faced any issues etc

Hi Steve,Great comments, sounds like we have had s...

2009-03-11T18:09:00.000-04:00

Hi Steve,
Great comments, sounds like we have had similar experiences in the trenches of the service world.

Mark

Good tips Mark. It is obvious that you are a "man ...

2009-03-11T09:30:00.000-04:00

Good tips Mark. It is obvious that you are a "man in the trenches." I agree with all your points, learning the hard way with experience.

One thing I do is separate my service interfaces by style of interaction. We have information retrieval (a.k.a. Data Services) that are separate from our action oriented services (a.k.a. Transaction Services). I have found that the rate of change is