TWO SEPARATED DATABASES

• A LOAN BUSINESS COMPANY HAS TWO DIFFERENT SEPARATED LOCATIONS TO PROVIDE LOANS TO CUSTOMERS

• This company uses two separated databases which have no communication and do hot share data in real time

• According to company policy, a customer can have one loan at the time before to get another to any location but the first loan must be paid off.

A customer can have two different accounts in these two locations

Problem

• HOW TO PREVENT SOMEONE TO GET A LOAN WHILE HE DID NOT PAID THE FIRST ONE.

• A manager approached me to help them to prevent this situation to happen over and over.

Solution

1. Implement a database-link cheap solution

2. Implement a distribution database management system: adequate solution.

3. Implement a golden gate, the replication tools: to much expensive

I want to implement a distributed database management system, replication tools can really solve this business problem and save them money and customers.

As two databases will able to communicate, we will able to prevent in case of duplicate loan when the first loan is not paid off.

My idea is to choose the distributed database management system because it is a solution for this small company and if this company plans to grow in the future de distributed database management system is the true solution. I want to develop more on distributed database management system.