Apache Pulsar: Finally an Alternative to Kafka?
summary
Claim: Apache Pulsar unifies messaging and streaming on one broker and separates compute from storage via Apache BookKeeper. It uses partitionless storage and a separation of broker and bookie to add brokers for CPU and bookies for capacity with no rebalance, offers tiered storage to S3, built‑in geo‑replication and multi‑tenancy, protocol handlers for Kafka/RabbitMQ compatibility, and runs on Kubernetes. Community: ~600 contributors, ~1,000 companies, >10 years in production; one case reports reduced nodes by 10.
AI-written summary · about
chapters (16)
- 0:00Apache Pulsar vs Kafka alternatives
- 1:10Discovering Pulsar by chance
- 2:12What is Apache Pulsar
- 3:36Streaming vs messaging use cases
- 8:58Why Kafka isn’t ideal for queues
- 15:22Pulsar as unified platform
- 16:04Scalability in Pulsar
- 18:13Pulsar’s broker and bookie architecture
- 20:19Partition-free storage benefits
- 23:53Tiered storage and recovery
- 27:47Multi-tenancy in Pulsar
- 29:15Kafka and RabbitMQ compatibility
- 31:02Pulsar open source advantages
- 32:26Pulsar history and adoption
- 34:16Pulsar complexity and operations
- 35:22Q&A
related talks
46mApache Pulsar: Finally an Alternative to Kafka?
50mApache Pulsar 101: architecture and features
51mEvent Streaming and Processing with Apache Pulsar
10mA tour of Apache Pulsar
22mBuilding FinTech Streaming Applications with Pulsar
31mThe Power of Apache Pulsar. Harnessing Dapr to Build High Scale Messaging
27mLeveraging Event Streaming to Super-Charge your Business Solutions.
34mBuild ML Enhanced Event Streaming Apps with Python Microservices