Fearless concurrency

Rust’s slogan “fearless concurrency” means the compiler rejects data races before you ship.

Message passing

Instead of two threads locking the same Vec, one task sends ownership through a channel; another receives it.

let (tx, mut rx) = tokio::sync::mpsc::channel(32);
tokio::spawn(async move {
    while let Some(event) = rx.recv().await {
        analyze(event).await;
    }
});
tx.send(payload).await?;

Use ConcurrencyChannels — send events from ingestion, receive in the analyzer side.

Why millipede prefers this

Kafka already is a distributed channel. Inside a service, mpsc or bounded queues backpressure slow producers instead of corrupting memory.

Teach-back prompt

When would you use Arc<Mutex<T>> instead of a channel?