Добавил:
Upload Опубликованный материал нарушает ваши авторские права? Сообщите нам.
Вуз: Предмет: Файл:
sg247887.pdf
Скачиваний:
18
Добавлен:
01.03.2016
Размер:
4 Мб
Скачать
☆

4.4 Integrate an existing application to work with solidDB UC

The solidDB Universal Cache is seen as a way for speeding up existing systems that are running on top of disk-based enterprise systems. This way is true if the workload is favorable. See Chapter 6, “Performance and troubleshooting” on page 147 for further details.

Feasibility of retrofitting a cache database between back-end database and existing application depends on how well the issues we listed are handled in the existing application and whether the existing application can live with the implicit compromises. Feasibility and effort required for retrofitting might not always be obvious. A thorough analysis might be required. In this section, we outline the process for the analysis and present several workarounds to typical problems.

IBM solidDB supports the standard Java Transaction API (JTA), through providing a set of XA (see entry XA in “Abbreviations and acronyms” on page 277) classes. JTA methods enable the Transaction manager to control solidDB as one of the transactional resources in a global transaction.

4.4.1 Programming interfaces used by the application

Converting an application using a legacy database to using a Universal Cache database between legacy database and the cache database can be a relatively simple effort or a major project, depending on how the application has been designed and implemented.

Generally, the applications that have been implemented directly using JDBC or ODBC APIs, or a middleware running on top of those APIs, might require no conversion at all. If no extensions to the SQL Standard are used, the applications are expected to work with minor modifications.

Because stored procedure languages are not compatible with each other, a rewrite for stored procedures will be required if they are used in the application. This can be automated to some level but a separate project is necessary for stored procedure conversion.

If APIs, access methods or programming paradigms that are not supported by IBM solidDB (such as embedded SQL) are used, and there is no ODBC or JDBC-based middleware available to act as a gateway, this part of the application must be rewritten altogether.

Chapter 4. Deploying solidDB and Universal Cache 89

4.4.2 Handling two database connections instead of one

Existing applications have most likely been written to handle connections to only one database, which would have all the required tables and data. Implementing the logic to an existing application that is capable for routing the queries to an appropriate database will not be a project without risks.

SQL pass-through provides a mechanism to combine the two database connections to one connection that routes every query to the front-end server at first. The front-end server might end up routing the query to the back-end based on table existence.

The change of transactional model included in moving from one physical database to a combination of front-end and back-end databases might prove to be a challenge to several applications. The combination of two databases is no longer strictly transactional, which might prevent migration the two database architecture altogether.

The strictness of the transactionality requirement should be estimated among the first things in technical feasibility assessment of moving to a front-end/back-end-based architecture. If the requirement is strict, the effort for implementing a transaction manager as part of a migration process (4.3.2, “Combining data from separate databases in a transaction” on page 87) must be included in the estimates.

Various applications rely heavily on a database’s capability of running complicated queries that combine data from several tables in one query. IBM solidDB does not have a capability of joining data residing in a front-end database and back-end database. The standard fallback mechanism is to direct all these kinds of queries to the back-end database. Although this approach works, it does not enable the application to take advantage of the performance benefits of main memory-based data management.

Based on analyzing the questions in this section, creating an estimate of the retrofitting effort for Universal Cache database is possible. It should be estimated in parallel to estimating expected performance and potential for other benefits of the product. The bigger the retrofitting effort is, the more substantial the benefits would need to be.

90 IBM solidDB: Delivering Data with Extreme Speed

Соседние файлы в предмете [НЕСОРТИРОВАННОЕ]