These are chat archives for atomix/atomix

3rd
Jul 2017
Jordan Halterman
@kuujo
Jul 03 2017 19:45

We still use Netty, but rather than connecting clients to servers and using sockets for bi-directional communication, all clients/servers start Netty TCP servers for communication. So, we basically just pass around a MemberId that’s used to send messages between servers and from clients to servers and vice versa. There’s just no more client/server/connection abstraction, only a simple messaging abstraction:
https://github.com/atomix/atomix/blob/master/core/src/main/java/io/atomix/cluster/messaging/ClusterCommunicationService.java

That messaging is also used in other peer-to-peer protocols (gossip/anti-entropy/failure detection), and supports location agnostic messaging for microservices