Historical Development of Databases (Cont.)


Third Generation (since mid 1990s)
Object-oriented, object-relational, and extended-relational databases aim at an appropriate integration of programming languages and databases. The object-oriented data model does not need to follow the first normal form rule of the relational model: A table cell must contain a single, unstructured value.
Object-oriented data model
It is a system offering DBMS facilities in an object-oriented programming environment. Data is stored as objects and can be interpreted only using the methods specified by its class.

Fourth Generation? [since late 2000s (decade)]

NoSQL data model
Much of current data processing requires horizontal scaling, faster speed, and processing different kinds of data. A NoSQL database is to meet the requirements by providing a simple and efficient mechanism for data storage and retrieval. The approach it uses is different from the one used by a relational database, a general-purpose data store.

Whereas a NoSQL database is normally a key–value store for simple insertion and retrieval operations. Check the NoSQL forecast: people who are looking for NoSQL are doing it mostly because it’s still “hype.”

Review: Database Models
    Which data model is the IBM’s IMS (Information Management System) based on?

      Hierarchical data model
      Network data model
      NoSQL data model
      Object-oriented data model
      Object-relational data model
      Relational data model
        Result: