A centralized database (sometimes abbreviated CDB) is a database that is located, stored, and maintained in a single location. This location is most often a central computer or database system, for example a desktop or server CPU, or a mainframe computer. In most cases, a centralized database would be used by an organization (e.g. a business company) or an institution (e.g. a university.) Users access a centralized database through a computer network which is able to give them access to the central CPU, which in turn maintains to the database itself.[1][2]

Historical context

The need for databases rose in the 60's with the invention of direct access storage, which allowed users to directly access records. Previously, computer systems were tape based, meaning records could only be accessed sequentially.[3] Organizations quickly adopted databases for storage and retrieval of data. The traditional approach for storing data was to use a centralized database, and users would query the data from various points over a network.[1]

An example for a centralized database could be given with the Australian Department of Defense, which centralized their databases in the mid 1970s.[3]

Advantages

Centralized databases hold a substantial amount of advantages against other types of databases. Some of them are listed below:

  • Data integrity is maximized and data redundancy is minimized, as the single storing place of all the data also implies that a given set of data only has one primary record. This aids in the maintaining of data as accurate and as consistent as possible and enhances data reliability.[4]
  • Central host computer can be more easily protected from unauthorized access.[4]
  • Generally easier data portability and database administration.
  • Data kept in the same location is easier to be changed, re-organized, mirrored, or analyzed
  • Transactions can more easily comply with the properties of ACID.[5]

Disadvantages

Centralized databases also have a certain amount of limitations, such as those described below:

  • Access speed is limited by network speed.[4]
  • The central computer is a single point of failure, if the computer experiences downtime, users will not be able to access any data.
  • If there is no fault-tolerant setup and hardware failure occurs, all the data within the database will be lost.
  • If someone accesses the central computer, all of the data can easily be compromised.
  • Difficult to scale as the centralized computer would need to be replaced to scale up.[6]

Centralized databases vs. Distributed databases

The underlying idea of centralized databases is that they should be able to receive, maintain, and complete every single request that the main system must perform by themselves. There is only one database file, kept at a single location on a given network.

A distributed database, however, is a database in which all the information is stored on multiple physical locations.[7] Distributed databases are divided into two groups: homogeneous and heterogeneous. It relies on replication and duplication within its multiple sub-databases in order to maintain its records up to date. It is composed of multiple database files, all controlled by a central DBMS.

The main differences between centralized and distributed databases arise due to their respective basic characteristics. Differences include but are not limited to:

  • Centralized databases store data on a single CPU bound to a single certain physical/geographical location. Distributed databases, however, rely on a central DBMS which manages all its different storage devices remotely, as it is not necessary for them to be kept in the same physical and/or geographical location.
  • As outlined above, centralized databases are easier to maintain up to date than distributed databases. This is so because distributed databases require additional (often manual) work to keep the data stored relevant, and to avoid data redundancy, as well as to improve the overall performance.[8]
  • If data is lost in a centralized system, retrieving it would be much harder. If, however, data is lost in a distributed system, retrieving it would be very easy, because there is always a copy of the data in a different location of the database.
  • Designing a centralized database is generally much less complex than designing a distributed database, as distributed database systems are based on a hierarchical structure.

See also

References

  1. 1 2 Turban, Efraim; Carol Pollard; Gregory R. Wood (2021). Information technology for management: driving digital transformation to increase local and global performance, growth and sustainability (Twelfth ed.). Hoboken. p. 71. ISBN 978-1-119-70290-0. OCLC 1333952841.{{cite book}}: CS1 maint: location missing publisher (link)
  2. ↑ Neelankavil, James P. (2007). International business research. Armonk, N.Y.: M.E. Sharpe. pp. 96–97. ISBN 978-1-317-42545-8. OCLC 647515744.
  3. 1 2 Lake, Peter (2013). Concise guide to databases: a practical introduction. Paul Crowther. London. ISBN 978-1-4471-5601-7. OCLC 868889675.{{cite book}}: CS1 maint: location missing publisher (link)
  4. 1 2 3 Sumathi, S. (2007). Fundamentals of relational database management systems. S. Esakkirajan. Berlin: Springer. ISBN 978-3-540-48399-1. OCLC 184984668.
  5. ↑ Iacob, Nicoleta Magdalena; Moise, Mirela Liliana (December 2015). "Centralized vs. Distributed Databases. Case Study" (PDF). Academic Journal of Economic Studies. 1 (4). Archived from the original (PDF) on 2022-11-23. Retrieved 2022-11-23.
  6. ↑ Silberschatz, Abraham; Henry F. Korth; S. Sudarshan (2011). Database system concepts (Sixth ed.). New York: McGraw-Hill. ISBN 978-0-07-352332-3. OCLC 436031093.
  7. ↑ "Wikispaces".
  8. ↑ "Q. What are differences in Centralized and Distributed Database Systems? List the relative advantages of data distribution? - Solved Assignments". Archived from the original on 2023-05-02. Retrieved 2014-10-29.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.