Question: what constitutes identity in SOA? When can a client consider two services to be identical?
- when they have the same address? - when they have the same type (as in myService ---isInstanceOf---> ShoeOrderProcessor)? - when they have the same description? - unspecified; every SOA style software system must define identity for itself Jan On Nov 6, 2005, at 2:21 AM, JP Morgenthal wrote: > > Here's what I propose: > > A) Loose-coupling - every service is atomic, self-describing, > accessible, declarative, stateless and composite > B) Contracted - All services in an SOA are represented by a contract > that describes its inputs, outputs, access policies, QoS > requirements and > error handling procedures > C) Manageable - all services can be individually managed or managed > as a group > D) Versioned - multiple versions of the same service should be able > to co-exist to maintain backward compatibility in a changing > environment > E) Discoverable - services should be able to be discoverable at time > of execution. > F) Addressable - A service should be able to be uniquely identified > in a network > G) Distributed - Services in an SOA are separated by geographic and > machine boundaries and, therefore, must be good netizen > applications. That > is, they must be developed with the ability to recover from loss of > communications. > H) Point-to-Point - At any point in time one consumer uses one and > only one producer > > ------------------------------------ > Avorcor, Inc. > JP Morgenthal > Managing Partner > [EMAIL PROTECTED] > 12110 Sunset Hills Road, Suite 450 > Reston, VA 20190 > tel: (703) 648-1520 > fax: (703) 648-1523 > mobile: (703) 554-5301 > ------------------------------------ > > -----Original Message----- > From: [email protected] > [mailto:[EMAIL PROTECTED] On Behalf > Of Jan > Algermissen > Sent: Saturday, November 05, 2005 9:03 AM > To: [email protected] > Subject: Re: [service-orientated-architecture] Re: request for > pointers to > relevant information/documentation about SOA/SOC > > >>> >>> documents/publications related to SOA, starting from the basic >>> principles to more complicated stuff. > > I know this has propably been stressed too much, but simply cannot > resist :o) > > > > What are the basic principles of SOA? > > <duck/> > > Jan > > > > > > > > > Yahoo! Groups Links > > > > > > > > > > > > ------------------------ Yahoo! Groups Sponsor -------------------- > ~--> > Get Bzzzy! (real tools to help you find a job). Welcome to the > Sweet Life. > http://us.click.yahoo.com/A77XvD/vlQLAA/TtwFAA/NhFolB/TM > -------------------------------------------------------------------- > ~-> > > > Yahoo! Groups Links > > > > > > ________________________________________________________________________ _______________ Jan Algermissen, Consultant & Programmer http://jalgermissen.com Tugboat Consulting, 'Applying Web technology to enterprise IT' http://www.tugboat.de ------------------------ Yahoo! Groups Sponsor --------------------~--> Get Bzzzy! (real tools to help you find a job). Welcome to the Sweet Life. http://us.click.yahoo.com/A77XvD/vlQLAA/TtwFAA/NhFolB/TM --------------------------------------------------------------------~-> Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
