Difference between revisions of "Distributed Consistency"

From MgmtWiki
Jump to: navigation, search
(Solutions)
(Solutions)
Line 4: Line 4:
 
* Decentralized Consistency is an easier problem when each [[Registration Authority]] is given control of a portion of a name space where it can control registration.
 
* Decentralized Consistency is an easier problem when each [[Registration Authority]] is given control of a portion of a name space where it can control registration.
 
* With the advent of fully distributed systems where any one machine could desire the ability to create an identifier, this problem needs a practical resolution.
 
* With the advent of fully distributed systems where any one machine could desire the ability to create an identifier, this problem needs a practical resolution.
 +
==Problems==
 +
* Coordination is tricky to implements and expensive in terms of latency added.
 +
 
==Solutions==
 
==Solutions==
 
*CALM<ref>Joseph Hellerstein and Peter Alvaro, ''Keeping CALM: When Distributed Consistency is Easy'' (2020-09) '''CACM 63''' no 3 pp. 72ff</ref>
 
*CALM<ref>Joseph Hellerstein and Peter Alvaro, ''Keeping CALM: When Distributed Consistency is Easy'' (2020-09) '''CACM 63''' no 3 pp. 72ff</ref>

Revision as of 15:00, 8 September 2020

Full Title or Meme

Distributed Consistency in Identity Management is required when more than one process might be assigning identifiers that are required to be unique.

Context

  • Decentralized Consistency is an easier problem when each Registration Authority is given control of a portion of a name space where it can control registration.
  • With the advent of fully distributed systems where any one machine could desire the ability to create an identifier, this problem needs a practical resolution.

Problems

  • Coordination is tricky to implements and expensive in terms of latency added.

Solutions

References

  1. Joseph Hellerstein and Peter Alvaro, Keeping CALM: When Distributed Consistency is Easy (2020-09) CACM 63 no 3 pp. 72ff