0% found this document useful (0 votes)
8 views3 pages

Network Model

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
8 views3 pages

Network Model

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Network model

In computing, the network model is a database


model conceived as a flexible way of representing
objects and their relationships. Its distinguishing
feature is that the schema, viewed as a graph in
which object types are nodes and relationship
types are arcs, is not restricted to being a hierarchy
or lattice.

The network model was adopted by the


CODASYL Data Base Task Group in 1969 and
underwent a major update in 1971. It is sometimes
known as the CODASYL model for this reason. A
Bachman diagram of a simple network database
number of network database systems became
popular on mainframe and minicomputers through
the 1970s before being widely replaced by relational databases in the 1980s.

Overview
While the hierarchical database model structures data as a tree of records, with each record having one
parent record and many children, the network model allows each record to have multiple parent and child
records, forming a generalized graph structure. This property applies at two levels: the schema is a
generalized graph of record types connected by relationship types (called "set types" in CODASYL), and
the database itself is a generalized graph of record occurrences connected by relationships (CODASYL
"sets"). Cycles are permitted at both levels. Peer-to-Peer and Client Server are examples of Network
Models.

The chief argument in favour of the network model, in comparison to the hierarchical model, was that it
allowed a more natural modeling of relationships between entities. Although the model was widely
implemented and used, it failed to become dominant for two main reasons. Firstly, IBM chose to stick to
the hierarchical model with semi-network extensions in their established products such as IMS and DL/I.
Secondly, it was eventually displaced by the relational model, which offered a higher-level, more
declarative interface. Until the early 1980s the performance benefits of the low-level navigational
interfaces offered by hierarchical and network databases were persuasive for many large-scale
applications, but as hardware became faster, the extra productivity and flexibility of the relational model
led to the gradual obsolescence of the network model in corporate enterprise usage.
History
The network model's original inventor was Charles Bachman, and it was developed into a standard
specification published in 1969 by the Conference on Data Systems Languages (CODASYL)
Consortium. This was followed by a second publication in 1971, which became the basis for most
implementations. Subsequent work continued into the early 1980s, culminating in an ISO specification,
but this had little influence on products.

Bachman's influence is recognized in the term Bachman diagram, a diagrammatic notation that
represents a database schema expressed using the network model. In a Bachman diagram, named
rectangles represent record types, and arrows represent one-to-many relationship types between records
(CODASYL set types).

Database systems
Some well-known database systems that use the network model include:

IMAGE for HP 3000


Integrated Data Store[1] (IDS)
IDMS[1] (Integrated Database Management System)
Univac DMS-1100
Norsk Data SIBAS
Oracle CODASYL DBMS for OpenVMS (originally known as DEC VAX DBMS)

See also
Navigational database
Graph database

References
David M, k., 1997. Fundamentals, Design, and Implementation. database processing ed. s.l.:Prentice-
Hall.

Further reading
Charles W. Bachman, The Programmer as Navigator. Turing Award lecture,
Communications of the ACM, Volume 16, Issue 11, 1973, pp. 653–658, ISSN 0001-0782 (ht
tps://search.worldcat.org/issn/0001-0782), doi:10.1145/355611.362534 (https://doi.org/10.11
45%2F355611.362534)
External links
"CODASYL Systems Committee "Survey of Data Base Systems" " (https://web.archive.org/w
eb/20071012095137/http://www.sqlsummit.com/PDF/DatabaseSurvey_CODASYL_1968.pd
f) (PDF). 1968-09-03. Archived from the original (http://www.sqlsummit.com/PDF/DatabaseS
urvey_CODASYL_1968.pdf) (PDF) on 2007-10-12.
Network (CODASYL) Data Model (https://web.archive.org/web/20060904190944/http://coro
net.iicm.edu/wbtmaster/allcoursescontent/netlib/ndm1.htm)
SIBAS Database running on Norsk Data Servers (http://www.ndwiki.org/wiki/SIBAS)
1. "RDBMS Plenary 1: Early Years" (https://archive.computerhistory.org/resources/access/text/
2013/05/102702562-05-01-acc.pdf) (PDF) (PDF). Interviewed by Burton Grad. Computer
History Museum. 2007-06-12. Retrieved 2025-05-30.

Retrieved from "https://en.wikipedia.org/w/index.php?title=Network_model&oldid=1293182941"

You might also like