Add resource "CRDTs for Mortals - James Long at dotJS 2019" Accepted
The requested resource couldn't be found.
Changes: 8
-
Add CRDTs for Mortals - James Long at dotJS 2019
- Title
-
- Unchanged
- CRDTs for Mortals - James Long at dotJS 2019
- Type
-
- Unchanged
- Video
- Created
-
- Unchanged
- 2019
- Description
-
- Unchanged
- What do CRDTs and frontends have to do with each other? James talks about how CRDTs finally deliver on the promise of local-first apps, which provide superior user experience, and explains how simple CRDTs can be and how to leverage them to create robust local-first apps.
- Link
-
- Unchanged
- https://www.dotconferences.com/2019/12/james-long-crdts-for-mortals
- Identifier
-
- Unchanged
- no value
Resource | v1 | current (v1) -
Add Conflict-free Replicated Data Types: An Overview
- Title
-
- Unchanged
- Conflict-free Replicated Data Types: An Overview
- Type
-
- Unchanged
- Paper
- Created
-
- Unchanged
- 2018-06-26
- Description
-
- Unchanged
- Internet-scale distributed systems often replicate data at multiple geographic locations to provide low latency and high availability, despite node and network failures. Geo-replicated systems that adopt a weak consistency model allow replicas to temporarily diverge, requiring a mechanism for merging concurrent updates into a common state. Conflict-free Replicated Data Types (CRDT) provide a principled approach to address this problem. This document presents an overview of Conflict-free Replicated Data Types research and practice, organizing the presentation in the aspects relevant for the application developer, the system developer and the CRDT developer.
- Link
-
- Unchanged
- https://arxiv.org/pdf/1806.10254.pdf
- Identifier
-
- Unchanged
- no value
Resource | v1 | current (v1) -
Add Logical Physical Clocks and Consistent Snapshots in Globally Distributed Databases
- Title
-
- Unchanged
- Logical Physical Clocks and Consistent Snapshots in Globally Distributed Databases
- Type
-
- Unchanged
- Paper
- Created
-
- Unchanged
- 2014-04
- Description
-
- Unchanged
- There is a gap between the theory and practice of distributed systems in terms of the use of time. Theory of distributed systems shunned the notion of time, and introduced “causality tracking” as a clean abstraction to reason about concurrency. The practical systems employed physical time (NTP) information but in a best effort manner due to the difficulty of achieving tight clock synchronization. In an effort to bridge this gap and reconcile the theory and practice of distributed systems on the topic of time, we propose a hybrid logical clock, HLC, that combines the best of logical clocks and physical clocks. HLC captures the causality relationship like logical clocks, and enables easy identification of consistent snapshots in distributed systems. Dually, HLC can be used in lieu of physical clocks since it maintains its logical clock to be always close to the NTP clock. Moreover HLC fits in to 64 bits NTP timestamp format, and is masking tolerant to NTP kinks and uncertainties.
- Link
-
- Unchanged
- https://cse.buffalo.edu/tech-reports/2014-04.pdf
- Identifier
-
- Unchanged
- no value
Resource | v1 | current (v1) -
Add Hybrid logical clock
- Title
-
- Unchanged
- Hybrid logical clock
- Description
-
- Proposed
- Hybrid logical clock, HLC, combines the best of logical clocks and physical clocks. HLC captures the causality relationship like logical clocks, and enables easy identification of consistent snapshots in distributed systems. Dually, HLC can be used in lieu of physical/NTP clocks since it maintains its logical clock to be always close to the NTP clock. Moreover HLC fits in to 64 bits NTP timestamp format, and is masking tolerant to NTP kinks and uncertainties.
- Current
- Hybrid logical clock, HLC, combines the best of logical clocks and physical clocks. HLC captures the causality relationship like logical clocks, and enables easy identification of consistent snapshots in distributed systems. Dually, HLC can be used in lieu of physical/NTP clocks since it maintains its logical clock to be always close to the NTP clock. Moreover HLC fits in to 64 bits NTP timestamp format, and is masking tolerant to NTP kinks and uncertainties.
- Link
-
- Proposed
- no value
- Current
- https://cse.buffalo.edu/tech-reports/2014-04.pdf
Topic | v1 | current (v3) -
Add Conflict-free replicated data type (CRDT) relates to CRDTs for Mortals - James Long at dotJS 2019
- Current
- relates to
Topic to resource relation | v1 -
Add Conflict-free replicated data type (CRDT) treated in Conflict-free Replicated Data Types: An Overview
- Current
- treated in
Topic to resource relation | v1 -
Add Hybrid logical clock has official Logical Physical Clocks and Consistent Snapshots in Globally Distributed Databases
- Current
- has official
Topic to resource relation | v1 -
Add CRDTs for Mortals - James Long at dotJS 2019 references Logical Physical Clocks and Consistent Snapshots in Globally Distributed Databases
- Current
- references
Resource to resource relation | v1