Skip to content

Latest commit

 

History

History
144 lines (104 loc) · 4.08 KB

GettingStarted.md

File metadata and controls

144 lines (104 loc) · 4.08 KB
Raw

Getting started with Pulsar

Basic concepts

Pulsar is a messaging system built on the pub-sub paradigm. The topic is the key resource to connect producers and consumers.

A producer can connect to a topic and publish messages. A consumer can subscribe to a topic and receive messages.

Once a subscription has been created, all messages will be retained by the system, even if the consumer gets disconnected, until a consumer will acknowledge their successful processing.

Topic name

A topic name will look like:

persistent://my-property/us-west/my-namespace/my-topic

The topic name structure is linked to the multi-tenant nature of Pulsar. In this example:

  • persistent → Identifies a topic where all messages are durably persisted on multiple disks. This is the only supported type of topic at this point
  • my-property → Property identifies a tenant in the Pulsar instance
  • us-west → Cluster where the topic is located. Typically there will be a cluster for each geographical region or data-center
  • my-namespace → Namespace is the administrative unit and it represents a group of related topics. Most of the configuration is done at the namespace level. Each property can have multiple namespaces
  • my-topic → Final part of topic name. It's free form and has no special meaning to the system

Subscription modes

Each topic can have multiple subscriptions, each with a different subscription name and subscriptions can be of different types:

  • Exclusive → Only one consumer is allowed to attach to the subscription. Ordering is guaranteed.
  • Shared → Multiple consumers can connect to the same subscription and messages are delivered in round-robin across available consumers. Messages ordering can be rearranged.
  • Failover → Only one consumer will be actively receive messages, while other consumer will be on standby. Ordering is guaranteed.

For a more detailed explanation, refer to Architecture page.

Getting the software

Download latest binary release from

https://github.com/yahoo/pulsar/releases

$ tar xvfz pulsar-X.Y-bin.tar.gz
$ cd pulsar-X.Y

Starting a standalone Pulsar server

For application development or to quickly setup a working service, we can use the Pulsar standalone mode. In this mode, we'll start a broker, ZooKeeper and BookKeeper components inside a single JVM process.

$ bin/pulsar standalone

The Pulsar service is now ready to use and we can point clients to use service URL http://localhost:8080/

A sample namespace, sample/standalone/ns1, is already available.

Using the Pulsar Java client API

Include dependency for Pulsar client library:

<dependency>
  <groupId>com.yahoo.pulsar</groupId>
  <artifactId>pulsar-client</artifactId>
  <version>${pulsar.version}</version>
</dependency>

Consumer

PulsarClient client = PulsarClient.create("http://localhost:8080");

Consumer consumer = client.subscribe(
            "persistent://sample/standalone/ns1/my-topic",
            "my-subscribtion-name");

while (true) {
  // Wait for a message
  Message msg = consumer.receive();

  System.out.println("Received message: " + msg.getData());

  // Acknowledge the message so that it can be deleted by broker
  consumer.acknowledge(msg);
}

client.close();

Producer

PulsarClient client = PulsarClient.create("http://localhost:8080");

Producer producer = client.createProducer(
            "persistent://sample/standalone/ns1/my-topic");

// Publish 10 messages to the topic
for (int i = 0; i < 10; i++) {
    producer.send("my-message".getBytes());
}

client.close();