Diploma Thesis Santiago GÃ³mez SÃ¡ez - IAAS

More documents

Recommendations

Info

5. Design External Application Legend Data Access Layer (MySQL ConnectorJ) SELECT * FROM myTable / INSERT * INTO * VALUES * T1 ... TN (*) Tenant-aware Endpoint Tenant1 ... TenantN Query and data transformation might exist Multi-tenant context & messaging Multi-tenant messaging OSGi JBI Environment Registry-Cache SQL Cache instance SQL Server (port 3306) MySQL Proxy Bundle Standardised Interfaces for Binding Components Normalized Message API !"#$%&'()*+,)--%.)+/"01)#+ (*) Standardised Interfaces for Service Engines JBItoCamelJdbc Smx-Camel ... T1 T2 T3 TN Camel JBI Smx-Camel-mt CdasmixJDBC JNDI PostgreSQL Service Registry Amazon RDS Local VM MySQL Oracle ... MySQL PostgreSql Figure 5.5.: Architectural overview of the design approach two to support the MySQL communication protocol and routing to backend SQL databases. 60
5.4. NoSQL Support Architectural Overview 5.4. NoSQL Support Architectural Overview Transparent access to different NoSQL family databases and providers, e.g. Amazon DynamoDB, Google Cloud Storage, MongoDB, must be supported in the system. In this section we provide an architectural design to support the communication between the tenant and backend NoSQL databases. We first discuss the integration mechanisms with the components implemented in [Muh12] and [Sá12], and then provide the required adaptations. 5.4.1. Integration ServiceMix-mt is shipped with an HTTP BC which supports the SOAP over HTTP communication protocol. As discussed in Chapter 3, most of the Cloud data store providers offer a REST interface for accessing, and modifying data. The payload format supported by most of the vendors, and specified in the CDMI specification is JSON [Sto12]. Therefore, we find suitable the reuse of this component, and its enrichment with the required operations which are described in the following subsection. The packaging required to deploy the component as a SA forces us to statically include the imported packages in the BC SA. Unlike in the SQL architectural approach one, the deployed HTTP endpoint configuration in this case references an endpoint which is addressed in the BC the configuration refers to. Therefore, we can include the needed packages in the BC and not in the SAs containing the tenant-aware endpoint configurations. 5.4.2. Architectural Overview The multi-tenant aware HTTP BC provides tenant isolation at the tenant level. As in the Servicemix-camel-mt, we extend the component and provide isolation at the tenant and user level. The architectural design presented in Figure 5.6 is similar to the one presented in [Sá12]. The main reason of this similitude is that we must extend the functionalities of the BC rather than making a substantial architectural modification. In this approach we consider that the tenant in using the driver provided by the Cloud data store provider to access the consumer endpoint in ServiceMix-mt. The different Java SDKs which are offered by the providers support a set operations and data conversions, build the HTTP request, and forward it to the data store endpoint. To support the different storage structures naming, authentication mechanisms, and data types, we extend the HTTP BC at the marshaling level, routing level, and enhance it with I/O operations with the service registry. Furthermore, to avoid adversely performance effects, it must support cashing mechanism. HTTP provider endpoints are modified in order to able data retrieval from different backend data stores, as long as the source and target database’s family and version are the same. 61
Page 1:
Institute of Architecture of Applic
Page 5 and 6:
Contents 1. Introduction 1 1.1. Pro
Page 7 and 8:
Contents 7.3.3. Evaluation Analysis
Page 9 and 10:
List of Figures 1.1. Migration Scen
Page 11 and 12:
List of Tables 4.1. Description of
Page 13:
List of Listings 5.1. Tenant-aware
Page 16 and 17:
1. Introduction and multi-protocol
Page 18 and 19:
1. Introduction Definitions List of
Page 20 and 21:
1. Introduction • Implementation,
Page 22 and 23:
2. Fundamentals usage of it. PaaS p
Page 24 and 25: 2. Fundamentals 2.2.1. Enterprise S
Page 26 and 27: 2. Fundamentals through the network
Page 28 and 29: Management Framework Component Fram
Page 30 and 31: 2. Fundamentals corresponding works
Page 32 and 33: 2. Fundamentals the tenant level, b
Page 34 and 35: 2. Fundamentals 2.9. Structured Que
Page 36 and 37: 2. Fundamentals 2.9.2. PostgreSQL D
Page 38 and 39: 2. Fundamentals 2.10.1. Key-value D
Page 40 and 41: 2. Fundamentals User Interface Web
Page 42 and 43: 28 2. Fundamentals
Page 44 and 45: 3. Related Works and balancing the
Page 46 and 47: 3. Related Works store may contain
Page 48 and 49: 3. Related Works In the second plac
Page 50 and 51: 4. Concept and Specification VM0 or
Page 52 and 53: 4. Concept and Specification then f
Page 54 and 55: 4. Concept and Specification 4.3. D
Page 56 and 57: 4. Concept and Specification 4.6. U
Page 58 and 59: 4. Concept and Specification Name G
Page 60 and 61: 4. Concept and Specification Name G
Page 62 and 63: 4. Concept and Specification 4.8.3.
Page 64 and 65: 5. Design stores have two main stor
Page 66 and 67: 5. Design userId serviceName XMLNam
Page 68 and 69: 5. Design received in the vendor’
Page 70 and 71: 5. Design JBI SA into an OSGi conta
Page 72 and 73: 5. Design Apache Camel provides a s
Page 76 and 77: 5. Design External Application Exte
Page 78 and 79: 6. Implementation the bundle activa
Page 80 and 81: 6. Implementation each of the queri
Page 82 and 83: 6. Implementation multi-tenancy awa
Page 84 and 85: 6. Implementation The HTTP endpoint
Page 86 and 87: 6. Implementation stored. Both auth
Page 88 and 89: 74 6. Implementation
Page 90 and 91: 7. Validation and Evaluation We mus
Page 92 and 93: 7. Validation and Evaluation When t
Page 94 and 95: 7. Validation and Evaluation in the
Page 96 and 97: 1. Introduction 1. Introduction 7.
Page 98 and 99: 7. Validation and Evaluation proble
Page 100 and 101: 7. Validation and Evaluation access
Page 102 and 103: 8. Outcome and Future Work The func
Page 104 and 105: 90 8. Outcome and Future Work
Page 106 and 107: Appendix A. Components A.2. CDASMix
Page 108 and 109: 94 Appendix A. Components
Page 110 and 111: Appendix B. Messages 20 - target da
Page 112 and 113: Appendix B. Messages 110 111 - OK r
Page 114 and 115: Appendix B. Messages 1 interface: l
Page 116 and 117: 102 Appendix B. Messages
Page 118 and 119: Bibliography [CC06] F. Chong and G.
Page 120 and 121: Bibliography [SAS + 12] [SBK + 12]
Page 122 and 123: Acknowledgement I am heartily thank
show all

Diploma Thesis Santiago GÃ³mez SÃ¡ez - IAAS

Create successful ePaper yourself

Delete template?

Save as template?