When to use distributed database?

Distributed Databases

The Distributed Database concept basically consists of maintaining distinct instances of a database running concurrently.

There are several ways to distribute a database:

• Multiple physical locations
• Local networks
• Intranet / Extranets
• Distinguished Providers

When database distribution becomes necessary?

• Need to ensure availability if one server drops the other is likely to be available.
• Security to prevent loss of information.
• Improve database performance, rather than a single machine being responsible for providing the data Two or more machines assume this responsibility

But unfortunately as every solution has its problems, distributing a bunch of data requires you to do one of the following:

Replication , involves the use of software that identifies changes to the database. Once the changes have been identified, the replication process causes all databases to look the same. The replication process can be complex and time-consuming depending on the size and number of distributed databases. This process may also require a lot of computer time and resources.

Duplication , on the other hand, with less complexity, this process basically identifies a database as a master and then duplicates that database in another location. The duplication process is usually done at a predefined interval to ensure that each distributed site has the same data. In the replication process, users can only change the master database. This ensures that data is always up-to-date in other instances.