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

More documents

Recommendations

Info

Chapter 4. Service Oriented Architecture 764.2 Elements of SOAThis section describes briefly elements of service oriented architecture.1. Main elements – This section focuses on elements presented in the defitionprovided by Krafzig[47].2. Other elements – The second section presents other elements of SOA thatare not mentioned in the definition but they were identified during researches.3. Types of Services – While the first section describes the idea behind services,this section presents briefly types of services.4. Structure of a service – this section presents structure of a service4.2.1 Main elementsService — derives from business context of an organisation. Service can bedescribed as [59] “an asset that corresponds to real–world business activities orrecognisable business functions.” Service does not only provide functionality, italso consumes or consumes and provides functionality. A service should be discoverable(available through discovery mechanism like for instance service registry)and bound in run-time, however static bound is also possible . A service can bealso be characterized by some properties [42] ] such as performance, capacity, andreliability. Service is a complex entity and consists of Service Contract, Interfaceand Implementation [46].Service repository [46][31] —contains descriptions of services and providesall information required to access them. The information includes localization,provider, technical constrains, terms of usage, fees, service subscription and userregistration if the services are public. Repositories can be stored in databases tostore contract of descriptions for each service version. The database may storecontracts, description of each version of a service and some administrative data.The term repository is also interchanged in literature with registry. In fact bothterms are very similar and differ only in one aspect. Repository is a term usedduring design time, while registry is associated with runtime usage [31]Enterprise Service bus — Service Bus is also referred as Enterprise ServiceBus (ESB). The bus is a middleware concept that enables interaction betweendifferent applications [25].(Enterprise) Service Bus can be implemented as forinstance Enterprise Application Integration middleware [25] [13], brokering technology[13] or a platform specific component like WebShare application Server[13] [60]. In fact, ESB is a communication mechanism that performs followingactivities [59]:
Chapter 4. Service Oriented Architecture 771. Accepts information requests from service requesters.2. Consults a metadata registry to determine how to assemble the requestedinformation using known data services.3. Retrieves the data from one or more data service providers.4. Applies data transform rules using a data transformation service that removesduplicate data and converts the data that have been collected intothe format specified by the service contract.5. Returns the results to the service requester.Frontend —corresponds to an upper layer of a traditional application likeWeb page or a rich client[46]. Frontends are used to initialize a process and retrievea result. The initiation does not have to be invoked by end user. It canbe a long living process which invokes specific events in some circumstances likeperiodical events.4.2.2 Other elementsThe definition of SOA[46] does not mention about one more element of ServiceOriented Architecture, namely Service Inventory. This element is not obligatorybut it simplifies maintenance of large amount of services.Service Inventory [31] [46] – inventory is an independent element of thearchitecture and independently manages collection of services. The collectionscontain services important from point of view of the company.4.2.3 Types of servicesServices can be divided into following groups:1. Application Frontend – in general it does not have to be a service in termsof previously stated definition - it is rather a client of an application butit can also be other services like services from other company or a batchservice executing tasks periodically [46] .2. Basic Service[46] [31] – represents basic and stateless element of a domain.A basic service can be Data Centric Service or Logic Centric Services.(a) Data Centric Services – are responsible for maintaining only one maindata entity. The maintenance does not mean that a service executesonly CRUD operations - a service has to care also about locking mechanismand transactional management. To fulfill all his responsibilities,the service has to maintain database connection.
Page 1 and 2:
Master ThesisSoftware EngineeringTh
Page 3 and 4:
AbstractContext: Several examples o
Page 5 and 6:
List of Figures1.1 Research methodo
Page 7 and 8:
List of Tables3.1 Summary of archit
Page 9 and 10:
3.3.1 Definition of Pattern Languag
Page 11 and 12:
Chapter 1Introduction1.1 Background
Page 13 and 14:
Chapter 1. Introduction 3technique
Page 15 and 16:
Chapter 1. Introduction 5was notice
Page 17 and 18:
Chapter 1. Introduction 7do not pro
Page 19 and 20:
Chapter 1. Introduction 9Chapter 4
Page 21 and 22:
Chapter 2. Related Work 11This chap
Page 23 and 24:
Chapter 2. Related Work 13(b) Chara
Page 25 and 26:
Chapter 2. Related Work 15Figure 2.
Page 27 and 28:
Chapter 2. Related Work 17Drawbacks
Page 29 and 30:
Chapter 2. Related Work 19Figure 2.
Page 31 and 32:
Chapter 2. Related Work 21Advantage
Page 33 and 34:
Chapter 2. Related Work 23between a
Page 35 and 36: Chapter 2. Related Work 252. Applic
Page 37 and 38: Chapter 2. Related Work 274. Mediat
Page 39 and 40: Chapter 2. Related Work 292.3 Summa
Page 41 and 42: Chapter 3. Architectural Patterns 3
Page 85: Chapter 4. Service Oriented Archite
Page 89 and 90: Chapter 4. Service Oriented Archite
Page 113 and 114: Chapter 5. Guidelines 1035.1 Patter
Page 115 and 116: Chapter 5. Guidelines 105Descriptio
Page 117 and 118: Chapter 5. Guidelines 107Result Con
Page 119 and 120: Chapter 5. Guidelines 109ContextAn
Page 121 and 122: Chapter 5. Guidelines 111Result Con
Page 123 and 124: Chapter 5. Guidelines 113System’s
Page 125 and 126: Chapter 5. Guidelines 115ViewSchema
Page 127 and 128: Chapter 5. Guidelines 117ViewViewCo
Page 129 and 130: Chapter 5. Guidelines 119ViewViewCo
Page 131 and 132: Chapter 5. Guidelines 121ViewViewPr
Page 133 and 134: Chapter 5. Guidelines 123FrontendFr
Page 135 and 136: Chapter 5. Guidelines 125complicati
Page 137 and 138:
Chapter 5. Guidelines 127Concluding
Page 139 and 140:
Chapter 5. Guidelines 129UsecasesTh
Page 141 and 142:
Chapter 5. Guidelines 131puter (ext
Page 143 and 144:
Chapter 5. Guidelines 133Group 3 ma
Page 145 and 146:
Chapter 5. Guidelines 135Output: Du
Page 147 and 148:
Chapter 5. Guidelines 137generation
Page 149 and 150:
Chapter 5. Guidelines 139(a) Fronte
Page 151 and 152:
Chapter 5. Guidelines 141Figure 5.1
Page 153 and 154:
Chapter 5. Guidelines 143Figure 5.1
Page 155 and 156:
Chapter 5. Guidelines 145FrontendSc
Page 157 and 158:
Chapter 6. Conclusion 147There are
Page 159 and 160:
Chapter 6. Conclusion 149RQ.6 How t
Page 161 and 162:
References[1] http://www.soa-manife
Page 163 and 164:
References 153[22] Frank Buschmann,
Page 165 and 166:
References 155[46] Dirk Krafzig, Ka
Page 167 and 168:
References 157[67] Xiaohong Qiu. Bu
show all

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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?