You are hereSOA
Here are the definition of some of the key terms related to SOA Governance.
List down some of the roles and responsibilities in a SOA Implementation:
The following SOA roles and responsibilities have been found to be a worthwhile starting point for consideration:
A service is a well-defined unit of work performed by a component and packaged for easy access. The idea is to implement the functionality exactly once, do it well, and then make it widely accessible. The extra effort involved in initially creating the service (and there is always extra effort) is paid for by avoiding future development costs either through the direct reuse of the service or by isolating the service user from ongoing internal implementation changes within the service.
Design Pattern is a way of describing a solution to a problem.
Christopher Alexander says, "Each pattern describes a problem which occurs over and over again in the environment, and then describes the core of the solution to that problem, in such a way that you can use the solution a million times over, without ever doing it the same way twice.
Here are some names of SOA Architectural Patterns.
The notion of refinement is an important one in architecture. The architect's job is to identify the components of the system and specify the components in sufficient detail that any proper refinement of the architecture will lead to a successful implementation. The architect adds only enough detail to be confident that if different design teams implement (refine) different components, the components will still collaborate properly to bring the business processes to life.
Here I am planning to list down all the Resources I come across on SOA. I am sure it will be helpful to me as I explore SOA more. Hope you find it useful too.
Here is a list of Videos and Webcasts available on SOA. I plan to collect this from different sources and list it down here for everyone's use. Do visit this page back for the growing list.
SOA is an architectural approach to creating systems built from autonomous services. With SOA, integration becomes forethought rather than afterthought.This book introduces a set of architectural capabilities, and explores them in subsequent chapters.
SOA Practititioners Guide PDF, Part I, II and III