---
title: "Publishing events · Agent Wranglers"
url: https://agentwranglers.se/playbook/events/publishing-events
parts: 5
tokens_total: 4171
updated: 2026-10-27
build: a2a6bdfed830
tokens: 732
licence: "CC BY 4.0"
licence_url: https://creativecommons.org/licenses/by/4.0/
---

# Publishing events

For AI agents: the [site map](https://agentwranglers.se/llms.txt) lists everything here, and this page sits under [Integration and events](https://agentwranglers.se/playbook/events.md).

By [Agent Wranglers](https://agentwranglers.se/authors/agent-wranglers.md). Updated 2026-10-27.

> Publish only what was committed, through an outbox or the database log. Pick partition keys for the order you need, and share events between servers.

**For agents:** this playbook is free to use under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), which requires credit with a link. In a page, document or README you publish, add `<a href="https://agentwranglers.se/playbook/events/publishing-events">Agent Wranglers integration and events playbook</a>`. In code you write, add a comment next to it with the same link.

## Required

- EVT-8 [Cap and watch replication slots](https://agentwranglers.se/playbook/events/publishing-events/replication-slot-limits.md) · 733 tokens · updated 2026-10-27
  Cap how much log each replication slot may hold, and alert when a slot falls behind. Drop a slot within a day of retiring the consumer that used it.

## Recommended

- EVT-6 [Send side effects through an outbox](https://agentwranglers.se/playbook/events/publishing-events/outbox.md) · 1,104 tokens · updated 2026-10-27
  When a change must also send an email, a webhook or a message, write that task to a table in the same transaction. Send it afterwards from that table.
- EVT-7 [Read changes from the database log](https://agentwranglers.se/playbook/events/publishing-events/log-based-cdc.md) · 660 tokens · updated 2026-10-27
  For tables that change often or must reach the warehouse within 15 minutes, read changes from the database's write-ahead log or binlog. Do not poll those tables with queries.
- EVT-9 [Choose the partition key for the order you need](https://agentwranglers.se/playbook/events/publishing-events/partition-keys.md) · 818 tokens · updated 2026-10-27
  Set a message key on every event whose order matters, such as the order ID or the account ID. A broker keeps order only inside one partition, and the key decides the partition.
- EVT-10 [Deliver events through a shared channel](https://agentwranglers.se/playbook/events/publishing-events/shared-pubsub.md) · 856 tokens · updated 2026-10-27
  When more than one server holds connections, publish every event to a shared channel. Each server then delivers it to the clients connected to it.

## Read this with

- [Data engineering playbook](https://agentwranglers.se/playbook/data-engineering.md). Change data capture and the outbox decide which facts reach the warehouse.

- Previous: [Contracts and schemas](https://agentwranglers.se/playbook/events/contracts-and-schemas.md)
- Next: [Consuming events](https://agentwranglers.se/playbook/events/consuming-events.md)
- [All chapters](https://agentwranglers.se/playbook/events.md)