> Even Riak, the poster child for this sort of thing, was straight up last-write-wins for years while they were making fun of everyone else. Disclaimer: I've o

> Even Riak, the poster child for this sort of thing, was straight up last-write-wins for years while they were making fun of everyone else. Disclaimer: I've only used Riak for toy projects, never on a real production app, but... I think that's being overly simplistic. They've had vector clocks from basically the beginning (though I gather they've been superseded now) and have favored the strategy of offloading conflict resolution to the code that's reading the value. Without implementing that conflict resolution, then it might default to last-write-wins, but that's not the same thing as "straight up last-write-wins" since they give you the tools to implement something more intelligent.