1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
//! The [`Broker`] / [`ConnectedBroker`] ladder: the entry point of any broker implementation.
use ;
/// An unconnected broker: configuration captured, no I/O performed yet.
///
/// `Broker` is the entry point of any broker crate (`ruststream-nats`, `ruststream-kafka`, ...).
/// The lifecycle is a ladder of consuming transitions, so each state is a distinct type and
/// out-of-order calls do not compile:
///
/// ```text
/// B::new(config) unconnected: sync, I/O-free construction
/// broker.connect(self) -> Connected the live connection, a typed witness
/// connected.shutdown(self) -> Closed the terminal witness (may carry diagnostics)
/// ```
///
/// Subscribing is described separately by a [`SubscriptionSource`](crate::SubscriptionSource)
/// (or the [`Subscribe`](crate::Subscribe) capability for the by-name case), resolved against the
/// [`Connected`](Self::Connected) form. Publishers are likewise produced by broker-specific
/// constructors.
///
/// `Send + Sync` is required so the runtime can move the broker across tasks.
///
/// # Writing a broker crate
///
/// A broker is a crate of its own that implements the traits below. It depends on the core with
/// the default features off, so it takes the trait surface and the runtime without the bundled
/// JSON codec or any other broker:
///
/// ```toml
/// [dependencies]
/// ruststream = { version = "0.7", default-features = false }
/// ```
///
/// [`MemoryBroker`](crate::memory::MemoryBroker) is the reference implementation of every trait
/// on this list, and `ruststream-nats`
/// ([docs.rs](https://docs.rs/ruststream-nats/latest/ruststream_nats/)) is a worked example over
/// a real client.
///
/// The required surface:
///
/// - `Broker` and [`ConnectedBroker`]: the lifecycle ladder described here.
/// - [`Subscribe`](crate::Subscribe) on the connected form, for subscriptions a name alone
/// identifies, and a [`SubscriptionSource`](crate::SubscriptionSource) descriptor for the ones
/// that need settings of the broker's own.
/// - [`Subscriber`](crate::Subscriber), the stream of deliveries, and
/// [`IncomingMessage`](crate::IncomingMessage), one delivery and its settlement.
/// - [`Publisher`](crate::Publisher), the live publish handle, constructed from a
/// [`PublishPolicy`](crate::PublishPolicy); [`DefaultPublish`](crate::DefaultPublish) names the
/// policy a reply and a retry copy use when the mount site names none.
///
/// Settings in the broker's own vocabulary ride the mount chain:
/// [`SubscriberBuilder`](crate::runtime::SubscriberBuilder) for a subscription's descriptor,
/// [`MapPublisher`](crate::runtime::MapPublisher) for a publish policy, and
/// [`Publisher::Options`](crate::Publisher::Options) for one message.
///
/// Optional capabilities, each implemented only where the transport supports it and each checked
/// by its own suite in [`conformance::capabilities`](crate::conformance::capabilities):
///
/// | Trait | For a broker that supports |
/// |---|---|
/// | [`BatchSubscriber`](crate::BatchSubscriber) | receiving messages in batches (offer it wherever you can) |
/// | [`TransactionalPublisher`](crate::TransactionalPublisher) | begin, commit and abort around publishes on the publisher handle |
/// | [`OwnedTransactions`](crate::OwnedTransactions) / [`Transaction`](crate::Transaction) | many transactions open at once per handle, each with its own buffer |
/// | [`RequestReply`](crate::RequestReply) | native request-reply |
/// | [`Partitioned`](crate::Partitioned) | a partition key on outgoing messages |
/// | [`Seekable`](crate::Seekable) / [`Seeker`](crate::Seeker) | repositioning a live subscription in a replayable log |
/// | [`Positioned`](crate::Positioned) | reporting a delivery's own position in the log |
/// | [`Carries`](crate::Carries) / [`CarriesBatch`](crate::CarriesBatch) | lending the decoded value a delivery already holds |
/// | [`DescribeServer`](crate::DescribeServer) | reporting a [`ServerSpec`](crate::ServerSpec) for `AsyncAPI` |
///
/// A body bounds its `Out` slot with the capability it needs (`Out<impl TransactionalPublisher>`)
/// and never with a broker's type, and the mount site checks the bound policy's live form against
/// it at compile time. Implementing the trait on the live publisher is all a service needs to
/// reach the typed form of that capability. A live value that offers more than the core's
/// capabilities extends the vocabulary as [`OutSlot`](crate::runtime::OutSlot) describes.
///
/// Around the traits: a per-delivery context with [`ContextField`](crate::ContextField) keys and
/// a batch context through [`BuildBatchContext`](crate::BuildBatchContext); protocol bindings for
/// the `AsyncAPI` document on the descriptor and the policies
/// ([`asyncapi::Bindings`](crate::asyncapi::Bindings)); a prelude of the crate's own ([`prelude`](crate::prelude#a-broker-crates-prelude));
/// the in-process mode under a `testing` feature ([`InProcess`](crate::testing::InProcess),
/// [`TestableBroker`](crate::testing::TestableBroker),
/// [`register_testable_broker!`](crate::register_testable_broker)); and
/// [`conformance`](crate::conformance), whose suites prove the crate and whose overview ends with the author checklist. Async work around encode and decode
/// (a schema registry, an envelope) belongs on the async edges, not in a codec, as the
/// [`codec`](crate::codec) overview describes.
///
/// # Lazy startup contract
///
/// Implementations MUST be constructible **synchronously**, without performing I/O: expose a plain
/// `new(..)` constructor that only captures configuration (addresses, credentials). All network
/// setup happens in [`connect`], which the runtime calls once at startup, after the synchronous
/// `#[ruststream::app]` builder has run. This is what lets a service be assembled with the app
/// macro regardless of broker. A broker that can only be built by connecting (an `async` "connect
/// and return the handle" constructor) does not satisfy this contract. Each broker also ships a
/// [`SubscriptionSource`](crate::SubscriptionSource) for its subjects, resolved against the
/// connected form.
/// [`conformance::harness::lifecycle`](crate::conformance::harness::lifecycle) checks the whole
/// ladder: synchronous construction, `connect`, subscribe through the source, deliver, ack,
/// `shutdown`, and the post-shutdown behaviour of aliased handles below.
///
/// The connected form holds the live client directly, so its operations never check a "maybe
/// connected" state. A broker may also keep a shared cell that `connect` fills, or shareable
/// in-process state, as the in-memory broker does: publishers can then be handed out while the
/// application is still being assembled, and the cell serves those early handles.
///
/// # Internal tasks run on the runtime the broker connected on
///
/// A task the broker starts on its own behalf (a delayed-redelivery timer, a reply dispatcher,
/// a commit window) runs on the runtime [`connect`] ran on. The connected form keeps
/// `tokio::runtime::Handle::current()` from `connect` and spawns every such task through it,
/// whichever thread publishes, settles or requests. A handler on a dedicated thread publishes and
/// settles from that thread's own runtime: a task spawned there waits behind the handler's
/// computation and stops with that runtime, while the connection it serves lives on.
/// [`conformance::harness::lifecycle`](crate::conformance::harness::lifecycle) publishes and
/// settles with a delay from a runtime that stops at once, and
/// [`conformance::capabilities::request_reply`](crate::conformance::capabilities::request_reply)
/// requests from one; both then expect the work to complete.
///
/// ```
/// use std::time::Duration;
///
/// use tokio::runtime::Handle;
/// use tokio::sync::mpsc::UnboundedSender;
/// use tokio::time::sleep;
///
/// struct ConnectedExample {
/// // Captured in `connect`.
/// runtime: Handle,
/// }
///
/// impl ConnectedExample {
/// fn requeue_after(&self, back: UnboundedSender<Vec<u8>>, delivery: Vec<u8>, delay: Duration) {
/// self.runtime.spawn(async move {
/// sleep(delay).await;
/// let _ = back.send(delivery);
/// });
/// }
/// }
/// # let _ = ConnectedExample::requeue_after;
/// ```
///
/// # Shutdown is a type, not a flag
///
/// [`ConnectedBroker::shutdown`] consumes the connected broker, so misuse by the owner of the
/// handle (a publish or subscribe after shutdown) is a compile error, not a runtime one. What
/// remains dynamic is transport reality, not contract bookkeeping: handles aliasing the
/// connection (publishers created before shutdown, clones of a shareable broker) MUST surface an
/// error when used after the connection closed, never a silent success against a dead
/// connection. The conformance lifecycle check verifies that aliased-handle behaviour.
///
/// `shutdown` never blocks or panics: every teardown step that can fail runs there and returns
/// its error. The [`Closed`](ConnectedBroker::Closed) witness carries teardown diagnostics as
/// plain data, or is `()`; [`ClosedMemoryBroker`](crate::memory::ClosedMemoryBroker) reports how many
/// subscriber registrations the shutdown dropped.
///
/// # Configuration and errors
///
/// The crate owns its `Config`; the core carries no broker-specific configuration. A field with
/// no sane default gets no `Default`, so a user sets it explicitly instead of inheriting a value
/// that breaks later.
///
/// Errors use `thiserror`: one crate-level error enum with variants by source, marked
/// `#[non_exhaustive]`. A library crate never uses `anyhow`.
///
/// # Examples
///
/// ```
/// use ruststream::{Broker, ConnectedBroker};
///
/// async fn ladder<B: Broker>(broker: B) -> Result<(), Box<dyn std::error::Error + Send + Sync>> {
/// let connected = broker.connect().await?;
/// let _closed = connected.shutdown().await?;
/// Ok(())
/// }
/// ```
///
/// [`connect`]: Self::connect
/// A connected broker: the typed witness of a live connection.
///
/// Obtained only from [`Broker::connect`]. The `'static` supertrait keeps the connected form an
/// owned value the runtime can hold and erase.
///
/// # Examples
///
/// ```
/// use ruststream::ConnectedBroker;
///
/// async fn stop<C: ConnectedBroker>(connected: C) -> Result<C::Closed, C::Error> {
/// connected.shutdown().await
/// }
/// ```
/// Shorthand for a broker's connected form, so bounds read
/// `S: SubscriptionSource<Connected<B>>` instead of spelling the associated type projection.
pub type Connected<B> = Connected;