Tow pages of the white paper "Taking a Deep-Dive into Apache Pulsar Architecture for Performance Tuning"

Taking a Deep-Dive into Apache Pulsar Architecture for Performance Tuning

When we talk about Apache Pulsar’s performance, we are usually referring to the throughput and latency associated with message writes and reads. Pulsar has certain configuration parameters that allow you to control how the system handles message writes or reads. I’d like to start a series to discuss how this type of performance tuning works in Apache Pulsar. This is the first post in that series.

In this post, I’ll try to give you a deep explanation of Apache Pulsar’s architecture and also describe its storage layer, Apache BookKeeper™. Knowledge of BookKeeper is essential to the Apache Pulsar tuning process.

Before we begin, you will need to become familiar with some basic concepts. At a minimum, you need to know how messages are sent and received (that is, produced and consumed) in Apache Pulsar.

picture of Pengui Li in a city
Penghui Li
Penghui Li is passionate about helping organizations to architect and implement messaging services. Prior to StreamNative, Penghui was a Software Engineer at, where he was the leading Pulsar advocate and helped the company adopt and implement the technology. He is an Apache Pulsar Committer and PMC member. Penghui lives in Beijing, China.


The latest content on data streaming, delivered right to your inbox

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.