Channel/Membership:
The Membership component is responsible for auto discovering new nodes in the cluster
and also to provide for notifications for any nodes that have not responded with a heartbeat.
The default implementation uses multicast.
In the membership component you configure how your nodes, aka. members, are to be discovered and/or
divided up.
You can always find out more about Apache Tribes
Channel/Sender:
The Sender component manages all outbound connections and data messages that are sent
over the network from one node to another.
This component allows messages to be sent in parallel.
The default implementation uses TCP client sockets, and socket tuning for outgoing messages are
configured here.
You can always find out more about Apache Tribes
Channel/Sender/Transport:
The Transport component is the bottom IO layer for the sender component.
The default implementation uses non-blocking TCP client sockets.
You can always find out more about Apache Tribes
Channel/Receiver:
The receiver component listens for messages from other nodes.
Here you will configure the cluster thread pool, as it will dispatch incoming
messages to a thread pool for faster processing.
The default implementation uses non-blocking TCP server sockets.
You can always find out more about Apache Tribes
Channel/Interceptor:
The channel will send messages through an interceptor stack. Because of this, you have the ability to
customize the way messages are sent and received, and even how membership is handled.
You can always find out more about Apache Tribes
