Skip to content

Streaming · Editable reference architecture

Apache Pulsar architecture

An editable apache pulsar architecture reference showing Producer → Broker → BookKeeper storage. Separate broker serving from durable storage.

Open & Edit in DrawArc (Free, No Login Required)

Your changes stay in a separate draft on this browser. Download an editable project to keep a portable copy.

LinkedInTelegramReddit

Apache Pulsar architecture diagram: Producer, Broker, BookKeeper storage, Consumer subscription and their connections
Apache Pulsar architecture — follow the component relationships, then open the editor to adapt the design. View diagram image.

6 components · 5 connections · Open the editor to zoom, move nodes and edit source.

Architectural overview

Apache Pulsar architecture addresses the responsibilities and boundaries shown in this reference rather than prescribing an entire production deployment. The primary flow starts at Producer and reaches BookKeeper storage through Broker. Use this view to explain which component initiates work, which component owns a decision, and where a dependency can affect the caller. Separate broker serving from durable storage.

The diagram contains 6 distinct components and 5 directed relationships. A separate path connects Broker → Consumer subscription → Consumer. A separate path connects Metadata store → Broker. These arrows describe logical interactions; they do not establish authentication, network access, atomic transactions or delivery guarantees. Label the actual protocol, payload contract and owner when adapting the drawing to your system. Keep synchronous and asynchronous boundaries explicit so that a reviewer can identify where a request ends and a later operation begins.

Before implementing this architecture, define expected load, data classification, latency budgets and recovery objectives. Give Broker a bounded dependency timeout and a documented failure response. For BookKeeper storage, Metadata store, specify ownership, retention, access control and a tested recovery procedure. Validate the decision above against your workload instead of treating the presence of a component as proof of reliability. Open the editable canvas, replace generic labels with real deployment units, and document the decisions that differ from this reference.

The real-world problem

Design or explain apache pulsar architecture with explicit ownership and dependency paths. Separate broker serving from durable storage.

Data flow

Connections from this diagram. Branches and control signals are not a single chronological sequence.

  • Producer → Broker. Define the interaction contract and trace the resulting response or state change.
  • Broker → BookKeeper storage. Define the interaction contract and trace the resulting response or state change.
  • Broker → Consumer subscription. Define the interaction contract and trace the resulting response or state change.
  • Consumer subscription → Consumer. Define the interaction contract and trace the resulting response or state change.
  • Metadata store → Broker. Define the interaction contract and trace the resulting response or state change.

Security boundaries

  • Authenticate callers at the boundary before Broker accepts protected work; authorize the specific operation rather than trusting network placement.
  • Use separate service identities and least-privilege permissions for Broker, BookKeeper storage, Consumer subscription. Encrypt sensitive traffic, protect credentials and avoid placing confidential payloads in logs.
  • Restrict and audit access to BookKeeper storage, Metadata store; define retention and deletion requirements for the actual data.

Failure handling

Broker is unavailable or slow

Response: Apply bounded timeouts and controlled backoff only where retrying is safe. Return an explicit failure or durable acceptance; do not report success before required work is committed.

Verify: Interrupt Broker in an isolated test and measure errors, recovery and any repeated side effects.

BookKeeper storage loses or returns stale state

Response: Use workload-specific durability, reconciliation and tested recovery. Specify how stale reads or a failed write affect callers.

Verify: Exercise the failure path with representative records and verify both the visible response and the resulting state.

An invalid or incompatible input reaches Broker

Response: Validate the input contract before effects are committed. Preserve rejected input identifiers without exposing secrets, and document a safe replay or correction procedure.

Verify: Send malformed and older-version inputs through Producer and verify rejection, observability and unchanged valid state.

Trade-offs and alternatives

Separate broker serving from durable storage.

Benefit
Makes the ownership and interaction boundaries visible for a focused design review.
Cost
The 6 illustrated components still require contracts, monitoring and operational ownership; extra boundaries can add latency and failure modes.
Alternative
Use a simpler deployment when it meets the same requirements, or split a boundary only after measuring a specific need.

Logical boundaries versus deployment units in Apache Pulsar architecture

Benefit
Keeps the responsibilities of Producer, Broker, BookKeeper storage visible without requiring a separate server for each box.
Cost
A logical view does not establish isolation, independent scaling or high availability; those require a separate deployment design and operational tests.
Alternative
Co-locate components in a simpler deployment first when ownership and workload requirements permit it.

When to use this architecture

  • Explain apache pulsar architecture to engineers or stakeholders using a concrete visual flow.
  • Review this decision before deployment: Separate broker serving from durable storage.
  • Adapt a starting diagram for your own requirements, then record and validate every changed boundary.

Key components

Producer
Producer participates in apache pulsar architecture. Producer → Broker. Define its contract, owner and access permissions in your implementation.
Broker
Broker participates in apache pulsar architecture. Producer → Broker; Broker → BookKeeper storage; Broker → Consumer subscription; Metadata store → Broker. Define its contract, owner and access permissions in your implementation.
BookKeeper storage
BookKeeper storage participates in apache pulsar architecture. Broker → BookKeeper storage. Define its contract, owner and access permissions in your implementation.
Consumer subscription
Consumer subscription participates in apache pulsar architecture. Broker → Consumer subscription; Consumer subscription → Consumer. Define its contract, owner and access permissions in your implementation.
Consumer
Consumer participates in apache pulsar architecture. Consumer subscription → Consumer. Define its contract, owner and access permissions in your implementation.
Metadata store
Metadata store participates in apache pulsar architecture. Metadata store → Broker. Define its contract, owner and access permissions in your implementation.

Questions about this template

What does this apache pulsar architecture diagram show?

It shows 6 components with the core flow Producer → Broker → BookKeeper storage. Separate broker serving from durable storage.

Can I edit this diagram without signing in?

Yes. Open the template in the browser-local canvas to change nodes, connections and source. AI generation and cloud account storage require sign-in.

Is this a complete production implementation?

No. It is an editable reference. Validate the security controls, dependency behavior, capacity and recovery plan against your own requirements before implementation.

Validate your implementation

Use the relevant platform documentation to verify service limits, supported features and configuration. This diagram is an original reference rather than a reproduction of a provider deployment.