--- In [email protected], "Steve Jones" <jones.ste...@...> wrote: > > > Capability != service, a service should manage multiple > capabilities.
I used "capability" to simply avoid using service. > But yes it could be more complex. Worst presentation I ever saw was > from a major package vendor who boldly said that they would be > replacing their current 8 modules in the company with "over 3,000 > services" and didn't quite understand why the CIO nearly exploded > with concern. Yikes! An extreme case, not doubt. But illustrates my concern. How can we be sure that an SO approach reduces complexity? At one level it seems likely to increase complexity. A general rule of thumb: as flexibility increases so too does complexity. Obviously a generalization but one to be aware of, no? "SOA reduces complexity" is not something I'd be comfortable with as a general statement. -Rob
