Integration / Apache Pulsar Interview questions
How does Pulsar separate compute and storage?
Brokers handle all client-facing operations - accepting publishes, dispatching to consumers, enforcing policies - but hold no message data on local disk; when a broker needs to read or write an entry, it calls out to a BookKeeper ensemble over the network.
Bookies handle only durable, replicated storage of ledger entries, with no awareness of topics, subscriptions, or pub-sub semantics at all - that logic lives entirely in the broker layer.
Because neither layer needs to understand the other's internal concerns, you can add bookies purely to grow capacity, or add brokers purely to grow request-handling capacity, and either layer can be upgraded, restarted, or rebalanced without directly disrupting the other's state.
Bookies are aware of:
A benefit of this separation is:
More Related questions...
