[GitHub] [couchdb-documentation] flimzy commented on a change in pull request #597: More inclusive terminology

[GitBox <gi...@apache.org>]

flimzy commented on a change in pull request #597:
URL: https://github.com/apache/couchdb-documentation/pull/597#discussion_r500061914



##########
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:
       I'm not sure if we came to an agreement on this term elsewhere, but "multi-primary" is a bit of an oxymoron, in a way that "multi-master" isn't.  Primary literally means "first", whereas "master" doesn't have that connotation.
   
   If this is still open for discussion, perhaps we can consider "multi-leader" instead?
   
   Or, my own 2¢, we can stick with "master", since this term isn't nearly as loaded as the "s" word, which CouchDB has never used.




----------------------------------------------------------------
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