
TL;DR
This paper challenges the assumption that only the system managing an object's state can provide its integrity, demonstrating that objects can maintain integrity independently of state management.
Contribution
It introduces a novel approach where objects preserve their invariants and integrity separately from the system managing their state.
Findings
Objects can maintain integrity independently of state management.
The traditional assumption that state management and integrity must be coupled is incorrect.
This separation enables new designs for reliable distributed systems.
Abstract
An important use of computational systems is updating the state of an object while preserving some set of invariants. That object might be a file, a row in a database, or perhaps an entry in a distributed system. Its invariants may place limits on its relationships with other objects, and generally include maintaining a unique identity across updates. The system maintaining these invariants is responsible for not equivocating, or presenting conflicting versions of an object. We call this absence of equivocation integrity. Today the system providing integrity to an object also manages its state. Indeed, it has long been assumed that this must be the case, and that only the system managing an object's state can provide it with integrity. We show that this assumption is wrong. Objects can maintain the integrity of one system while having their state fully managed by another.
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
Taxonomy
TopicsDistributed systems and fault tolerance · Advanced Database Systems and Queries · Data Quality and Management
