Installation topologies
This page describes recommended starting points for Pulsar deployments.
-
SANDBOX (or Pulsar Standalone) is an all-in-one single-node deployment that is useful for taking Pulsar for a test drive.
-
DEVELOPMENT is a 3-node deployment that is not highly available, but able to maintain parity with the TESTING environment.
-
SINGLE REGION TESTING ENVIRONMENT is a highly-available 3/3/3 deployment.
-
HIGH-AVAILABILITY PRODUCTION ENVIRONMENT is a highly-available deployment replicated across 3 zones in 1 region.
Minimum sizing
The number of nodes in a highly available cluster depends on the number of zones in the region. DataStax recommends aligning the replication factor with the AZ count. For example, if there are 3 zones, then set a replication factor of 3.
| Environment | Server Component | Node Count | Note |
|---|---|---|---|
SANDBOX (STANDALONE) |
ZooKeeper, broker, and bookie (combined) |
1 |
|
DEVELOPMENT (1 region, 1 zone) |
ZooKeeper |
1 |
|
Broker |
1 |
||
Bookie |
1 |
||
SINGLE REGION TESTING ENVIRONMENT (1 region, 1 zone) |
ZooKeeper |
3 |
|
Broker |
3 |
||
Bookie |
3 |
||
Pulsar proxy |
3 |
||
Function worker (dedicated) |
3 |
||
HIGH-AVAILABILITY PRODUCTION ENVIRONMENT (1 region, 3 zones) |
ZooKeeper |
5 |
2/2/1 nodes* |
Broker |
3 |
1 nodes per AZ* |
|
Function worker (dedicated) |
3 |
1 node per AZ* The number of function workers depends on the cluster’s functions workload. |
|
Bookie |
6 |
2 nodes per AZ* |
|
Pulsar proxy |
3 |
1 node per AZ* |
|
AutoRecovery |
3 |
1 per AZ* |
* Assuming a replication factor of 3.
Hardware sizing
The following table lists the minimum hardware requirements for a Pulsar cluster.
| Environment | Server Component | Hardware Spec | Note |
|---|---|---|---|
DEVELOPMENT |
ZooKeeper, broker, and BookKeeper |
|
Data disks are shared by ZooKeeper data, BookKeeper journal, and BookKeeper ledger |
TEST |
ZooKeeper |
|
|
Broker and function worker |
|
No data disk |
|
Bookie |
|
||
Pulsar proxy, function worker |
|
||
PRODUCTION |
ZooKeeper |
|
|
Broker |
|
||
Bookie |
|
Ledger disk capacity can be beyond 1TB. |
|
Pulsar proxy, AutoRecovery |
|
||
Function worker (dedicated) |
|
Next steps
For more on cluster sizing, see Production Cluster Sizing.
