Gary Raferzeder-Moison

Using TCP Communication in an RSA Identity Governance and Lifecycle Cluster

Blog Post created by Gary Raferzeder-Moison Employee on Dec 17, 2018

For larger enterprises, creating a clustered environment for RSA Identity Governance and Lifecycle helps to scale the product. The RSA Identity Governance and Lifecycle 7.1 Configuring WildFly Clustering document (RSA Identity Governance and Lifecycle 7.1: Configuring Wildfly Clustering ) describes how to configure a cluster using multicast/UDP for communication between the nodes of the cluster. 

 

RSA Identity Governance and Lifecycle 7.1 now allows communication between the nodes in a cluster to use TCP, rather than multicast/UDP, because TCP is highly reliable and key to a more stable cluster. The new document,

 

Configure WildFly Cluster to Use TCP (RSA Identity Governance and Lifecycle 7.1 Configure WildFly Cluster to Use TCP ), describes how to change current UDP/multicast clusters to use TCP-based communication.

RSA recommends that clusters use TCP rather than multicast/UDP because of some of the key differences between UDP and TCP:

 

1. TCP is connection-oriented, unlike UDP, which is a connectionless protocol.
2. TCP is highly reliable for transferring data because it uses the acknowledgment of sent information and automatically resends any lost packets. UDP does not request retransmission if the packet is lost.
3. While TCP is slower compared to UDP, this is because TCP establishes the connection before transmitting data, and ensures the proper delivery of packets. 
4. The header size of UDP is 8 bytes, while the header size of TCP is more than 16 bytes.  Releases higher than 7.1 deprecate the UDP/Multicast setup in favor of TCP protocol.

Outcomes