aetelier_connect::workers::topic_publisher¶
Topic-keyed broadcast channels for raw event publishing. Topic-keyed broadcast channels for raw event publishing.
The TopicPublisher is the output interface of the
DataWorker (see super::data_worker::DataWorker). Each exchange
subscription maps to exactly one topic, and the DataWorker
publishes raw (un-normalised) events through the matching publisher.
Topic naming convention¶
Examples:
- orderbook.50.BTCUSDT
- trade.all.BTCUSDT
- liquidation.all.BTCUSDT
- funding.all.BTCUSDT
- open_interest.all.BTCUSDT
Back-pressure¶
The underlying tokio::sync::broadcast channel has a bounded
capacity. If all receivers lag behind, the oldest messages are
silently dropped — this is acceptable because the data_worker's
contract is best-effort ingestion, not guaranteed delivery.
Guaranteed delivery is the downstream consumer's responsibility.
Skeleton API reference
This page lists the public items in aetelier_connect::workers::topic_publisher with a
one-line summary each. Signatures and source live in the SDK
repository.
Structs¶
| Item | Summary |
|---|---|
TopicMessage |
Envelope wrapping a raw exchange event with ingestion metadata. |
TopicPublisher |
A single named broadcast channel. |
TopicRegistry |
Collection of TopicPublishers keyed by topic name. |
Enums¶
| Item | Summary |
|---|---|
PublishError |
Error from TopicRegistry::publish(). |
Constants¶
| Item | Summary |
|---|---|
DEFAULT_CHANNEL_CAPACITY |
Default broadcast channel capacity per topic. |