The recently released bloomberg comdb2 seems to be on the ‘far right’ of the HA spectrum.
- on detecting a crashed node, or network partition, in the driver code automatically route the request to another node.
- if a node crashes in the middle of a transaction, the transaction will automatically be resumed from where it left off transparently in a different code.
In both above cases, there is no separate ‘retry’ code that needs to be written in apps.
While cockroachdb does offer HA on the box, how does it compare to Comdb2 in the above 2 regards. Specifically how much ‘retry’ logic has to be written in the apps vs how much is transparently handled by the db itself?