Re: [service-orientated-architecture] Re: request for pointers to relevant information/documentation about SOA/SOC

Sun, 06 Nov 2005 22:58:31 -0800

It is interesting that if we haven't even reached a consensus on the principles, benefits, or features of SOA, maybe what the folks in the real world are deploying is DOA!
 
M. R. Pamidi
 
-----Original Message-----
From: JP Morgenthal <[EMAIL PROTECTED]>
To: [email protected]
Sent: Sun, 6 Nov 2005 17:08:52 -0500
Subject: RE: [service-orientated-architecture] Re: request for pointers to relevant information/documentation about SOA/SOC

I'm usually careful to avoid criticism in these types of lists, but I feel it necessary to point out the question was, "What are the principles of SOA, not, "what are the benefits of SOA" and not "what are the features".  If your point was other than to criticize incorrectly, then it was lost in your posting.
 
Avorcor, Inc.
Integrating across the Hinges of Business
 
JP Morgenthal
Managing Partner
Avorcor, Inc.
12110 Sunset Hills Road, Suite 450
Reston, VA 20190
[EMAIL PROTECTED]
tel:
fax:
mobile:
(703) 648-1520
(703) 648-1523
(703) 554-5301
 
Add me to your address book...
Want a signature like this?
 
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Vikas Deolaliker
Sent: Sunday, November 06, 2005 2:19 PM
To: [email protected]
Subject: RE: [service-orientated-architecture] Re: request for pointers to relevant information/documentation about SOA/SOC
 
 
I think the features and benefits of SOA are mixed up in this list.
 
If you have  addressable, named, discoverable and distributed services then you will get the benefits of loosely coupling which include contracts based computing and SLA based management.

Vikas
 
 
From: [email protected] [mailto:[email protected]] On Behalf Of JP Morgenthal
Sent: Saturday, November 05, 2005 5:21 PM
To: [email protected]
Subject: RE: [service-orientated-architecture] Re: request for pointers to relevant information/documentation about SOA/SOC
 

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 LINKS





SPONSORED LINKS
Computer monitoring software Computer and internet software Free computer monitoring software

YAHOO! GROUPS LINKS



Reply via email to