All geek questions in one place

What source management systems use a document database for storage?

One of those issues that are difficult for Google.

The other day we ran into problems with the speed of our svn repository. The standard solution for this is "more RAM! More CPU!" etc. What made me wonder if there are any version control systems that use the document / nosql database (mongodb, couchdb, etc.) for the database? It seems like it could be natural - but I "There is no expert on the theory of the source-control database. Perhaps there is a way to configure a later control source to use the db document as storage?"

+3
source share
3 answers

No, that I know, and they will not want. Given the difference in the degrees of testing, this is likely to damage reliability (very bad for the source code repository). This will probably also hurt performance due to the impossibility of delta storage.

Please note that Subversion has two very different storage mechanisms, one of which is supported by the built-in DB Berkeley, and the other by simple files. One or the other of these may be better for your use.

Also, since you asked your question fairly broadly, I will comment on Git and TFS.

Git . , . , , 57MiB, ( ) - 56MiB.

TFS (, ) SQL.

+3

Git , MongoDB:)

Git MongoDB, , . Git, NoSQL, DB.

+3

, VCS , noSQL/. couchdb .. ... ​​...

0

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

More articles:


All Articles