Building resilient and scalable API backends with Apache Pulsar and Spring Reactive
summary
A Reactive Streams adapter for the Apache Pulsar Java Client plus a Spring Boot starter wraps Pulsar async APIs into Flux/Mono senders readers and consumers, adds message producer caching, lifecycle management and reactive backpressure, and provides per-key in-order parallelism via grouping. A demo IoT backend ingests and serves events over server-sent events, handling 1,000,000 messages ~20k/sec end to end, requires Pulsar (Docker) locally, and the adapter is experimental on GitHub under the ESL 2.0 license.
AI-written summary · about
chapters (16)
- 0:00Intro
- 0:36About Lari
- 2:37Why Reactive
- 5:43Reactive Streams Adapter Library
- 7:35Building Blocks
- 10:15Reactive Programming Model
- 11:23Reactive Pulsar Client
- 12:35Scaling Performance
- 13:35Pipelining
- 14:34Parallel processing strategies
- 18:00Reactive message consumer
- 20:07Sample use case
- 21:25Live coding example
- 33:20Running the application
- 35:10Summary
- 36:28Questions
related talks
57mLet's Spring Forth and Stream with Apache Pulsar
22mBuilding FinTech Streaming Applications with Pulsar
31mThe Power of Apache Pulsar. Harnessing Dapr to Build High Scale Messaging
51mEvent Streaming and Processing with Apache Pulsar
46mApache Pulsar: Finally an Alternative to Kafka?
45mApache Pulsar: Finally an Alternative to Kafka?
50mApache Pulsar 101: architecture and features
34mBuild ML Enhanced Event Streaming Apps with Python Microservices