| Class | Description |
|---|---|
| BFTNonValidatingNotaryService |
A non-validating notary service operated by a group of parties that don't necessarily trust each other.
|
| BFTSMaRt |
Implements a replicated transaction commit log based on the BFT-SMaRt
consensus algorithm. Every replica in the cluster is running a
class BFTSMaRt.Replica maintaining the state, and a class BFTSMaRt.Client is used
to relay state modification requests to all class BFTSMaRt.Replicas. |
| BFTSMaRtConfig |
BFT SMaRt can only be configured via files in a configHome directory.
Each instance of this class creates such a configHome, accessible via path.
The files are deleted on
PathManager.close typically via use, see class PathManager for details. |
| BFTSMaRtConfigKt | |
| DistributedImmutableMap<K,V> |
A distributed map state machine that doesn't allow overriding values. The state machine is replicated
across a Copycat Raft cluster.
|
| InMemoryTransactionVerifierService | |
| NonValidatingNotaryFlow | |
| OutOfProcessTransactionVerifierService | |
| PathManager<T extends PathManager<T>> |
An instance of this class is a handle on a temporary path.
If necessary, additional handles on the same path can be created using the
PathManager.handle method.
The path is (recursively) deleted when PathManager.close is called on the last handle, typically at the end of a use expression.
The value of eager cleanup of temporary files is that there are cases when shutdown hooks don't run e.g. SIGKILL. |
| PersistentUniquenessProvider |
A RDBMS backed Uniqueness provider
|
| RaftNonValidatingNotaryService |
A non-validating notary service operated by a group of mutually trusting parties, uses the Raft algorithm to achieve consensus.
|
| RaftUniquenessProvider |
A uniqueness provider that records committed input states in a distributed collection replicated and
persisted in a Raft cluster, using the Copycat framework (http://atomix.io/copycat/).
|
| RaftUniquenessProviderKt | |
| RaftValidatingNotaryService |
A validating notary service operated by a group of mutually trusting parties, uses the Raft algorithm to achieve consensus.
|
| SimpleNotaryService |
A simple Notary service that does not perform transaction validation
|
| ValidatingNotaryFlow |
A notary commit flow that makes sure a given transaction is valid before committing it. This does mean that the calling
party has to reveal the whole transaction history; however, we avoid complex conflict resolution logic where a party
has its input states "blocked" by a transaction from another party, and needs to establish whether that transaction was
indeed valid.
|
| ValidatingNotaryService |
A Notary service that validates the transaction chain of the submitted transaction before committing it
|