We use Hazelcast at Verizon Labs for a couple services, and one of the issues we ran into is how much work it takes to replicate split brain to test various and

We use Hazelcast at Verizon Labs for a couple services, and one of the issues we ran into is how much work it takes to replicate split brain to test various and custom merge policies. When reading that the distributed map implements the ConcurrentHashMap interface we were immediately skeptical, but it took more work to prove our skepticism was founded. Hazelcast has a fantastic foundation for building clustered applications, but some of the design choices they made both internally and API wise are not choices we would have made. We are moving to a custom merge policy because of some of these choices.