The current MongoMK implementation has some disadvantages we would like to address:
- some of the collections can't be sharded easily
- instances synchronize on the "sync" collection
- concurrent changes to the same node are detected relatively late,
and merging them requires a re-try
To address those issues, we will write a prototype of a MongoMK implementation that uses a different storage model, that is, only one "nodes" collection.