Object
Middleware for CMS
With increasing use of relational databases in the grid
environment, a need has arisen to complement these databases with
software layers between the database and its clients.
These intermediate layers solve the following problems:
-
Native drivers (i.e. OCI for Oracle, TDS for SqlServer,
etc.) were not designed to operate efficiently in a WAN environment
due to high network
latencies.
-
Client software frequently contains database vendor
specific code (native driver access) which makes it difficult to
switch database vendors once projects are in motion. Database
"brands" should be pluggable with no client code changes, and would
additionally require no recompile of client code.
-
Client software frequently
contain table and column information from the relational schema.
If the database schema is modified, client code must
also be modified. Intermediate software layers should hide all
database schema (e.g. relational table and column names)
information from client code.
-
Results from database queries are presented in forms
somewhat unnatural for our target language, C++.
Next>
