1 Introduction to Apache Pulsar
This chapter covers
- The evolution of the enterprise messaging system and why Apache Pulsar represents the next step in the evolutionary process.
- A comparison of Apache Pulsar to existing enterprise messaging systems
- How Pulsar’s segment-centric storage differs from the partition-centric storage model used in Apache Kafka.
- Real-world use cases where Pulsar is used for stream processing and why you should consider using Apache Pulsar.
Developed at Yahoo in 2013, Pulsar was first open sourced in 2016, and only 15 months after joining the Apache Software Foundations’ incubation program graduated to Top Level Project status. Apache Pulsar was designed from the ground up to address the gaps in current open-source messaging systems such as multi-tenancy, geo-replication, and strong durability guarantees.
The Apache Pulsar site describes it as a distributed pub-sub messaging system that provides very low publish and end-to-end latency, guaranteed message delivery, zero data loss, and a serverless lightweight computing framework for stream data processing. Apache Pulsar provides the three key capabilities for processing large data sets: