DaveDuggins commented on code in PR #15809: URL: https://github.com/apache/pulsar/pull/15809#discussion_r908528595
########## site2/docs/architecture-overview.md: ########## @@ -0,0 +1,143 @@ +--- + +id: concepts-architecture-overview + +title: Architecture overview + +sidebar_label: Concepts + +--- + +The following overview describes the components that make up a Pulsar cluster, from general to specific. + +### Instance + +*** + +A Pulsar instance is composed of one or more Pulsar clusters. Clusters within an instance can [replicate](concepts-replication.md) data amongst themselves. + +### Cluster + +*** + + + +In a Pulsar cluster: + +* One or more **brokers** handles and load balances incoming messages from **producers**, dispatches **messages** to **consumers**, communicates with the Pulsar **configuration store** to handle various coordination tasks, stores messages in BookKeeper instances (aka **bookies**), relies on a cluster-specific ZooKeeper cluster for certain tasks, and more. + +* A BookKeeper cluster consisting of one or more bookies handles [persistent storage](#persistent-storage) of messages. + +* A ZooKeeper cluster specific to that cluster handles coordination tasks between Pulsar clusters. + +An instance-wide ZooKeeper cluster called the Configuration Store handles coordination tasks involving multiple clusters, for example [geo-replication](concepts-replication.md). + +For a guide to managing Pulsar clusters, see the [clusters](admin-api-clusters.md) guide. Review Comment: "Managing" is a gerund - a verb in present participle form acting as a noun. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
