ID represents a generic identifier in format of Zone.Node

Key type of the key-value database TODO key should be general too

Value type of key-value database

sort operations by invocation time

Ballot is ballot number type combines 32 bits of natual number and 32 bits of node id into uint64

Accept phase 2a

Accept phase 2a

Accept phase 2a

Accepted phase 2b

Accepted phase 2b

Accepted phase 2b

Ack from follower to leader

AdminClient interface provides fault injection opeartion

Bconfig holds all benchmark configuration

Benchmark is benchmarking tool that generates workload and collects operation history and latency

Block contains some amount of data in blockchain

CMap is concurrent map with generic key and value as interface{}

CSet is concurrent set with generic data as interface{}

Client interface provides get and put for key value store

Client overwrites read operation for Paxos

Codec interface provide methods for serialization and deserialization combines json and gob encoder decoder interface

Command of key-value database

CommandBallot conbines each command with its ballot number

Commit phase 3

Commit phase 3

Commit phase 3

Commit phase 3

Config contains every system configuration

DB is general interface implemented by client to call client library

Database defines a database interface TODO replace with more general StateMachine interface

Get message

GetReply message returns value and version

HTTPClient inplements Client interface with REST API

HashRing implements a hash ring like Chord using md5

History client operation history mapped by key

Info is reply message for both query and Move message Info announce new ballot number

LeaderChange switch leader

LeaderChange switch leader

LeaderChange switch leader

Limiter limits operation rate when used with Wait function

Miner is the maintainer of blockchain

Move message suggest master to move an object

************************** * Intra-Cluster Messages * **************************/ NewBallot message starts a new leader election

NewLeader message actives leader

Node is the primary access point for every replica it includes networking, state machine and RESTful API server

P1a prepare message

********************** * Paxos Messages * **********************/

P1a prepare message

P1b promise message

P1b promise message

P2a accept message

P2a accept message

P2a accept message

P2b accepted message

P2b accepted message

P2b accepted message

P3 commit message

P3 commit message

P3 commit message

Paxos instance

Paxos instance

Policy defines a trigger for data access patterns, that can be used in data migration protocols

************************** * Inter-Replica Messages * **************************/ Prepare phase 1a

************************** * Inter-Replica Messages * **************************/ Prepare phase 1a

************************** * Inter-Replica Messages * **************************/ Prepare phase 1a

Promise phase 1b

Promise phase 1b

Promise phase 1b

Proposal from leader to followers

*********************** * Master Messages * ***********************/ Query message request the current info on key from master

Quorum records each acknowledgement and check for different types of quorum satisfied