@RojaB  Hazelcast is used for cluster communication in Pega, helping to maintain a common cache across all Pega nodes in a cluster environment. The cache can contain various types of data, including Customer Data Keys (CDKs) for encryption and decryption purposes. The cache uses a size-based eviction policy, where old cache entries are removed once the cache is full. Pega supports configuring authentication credentials using a secret in an external secrets operator, which suggests that credentials used to access the cache are stored securely. However, the context does not provide information about whether the cache is tied to a session, has a defined expiry, should be encrypted at rest, whether credentials used to access the cache can be auto-rotated, or whether payments and highly confidential data are stored in the cache.

⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.

Apache Ignite vs Hazel Cast

Cache in multiple node setup in Pega

Caching in Pega 7.3

Platform cipher - Customer data key (CDK) cache management