I have struggled to define a "service" in the first place.. What is a service? We all know SOA and WS are not the same... Must a service be machine discoverable? Must it follow WS*? How decoupled and atomic should the services be? how important are service life cycle management, service operations management aspects?
Then there are questions specific to quintessential SOA characteristics.... What do you think at the minimum should be followed? Is service registry a must? Do you need to define a Common Message Format? Should the architecture support the capability to compose and orchestrate services? is a BPM layer essential? is a Service Bus needed ? how important is service virtualization? Which standards to be followed? without having clear answers to many questions questions such as above we can not unambiguously define SOA. On Thu, Jun 5, 2008 at 10:41 PM, Rob Eamon <[EMAIL PROTECTED]> wrote: > +1 > > -Rob > > --- In > service-orientated-architecture@yahoogroups.com<service-orientated-architecture%40yahoogroups.com>, > Michael Poulin > <[EMAIL PROTECTED]> wrote: > > > > I would disagree with "üA service-oriented architecture is > essentially a collection of services"; it is not an architecture. > > > > - Michael > > >
