This article was accepted into the corpus but its outbound wikilinks were never NER-processed — typical at the deepest BFS hop or when the run's entity cap was reached. No expansion funnel to show.
| IDS (Integrated Data Store) | |
|---|---|
| Name | IDS (Integrated Data Store) |
| Developer | Honeywell, Martin Marietta, IBM |
| Released | 1960s |
| Latest release version | proprietary/various |
| Operating system | UNIX, VMS, MS-DOS |
| Genre | Database management system |
IDS (Integrated Data Store) is an early network-model database management system developed for high-performance transaction processing and data sharing in enterprise environments. It influenced subsequent database designs and commercial products by demonstrating record-level relationships, pointer-based navigation, and integrated transaction controls. IDS has been studied in academic and industrial contexts alongside systems originating from research at institutions such as Bell Labs, MIT, and Stanford University.
IDS emerged during an era when organizations such as NASA, US Air Force, Lockheed Corporation, and General Electric required robust systems to manage complex, interrelated data for projects comparable to Apollo program and Skylab. Its design prioritized direct access via physical pointers, deterministic navigation, and transaction integrity for concurrent users, features explored contemporaneously by researchers at IBM Research, Bell Labs, and University of California, Berkeley. IDS positioned itself among other influential systems like CODASYL, IMS, and work stemming from Project MAC.
Development traces to teams at Honeywell and collaborating industrial partners during the 1960s and 1970s, a period marked by computing milestones such as the development of UNIVAC, the founding of DEC, and the rise of commercial database offerings from IBM. Influences included earlier file-structure work at General Electric Research Laboratory and conceptual models proposed by groups at Princeton University and Carnegie Mellon University. IDS deployments occurred in sectors such as aerospace and defense, overlapping with procurement programs like those managed by Northrop Grumman and Raytheon Technologies. Over time, maintenance and ports involved companies that later became parts of Siemens and Honeywell International Inc..
IDS implements a network model in which records are interconnected by explicit pointers, an approach paralleling concepts from CODASYL database proponents and contrasted with the relational proposals by E. F. Codd at IBM. Architectural components include buffer management inspired by practices at Hewlett-Packard, hashing strategies comparable to those developed at Bell Labs, and log-based recovery resembling methods used by teams at IBM Research and DEC. The system emphasizes record locking, pointer stability, and cursor-like navigation similar to concepts explored at Stanford University and Massachusetts Institute of Technology.
The IDS data model is built on record types, sets, and pointer chains with storage organized to minimize I/O for typical transactions. This organization reflects parallel developments in indexed and hashed file systems seen at National Security Agency projects and academic work at University of Illinois Urbana–Champaign. Physical storage layouts accounted for block-oriented devices from manufacturers such as Seagate Technology and Western Digital and matched device constraints documented by vendors like Control Data Corporation. Schema evolution and access paths were managed via utilities similar to those offered by Sybase and early Oracle Corporation products.
Transaction control in IDS uses write-ahead logging, commit protocols, and fine-grained locking mechanisms influenced by theoretical and practical advances at Bell Labs, IBM, and University of Toronto. Concurrency strategies balanced throughput and integrity requirements analogous to those in systems deployed by AT&T and Siemens. Recovery and checkpointing mechanisms paralleled methods developed in large-scale deployments for organizations such as European Space Agency and NASA Jet Propulsion Laboratory.
IDS was optimized for OLTP-style workloads typical of banking, reservations, and telemetry—domains served by institutions like American Express, United Airlines, and IBM consulting projects. Its pointer-based navigation yielded low-latency access for traversals, enabling competitive performance on hardware from Digital Equipment Corporation and IBM System/360. Scalability considerations led to clustering and replication approaches that anticipated later distributed databases used by corporations such as Oracle Corporation and Microsoft in enterprise settings.
Commercial and internal implementations of IDS ran on systems from IBM, DEC, Honeywell, and workstation environments influenced by Sun Microsystems and Xerox PARC innovations. Ports and interoperability work connected IDS-like stores with middleware and transaction monitors provided by vendors such as Tandem Computers and BEA Systems. Academic analysis and reimplementations appeared in research groups at Cornell University and University of California, San Diego, contributing to the preservation of design lessons that informed later projects at Google, Amazon (company), and Facebook engineering teams.