I disagree on this point. Loose coupling has to do with semantic dependency. Just because something is addressable, named, discoverable, and distributed, that doesn't mean it doesn't have a tight, brittle dependency on another service or processing entity. I don't see any direct linkage between loose coupling and SLA management. And while there is a linkage between loose coupling and contracted, the linkage goes only one way (e.g., You can't do loose coupling without contracts, but you can have contracts without loose coupling).
Also note that this is a list of "principles", not of features and benefits. As principles, these are characteristics that developers are trying to achieve when designing services.
Anne
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
SPONSORED LINKS
Computer monitoring software Computer and internet software Free computer monitoring software
YAHOO! GROUPS LINKS
- Visit your group "service-orientated-architecture " on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
| Service-oriented architecture | Computer monitoring software | Computer and internet software |
| Free computer monitoring software |
YAHOO! GROUPS LINKS
- Visit your group "service-orientated-architecture" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
