The patterns contained within this section are primarily logical and SOA specific, and secondarily integration/interoperability specific.
Each pattern solves a specific problem, and in most cases there is no direct duplication within separate patterns that will solve the same problem in all cases. There is always a level of variance.
Each pattern is constructed with a series of logical components. A logical component can be physically implemented with one or more physical components, and can comprise of one or more pieces of technology.
Similarly, the separation between components is a logical one; therefore two logical components can be physically implemented with one or more physical components.
There is therefore another level of re-use beyond the scope of this section that ensures logical patterns are reused and physical patterns of implementation are also likewise reused.
Each pattern considers a standard set of architectural statements and non-functional requirements. Where the pattern deviates from these (usually requiring additional non-functional requirements) then these will be explicitly highlighted within the pattern
The following pattern and sub patterns have been identified:
· Request Reply Method
o Basic Request-Reply (Asynchronous)
o Request-Reply (with ownership transfer in reply)
o Request-Reply (Synchronous consumer)
o Request-Reply (Decoupled reply)