N-Region Commit

Currently, for less than strong consistency, the Client SDK emits an acknowledgement for a write operation as soon as the Primary and two secondaries in the Write region have committed. In a multi-region configuration, this can create data-loss since an acknowledged write operation can be lost in the case of the Write region failure. To increase durability and minimize chances of data loss, we propose to enforce that the Write region plus N Read regions must commit before the Client SDK emits an acknowledgement.