Topology and Communication General Concepts
Before you configure your VMware Tanzu GemFire for Kubernetes Cluster members, make sure you understand the options for topology and communication.
The VMware Tanzu GemFire for Kubernetes Cluster topology options allow you to scale horizontally and vertically.
Create a topology plan and a detailed list of machines and communication ports that your members will use. Configure your VMware Tanzu GemFire for Kubernetes Cluster systems and the communication between systems.
VMware Tanzu GemFire for Kubernetes Cluster provides various options for member discovery within a cluster and between clients and servers.
Tanzu GemFire uses a combination of TCP and UDP unicast and multicast for communication between members. You can change the default behavior to optimize communication for your system.
You use a bind address configuration to send network traffic through non-default network cards and to distribute the load of network traffic for Tanzu GemFire across multiple cards. If no bind address setting is found, Tanzu GemFire uses the host machine’s default address.
By default, VMware Tanzu GemFire for Kubernetes Cluster uses Internet Protocol version 4 for Tanzu GemFire address specifications. You can switch to Internet Protocol version 6 if all your machines support it. You may lose performance, so you need to understand the costs of making the switch.