Revision as of 10:21, 29 October 2019 edit Haeinous (talk \| contribs) Extended confirmed users 9,257 edits copyedits, added references, trimmed see also section ← Previous edit		Revision as of 06:53, 2 September 2020 edit undo NicDumZ (talk \| contribs) Extended confirmed users 983 edits Add a pointer to leader election. This feels relevant to parts of the industry where "Leader election" has replaced "Master election". (Master election redirects here) Next edit →
Line 17: * '''Passive replication''', which involves processing every request on a single replica and transferring the result to the other replicas When one ~~master~~leader replica is designated via [[leader election]] to process all the requests, the system is using a primary-backup or [[Master-slave (computers)\|master-slave]] scheme, which is predominant in [[high-availability cluster]]s. In comparison, if any replica can process a request and distribute a new state, the system is using a multi-primary or [[Multi-master replication\|multi-master]] scheme. In the latter case, some form of [[distributed concurrency control]] must be used, such as a [[distributed lock manager]]. [[Load balancing (computing)\|Load balancing]] differs from task replication, since it distributes a load of different computations across machines, and allows a single computation to be dropped in case of failure. Load balancing, however, sometimes uses data replication (especially [[multi-master replication]]) internally, to distribute its data among machines.

Replication (computing): Difference between revisions