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

More documents

Recommendations

Info

7. Validation and Evaluation accessing the MySQL database instance in Amazon RDS, the maximum values correlate with the scenarios 1.1.1.1 and 1.1.2.1, but in average the CPU utilization is lower due to a higher number of blocked threads. Figure 7.6.: CPU utilization (%) for the different scenarios described in Table 7.1 where ServiceMix-mt is involved. 86
8. Outcome and Future Work Migration of one or more application layers to the Cloud aims to reduce the cost in the required IT infrastructure to host and maintain such layer within an organization. Adaptations on both migrated and non migrated layers are a must when part of an application is migrated to a Cloud infrastructure. In this diploma thesis we start from the basis of a partial migration of the application, particularly the database layer. The database layer includes the operations which provide data storage and retrieval support. Furthermore, the software, hardware and maintenance required to host and maintain this layer require an economical budget substantially greater than the needed for the business, or presentation layers of an application. Migrating the application’s data to the Cloud requires rewiring the database connections to the backend Cloud data store, and adaptating the upper layers to match the operations, and data representations supported. Providing transparent communication support for accessing and storing data on application’s databases in the Cloud demands a multi-protocol, and multi-tenant component. In this diploma thesis we extend a multi-tenant aware ESB in order to utilize it as the database layer of the application, and access multiple Cloud data stores providing SQL and NoSQL databases. In Chapter 2 we present the necessary background about the technologies we use, and the components we reuse in this diploma thesis, e.g. JBIMulti2 [Muh12], JBI and OSGi frameworks, etc. Furthermore, we categorize the databases systems which are supported in the prototype, and subcategorize them based on their storage model and communication protocols. After researching on the SQL and NoSQL database systems properties in Chapters 2 and 3, we find that most of database communication protocols are not standardized, and differ along the different database vendors. Therefore, we are forced in Chapter 5 to develop components which adjust to specific communication protocols: HTTP, and MySQL. The research described in Chapter 3 leads us to find a lack of standardization in the communication at the TCP level of the SQL database vendors, but the existence of components which support other communication protocols for incoming requests, e.g. HTTP, and utilize via JDBC the different database vendors’ native driver to forward them to the backend database system [Red11]. However, approaches in this direction forces the developer to adjust their data access layer, whose adaptations we aim to minimize when utilizing our system. NoSQL Cloud data store providers show a lack of standardized naming, and provide the database users with their drivers for I/O operations. In order to address the lack of a standardized naming and access in the NoSQL providers, we categorize in the system’s registry the user’s databases meta-data into different categories and subcategories, and access the backend data stores via the HTTP protocol supported in ServiceMix-http-mt [Sá12]. 87
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 74 and 75: 5. Design External Application Lege
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 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

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

Delete template?

Save as template?