Skip to content

Comment on Coordination Avoidance in Database Systems [pdf]parent

Comments

Ah...you might be interested in Glitch, also a system (from a PL rather than DB perspective) based on eventual consistency:

http://research.microsoft.com/pubs/211297/onward14.pdf

The idea is to let computations proceed uncoordinated, build a dependency graph, and then "fix" computations that read stale information by re-executing them (like transactions, except retry is automatic and effects are undone after re-execution).

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.