Event Streaming and Processing with Apache Pulsar
summary
Content gives concrete claims and concrete tools: supports Pub-Sub and Message Queues, offers built-in stream processing and Pulsar Functions for mediation and transformation, and relies on Apache Bookkeeper for durable, segment‑centric storage plus Apache Zookeeper for metadata. Slides list tiered storage offload, separation of compute and storage for easier rebalancing, native geo‑replication, multi‑tenancy, and benchmarks claiming billions of messages with lower latency and higher throughput. Demonstrations emphasize deployability and zero‑downtime patching.
AI-written summary · about
chapters (15)
- 0:00Start
- 23:30What is Apache Pulsar
- 25:22Who else is using Pulsar?
- 26:12Brief History of Apache Pulsar
- 34:17Solves the Problems of Bolton
- 40:03Pulsar Features
- 41:11Separation between Compute and Storage
- 41:33Native Geo-Replication
- 42:01Multi-Tenancy
- 43:08Flexible Message Processing Model
- 44:30So why Pulsar?
- 45:58DataStax is taking Pulsar 10x farther
- 46:27Pulsar meets you where you are
- 48:06Partition-Centric vs. Segment-Centric
- 49:08Architecture Advantage of Pulsar
related talks
53mEvent Messaging and Streaming with Apache Pulsar
46mApache Pulsar: Finally an Alternative to Kafka?
32mStreaming Analytics with Apache Pulsar
45mApache Pulsar: Finally an Alternative to Kafka?
27mLeveraging Event Streaming to Super-Charge your Business Solutions.
22mBuilding FinTech Streaming Applications with Pulsar
46mScalable messaging and streaming with Apache Pulsar
10mA tour of Apache Pulsar