Externalising Kafka for Pega Platform
We are proceeding to upgrade to Infinity 24.1.2 leveraging on Enterprise Kafka Platform. There are limited options for us to refine the Enterprise Kafka configuration for Pega. Does Pega creates the Kafka topics within Enterprise kafka platform with required kafka properties (like thread management, io, network, replication, offset, topics, log folders, mgmt, retries, ...), so that no special/additional configurations are required to be defined within Enterprise Kafka platform for Pega stream processing. This allows Pega is not depending on Enterprise Kafka platform to meet its performance needs. If Pega is not able to self-manage the configurations of its topics, and depending on Enterprise Kafka platform, do help to list down ALL the Kafka properties required to support dynamic QP configuration creation/updates/DSS, and its associated calculations to be provided to Enterprise Kafka platform for their configurations, so that Pega platform is able to meet for its performance requirements and resiliencies.
Pegasystems Inc.
GB
Pega Platform does require some specific Kafka configurations to optimize its stream functionality. These include message.max.bytes set to 5000000, unclean.leader.election.enable set to false, and auto.create.topics.enable set to false. However, Pega Platform does not create the Kafka topics within the Enterprise Kafka platform with these properties. These configurations need to be set in your external Kafka cluster. Pega Platform does not support vendor-specific security features. For dynamic QP configuration creation/updates/DSS, Pega Platform does not require any additional Kafka properties. However, it's important to note that Pega Platform deployments require access to an external Kafka cluster to use the streaming functionality in the software. Without this Kafka cluster, Pega Platform is not fully functional.
Note: This is a GenAI-powered answer. All generated answers require validation against the provided references.
Platform Support Guide > Kafka
Third-party externalized services Deployment Changes FAQs
Pega Platform does require some specific Kafka configurations to optimize its stream functionality. These include message.max.bytes set to 5000000, unclean.leader.election.enable set to false, and auto.create.topics.enable set to false. However, Pega Platform does not create the Kafka topics within the Enterprise Kafka platform with these properties. These configurations need to be set in your external Kafka cluster. Pega Platform does not support vendor-specific security features. For dynamic QP configuration creation/updates/DSS, Pega Platform does not require any additional Kafka properties. However, it's important to note that Pega Platform deployments require access to an external Kafka cluster to use the streaming functionality in the software. Without this Kafka cluster, Pega Platform is not fully functional.
Note: This is a GenAI-powered answer. All generated answers require validation against the provided references.
Platform Support Guide > Kafka
Third-party externalized services Deployment Changes FAQs
External Kafka in your deployment > Additional Kafka configurations