    Merge and serialization functions for Riak  Tom Crayford
(Yeller) describes how to test the merge and serialization
functions used to resolve potential conflicts in Riak:  The way
I prefer using riak, is with allow_mult=true. This means that
whenever you have causally conflicting writes to a key, riak
will store all of them, and upon your next read of that key you
have to resolve them yourself. Designing your datatypes such
that you can merge them is a huge topic, and an area of active
research. However, even once you have a merge strategy worked
out, how can you be sure that your reasoning is good? The merge
functions you use have to obey a few properties: they have to be
commutative, idempotent and associative, or you’ll mess things
up when you have conflicts  Original title and link: Merge and
serialization functions for Riak (NoSQL database©myNoSQL)