Taking a Deep-Dive into Apache Pulsar Architecture for Performance Tuning
Executive Summary
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.
Download and review our White Paper for an in-depth look at Pulsar Architecture for performance tuning.
Penghui Li is a PMC member of Apache Pulsar and a tech lead in Zhaopin.com, where he serves as the leading promoter to adopt Pulsar. His career has always involved messaging service from the messaging system, through the microservice, and into the current world with Pulsar.
StreamNative is a global team of knowledgeable experts in Apache Pulsar, Apache BookKeeper, and messaging and streaming.
If you have any questions or suggestions, click here to send us an email directly. We’ll reply to you as soon as possible.
