Data grid between Payara Full editions

Technical Discussion
6

I am not familiar with GCP. Anyhow I found that the Google Cloud: VPC network overview mentions as the following: -

VPC networks do not support broadcast or multicast addresses within the network.

This may mean that we may not achieve the automatic joining / unjoining with Multicast Discovery Mode and may have only two choices as TCPIP Discovery Mode and DNS Discovery Mode. We have to add/remove the members via asadmin manually or create a customized scripts to execute that asadmin command so that it is a DRY.

Note: Regarding to my previous reply about the Domain Discovery Mode, I may be wrong. The Domain Discovery Mode may use the multicast as well ?

Moreover, the Hazelcast: Discovery Mechanisms: GCP Cloud Discovery also mentions as the following: -

Hazelcast supports discovering members in the GCP Compute Engine environment. You can easily configure Hazelcast members discovery, WAN replication, and Hazelcast Client to work seamlessly on the native GCP VM Instances. This discovery feature is provided as a Hazelcast plugin. See the Cloud Discovery Plugins: Hazelcast GCP section.

While the Cloud Discovery Plugins: Hazelcast GCP section mentions as the following:-

Hazelcast provides support for Google Compute Engine, covering the following environments:

In both scenarios you can use the ZONE_AWARE feature to create partition backups in other Availability Zones (AZ) and therefore prevent any data loss in case of AZ failures.

You can easily configure your Hazelcast member/client to use GCP discovery by having the hazelcast-all (or hazelcast-gcp ) JAR on your classpath and enabling GCP in your Hazelcast configuration.

See the Hazelcast GCP Plugin documentation for more details.

Then we may take our life to the risk by using trial and error by providing the Hazelcast GCP to the Payara classpath, configuring the hazelcast.config to use that plugin manually and last but not least, letting the Payara to use that configuration file by following the Configuring the Domain Data Grid underlying Hazelcast