Our server-sided solution makes use of Hazelcast-provided distributed data structures to make available state related to entities that live on particular cluster members.
When a cluster member joins or leaves the cluster, we have a need for the other cluster nodes to be aware of 'what changed': for example, when a cluster member leaves, the other cluster members need to be able to determine what entities have become unavailable as a result of the cluster event, separating that from the changes in availability of entities that have other causes (eg: related to the normal lifecycle behavior of such entities).
A naive implementation could be based on a keeping a record, on each cluster member, that tracks what resources is provided by what cluster member. Such a record could then be used when cluster events are detected. However, this very much feels like re-inventing a wheel.
Can Hazelcast facilitate a solution?