Component Design for Relational Databases - High-Performance Web Databases: Design, Development, and Deployment - page 381

Chapter 25

Component Design
for Relational
Databases

Ashvin Iyengar

INTRODUCTION

C - -

are becoming
increasingly popular in building industrial strength applications. However,
relational databases are not going to be replaced by object databases in the
foreseeable future. This paper explores the ramifications of component-
based designs on data management and offers strategies which could be
deployed in the use of relational centralized databases with object-ori-
ented component-based application architectures.

OMPONENT BASED OBJECT ORIENTED ARCHITECTURES

WHY RELATIONAL DATABASES ARE HERE TO STAY

From a pure application design perspective, object-oriented databases
would be much more suitable for use with object-oriented component-
based application architectures. However, the business realities are more
complex and include the following considerations:

• Object-oriented databases are not mature enough to be entrusted with
the job of managing large corporate data;
• It is more difficult to find professionals with experience in administra-
tion as well as the design of object-oriented databases;
• The vast majority of corporations are currently using relational data-
bases to manage business information; and
• Most current live applications have been designed and developed to
work with relational databases.

MOVING TOWARDS A COMPONENT-BASED ARCHITECTURE STANDARD

The subject of object-oriented design and programming involving rela-
tional databases has been well explored. More often than not, the data