Running head: DISTRIBUTED DATABASE

Distributed Database and Design CISIII August 17, 2013

DISTRIBUTED DATABASE

Growth in a company leads to challenges in database management. The need to share information dynamically increases with company growth. This report will discuss three reasons why an organization may have a need for distributed databases and the best practices for implementation. In addition, the report will contain a list and explanation of the software and hardware components, techniques for distributed data placement and strategies for distributed query processing. The report will also explain how an organization would allow programmatic access to a database through the internet and conclude with a proposed solution for the national restaurant. Persuasive argument for distributed database Primarily, the most important reason for a distributed database is communication. If data is not already distributed, there will be a need for distribution in order to share information. Data will need to be organized from multiple systems and distributed throughout the organization providing interconnection of existing databases. Scalability and performance is the second reason for a distributed database by providing incremental growth and reduced communication overhead. With the advance of a variety of hardware technologies such as multicore processors, database management can be scaled appropriately depending on technological advances. In essence, a distributive database is modular, allowing hardware upgrades where needed. Lastly, distributive databases are resilient to failures. Because data is spread over multiple machines in different locations, a single failure or natural/unnatural disaster would not bring down every system in the cluster.

DISTRIBUTED DATABASE

Implementation To save on complexity and cost, homogeneous system is the best design. Homogeneous relies on all nodes to use the same hardware and software for the database system. This type of system will allow training of the DBMS to be uniform. The architecture will

contain a parallel database in a hierarchical system, also known as cluster architecture; an interconnection network connects nodes that are shared-memory. Software and hardware components The following components are typical of a distributed database management system (DBMS). Not all components have to be in all areas of each node. (See figure 1.) Computer workstations (Nodes) - A number of computer workstations that form the network system. Data communications component (DC) Data communication component at each node that links it to the network. Local database management component (LDBMS) Functions as a standard DBMS, responsible for controlling local data at each site that has a database. Global data dictionary (GDD) - A repository of information about the distributed database. Distributed database management component (DDBMS) Management system for the global database (Rhodes, 2012). Distributed data placement In a hybrid, portions of the database are distributed according to popularity. If all nodes frequently use a set of data, data is shared with all nodes, while other data remains on a local node. This has all the advantages of partition and replication without the disadvantages (Ricardo, 2012).

DISTRIBUTED DATABASE

Strategies for distributed query processing In distributed query processing, leader nodes pass work units to worker nodes and threads running on both the leader and worker nodes perform the work. Sybase best describes query processing (2011): The leader node can be any node in the cluster where a query originates. A worker node can be any node in the cluster that is capable of accepting distributed query processing work. When a query is submitted to a node, work units may be distributed, but only to those nodes that are members of the logical server of the current connection. .. The leader node automatically chooses worker nodes for the distributed query from within the same logical server as the leader node (Sybase). Programmatic access to a database through the internet Hypertext Markup Language, (HTML) is used for presenting content on a browser from the Internet. Standard Generalized Markup Language (SGML) is a complex Meta language and Extensible Markup Language and (XML) is a simpler language that retains the flexibility of SGML and simplicity of HTML allowing multiple user access. Conclusion I propose a solution for the national restaurant chain on a distributed database system as a homogeneous system as this is the best design to save money and resources by producing all nodes with the same hardware and software. The DBMS should contain a parallel database in a hierarchical system, also known as cluster architecture, in a hybrid distributed data placement to produce availability and redundancy of important data.

DISTRIBUTED DATABASE

Figure 1

DISTRIBUTED DATABASE

References Rhodes, L. K. (2012, November 18). Distributed Databases. Retrieved from Juniata: http://jcsites.juniata.edu/faculty/rhodes/dbms/distrib.htm Ricardo, C. (2012). Databases Illuminated (Second Edition ed.). Sudsbury: Jones & Bartlett Learning. Sybase. (2011, May 26). Leader and Worker Nodes. Retrieved from Sybase: http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc00802.1530/ doc/html/jan1289851428857.html