Skip to main content

Pulsar Features

The complete platform for messaging and streaming.

The combination of features that makes Apache Pulsar more than just a message broker.

Rapid Horizontal Scalability

Scales horizontally to handle the increased load. Its unique design and separate storage layer enable controlling the sudden surge in traffic by scaling out in seconds.

Low-latency, messaging and streaming

Acknowledge messages individually (RabbitMQ style) or cumulative per partition (i.e., offset-like). Enables use cases such as distributed work queues or order-preserving data streams at massive scales (hundreds of nodes) and low latency (<10ms).

Supports up to 1M topics

Pulsar's unique architecture supports up to 1 million topics in a single cluster. Simplify your architecture by avoiding multiplexing multiple streams into a single topic.

Multi-tenancy as a first-class citizen

Maintain one cluster for your entire organization using tenants. Control which user has access across data (namespaces/topics) and actions (produce/consume/…).

Automatic Load Balancing

Add or remove nodes and let Pulsar load balance topic bundles automatically. Hot spotted topic bundles are automatically split and evenly distributed across the brokers.

K8s Ready

Pulsar was built for the cloud from day one. Both Pulsar and Bookkeeper nodes can scale up quickly as Pulsar is stateless, and Bookkeeper was designed to avoid data reshuffling while still utilizing all newly joined nodes.

Seamless Geo-Replication

Protect against complete zone outages using replication across different geographic regions. Flexible and configurable replication strategies across distant Pulsar Clusters. Uniquely supports automatic client failover to healthy clusters.

Official multi-language support

Officially maintained Pulsar Clients for Java, Go, Python, C++, Node.js, and C#.

Tiered storage support for unlimited retention

Unlimited retention by seamless data offloading from Bookkeeper to blob storage (e.g., S3). Keep high performance with resiliency by keeping warm data both in Bookeeper and S3.

Built-in Schema Registry

Support validating incoming and outgoing data against a topic schema. Future proof by supporting backward and forward compatibility checks for each new schema version.

Granular Access Control

Pulsar supports user authentication with the ability to set access to specific namespaces or topics with limited permissions (consume, produce, etc.)

Guaranteed message persistency

Pulsar writes to Bookkeeper are guaranteed to be written to disk (a.k.a fsync), providing high resiliency to machine failures. It can be disabled to favor higher throughput.

Separate Compute from Storage

Choose the best instance types for storage and CPU separately due to Pulsar's unique architecture. Support massive parallel query engines by a direct read from Bookkeeper.

Built to support additional protocols
(Kafka, RabbitMQ, …)

Use popular messaging system clients with Pulsar as the backend, powered by community plugins: Kafka, RabbitMQ, and more. This facilitates moving to Pulsar gradually.

Serverless Functions

Write and deploy functions natively using Pulsar Functions. Process messages using Java, Go, or Python without deploying fully-fledged applications. Kubernetes runtime is bundled.

Official 3rd party Connectors

Write and deploy functions natively using Pulsar Functions. Process messages using Java, Go, or Python without deploying fully-fledged applications. Kubernetes runtime is bundled.

Support very large messages.

Very large messages are welcomed in Pulsar, using client-side chunking.

Delayed messaging

Write a message with a given delay before it is available for consumption. Great for scheduled tasks and exponential back-off retries.

Supports a Large Number of Connected Consumers

Supports a large number of concurrently connected consumers to a topic, regardless of partition count.

Easy to operate Coordination Metadata store

Zookeeper is just one of the plugins for the metadata store. Quickly isolate metadata-related issues as the system is separated from Pulsar itself. Allows future scalable metadata stores.

Easy to Operate

Built-in REST API and CLI for administrative operations

More Features

Flexible message retention
By time, size, or unacknowledge size

Topic compaction
Keep only the last of the same key messages.

Message deduplication
Achieve Exactly Once when producing.

Produce and acknowledge as an atomic operation

Ready to start?
Explore documentation to get more insights on how pulsar works