flimzy commented on a change in pull request #268: Rewrite sharding documentation URL: https://github.com/apache/couchdb-documentation/pull/268#discussion_r203280029
########## File path: src/cluster/sharding.rst ########## @@ -12,290 +12,490 @@ .. _cluster/sharding: -======== -Sharding -======== +================ +Shard Management +================ .. _cluster/sharding/scaling-out: -Scaling out -=========== +Introduction +------------ -Normally you start small and grow over time. In the beginning you might do just -fine with one node, but as your data and number of clients grows, you need to -scale out. +A `shard +<https://en.wikipedia.org/wiki/Shard_(database_architecture)>`__ is a +horizontal partition of data in a database. Partitioning data into +shards and distributing copies of each shard (called "shard replicas" or +just "replicas") to different nodes in a cluster gives the data greater +durability against node loss. CouchDB clusters automatically shard +databases and distribute the subsections of documents that compose each Review comment: "subsections of ducments" sounds like sharding happens on a sub-document level. Is that true? (are attachments and documents sharded separately, for example?) If so, is this clarified somewhere? Or should this read "subsets of documents"? ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
