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

More documents

Recommendations

Info

Contents 4.2. Multi-tenancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 4.2.1. Communication Requirements . . . . . . . . . . . . . . . . . . . . . . . 38 4.2.2. Storage Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 4.3. Dynamic Transparent Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 4.3.1. Transparency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 4.3.2. Dynamic Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 4.4. Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 4.5. Integration Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 4.6. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 4.7. Web Service Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 4.8. Non-functional Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 4.8.1. Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 4.8.2. Backward Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 4.8.3. Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 4.8.4. Scalability and Extensibility . . . . . . . . . . . . . . . . . . . . . . . . . 48 4.8.5. Maintainability and Documentation . . . . . . . . . . . . . . . . . . . . 48 5. Design 49 5.1. Service Registry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 5.2. Normalized Message Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 5.3. SQL Support Architectural Overview . . . . . . . . . . . . . . . . . . . . . . . 55 5.3.1. Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 5.3.2. Approach 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 5.3.3. Approach 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 5.4. NoSQL Support Architectural Overview . . . . . . . . . . . . . . . . . . . . . . 61 5.4.1. Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 5.4.2. Architectural Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 6. Implementation 63 6.1. SQL Support Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 6.1.1. CDASMix MySQL Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . 63 6.1.2. Multi-tenant ServiceMix Camel Service Engine . . . . . . . . . . . . . . 67 6.1.3. Camel CDASMix JDBC Component . . . . . . . . . . . . . . . . . . . . 68 6.2. NoSQL Support Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . 69 6.2.1. Multi-tenant ServiceMix HTTP Binding Component . . . . . . . . . . . 69 6.3. Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 6.3.1. JBIMulti2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 6.3.2. Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 7. Validation and Evaluation 75 7.1. Deployment and Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 7.2. Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 7.3. Evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 7.3.1. TPC-H Benchmark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 7.3.2. Evaluation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 iv
Contents 7.3.3. Evaluation Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 8. Outcome and Future Work 87 A. Components 91 A.1. CDASMix MySQL Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 A.2. CDASMix Camel JDBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 B. Messages 95 B.1. Normalized Message Format Content Description . . . . . . . . . . . . . . . . 95 B.2. MySQL TCP Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Bibliography 103 v
Page 1: Institute of Architecture of Applic
Page 5: Contents 1. Introduction 1 1.1. Pro
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 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?