Event bus
Sluice moves events between internal Keys Group services — order updates, billing events, audit records. Producers publish to a topic, consumers read at their own pace.
42
topics
6.1k/s
events, avg
118
consumer groups
99.95%
delivered, 30d
Busiest topics
| Topic | Producers | Rate | Retention | Status |
|---|---|---|---|---|
| orders.updated | 3 | 1.8k/s | 7 days | healthy |
| billing.charged | 1 | 420/s | 90 days | healthy |
| audit.trail | 11 | 2.4k/s | 365 days | healthy |
| notify.outbound | 4 | 640/s | 3 days | lag rising |
| search.reindex | 2 | 90/s | 1 day | healthy |
Delivery notes
- Delivery is at-least-once — consumers must handle duplicate events on reconnect.
notify.outboundlag is climbing; see consumers for the group behind.- Ordering is guaranteed per key within a topic, not across the whole topic.
New services should read the wire protocol before
writing a custom consumer — the reconnect and offset rules are easy to get wrong.