Service Oriented Architectures

Service Oriented Architectures

Postby Cuchulainn » Thu Sep 20, 2007 10:26 pm

http://en.wikipedia.org/wiki/Service-or ... chitecture



Compared to earlier attempts to promote software reuse via modularity of functions, or by use of predefined groups of functions known as classes, SOA's atomic level objects are 100 to 1,000 times larger, and are associated by an application designer or engineer using orchestration. In the process of orchestration, relatively large chunks of software functionality (services) are associated in a non-hierarchical arrangement (in contrast to a class's hierarchies) by a software engineer, or process engineer, using a special software tool which contains an exhaustive list of all of the services, their characteristics, and a means to record the designer's choices which the designer can manage and the software system can consume and use at run-time.



User avatar
Cuchulainn
 
Posts: 669
Joined: Mon Dec 18, 2006 2:48 pm
Location: Amsterdam, the Netherlands

Postby Cuchulainn » Thu Sep 20, 2007 10:33 pm

The following guiding principles define the ground rules for development, maintenance, and usage of the SOA[6]



Reuse, granularity, modularity, composability, componentization, and interoperability

Compliance to standards (both common and industry-specific)

Services identification and categorization, provisioning and delivery, and monitoring and tracking

User avatar
Cuchulainn
 
Posts: 669
Joined: Mon Dec 18, 2006 2:48 pm
Location: Amsterdam, the Netherlands

Postby zhouxing » Mon Jun 29, 2009 2:39 pm

SOA is very good. If you have intuitive understanding of it, you will love it :-)
zhouxing
 
Posts: 4
Joined: Mon Jun 29, 2009 12:20 am

Postby Cuchulainn » Wed Jul 01, 2009 9:44 am

User avatar
Cuchulainn
 
Posts: 669
Joined: Mon Dec 18, 2006 2:48 pm
Location: Amsterdam, the Netherlands


Return to Design Patterns

Who is online

Users browsing this forum: No registered users and 1 guest

cron