Geek Answers Handbook

Why is the RDBMS Partition Tolerant in the CAP Theorem and why is it available?

Two points that I do not understand about RDBMS being CA in the CAP theorem:

1) It says that RDBMS is not Partition Tolerance , but how does RDBMS share Tolerant less than other technologies like MongoDB or Cassandra? Is there an RDBMS installation where we abandon the CA to make it AP or CP?

2) How is CAP available? Is this through master subordinate configuration? As in the case when the master dies, the subordinate takes notes?

I am new to DB architecture and CAP theorem, so please bear with me.

+13
source share
5 answers

Currently, many databases have different configurations and depending on the settings you set, these can be CA, CP, AP, etc., but they cannot all three at the same time. Some databases actually make efforts to support all three, but still give priority to their particular path.

For example, MySQL may be CP and CA depending on configurations. By default, this is a CA because it follows the paradigm of the master slave, whose data is replicated to the slaves. Tolerance is divided into the fact that a set of slaves loses connection with the master and therefore decides to choose a new master that creates two masters with its own set of slaves.

MySQL , . CP , . , .

, MySQL , CAP, , , . , , .

CAP, CAP. , . , CA, - AP ..

+17

, RDBMS CAP. noSQL IBM DB2.

IBM DB2 3 CAP

  1. C: : - .

  2. A: : , , . , , .

  3. : : . DB2, , , 2 , . . 12 , . , . , .

, 3 CAP.

.

0

- CA, . . , (, -, ) ( , ), ( , ).

AlwaysOn master-slave RDBMS , . , .

, RDBMS - , , . .

0

More articles:


All Articles