Latest Activity In Study Groups

Join Your Study Groups

VU Past Papers, MCQs and More

We non-commercial site working hard since 2009 to facilitate learning Read More. We can't keep up without your support. Donate.


Total Marks 5
Starting Date Monday, February 15, 2021
Closing Date Tuesday, February 16, 2021
Status Open
Question Title GDB Topic
Question Description

GDB Topic

 

Orchid bank is a private sector bank which has branches in different countries. Orchid bank uses database for the storage of clients’ data because databases can store very large numbers of records efficiently. By using database, we can add, edit or delete data easily. It is more efficient in data searching and data sorting. Database can be used by more than one user to access same data simultaneously.

As a database designer, which type of database (distributed database & centralized database) you will use in this scenario to ensure data consistency, easy management and easy backup?

Also, what you think that replication of database suitable in the above given scenario?

Note: Your GDB answer should not exceed 4 to 5 lines.

GDB Instructions:

1.      You need to provide precise and to the point answer, avoid irrelevant details.

2.      Copied from the internet or another student will get zero marks.

3.      You cannot participate in the discussion after the due date via email.

4.      The GDB will open and close on specified date and time. Please note that no grace day or extra time will be given for posting comments on GDB.

Views: 463

Replies to This Discussion

Share the GDB Question & Discuss Here....         

Stay touched with this discussion, Solution idea will be uploaded as soon as possible in replies here before the due date.

CS403_GDB_Solution_Fall_2020

Click on the below link to download the file

CS403_GDB_Solution_Fall_2020.docx

(GDB) for CS403

W S STUDIO
Dear Students,

Graded Discussion Board (GDB) for CS403 course will be opened on Monday, February 15, 2021 and it will close on Tuesday, February 16, 2021.

 

 GDB Topic

Orchid bank is a private sector bank which has branches in different countries. Orchid bank uses database for the storage of clients’ data because databases can store very large numbers of records efficiently. By using database, we can add, edit or delete data easily. It is more efficient in data searching and data sorting. Database can be used by more than one user to access same data simultaneously.

As a database designer, which type of database (distributed database & centralized database) you will use in this scenario to ensure data consistency, easy management and easy backup?

Also, what you think that replication of database suitable in the above given scenario?

Note: Your GDB answer should not exceed 4 to 5 lines.

 

GDB Instructions:

  1. You need to provide precise and to the point answer, avoid irrelevant details.
  2. Copied from the internet or another student will get zero marks.
  3. You cannot participate in the discussion after the due date via email.
  4.   The GDB will open and close on specified date and time. Please note that no grace day or extra time will be given for posting comments on GDB

 

Answer:

In my opinion distributed database is better in the given scenario.

Yes, in my option replication of database suitable in the above given scenario.

The Advantages of Using Distributed Databases for the Banking Industry

Banks must be able to access a customer's information from any branch at a moment's notice. These information requests can include checking account balances, loan amounts and credit status. A distributed database system separates a business's data by business function or geographical area. Banks often use distributed database systems, because these systems are configured to carry out specific business tasks in different locations while allowing those locations to communicate freely with one another. These systems offer banks several advantages over non distributed systems.

Longer Uptime

A database management system that requires banks to access financial data stored in a central location can be vulnerable to downtime. The central location may be inaccessible due to communication infrastructure problems, natural disaster or malicious attack. The distributed system lets banks access the information they need at any time, regardless of the uptime status of a central server. A distributed database management system allows banks to reroute their information requests around the inaccessible location to another available site.

Faster Performance

A distributed database management system relies on multiple processors distributed throughout the network, and this is a plus. The distributed nature of the network allows each processor to take on part of the data access chores, rather than relying on a single processor to handle all the requests at once. This system allows banks to access the data they need faster and more reliably than they would with a centralized system.

Lower Costs

A distributed database management system allows each bank branch to have its own copy of the latest customer data. The bank's copy of the customer's account data allows the bank to record and process each transaction locally, rather than sending it forward to a central server. The ability to process transactions locally saves on communication costs. If a problem occurs with the local system, it can be addressed at the local level, which also saves time and money.

Easier Growth

A centralized database management system often lacks the flexibility to handle substantial growth. When such a system needs to expand its capabilities, the bank may need to purchase new equipment, upgraded software or both. The distributed database management system structure supports modular growth. As a bank expands into new geographic areas or offers new financial services, database managers can add the new functionality to the distributed database system without affecting the current system's functions.

 

Database replication

Database replication is the frequent electronic copying of data from a database in one computer or server to a database in another -- so that all users share the same level of information. The result is a distributed database in which users can quickly access data relevant to their tasks without interfering with the work of others. Numerous elements contribute to the overall process of creating and managing database replication.

 

How database replication works

Database replication can either be a single occurrence or an ongoing process. It involves all data sources in an organization's distributed infrastructure. The organization's distributed management system is used to replicate and properly distribute the data amongst all the sources.

 

Overall, distributed database management systems (DDBMS) work to ensure that changes, additions and deletions performed on the data at any given location are automatically reflected in the data stored at all the other locations. DDBMS is essentially the name of the infrastructure that allows or carries out database replication -- the system that manages the distributed database, which is the product of database replication.

 

The classic case of database replication involves one or more applications that connect a primary storage location with a secondary location that is often off site. Today, those primary and secondary storage locations are most often individual source databases -- such as Oracle, MySQL, Microsoft SQL and MongoDB -- as well as data warehouses that amalgamate data from these sources, offering storage and analytics services on larger quantities of data. Data warehouses are often hosted in the cloud.

Advantages and disadvantages

Database replication is often overseen by a database or replication administrator. A properly implemented replication system can offer several advantages, including the following:

 

Load reduction. Because replicated data can be spread over several servers, it eliminates the likelihood that any one server will be overwhelmed with user queries for data.

Efficiency. Servers that are less burdened with queries can offer improved performance to fewer users.

High availability. Employing multiple servers with the same data ensures high availability, meaning that if one server goes down, the entire system can still provide acceptable performance.

Many disadvantages of database replication stem from poor general data governance practices. These disadvantages include the following:

 

Data loss. Data loss can occur during replication when incorrect data or iterations or updates of a database are copied and, consequently, important data is deleted or unaccounted for. This can happen if the primary key used to verify the quality of data in the replica is malfunctioning or incorrect. It can also occur if database objects are incorrectly configured within the source database.

Data inconsistency. Similarly, incorrect or out-of-date replicas can cause different sources to be out of sync with each other. This may lead to wasted data warehouse costs that are spent needlessly analyzing and storing irrelevant data.

Multiple servers. Running multiple servers has an inherent maintenance and energy cost associated. It requires either the organization or a third party to address these costs. If a third party handles them, the organization runs the risk of vendor lock-in or service issues beyond the organization's control.

 

CS403_GDB_Solution_Fall_2020

Click on the below link to download the file

CS403_GDB_Solution_Fall_2020.docx

RSS

© 2021   Created by + M.Tariq Malik.   Powered by

Promote Us  |  Report an Issue  |  Privacy Policy  |  Terms of Service