Choosing the Right Messaging Platform for Your Event-Driven Application
summary
Compares Apache Pulsar to Kafka and RabbitMQ and claims Pulsar runs both streaming and queuing on one system by using segment-based storage, separating stateless broker nodes from stateful bookies so adding brokers moves no data and adding bookies immediately accepts new segments; messages replicate (example config 3x replication) and can be offloaded to S3 for cheap long-term retention. Supports key_shared subscription for ordered, scalable consumption without creating partitions; offers Kafka/Rabbit/MQTT protocol adapters, Kubernetes operators, ~1,000 orgs using it, 600+ contributors and ~10k Slack members.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 2:08What is Pesar
- 2:45What is streaming
- 4:39What is messaging
- 7:39What is data streaming
- 13:40What is a subscription
- 14:20Subscription types
- 18:20Scalability and elasticity
- 23:54Kubernetes operators
- 27:11Disaster recovery
- 28:01Multitency
- 29:01Compatibility
- 31:02Open Source
- 32:40Community
- 33:11Recap
- 33:58Questions
- 37:50Kafka vs Pulsar
- 43:30Bookies
related talks
46mScalable messaging and streaming with Apache Pulsar
45mScalable distributed messaging&streaming with Apache Pulsar
53mEvent Messaging and Streaming with Apache Pulsar
45mApache Pulsar: Finally an Alternative to Kafka?
47mEvent Streaming for the Best of All Worlds
28mBuild your next-generation stream platform based on Apache Pulsar
50mApache Pulsar 101: architecture and features
48mApache Pulsar: Event Streaming in The Cloud Native World