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
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
// Copyright (c) Sean Lawlor
//
// This source code is licensed under both the MIT license found in the
// LICENSE-MIT file in the root directory of this source tree.
//! # Factory actors
//!
//! A factory is a manager of a pool of workers on the same node. This
//! is helpful for job dispatch and load balancing when single-threaded execution
//! of a single [crate::Actor] may not be sufficient. Factories have a set "Job" syntax
//! which denotes a key and message payload for each action. Workers are effectively mindless
//! agents of the factory's will.
//!
//! ## Worker message routing mode
//!
//! The factory has a series of dispatch modes which are defined in the [routing] module and
//! control the way the factory dispatches work to workers. This should be selected based
//! on the intended workload. Some general guidance:
//!
//! 1. If you need to process a sequence of operations on a given key (i.e. the Job is a user, and
//! there's a sequential list of updates to that user). You then want the job to land on the same
//! worker and should select [routing::KeyPersistentRouting] or [routing::StickyQueuerRouting].
//! 2. If you don't need a sequence of operations then [routing::QueuerRouting] is likely a good choice.
//! 3. If your workers are making remote calls to other services/actors you probably want [routing::QueuerRouting]
//! or [routing::StickyQueuerRouting] to prevent head-of-the-line contention. Otherwise [routing::KeyPersistentRouting]
//! is sufficient.
//! 4. For some custom defined routing, you can define your own [routing::CustomHashFunction] which will be
//! used in conjunction with [routing::CustomRouting] to take the incoming job key and
//! the space which should be hashed to (i.e. the number of workers).
//! 5. If you just want load balancing there's also [routing::RoundRobinRouting] for general 1-off
//! dispatching of jobs
//!
//! ## Factory queueing
//!
//! The factory can also support factory-side or worker-side queueing of extra work messages based on the definition
//! of the [routing::Router] and [queues::Queue] assigned to the factory.
//!
//! Supported queueing protocols today for factory-side queueing is
//!
//! 1. Default, no-priority, queueing: [queues::DefaultQueue]
//! 2. Priority-based queuing, based on a constant number of priorities [queues::PriorityQueue]
//!
//! ## Worker lifecycle
//!
//! A worker's lifecycle is managed by the factory. If the worker dies or crashes, the factory will
//! replace the worker with a new instance and continue processing jobs for that worker. The
//! factory also maintains the worker's message queue's so messages won't be lost which were in the
//! "worker"'s queue.
//!
//! ## Example Factory
//! ```rust
//! use ractor::concurrency::Duration;
//! use ractor::factory::*;
//! use ractor::Actor;
//! use ractor::ActorProcessingErr;
//! use ractor::ActorRef;
//! use ractor::RpcReplyPort;
//!
//! #[derive(Debug)]
//! enum ExampleMessage {
//! PrintValue(u64),
//! EchoValue(u64, RpcReplyPort<u64>),
//! }
//!
//! #[cfg(feature = "cluster")]
//! impl ractor::Message for ExampleMessage {}
//!
//! /// The worker's specification for the factory. This defines
//! /// the business logic for each message that will be done in parallel.
//! struct ExampleWorker;
//! #[cfg_attr(feature = "async-trait", ractor::async_trait)]
//! impl Worker for ExampleWorker {
//! type Key = ();
//! type Message = ExampleMessage;
//! type State = ();
//! type Arguments = ();
//! async fn pre_start(
//! &self,
//! wid: WorkerId,
//! factory: &ActorRef<FactoryMessage<(), ExampleMessage>>,
//! startup_context: Self::Arguments,
//! ) -> Result<Self::State, ActorProcessingErr> {
//! Ok(startup_context)
//! }
//! async fn handle(
//! &self,
//! wid: WorkerId,
//! factory: &ActorRef<FactoryMessage<(), ExampleMessage>>,
//! Job { msg, key, .. }: Job<(), ExampleMessage>,
//! _state: &mut Self::State,
//! ) -> Result<(), ActorProcessingErr> {
//! // Actual business logic that we want to parallelize
//! tracing::trace!("Worker {} received {:?}", wid, msg);
//! match msg {
//! ExampleMessage::PrintValue(value) => {
//! tracing::info!("Worker {} printing value {value}", wid);
//! }
//! ExampleMessage::EchoValue(value, reply) => {
//! tracing::info!("Worker {} echoing value {value}", wid);
//! let _ = reply.send(value);
//! }
//! }
//! Ok(key)
//! }
//! }
//! /// Used by the factory to build new [ExampleWorker]s.
//! struct ExampleWorkerBuilder;
//! impl WorkerBuilder<ExampleWorker, ()> for ExampleWorkerBuilder {
//! fn build(&mut self, _wid: usize) -> (ExampleWorker, ()) {
//! (ExampleWorker, ())
//! }
//! }
//! #[tokio::main]
//! async fn main() {
//! let factory_def = Factory::<
//! (),
//! ExampleMessage,
//! (),
//! ExampleWorker,
//! routing::QueuerRouting<(), ExampleMessage>,
//! queues::DefaultQueue<(), ExampleMessage>,
//! >::default();
//! let factory_args = FactoryArguments::builder()
//! .worker_builder(Box::new(ExampleWorkerBuilder))
//! .queue(Default::default())
//! .router(Default::default())
//! .num_initial_workers(5)
//! .build();
//!
//! let (factory, handle) = Actor::spawn(None, factory_def, factory_args)
//! .await
//! .expect("Failed to startup factory");
//! for i in 0..99 {
//! factory
//! .cast(FactoryMessage::Dispatch(Job {
//! key: (),
//! msg: ExampleMessage::PrintValue(i),
//! options: JobOptions::default(),
//! accepted: None,
//! }))
//! .expect("Failed to send to factory");
//! }
//! let reply = factory
//! .call(
//! |prt| {
//! FactoryMessage::Dispatch(Job {
//! key: (),
//! msg: ExampleMessage::EchoValue(123, prt),
//! options: JobOptions::default(),
//! accepted: None,
//! })
//! },
//! None,
//! )
//! .await
//! .expect("Failed to send to factory")
//! .expect("Failed to parse reply");
//! assert_eq!(reply, 123);
//! factory.stop(None);
//! handle.await.unwrap();
//! }
//! ```
use Arc;
use crateDuration;
use crateInstant;
use crateBoxedDowncastErr;
use crateMessage;
use crateRpcReplyPort;
pub use DiscardHandler;
pub use DiscardMode;
pub use DiscardReason;
pub use DiscardSettings;
pub use DynamicDiscardController;
pub use Factory;
pub use FactoryArguments;
pub use FactoryArgumentsBuilder;
pub use Job;
pub use JobKey;
pub use JobOptions;
pub use MessageRetryStrategy;
pub use RetriableMessage;
pub use FactoryLifecycleHooks;
pub use LeakyBucketRateLimiter;
pub use RateLimitedRouter;
pub use RateLimiter;
use FactoryStatsLayer;
pub use DeadMansSwitchConfiguration;
pub use Worker;
pub use WorkerBuilder;
pub use WorkerCapacityController;
pub use WorkerMessage;
pub use WorkerProperties;
pub use WorkerStartContext;
/// The settings to change for an update request to the factory at runtime.
///
/// Note: A value of `Some(..)` means that the internal value should be updated
/// inside the factory's state. For values which are originally optional to the factory,
/// we use `Option<Option<T>>`, so if you want to UNSET the value, it would be `Some(None)`.
/// Unique identifier of a disctinct worker in the factory
pub type WorkerId = usize;
/// Messages to a factory.
///
/// **A special note about factory messages in a distributed context!**
///
/// Factories only support the command [FactoryMessage::Dispatch] over a cluster
/// configuration as the rest of the message types are internal and only intended for
/// in-host communication. This means if you're communicating to a factory you would
/// send only a serialized [Job] which would automatically be converted to a
/// [FactoryMessage::Dispatch(Job)]