Event Streaming and Processing Using Apache Pulsar
summary
Apache Pulsar is presented as a cloud‑native event streaming system that separates compute and storage by using BookKeeper for append‑only durable logs and ZooKeeper for metadata; brokers are stateless. It supports Java, Python and Go clients, schema formats (Avro/JSON/Protobuf), multi‑tenancy, native geo‑replication and tiered storage, and subscription modes (exclusive, failover, shared, key‑shared) to control ordering. Lightweight stream transforms run as Pulsar Functions serverless units and connectors use Pulsar IO; GitHub activity and committers are growing since Yahoo open‑sourced it.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:59Event streaming basics
- 11:06Complex event processing
- 22:25Event-driven architecture
- 25:55Why event streaming matters
- 31:33Pulsar architecture
- 39:59Pulsar scalability
- 46:19Multi-tenancy in Pulsar
- 49:08Pulsar developer features
- 54:47Next steps
related talks
34mEvent Streaming in the Cloud Native World with Apache Pulsar
55mEvent Messaging and Streaming with Apache Pulsar
48mApache Pulsar: Event Streaming in The Cloud Native World
48mEvent Streaming and Processing using Apache Pulsar and Apache Pinot.
35mStreaming Data Made Easy
51mApache Pulsar 101: architecture, concepts & benchmarks
45mApache Pulsar: Finally an Alternative to Kafka?
41mDeep Dive into Building Streaming Applications with Apache Pulsar
