Do document-oriented databases really have integrity?

I come from the background of MySQL, and I'm interested in document-oriented databases, in particular CouchDB. One of the things that interest me is data integrity. How are document-oriented databases handled? For example, in RDBMSes there are ways to prevent duplicate entries or to ensure that if you have one bit of information, you will have another or nothing at all.

I assume, in a broader sense, to my question, what types of problems are cut out by RDBMSes compared to the problems that DODBes use? I looked through some of the other stackoverflow questions for an explanation, but did not find any good ones.

In addition, when working with my databases, I make a lot of reports with summing and averaging values ​​and historical trend. Is this suitable for documented databases?

+3
source share
1 answer

Most document databases support only limited integrity or integrity checks. They rely on the application to guarantee the correctness of the data. I can tell you how this happens in CouchDB.

. , . , , , .., RDBMS . "" . - - . . , - . .

, . . .. . , , , , - , .

, . . - . "" , . , , . . Rob Conerys.

+2

Source: https://habr.com/ru/post/1728316/


All Articles