The Power of Apache Pulsar. Harnessing Dapr to Build High Scale Messaging

on YouTube ↗31m

" summary

FICO migrates eventing from Kafka to Apache Pulsar using Dapr and StreamNative operators, claiming better scalability because Pulsar separates storage from brokers, plus Kafka wire-protocol compatibility so existing clients run unchanged. Dapr becomes an abstraction layer with a sidecar model; community work adds schema, OIDC, and pluggable auth within a year while transactions arrive only after Pulsar 3.2. Benchmarks show low overhead—Dapr sidecar uses 48 MB and ~5–10% CPU—and metering buffers five records as a tunable durability/efficiency tradeoff. Kafka-compatible APIs run on Pulsar and transactional migration is ongoing.

AI-written summary · about

" chapters (12)

1. 0:00Introduction
2. 3:53Siloed point solutions challenges
3. 7:10Business to services decomposition
4. 10:24Event broker software requirements
5. 13:34FICO chose Apache Pulsar
6. 16:25Reasons for StreamNative Pulsar
7. 19:12Need for Dapr abstraction
8. 22:00What is Dapr
9. 24:47Dapr gaps for Pulsar
10. 26:53Dapr performance and transactions
11. 28:42Pulsar migration strategy
12. 30:25Scaling Dapr with Diagrid

" related talks

• 46mScalable messaging and streaming with Apache PulsarJulien Jakubowski · Voxxed Days Luxembourg 2023
• 45mApache Pulsar: Finally an Alternative to Kafka?Julien Jakubowski · Big Data & RPA Conference Europe 2024
• 45mScalable distributed messaging&streaming with Apache PulsarJulien Jakubowski · Berlin Buzzwords 2023
• 53mEvent Messaging and Streaming with Apache PulsarMary Grygleski · Build Stuff 2022
• 48mApache Pulsar: Event Streaming in The Cloud Native WorldMary Grygleski · GOTO Chicago 2023
• 45mApache Pulsar: Finally an Alternative to Kafka?Julien Jakubowski · Devoxx France 2024
• 46mApache Pulsar: Finally an Alternative to Kafka?Julien Jakubowski · DevDays Europe 2024
• 47mEvent Streaming for the Best of All WorldsMary Grygleski · Spring I/O 2022