Apache Pulsar: Finally an Alternative to Kafka?
summary
Apache Pulsar is presented as an alternative to Kafka and classic message queues by combining unified messaging and streaming on one broker. It uses Apache BookKeeper for durable segmented storage instead of Kafka partitions, supports elastic broker scaling and add-bookie storage growth without repartitioning, offers native geo-replication, multitenancy with quotas, per-message acknowledgements and key_shared ordering, transparent tiered storage to S3, and Kafka protocol handlers for compatibility, backed by production use since 2012 and an active open-source community.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 5:00Cloud-native Pulsar platform
- 13:28Messaging vs data streaming
- 17:45Why not Kafka for messaging
- 18:26Pulsar scalability and elasticity
- 23:02Segment-based storage model
- 29:20Replication and geo-replication
- 32:07Multitenancy in Pulsar
- 33:10Kafka compatibility and ecosystem
- 36:43Summary and conclusion
- 37:27Q&A
related talks
45mScalable distributed messaging&streaming with Apache Pulsar
53mEvent Messaging and Streaming with Apache Pulsar
46mScalable messaging and streaming with Apache Pulsar
50mApache Pulsar 101: architecture and features
51mApache Pulsar 101: architecture, concepts & benchmarks
28mBuild your next-generation stream platform based on Apache Pulsar
34mEvent Streaming in the Cloud Native World with Apache Pulsar
59mEvent Streaming and Processing Using Apache Pulsar
