Akka Typed noSender limits and replyTo behavior

Akka Typed 2.6.x noSender limits for optional replies

0 reputation · 01 Nov 2022, 18:10 UTC

21.5K views0

Fire-and-forget message design in Akka Typed

Goal is to define a message protocol in Akka Typed 2.6.x where some messages are fire-and-forget and others carry an explicit reply channel, without requiring a replyTo field on every message type.

The typed API does not expose a noSender reference. Classic ActorRef.noSender() is not available in the typed API, and message contracts rely on explicit ActorRef parameters for replies.

Is there a documented typed mechanism to signal a no-reply intent while keeping strict type checking?
What limits does the absence of a typed noSender impose on mixing fire-and-forget and request-response messages in the same protocol?
Are there version-specific notes for Akka 2.6.x regarding support for optional replies?

3,155 following

Keep exploring this topic

Akka Cluster Sharding: remember-entities vs passivation-only for sub-second recovery SLO

Choosing between remember-entities (persistent mapping) and passivation-only (in-memory) for 120k entities with an 800 ms recovery SLO. Persistent mode adds 1–3 s replay latency; passivation-only drops entities on rebalance. No hybrid mode exists. Seeking pattern to meet SLO without dual topology.

AskTimeoutException when actor does not reply within Timeout

Explore how Akka’s AskTimeoutException signals a timeout in the ask pattern and examine the unresolved semantics of Cancellable.cancel() after an actor has stopped. Key questions address return values, shutdown patterns, and supervision interactions.

Offset versus keyset pagination for bounding an Alpakka JDBC source without a unique ordered column

A design question comparing offset-based and keyset pagination for Akka Streams Alpakka JDBC sources when the table lacks a unique ordered column.

Default Fork‑Join Dispatcher vs. Pinned Dispatcher: Which Minimizes Idle Thread Cost for Low‑Traffic Akka Workloads?

How does Akka’s default fork‑join dispatcher behave under near‑zero traffic, and how does that compare to a pinned dispatcher in terms of idle thread cost? The minimum thread count for the default dispatcher is undocumented, creating uncertainty for low‑traffic cost optimization.

Akka Typed 2.6.x noSender limits for optional replies

Fire-and-forget message design in Akka Typed

0 answers

Your perspective belongs here.

0 question comments

Good answers start here.