Redundant

GoshawkDB maintains copies of each object on multiple nodes. There is no leader/follower design: all nodes are equal and all copies of each object are equal. Transactions must contact only a majority of copies of each object to progress, so GoshawkDB will continue to work successfully in the presence of failures, provided a majority of copies of each object can still be contacted. GoshawkDB is sharded: each object need not be copied to every node. GoshawkDB uses the Paxos Synod protocol to achieve consensus. Committed transactions are written and flushed to disk before the client learns the transaction outcome.