Exclusive Producer: Using Apache Pulsar to build distributed applications
summary
Apache Pulsar adds an exclusive producer mode (Pulsar 2.8) that exposes BookKeeper-style fencing to apps: a topic epoch counter in topic metadata increments when ownership changes, causing older producers to get fenced and any pending writes rejected. Two access modes exist (fail-fast or wait-for-exclusive). Using exclusive producers plus writing decisions to the same topic yields linear, non-interleaved histories and lets teams implement leader election, distributed locks and atomic broadcast on Pulsar without ZooKeeper/etcd, with fencing enforced by brokers.
AI-written summary · about
chapters (11)
- 0:00Introduction to exclusive producer
- 2:16Distributed locks patterns
- 5:27Leader election concepts
- 9:24Coordination services comparison
- 12:12Challenges in distributed systems
- 16:24Fencing for consistency
- 19:57Exclusive producer feature
- 24:12Topic epoch implementation
- 27:22Building leader election
- 29:26Distributed locks with Pulsar
- 30:29Summary and Q&A
related talks
51mApache Pulsar 101: architecture, concepts & benchmarks
45mScalable distributed messaging&streaming with Apache Pulsar
45mApache Pulsar: Finally an Alternative to Kafka?
50mApache Pulsar 101: architecture and features
47mEvent Streaming for the Best of All Worlds
53mEvent Messaging and Streaming with Apache Pulsar
28mBuild your next-generation stream platform based on Apache Pulsar
48mApache Pulsar: Event Streaming in The Cloud Native World
