Migration of a Chosen Architectural Pattern to Service Oriented ...

Migration of a Chosen Architectural Pattern to Service Oriented ... Migration of a Chosen Architectural Pattern to Service Oriented ...

12.07.2015 Views

Chapter 4. Service Oriented Architecture 90pattern), design of a single component (typical design pattern) or maybe designof a process (process pattern)(see section 3.1.1). The distinction grows in importancewhen architectural knowledge is taken into consideration. ArchitecturalKnowledge is meant to describe an architecture and rationale behind decisionmade during architecture designing [9]. The decisions do not refer only to rationaleof fine-grained components but also to a “big picture” – system architecture.Architecture requires more detailed studies, due to a large-scale impact on system.This subsection describes SOA architectural patterns in following manner..1. SOA patterns– presents a problem with SOA architectural patterns andpresents results of pattern investigation.2. The target architecture – presents the target architecture that is a result ofcombination of patterns found in section 4.6.14.6.1 SOA patternsThe book “SOA –Design Patterns” [32] is the largest and the most completesource of pattern in SOA domain[54]. Patterns presented in the book belong todesign patterns, but their descriptions question this adherence. The problem risesfrom definition of pattern and design pattern used by T.Erl in this book.According to T.Erl pattern [32]“provides a proven solution to a common problemindividually documented in a consistent format and usually as part of a largercollection” what corresponds to the definition of pattern presented in section 3.1.1.Design pattern is defined as follows [32]: “Patterns in the IT world that revolvearound the design of automated systems are referred to as design patterns.”.Thisdefinition can be also applied to other types of patterns. All the pattern describedin section 3.1.1 “revolve” around design of automated system, not only designpatterns.SOA patterns are described also in“Patterns: ServiceOriented Architectureand Web Services”[30] but they refer to Enterprise Application Integration. Integrationis out scope of this thesis.Selection of architectural patternsThe target architecture will be build on architectural patterns. Usage of the book“SOA –Design Patterns” [32] as a source of architectural patterns requires furtherstudies.Analysis of patterns presented by T. Erl (see [32]) results in division of presentedpattern into four categories. The categories are following

Chapter 4. Service Oriented Architecture 911. Architectural Patterns – describe general solution for a whole architecture ora part of architecture. Those patterns refer to structure and communicationwithin the system.2. Design Patterns – provide solution for a fine-grained problems that has alocal impact on the architecture3. Process patterns – describe patterns for processes that should be applied inorder to gain particular outcome.4. SOA Concepts – describe issues that already are part of Service OrientedArchitecture5. Technical Issues – describe both Design and Architectural patterns whichare build-in exiting frameworks and supported by external technologies.Table 4.1 presents summary of pattern assigned to particular categories.Pattern TypeAmountArchitectural 14Design 28Process 12Technology issue 9SOA concept 10Total 73Table 4.1: Summary of pattern typesExamples of pattern that were not classified as architectural (see table 4.2 forsummary):1. Canonical Expression –assumes up-front analysis in order to standardisenaming conventions, which is later applied to service contracts. A goodexample of Canonical Expression is CRUD.Motivation: Canonical Expression was classified as a Process pattern, becauseit defines a process – analysis.2. Service Encapsulation –defines a service as a containing logic entity. Thelogic can be encapsulated in a new service as well as become a part of anexisting service.Motivation: Encapsulation of logic in a service is a basic concept ofSOA,therefore there is nothing what could be considered as a pattern. SeeService Definition 4.2.1

Chapter 4. <strong>Service</strong> <strong>Oriented</strong> Architecture 90pattern), design <strong>of</strong> a single component (typical design pattern) or maybe design<strong>of</strong> a process (process pattern)(see section 3.1.1). The distinction grows in importancewhen architectural knowledge is taken in<strong>to</strong> consideration. <strong>Architectural</strong>Knowledge is meant <strong>to</strong> describe an architecture and rationale behind decisionmade during architecture designing [9]. The decisions do not refer only <strong>to</strong> rationale<strong>of</strong> fine-grained components but also <strong>to</strong> a “big picture” – system architecture.Architecture requires more detailed studies, due <strong>to</strong> a large-scale impact on system.This subsection describes SOA architectural patterns in following manner..1. SOA patterns– presents a problem with SOA architectural patterns andpresents results <strong>of</strong> pattern investigation.2. The target architecture – presents the target architecture that is a result <strong>of</strong>combination <strong>of</strong> patterns found in section 4.6.14.6.1 SOA patternsThe book “SOA –Design <strong>Pattern</strong>s” [32] is the largest and the most completesource <strong>of</strong> pattern in SOA domain[54]. <strong>Pattern</strong>s presented in the book belong <strong>to</strong>design patterns, but their descriptions question this adherence. The problem risesfrom definition <strong>of</strong> pattern and design pattern used by T.Erl in this book.According <strong>to</strong> T.Erl pattern [32]“provides a proven solution <strong>to</strong> a common problemindividually documented in a consistent format and usually as part <strong>of</strong> a largercollection” what corresponds <strong>to</strong> the definition <strong>of</strong> pattern presented in section 3.1.1.Design pattern is defined as follows [32]: “<strong>Pattern</strong>s in the IT world that revolvearound the design <strong>of</strong> au<strong>to</strong>mated systems are referred <strong>to</strong> as design patterns.”.Thisdefinition can be also applied <strong>to</strong> other types <strong>of</strong> patterns. All the pattern describedin section 3.1.1 “revolve” around design <strong>of</strong> au<strong>to</strong>mated system, not only designpatterns.SOA patterns are described also in“<strong>Pattern</strong>s: <strong>Service</strong>–<strong>Oriented</strong> Architectureand Web <strong>Service</strong>s”[30] but they refer <strong>to</strong> Enterprise Application Integration. Integrationis out scope <strong>of</strong> this thesis.Selection <strong>of</strong> architectural patternsThe target architecture will be build on architectural patterns. Usage <strong>of</strong> the book“SOA –Design <strong>Pattern</strong>s” [32] as a source <strong>of</strong> architectural patterns requires furtherstudies.Analysis <strong>of</strong> patterns presented by T. Erl (see [32]) results in division <strong>of</strong> presentedpattern in<strong>to</strong> four categories. The categories are following

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!