Question

Compare and contrast the numerous advantages and disadvantages of using a DDBMS.

Describe the optimal situations of when to use a DDBMS and why.

Include the CAP Theorem and BASE in your paper and analyze their importance.

Be sure to integrate an analysis of the mobile wireless revolution, smartphones, tablets, etc. with a focus on social media related to the use of a DDBMS.

PLEASE DO NOT HAND WRITE THE ANSWER!! PLEASE ANSER THE QUESTION THOROUGHLY!! IF YOU CANNOT PROVIDE 1,000 WORDS DO NOT ANSWER THE QUESTION!!

Answer 1

Answer 1) The distributed database management system contains the data in multiple locations. That can be in different systems in the same place or across different geographical locations.

Features

• It is used to create, retrieve, update and delete distributed databases.
• It synchronizes the database periodically and provides access mechanisms by the virtue of which the distribution becomes transparent to the users.
• It ensures that the data modified at any site is universally updated.
• It is used in application areas where large volumes of data are processed and accessed by numerous users simultaneously.
• It is designed for heterogeneous database platforms.
• It maintains confidentiality and data integrity of the databases.

The advantages and disadvantages of Distributed database management systems are as follows −

Advantages of DDBMS

• The database is easier to expand as it is already spread across multiple systems and it is not too complicated to add a system.
• The distributed database can have the data arranged according to different levels of transparency i.e data with different transparency levels can be stored at different locations.
• The database can be stored according to the departmental information in an organisation. In that case, it is easier for a organisational hierarchical access.
• there were a natural catastrophe such as fire or an earthquake all the data would not be destroyed it is stored at different locations.
• It is cheaper to create a network of systems containing a part of the database. This database can also be easily increased or decreased.
• Even if some of the data nodes go offline, the rest of the database can continue its normal functions.

Disadvantages of DDBMS

• The distributed database is quite complex and it is difficult to make sure that a user gets a uniform view of the database because it is spread across multiple locations.
• This database is more expensive as it is complex and hence, difficult to maintain.
• It is difficult to provide security in a distributed database as the database needs to be secured at all the locations it is stored. Moreover, the infrastructure connecting all the nodes in a distributed database also needs to be secured.
• It is difficult to maintain data integrity in the distributed database because of its nature. There can also be data redundancy in the database as it is stored at multiple locations.
• The distributed database is complicated and it is difficult to find people with the necessary experience who can manage and maintain it.

Answer 2) Distributed databases offer some key advantages over centralized databases. Many companies are switching to distributed databases (in which the database, as its name implies, is distributed throughout an array of servers in various locations), for a variety of reasons.

Here are the basic reasons why the centralized model is being left behind by many organizations in favor of database distribution:

1. Reliability - Building an infrastructure is similar to investing: diversify to reduce your chances of loss. Specifically, if a failure occurs in one area of the distribution, the entire database does not experience a setback.
2. Security - You can give permissions to single sections of the overall database, for better internal and external protection.
3. Cost-effective - Bandwidth prices go down because users are accessing remote data less frequently.
4. Local access - Similarly to #1 above, if there is a failure in the umbrella network, you can still get access to your portion of the database.
5. Growth - If you add a new location to your business, it's simple to create an additional node within the database, making distribution highly scalable.
6. Speed & resource efficiency - Most requests and other interactivity with the database are performed at a local level, also decreasing remote traffic.
7. Responsibility & containment - Because any glitches or failures occur locally, the issue is contained and can potentially be handled by the IT staff designated to handle that piece of the company.

Answer 3) The CAP theorem applies a similar type of logic to distributed systems—namely, that a distributed system can deliver only two of three desired characteristics: consistency, availability, and partition tolerance (the 'C,' 'A' and 'P' in CAP).

A distributed system is a network that stores data on more than one node (physical or virtual machines) at the same time. Because all cloud applications are distributed systems, it's essential to understand the CAP theorem when designing a cloud app so that you can choose a data management system that delivers the characteristics your application needs most.

Let's take a detailed look at the three distributed system characteristics to which the CAP theorem refers.

Consistency

Consistency means that all clients see the same data at the same time, no matter which node they connect to. For this to happen, whenever data is written to one node, it must be instantly forwarded or replicated to all the other nodes in the system before the write is deemed 'successful.'

Availability

Availability means that that any client making a request for data gets a response, even if one or more nodes are down. Another way to state this—all working nodes in the distributed system return a valid response for any request, without exception.

Partition tolerance

A partition is a communications break within a distributed system—a lost or temporarily delayed connection between two nodes. Partition tolerance means that the cluster must continue to work despite any number of communication breakdowns between nodes in the system.

CAP is basically a continuum along which BASE and ACID are on opposite ends.

CAP is Consistency, Availability, and Partition tolerance. Basically you can pick 2 of those but you can't do all 3.

ACID focuses on Consistency and availability.

BASE focuses on Partition tolerance and availability and throws consistency out the window.