Technical note

Introduction to Database Applications

A quick history of database technology and a rundown of when — and when not — to use a database management system.

Quick notes: the history and use of DBMS.

A Brief History of Database Technology

Early database applications

  • 1960s — hierarchical and network models were introduced.
  • A large share of the world's databases still run on these models.

Relational model based systems

  • Introduced in 1970.
  • Heavily researched and experimented with within IBM Research and several universities.
  • Relational database management system products emerged in the 1980s.

Object-oriented and emerging applications

  • OODBMS, or object-oriented database management systems, were introduced in the 1980s–1990s to cater to the needs of complex data processing in CAD and other applications.
  • Incorporating object database concepts led to ORDBMS.
  • Extended relational systems added further capabilities.

Data on the web and e-commerce applications

  • Data on websites is stored and processed using DBMS.
  • The web contains data in HTML, with links among pages.
  • E-commerce using new standards like XML was born.
  • Scripting languages such as PHP and JavaScript allow the generation of dynamic web pages that are partially generated from a database.

When Not to Use Database Management Systems

Main inhibitors (cost) of using a DBMS

  • High initial investment
  • Possible need for additional hardware
  • Overhead for providing generality, security, concurrency control, recovery, and integrity functions

When it's unnecessary

  • When the database and applications are simple, well-defined, and not expected to change.
  • If access to data by multiple users is not required.

When it's not feasible

  • When a general-purpose database management system won't fit the available storage for embedded systems.

When no DBMS may suffice

  • If there are stringent real-time requirements that may not be met by DBMS overhead.
  • If the database system isn't able to handle the complexity of the data because of modeling limitations.
  • If database users need special operations not supported by a DBMS.
← All writing