Home / Pulsar Components

This article explores how Pulsar SQL queries data and the components involved. It also walks through an SQL query example.

Although they have some similarities, ZooKeeper and BookKeeper provide different administrative services in Pulsar. This article will help you to understand how ZooKeeper and BookKeeper work, the roles these components play in Pulsar, and the differences between ZooKeeper and BookKeeper, highlighting use cases where each component is particularly useful.

The Apache Pulsar Schema is one of the most critical components of Apache Pulsar, an open-source distributed system messaging and streaming platform. In this article, we’ll explore the role of schemas in data streaming and how JSON, Avro, and Apache Pulsar work together to make edge computing possible.

This article will explore what Pulsar topics are, the differences between persistent and non-persistent topics in Apache Pulsar, and review some example use cases for both methods.

Both Pulsar and Kafka aim to increase the amount of data that can be consumed and processed by horizontal scaling — spreading data across many partitions. This is possible thanks to parallel processing, wherein the data producer writes to multiple partitions and the consumer reads them.

In this article, we’ll examine how Pulsar Schemas work and contrast them with schemaless systems to determine the best approach. We’ll also demonstrate how to use Java clients with Pulsar.

Enrico Olivelli speaks to the Japan Apache Pulsar User Group about how Apache Pulsar uses Apache ZooKeeper and Apache BookKeeper, with a particular focus on how Pulsar guarantees consistency even in spite of common failures in distributed systems.

Enrico Olivelli gives us a tour of how data moves from the Producer to the Consumer.