These are chat archives for atomix/atomix
We are no longer monitoring this channel, please join Slack! https://join.slack.com/t/atomixio/shared_invite/enQtNDgzNjA5MjMyMDUxLTVmMThjZDcxZDE3ZmU4ZGYwZTc2MGJiYjVjMjFkOWMyNmVjYTc5YjExYTZiOWFjODlkYmE2MjNjYzZhNjU2MjY
commitIndexis held only in memory since it can always be rebuilt from the log. The leader election algorithm ensures that any node that's elected leader will have all committed entries, so there's no risk of losing commits by losing the commit index. As for flushing entries to disk, they're only flushed when a node increases its commit index to reduce the frequency of flushes to disk. This is more for the leader and really should only be done on the leader since followers should be flushing to disk after writing a batch. Will have to change that.
Storageobject to write to disk or hold state in memory, and the state for a resource is simply replicated among the nodes in the cluster. An
AtomixReplicawill store the state of resources locally and replicate them to other nodes. An
AtomixClientwill connect to replicas remotely to access resource state.