Persistent • Consistent • Fault-tolerant • Asynchronous • Database • Coordination • Framework
Atomix is a high-level asynchronous framework for building fault-tolerant distributed systems. It combines the consistency of ZooKeeper with the usability of Hazelcast to provide tools for managing and coordinating stateful resources in a distributed system. Its strongly consistent, fault-tolerant data store is designed for such use cases as:
- Configuration management
- Service discovery
- Group membership
- Leader election
- Direct messaging
- Broadcast messaging
Users are encouraged to explore the examples in the
/examples directory. Perhaps the most interesting/revelatory example is the leader election example. This example demonstrates a set of replicas that elect a leader among themselves.
To run the leader election example:
- Clone this repository:
git clone --branch master https://github.com/atomix/atomix.git
- Navigate to the project directory:
- Compile the project:
- Run the following three commands in three separate processes from the same root directory of the project:
java -jar examples/leader-election/target/atomix-leader-election.jar logs/server1 localhost:5000 localhost:5001 localhost:5002 java -jar examples/leader-election/target/atomix-leader-election.jar logs/server2 localhost:5001 localhost:5000 localhost:5002 java -jar examples/leader-election/target/atomix-leader-election.jar logs/server3 localhost:5002 localhost:5000 localhost:5001
Each instance of the leader election example starts an
AtomixReplica, connects to the other replicas in the cluster, creates a
DistributedGroup, to perform an election. The first time a node is elected leader it will print the message:
"Elected leader!". When one of the processes is crashed, a new process will be elected a few seconds later and again print the message:
Note that the same election process can be done with
AtomixClients as well. Atomix provides the concept of stateful nodes (replicas) which store resource state changes on disk and replicate changes to other replicas, and stateless nodes (clients) which operate on resources remotely. Both types of nodes can use the same resources in the same ways. This makes Atomix particularly well suited for embedding in server-side technologies without the overhead of a Raft server on every node.
See the website for documentation and examples.