You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by GitBox <gi...@apache.org> on 2020/10/06 17:06:47 UTC
[GitHub] [couchdb-documentation] garbados commented on a change in pull request #597: More inclusive terminology
garbados commented on a change in pull request #597:
URL: https://github.com/apache/couchdb-documentation/pull/597#discussion_r500440711
##########
File path: src/intro/consistency.rst
##########
@@ -268,7 +268,7 @@ consistency between multiple database servers. If a client makes a write
operation on server `A`, how do we make sure that this is consistent with
server `B`, or `C`, or `D`? For relational databases, this is a very complex
problem with entire books devoted to its solution. You could use
-multi-master, single-master, partitioning, sharding, write-through caches,
+multi-primary, single-primary, partitioning, sharding, write-through caches,
Review comment:
Multi-leader :+1:
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org