Essay Undergraduate 729 words

Database Systems in the Enterprise: Architecture Overview

~4 min read

Abstract

This paper provides an overview of database systems as used in modern enterprise environments. It examines how relational database management systems (RDBMS) and object-oriented database management systems (OODBMS) differ in architecture, performance characteristics, and appropriate use cases. The paper covers fundamental database concepts such as schema, subschema, and data attributes, then focuses on relational databases — including products from Microsoft, Oracle, and IBM — and their role in transaction processing, supply chain management, ERP, and CRM systems. IBM's Service Management program is highlighted as a practical case study in RDBMS integration with legacy platforms.

📝 How to Write This Type of Paper Writing guide — click to expand

▼

What makes this paper effective

Grounds broad claims in specific real-world examples, such as IBM's Service Management program and CAD applications using OODBMS, which prevents the survey from feeling purely abstract.
Clearly distinguishes the strengths of RDBMS versus OODBMS, giving readers a practical decision framework rather than a neutral feature list.
Uses consistent citation support throughout, anchoring nearly every factual claim to a peer-reviewed or industry source.

Key academic technique demonstrated

The paper demonstrates comparative analysis as an organizational strategy. Rather than treating RDBMS and OODBMS as isolated topics, the author consistently contrasts them along specific dimensions — transaction volume, unstructured content, scalability, and security — allowing the reader to draw practical conclusions about when each architecture is appropriate.

Structure breakdown

The paper opens with an introductory section establishing the business rationale for database adoption across ERP, CRM, and CAD contexts. A second section covers shared fundamentals common to all database types. The third and most developed section focuses specifically on RDBMS architecture, its dominant enterprise role, and a concrete IBM case study. A full reference list closes the paper.

Introduction

The pervasive adoption of databases for aggregating, analyzing, parsing, reporting, and storing data continues to increase exponentially over time as the information needs of companies grow. The foundation of nearly every enterprise-wide system and computing platform includes integration with databases of many types, from object-oriented to relational (Lungu, Velicanu, & Botha, 2009). Every Enterprise Resource Planning (ERP) system today relies on databases for product management, pricing, costing, production scheduling, service coordination, and manufacturing execution task coordination (Bremer & Carey, 1987).

Databases have become an essential component of every enterprise system in use today, from coordinating supply chains and sourcing to tracking customer activity and sales through Customer Relationship Management (CRM) systems (Madduri, Shi, Baker, & Ayachitula, 2007). Object-oriented databases are also pervasively used in Computer-Aided Drawing (CAD) applications, given their speed and accuracy in managing geographic and graphic primitives (Chu, 1995).

Fundamentals of Database Architecture

All databases share a series of common features, functional areas, and approaches to data modeling. In addition, all have the ability to integrate with other databases in either batch or real-time mode (He, 1998). All databases also support a series of database schema and advanced taxonomy definitions, which are entirely dependent on the foundational elements of the underlying architecture.

Object-oriented databases use orthogonal objects that carry their own functional and taxonomy definitions (Hansen, 1995). Relational databases (RDBMS) rely on a more schema-based approach to define the data models used for completing analysis, reporting, and ensuring a high degree of integration reliability and security (Hansen, 1995). All databases rely on schema and subschema, and within these constructs, the ability to define data attributes. Of the two dominant types of databases — OODBMS and RDBMS — the latter performs best for high-volume transaction processing (Hooper & Page, 1996), while OODBMS is best for managing unstructured content and the rapid analysis and classification of object-based content (Newing, 1997).

2 Locked Sections · 410 words remaining

Defining Relational Database Architectures · 200 words

"RDBMS dominance, SQL platforms, and IBM case study"

References · 210 words

"Cited sources supporting all claims"

You’re 40% through this paper. Sign up to read the remaining 2 sections.

130,000+ paper examples AI writing assistant Citation generator Cancel anytime

Key Concepts in This Paper

RDBMS OODBMS Transaction Processing ACID Compliance Database Schema Enterprise Systems SQL Integration Supply Chain ERP Systems CRM Platforms