Information on externalized components (Kafka, ES, etc.,) in Pega '24 running on Pega cloud 3.

Hi Pega Team, Our client’s Pega instance currently running on Pega 8.8.4 on Pega Cloud 3. We are planning to upgrade to Pega 24.

We have following questions on the cloud offering before our upgrade :

  1. From which platform version, Pega uses externalized kafka, ES on Pega Cloud 3 ?
  2. Do the externalized Kafka cluster runs on same VPC or the cluster is shared with other cloud customers over internet ? Is this same for all the components elastic search, Hazelcast and other ?

Please let me know if more information neeed on this ask and share the documents on the Pega cloud 3 architecture if any.

Thanks !

@duraisankar From Pega Platform version 8.6, Pega has supported the externalization of services like Kafka, Elasticsearch, and Cassandra. This capability is independent of containerized deployments and can be utilized on virtual-machine setups as well.

Regarding the deployment of external Kafka clusters and other components like Elasticsearch and Hazelcast, Pega Cloud 3 manages these services for you. The externalized Kafka in Pega Cloud 3 is configured automatically, and the platform ensures high availability, scalability, and security. The specific details about whether these clusters run on the same VPC or are shared with other cloud customers over the internet are not explicitly mentioned in the provided context. However, Pega Cloud 3 simplifies the transition and manages these services, reducing the workload on your IT team.

For more detailed information on Pega Cloud 3 architecture, you can refer to the following documents:

  1. Kafka Externalization in Pega Infinity 23

  2. Exploring Pega Cloud 3: A Comprehensive Overview

  3. Third-party externalized services FAQs

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

External Kafka in your deployment

Externalization of services in your deployment > Overview of available external

External Hazelcast in your deployment

@vijap @sura2 @bajom1 can any of you provide some input?