SOA Patterns for Cloud Apps

Get flash to fully experience Pearltrees

Daily adhoc Pattern

SOA Specifications - XML Specs

XSL Vs CSS

SOA Systems Inc. is the sister school to Arcitura Education Inc.

Service Technology Magazine – Resources

"The Importance of Schema Design in SOA"

Introduction XML Schemas are a fundamental part of any XML-based service oriented architecture.

arcitura's Channel

This is the official Arcitura Education Inc. YouTube channel. Arcitura Education Inc. is a leading global provider of progressive, vendor-neutral training and certification programs.

Very Interesting set of videos on SOA, Cloud and Web2.0 by vikasjee Nov 29

Cloud Computing & SOA Connection Points Part 1 of 5 by Thomas Erl

SOA WOA

Three Specialized SOA Design Patterns (Audio)

eCanonical (Extensible Canonical) Schema patterns discussed here, requirement to extend is due to Governance issues with a rigid canonical schema in a large enterprise. by vikasjee Nov 29

The ESB and Related Messaging Patterns (Audio)

Many patterns covered here! Most recommended for beginner level patterns by vikasjee Nov 29

esb architecture for soa

ESB Architecture for SOA is an upcoming book from these authors by vikasjee Nov 29

ESB-oriented architecture: The wrong approach to adopting SOA

http://www.ibm.com/developerworks/webservices/library/ws-soa-esbarch/

Editor's note: Since its publication, Bobby’s article has drawn a lot of interest, and we appreciate the discussion surrounding this article.

Yet to read - seems to be a sort of an anti-pattern! :) by vikasjee Nov 29

Data-Related SOA Design Patterns (Audio)

In software engineering , Canonical Schema is a design pattern , applied within the service-orientation design paradigm , which aims to reduce the need for performing data model [ 1 ] transformation when services [ 2 ] exchange messages that reference the same data model. [ 3 ] [ edit ] Rationale

Canonical schema pattern

"This design pattern is fully supported by the application of the Standardized Service Contract design principle. The Standardized Service Contract design principle advocates that the service contracts be based on standardized data models. This is achieved by performing an analysis of the service inventory blueprint[7] in order to find out the commonly occurring business documents that are exchanged between services. These business documents are then modeled in a standardized manner. For example, in case of web services, the business documents are modeled as XML schemas. Once a standardized data representation layer exists in a service inventory, different service contracts can make use of the same data models if they need to exchange the same business documents. This eliminates the need for any data model transformation and reduces the processing overhead associated with the data model transformation. It also increases the reusability potential of a service as now the service can be." by vikasjee Nov 29

SOA Patterns - Master Pattern List (Category)

This pearl contains the links to List of Erl's Master Patterns! Explore... by vikasjee Nov 29

OnSOA (Audio + Video)

This site contains lots of videos and audios for SOA Givernance and other topics by vikasjee Nov 29

One of the greatest challenges to carrying out successful SOA projects is in understanding how they should be carried out. Without being able to rely on proven processes and practices, an SOA initiative can turn into a high-risk venture because you simply may not know what to expect. A sound methodology can alleviate this risk by providing a solid foundation from where you can shape a delivery approach that accommodates your goals and requirements while also laying out a path to realizing the benefits of SOA and service-oriented computing. The concepts, processes, and strategies described throughout this site are part of a larger Mainstream SOA Methodology (MSOAM). This methodology is classified as "mainstream" because it really does just provide a set of generic processes and practices that almost always require further customization when incorporated into enterprise environments.

http://serviceorientation.com/index.php/soamethodology/index