> ## Documentation Index
> Fetch the complete documentation index at: https://iii.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Ch. 5: Stream live clicks

> Push clicks to subscribers in real time with a dedicated click-streamer worker and iii-stream.

`iii-stream` is for **real-time data transmission**: pushing data to a client the moment it changes,
like a live feed of clicks for a dashboard. A stream is bidirectional (subscribers can send messages
back as well as receive them), but here you only need to broadcast clicks outward. You'll move the
live-broadcast concern into its own `click-streamer` worker so the `link` worker stays focused on
links.

## Add the workers

`iii-stream` is how we will send clicks to clients in Chapter 7, and the `click-streamer` worker
manages the streaming. `iii-stream` is an engine worker, so it runs from the start; you only enable
the `click-streamer` container here. Uncomment the Ch. 5 block under `containers`:

```yaml worker-compose.yaml theme={"theme":{"light":"catppuccin-latte","dark":"dark-plus"}}
click-streamer:
  worker: path://./click-streamer
  start_after: [pubsub]
```

## Broadcast clicks in real time

Have `link` announce each click with a `pubsub` event. Then, have `click-streamer` push the event
onto the live feed.

### Add a `link.clicked` event to the `link` worker

First, publish a `link.clicked` event from `link::record_click`:

```typescript link/src/index.ts {12-16} theme={"theme":{"light":"catppuccin-latte","dark":"dark-plus"}}
worker.registerFunction(
  "link::record_click",
  async (payload: { code: string; clicked_at: string }) => {
    await worker.trigger({
      function_id: "database::execute",
      payload: {
        db: DB,
        sql: "INSERT INTO clicks (code, clicked_at) VALUES (?, ?)",
        params: [payload.code, payload.clicked_at],
      },
    });
    worker.trigger({
      function_id: "publish",
      payload: { topic: "link.clicked", data: payload },
      action: TriggerAction.Void(),
    });
    return { recorded: true };
  },
);
```

> [!NOTE]
>
> In the new code above we didn't use `await` and set the `action` to `TriggerAction.Void()`. This
> causes the function to return immediately before it completes. This is a simple performance
> enhancement with things like pubsub where we don't need guaranteed execution.

### Setup the `click-streamer` worker

Now write the `click-streamer` worker. It subscribes to `link.clicked` and broadcasts each click to
a `clicks` stream with `stream::set`. A `stream::set` both stores the item and pushes it to every
WebSocket subscribed to that stream and group. Create `click-streamer/src/index.ts`:

```typescript click-streamer/src/index.ts theme={"theme":{"light":"catppuccin-latte","dark":"dark-plus"}}
import { registerWorker } from "iii-sdk";
import { Logger } from "@iii-dev/helpers/observability";

const worker = registerWorker(process.env.III_URL ?? "ws://localhost:49134", {
  workerName: "click-streamer",
});
const logger = new Logger();

worker.registerFunction(
  "click-streamer::broadcast",
  async (data: { code: string; clicked_at: string }) => {
    await worker.trigger({
      function_id: "stream::set",
      payload: {
        stream_name: "clicks",
        group_id: "all",
        item_id: `${data.code}-${data.clicked_at}`,
        data,
      },
    });
    return { streamed: true };
  },
);

worker.registerTrigger({
  type: "subscribe",
  function_id: "click-streamer::broadcast",
  config: { topic: "link.clicked" },
});

logger.info("click-streamer ready");
```

Restart Compose so it picks up the change:

```bash theme={"theme":{"light":"catppuccin-latte","dark":"dark-plus"}}
iii trigger compose::restart
```

The browser you build in Chapter 7 subscribes to `clicks`/`all` and counts those broadcasts live.

## See it work

With the engine running, create a few links and follow each:

```bash theme={"theme":{"light":"catppuccin-latte","dark":"dark-plus"}}
for n in $(seq 4 6); do
  curl -s -X POST http://127.0.0.1:3111/links \
    -H 'Content-Type: application/json' -d "{\"url\":\"https://iii.dev\",\"code\":\"iii-example-$n\"}"
  curl -s -o /dev/null "http://127.0.0.1:3111/s/iii-example-$n"
done
```

Then read the live `clicks` stream:

```bash theme={"theme":{"light":"catppuccin-latte","dark":"dark-plus"}}
iii trigger stream::list stream_name=clicks group_id=all
```

Each redirect lands in the stream as the `click-streamer` worker broadcasts it.

## Conclusion

Linkly now streams every click to subscribers in real time through a dedicated `click-streamer`
worker. Next, in [Ch. 6: Move bulk data with channels](/docs/tutorials/linkly/channels.md), you bulk-load
links from a CSV in a single streamed upload.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.