Subscription basics

Subscriptions allow you to subscribe to a stream and receive notifications for changes in the stream.

You provide an event handler and an optional starting point to the subscription. The handler is called for each event from the starting point onward.

If events already exist, the handler will be called for each event one by one until it reaches the end of the stream. From there, the server will notify the handler whenever a new event appears.

TIP

Check connecting to EventStoreDB instructions to learn how to configure and use the client SDK.

Subscribing to a stream

The simplest stream subscription looks like the following :

await client.SubscribeToStreamAsync("some-stream",
	async (subscription, evnt, cancellationToken) => {
		Console.WriteLine($"Received event {evnt.OriginalEventNumber}@{evnt.OriginalStreamId}");
		await HandleEvent(evnt);
	});

const subscription = client
  .subscribeToStream("some-stream")
  .on("data", function (resolvedEvent) {
    console.log(
      `Received event ${resolvedEvent.event.revision}@${resolvedEvent.event.streamId}`
    );
    handleEvent(resolvedEvent);
  });

// Make sure to add code blocks to your code group

The provided handler will be called for every event in the stream.

Subscribing to $all

Subscribing to $all is much the same as subscribing to a single stream. The handler will be called for every event written after the starting position.

await client.SubscribeToAllAsync(
	async (subscription, evnt, cancellationToken) => {
		Console.WriteLine($"Received event {evnt.OriginalEventNumber}@{evnt.OriginalStreamId}");
		await HandleEvent(evnt);
	});

  const subscription = client.subscribeToAll().on("data", handleEvent);

// Make sure to add code blocks to your code group

Subscribing from a specific position

The previous examples will subscribe to the stream from the beginning. This will end up calling the handler for every event in the stream and then wait for new events after that.

Both the stream and $all subscriptions accept a starting position if you want to read from a specific point onward. If events already exist at the position you subscribe to, they will be read on the server side and sent to the subscription.

Once caught up, the sever will push any new events received on the streams to the client. There is no difference between catching up and live on the client side.

WARNING

The positions provided to the subscriptions are exclusive. You will only receive the next event after the subscribed position.

Subscribing to a stream

To subscribe to a stream from a specific position, you need to provide a stream position. This can be Start, End or a big int (unsigned 64 bit integer) position.

The following subscribes to the stream "some-stream" at position 20, this means that events 21 and onward will be handled:

await client.SubscribeToStreamAsync(
	"some-stream",
	StreamPosition.FromInt64(20),
	EventAppeared);

const subscription = client
  .subscribeToStream("some-stream", { fromRevision: BigInt(20) })
  .on("data", handleEvent);

// Make sure to add code blocks to your code group

Subscribing to $all

Subscribing to $all is much like subscribing to a stream, but you need to provide a Position instead. This can be Start, End or a Position created from a commit and prepare position.

The corresponding $all subscription will subscribe from the event after the one at commit position 1056 and prepare position 1056.

Please note that this position will need to be a legitimate position in $all.

await client.SubscribeToAllAsync(
	new Position(1056, 1056),
	EventAppeared);

const subscription = client
  .subscribeToAll({
    fromPosition: {
      commit: BigInt(1056),
      prepare: BigInt(1056),
    },
  })
  .on("data", function (resolvedEvent) {
    console.log(
      `Received event ${resolvedEvent.event.revision}@${resolvedEvent.event.streamId}`
    );
    handleEvent(resolvedEvent);
  });

// Make sure to add code blocks to your code group

Subscribing to a stream for live updates

You can subscribe to a stream to get live updates by subscribing to the end of the stream :

await client.SubscribeToStreamAsync(
	"some-stream",
	StreamPosition.End,
	EventAppeared);

const subscription = client
  .subscribeToStream("some-stream", { fromRevision: END })
  .on("data", handleEvent);

// Make sure to add code blocks to your code group

And the same works with $all :

await client.SubscribeToAllAsync(
	Position.End,
	EventAppeared);

const subscription = client
  .subscribeToAll({ fromPosition: END })
  .on("data", handleEvent);

// Make sure to add code blocks to your code group

This won't read through the history of the stream, but will rather notify the handler when a new event appears in the respective stream.

Resolving link-to's

Link-to events point to events in other streams in EventStoreDB. These are generally created by projections such as the $by_event_type projection which links events of the same event type into the same stream. This makes it easier to look up all events of a certain type.

TIP

Filtered subscriptions make it easier and faster to subscribe to all events of a certain type or matching a prefix. See the Filtering section for more information.

When reading a stream you can specify whether to resolve link tos or not. By default, link-to events are not resolved. You can set this with the resolveLinkTos parameter :

await client.SubscribeToStreamAsync(
	"$et-myEventType",
	StreamPosition.Start,
	EventAppeared,
	resolveLinkTos: true);

const subscription = client
  .subscribeToStream("$et-myEventType", {
    fromRevision: START,
    resolveLinkTos: true,
  })
  .on("data", handleEvent);

// Make sure to add code blocks to your code group

Dropped subscriptions

When a subscription stops or experiences an error, it will be dropped. The subscription provides a subscriptionDropped handler which will get called when this happens.

The subscriptionDropped handler allows you to inspect the reason the subscription dropped as well as any exceptions that occurred.

The possible reasons for a subscription dropping are :

Reason	Why it might happen
Disposed	The subscription got cancelled or disposed by the client.
SubscriberError	An error occurred while handling an event in the subscription handler.
ServerError	An error occurred on the server, and the server closed the subscription. Check the server logs for more information.

Handling subscription drops

You can start from where you left off by keeping a record of the last processed event and continuing from there :

var checkpoint = StreamPosition.Start;
await client.SubscribeToStreamAsync(
	"some-stream",
	checkpoint,
	eventAppeared: async (subscription, evnt, cancellationToken) => {
		await HandleEvent(evnt);
		checkpoint = evnt.OriginalEventNumber;
	},
	subscriptionDropped: ((subscription, reason, exception) => {
		Console.WriteLine($"Subscription was dropped due to {reason}. {exception}");
		if (reason != SubscriptionDroppedReason.Disposed) {
			// Resubscribe if the client didn't stop the subscription
			Resubscribe(checkpoint);
		}
	}));

// TODO

// Make sure to add code blocks to your code group

When subscribed to $all you want to keep the position of the event in the $all stream :

var checkpoint = Position.Start;
await client.SubscribeToAllAsync(
	checkpoint,
	eventAppeared: async (subscription, evnt, cancellationToken) => {
		await HandleEvent(evnt);
		checkpoint = evnt.OriginalPosition.Value;
	},
	subscriptionDropped: ((subscription, reason, exception) => {
		Console.WriteLine($"Subscription was dropped due to {reason}. {exception}");
		if (reason != SubscriptionDroppedReason.Disposed) {
			// Resubscribe if the client didn't stop the subscription
			Resubscribe(checkpoint);
		}
	}));

// TODO

// Make sure to add code blocks to your code group

Filter options

Subscriptions to $all can include a filter option. This will only notify the event handler if the event matches the provided filter.

A simple stream prefix filter looks like this :

var prefixStreamFilter = new SubscriptionFilterOptions(StreamFilter.Prefix("test-", "other-"));
await client.SubscribeToAllAsync(
	EventAppeared,
	filterOptions: prefixStreamFilter);

const prefixes = ["test-", "other-"];
const filter = { filterOn: STREAM_NAME, prefixes };
const subscription = client
  .subscribeToAll({
    filter,
  })
  .on("data", handleEvent);

// Make sure to add code blocks to your code group

The filtering api is described more in-depth in the filtering section.

User credentials

The user creating a subscription must have read access to the stream it's subscribing to, and only admin users may subscribe to $all or create filtered subscriptions.

You can provide user credentials to be used by the subscription as follows. This will override the default credentials set on the connection.

await client.SubscribeToAllAsync(
	EventAppeared,
	userCredentials: new UserCredentials("admin", "changeit"));

const credentials = {
  username: "admin",
  password: "changeit",
};
const subscription = client
  .subscribeToStream({
    credentials,
  })
  .on("data", handleEvent);

// Make sure to add code blocks to your code group