Apache Pulsar helps applications exchange messages without requiring the sender and receiver to work at the same moment. It stores messages in streams that other applications can read, making it useful for background processing and systems that react to events. The software that accepts messages and the storage that keeps them are separate parts of the deployment. That separation brings operational choices about capacity, retention and recovery.
Chart ownership
The Apache project publishes the official Pulsar Helm chart through pulsar.apache.org/charts. The repository states that chart releases follow a separate schedule from Pulsar itself and can lag. It describes the chart as a deployment starting point that may need customization.
Before adoption
Upstream explicitly warns that default values do not meet production security requirements. Configure authentication, authorization, encrypted communication and network isolation for the deployed components. The repository also warns against exposing the Pulsar proxy directly to the public internet. Plan persistent storage, retention, placement and recovery for the complete deployment, then test component loss under load. Check chart, application and dependency compatibility before upgrades. Choose Pulsar because its messaging model fits the application, with staffing and capacity for the additional services.
Sources & further reading
Spotted something that needs another look?
Help improve this page →