meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
user:hevi:service_oriented_communications [2009/11/20 15:28]
hevi
user:hevi:service_oriented_communications [2011/09/02 12:05] (current)
Line 32: Line 32:
  
 SOA Design Principles. primitive [[SOA]]. SOA Design Principles. primitive [[SOA]].
-  - Loose Coupling – Services maintain a relationship that minimizes dependencies +  - [[Loose Coupling]] – Services maintain a relationship that minimizes dependencies 
-  - Service Contract – Services ​adhere to a communications agreement defined by one or more service descriptions and related documents+  - Service Contract – [[Service]]s ​adhere to a communications agreement defined by one or more service descriptions and related documents
   - Autonomy – Services have control over the logic they encapsulate   - Autonomy – Services have control over the logic they encapsulate
   - Abstraction – Beyond what is described in the service contract, services hide logic from the outside world   - Abstraction – Beyond what is described in the service contract, services hide logic from the outside world
Line 40: Line 40:
   - Statelessness – Services minimize retaining information specific to an activity   - Statelessness – Services minimize retaining information specific to an activity
   - Discoverability – Services are designed to be outwardly descriptive so they can be found and accessed via discovery mechanisms   - Discoverability – Services are designed to be outwardly descriptive so they can be found and accessed via discovery mechanisms
 +
 Contemporary SOA Contemporary SOA