Distributed database. Examples, promises and problems

Share on facebook
Share on twitter
Share on linkedin
Share on telegram
Share on whatsapp


A distributed database is distributed over multiple nodes, as a collection of different databases, logically interrelated, in a computer network. This type of database promotes integration, not centralization (these are two very different concepts), and has like objective transparency in data distribution.


Photo credits: blessed 68

Those who bet on the use of a distributed database seek to make their systems more available. This effort in favor of availability responds to an increasingly acute need of many companies and requires a large number of different types of hardware capable of responding to various requests.. This way of working makes it possible to avoid fatal errors related to service failures..r, that are overcome by running, not just one, but a group of servers in different locations and with horizontal scaling.

Applications of a distributed database they are very varied. Can be used in manufacturing environments, especially when production takes place in multiple plants, it is also the option of choice for airlines and hotel chains, multinational groups and, in general, the alternative posed by any organization with a decentralized organizational structure.

Promises and problems of a distributed database

Systems distributed database ensure the availability of data with the necessary agility in today's market environment. At the same time, offer the following advantages:

  1. They contribute to the improvement of performance at the organization level.
  2. Facilitate system expansion.
  3. Optimize the transparency of distributed and replicated data.
  4. They favor the agility of operations.
  5. They improve the visibility of corporate information.

Despite this, Benefiting from all these benefits depends on Being able to overcome the complications that are generally associated with the use of a relational database, or a system of them., like those that have to do with:

A / Consistency: the limitations of relational databases in this area, and what it explains CAP theoremThey are not the only ones who can pose an obstacle; but you also have to pay attention to what, instead of forcing a choice between consistency and agility, propose the choice between consistency and latency. To minimize the effects of both restrictions, the answer is work for time.

B / Complexity: Lack of standards or user experience can affect the performance of a distributed database system. At the same time, this environment makes more difficult to perform an information integrity check that, as an example, the one that can be done relationally. To end, it should not be forgotten that the architectural designs you need are much more complex than traditional alternatives. All of this has a clear impact on associated costs to pay attention.

C / Security: exceed the security issues presented by a distributed database compared to a relational database depends on take actions like adding granularity in access. At the same time, When opting for a system of this type, it is always advisable to have the necessary expert support to carry out reviews of the relevant codes that help to detect possible problems.

Is your organization prepared to overcome the challenges that separate you from the benefits of having a distributed database? Integration is the first step to ensure data availability, a premise that is even more important in hybrid and cloud environments. You have a plan?

(function(d, s, id) {
var js, fjs = d.getElementsByTagName(s)[0];
if (d.getElementById(id)) return;
js = d.createElement(s); js.id = id;
js.src = “//connect.facebook.net/es_ES/all.js#xfbml=1&status=0”;
fjs.parentNode.insertBefore(js, fjs);
}(document, ‘script’, 'facebook-jssdk'));

Subscribe to our Newsletter

We will not send you SPAM mail. We hate it as much as you.