PubSub

A PubSub serves as an asynchronous message hub, allowing publishers to send messages that can be received by all current subscribers.

Unlike a Queue, where each value is delivered to only one consumer, a PubSub broadcasts each published message to all subscribers. This makes PubSub ideal for scenarios requiring message broadcasting rather than load distribution.

Basic Operations

A PubSub<A> stores messages of type A and provides two fundamental operations:

Example (Publishing a Message to Multiple Subscribers)

1
import { Effect, PubSub, Queue } from "effect"
2

3
const program = Effect.scoped(
4
  Effect.gen(function* () {
5
    const pubsub = yield* PubSub.bounded<string>(2)
6

7
    // Two subscribers
8
    const dequeue1 = yield* PubSub.subscribe(pubsub)
9
    const dequeue2 = yield* PubSub.subscribe(pubsub)
10

11
    // Publish a message to the pubsub
12
    yield* PubSub.publish(pubsub, "Hello from a PubSub!")
13

14
    // Each subscriber receives the message
15
    console.log("Subscriber 1: " + (yield* Queue.take(dequeue1)))
16
    console.log("Subscriber 2: " + (yield* Queue.take(dequeue2)))
17
  }),
18
)
19

20
Effect.runFork(program)
21
/*
22
Output:
23
Subscriber 1: Hello from a PubSub!
24
Subscriber 2: Hello from a PubSub!
25
*/

Creating a PubSub

Bounded PubSub

A bounded PubSub applies back pressure to publishers when it reaches capacity, suspending additional publishing until space becomes available.

Back pressure ensures that all subscribers receive all messages while they are subscribed. However, it can lead to slower message delivery if a subscriber is slow.

Example (Bounded PubSub Creation)

1
import { PubSub } from "effect"
2

3
// Creates a bounded PubSub with a capacity of 2
4
const boundedPubSub = PubSub.bounded<string>(2)

Dropping PubSub

A dropping PubSub discards new values when full. The PubSub.publish operation returns false if the message is dropped.

In a dropping pubsub, publishers can continue to publish new values, but subscribers are not guaranteed to receive all messages.

Example (Dropping PubSub Creation)

1
import { PubSub } from "effect"
2

3
// Creates a dropping PubSub with a capacity of 2
4
const droppingPubSub = PubSub.dropping<string>(2)

Sliding PubSub

A sliding PubSub removes the oldest message to make space for new ones, ensuring that publishing never blocks.

A sliding pubsub prevents slow subscribers from impacting the message delivery rate. However, there’s still a risk that slow subscribers may miss some messages.

Example (Sliding PubSub Creation)

1
import { PubSub } from "effect"
2

3
// Creates a sliding PubSub with a capacity of 2
4
const slidingPubSub = PubSub.sliding<string>(2)

Unbounded PubSub

An unbounded PubSub has no capacity limit, so publishing always succeeds immediately.

Unbounded pubsubs guarantee that all subscribers receive all messages without slowing down message delivery. However, they can grow indefinitely if messages are published faster than they are consumed.

Generally, it’s recommended to use bounded, dropping, or sliding pubsubs unless you have specific use cases for unbounded pubsubs.

Example

1
import { PubSub } from "effect"
2

3
// Creates an unbounded PubSub with unlimited capacity
4
const unboundedPubSub = PubSub.unbounded<string>()

Operators On PubSubs

publishAll

The PubSub.publishAll function lets you publish multiple values to the pubsub at once.

Example (Publishing Multiple Messages)

1
import { Effect, PubSub, Queue } from "effect"
2

3
const program = Effect.scoped(
4
  Effect.gen(function* () {
5
    const pubsub = yield* PubSub.bounded<string>(2)
6
    const dequeue = yield* PubSub.subscribe(pubsub)
7
    yield* PubSub.publishAll(pubsub, ["Message 1", "Message 2"])
8
    console.log(yield* Queue.takeAll(dequeue))
9
  }),
10
)
11

12
Effect.runFork(program)
13
/*
14
Output:
15
{ _id: 'Chunk', values: [ 'Message 1', 'Message 2' ] }
16
*/

capacity / size

You can check the capacity and current size of a pubsub using PubSub.capacity and PubSub.size, respectively.

Note that PubSub.capacity returns a number because the capacity is set at pubsub creation and never changes. In contrast, PubSub.size returns an effect that determines the current size of the pubsub since the number of messages in the pubsub can change over time.

Example (Retrieving PubSub Capacity and Size)

1
import { Effect, PubSub } from "effect"
2

3
const program = Effect.gen(function* () {
4
  const pubsub = yield* PubSub.bounded<number>(2)
5
  console.log(`capacity: ${PubSub.capacity(pubsub)}`)
6
  console.log(`size: ${yield* PubSub.size(pubsub)}`)
7
})
8

9
Effect.runFork(program)
10
/*
11
Output:
12
capacity: 2
13
size: 0
14
*/

Shutting Down a PubSub

To shut down a pubsub, use PubSub.shutdown. You can also verify if it has been shut down with PubSub.isShutdown, or wait for the shutdown to complete with PubSub.awaitShutdown. Shutting down a pubsub also terminates all associated queues, ensuring that the shutdown signal is effectively communicated.

PubSub as an Enqueue

PubSub operators mirror those of Queue with the main difference being that PubSub.publish and PubSub.subscribe are used in place of Queue.offer and Queue.take. If you’re already familiar with using a Queue, you’ll find PubSub straightforward.

Essentially, a PubSub can be seen as a Enqueue that only allows writes:

import type { Queue } from "effect"

interface PubSub<A> extends Queue.Enqueue<A> {}

Here, the Enqueue type refers to a queue that only accepts enqueues (or writes). Any value enqueued here is published to the pubsub, and operations like shutdown will also affect the pubsub.

This design makes PubSub highly flexible, letting you use it anywhere you need a Enqueue that only accepts published values.