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
DistributedGrouppartitions were removed as they were determined to be outside the scope of Atomix 1.0, potentially too opintimated, and didn't solve any problem that can't already be solved with
DistributedGroup. The same semantics can be achieved simply by maintaining multiple
DistributedGroups, and that is the pattern we'd prefer to encourage over more complexity in resources themselves. Resources should be composable and limited in their scope to things that can't be done through composition or client-side operations.
DistributedGroupstate machine is just a map of members which should be tiny. Atomix resource shared expensive resources like connections and heartbeats. So, 100 groups will all communicate on the same socket and still have a single heartbeat.