When to use distributed database?

Asked

Viewed 298 times

6

I would like to know an example in which situation I would need to use a distributed database?

1 answer

4


Distributed Databases

The concept Distributed Database basically consists of keeping separate instances of a database running simultaneously.


There are several ways to distribute a database and these can be:

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

When database distribution is needed?

  • Need to ensure availability, if one server crashes the other will probably be available.
  • Security to prevent information loss.
  • Improve database performance, instead of 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 adopt one of the measures below:

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

Doubling, 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 in a predefined interval to ensure that each distributed location has the same data. In the duplication process, users can change only the master database. This ensures that data is always intact in other instances.

Browser other questions tagged

You are not signed in. Login or sign up in order to post.