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
DistributedMessageBuswhich is direct point-to-point, fast but unreliable messaging.
DistributedTopicpublishes to all consumers as you mentioned.
DistributedMembershipGroupnow allows reliable messaging between specific members of the group, so you can e.g. send a task to be handled by a specific group member.
DistributedQueueis the right data structure to use for work queues, but there's been some discussion about creating a
DistributedWorkQueuethat distributes work among consumers. I think there's a GitHub issue for it. But the problem is that the Copycat event framework pipelines events to clients, and that's not great for work. We'll have to add some commands to
DistributedWorkQueueto ack a previous item and fetch the next queue item in one request. But this should be easy to do. I'll submit a PR for it probably before you're around again.