Re:Antidote: CRDT-based distributed database
by runT1ME on Thursday December 07, 2017 @11:54AM
(#15871651)
CRDTs accumulate garbage, and need a global "sync" to GC. How do you mitigate this from having performance impacts?
[ Parent
| on HN ]
Re:Antidote: CRDT-based distributed database
by anne_biene on Thursday December 07, 2017 @04:55PM
(#15874719)
[Disclaimer: I am an Antidote maintainer]
Some CRDTs support garbage collection directly - if you run them in a causally consistent environment. Antidote is causally consistent and has a Set and Map implementation that work like this; for these CRDTs you don't need a global sync.
Re:Antidote: CRDT-based distributed database
by runT1ME on Tuesday December 12, 2017 @07:09PM
(#15910777)
Thanks for the reply. Don't you negate some of the advantages of CRDTs by mandating casually consistent environments? Can you speak to that more?
Re:Antidote: CRDT-based distributed database
by marc_shapiro on Sunday December 10, 2017 @09:54AM
(#15891615)
This was true of the early CRDT designs, but they have improved since then. You will find plenty of inspiration here: http://dblp.uni-trier.de/pers/hd/b/Baquero:Carlos