durga_mm
Re:Keeping CALM: when distributed consistency is easy
on Wednesday March 06, 2019 @03:13AM (#19317179)
Well written explanation. I think categorizing problem into monotonic and non-monotonic pieces will be especially helpful for a developer when the underlying database provides multiple consistency levels to choose from.
Re:We built a distributed DB capable of running across 100s of global ...
on Tuesday March 05, 2019 @03:07PM (#19313757)
Hi zzzcpan - Yes. The global edge fabric internally uses CRDT operations. It is a conscious choice to not expose the CRDT data types. The idea being the developer work with APIs & Query layer as they do with other databases and underneath the system take care of translating to necessary CRDT operations. Convergent counter is in the works and will be available shortly.
The system has strong consistency within a region (aka datacenter) and strong eventual consistency across data centers. Answering your question, yes we do converge (merge) the changes across regions using conflict-free operations.
Intent prioritization rules comes into picture only when it is impossible for the system to determine the intent of the developer when two conflicting changes occur across regions.
I hope the above helps.
Regards
Re:We built a distributed DB capable of running across 100s of global ...
on Tuesday March 05, 2019 @02:54PM (#19313637)
Hi CharlesW - Thanks. Probably we will publish another post with details on how people can try out the global edge fabric. That probably would be good fit for "Show HN"?
Regards
Re:We built a distributed DB capable of running across 100s of global ...
on Tuesday March 05, 2019 @02:51PM (#19313617)
Hi Ignoramous - Thanks. Very helpful comment with good questions. I will update or cover in the next post.
Regards
Re:We built a distributed DB capable of running across 100s of global ...
on Tuesday March 05, 2019 @02:49PM (#19313603)
Hi willvarfar - I am one of the authors of the post. Very good feedback. Appreciate much. I will update the post or write a separate post on `double-spend` problem with clear example.