ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #akka
Learn how to use Akka Cluster Sharding to ensure single-writer consistency across distributed nodes, preventing race conditions in stateful applications.
Learn how Akka Typed Actors enforce message protocols at compile time, reducing runtime errors and simplifying refactors in Scala/Java applications.
Learn how Akka Typed Actors enforce compile‑time message safety, see a counter example, and avoid common pitfalls like blocking calls or mixed APIs.
Diagnosing a Backpressure Bottleneck We need to determine why throughput drops and latency spikes in an Akka Streams pipeline. The suspect is a backpressure signal propagating from a downstream stage, potentially causing upstream stages to pause and queues to grow. Constraints include the default 16‑element buffer per stage, the configured overflow strategy,
Integration Boundary: Akka HTTP & java.time The goal is to ensure that HTTP requests containing an ISO‑8601 formatted Date header are correctly interpreted by an Akka HTTP service that otherwise relies on java.time for time‑zone handling. Akka HTTP’s current HttpDate parser accepts only RFC1123, RFC1036, and ANSI C asctime formats, omitting ISO‑8601 and
Schema Evolution in Akka Persistence When updating the event schema for a Persistent Actor, the primary goal is ensuring that a previous binary version can still recover state if a deployment must be rolled back after new events have been written to the journal. The Compatibility Constraint Akka Persistence provides EventAdapter and upcaster chains to handle
Goal Determine the best approach for reducing latency in Scala applications that process many concurrent requests involving blocking operations. Constraints & Uncertainty Thread starvation in the global ExecutionContext can inflate response times, while the actor model introduces context‑switch overhead and queue back‑pressure. The impact of dispatcher c
In an Akka system, an actor can be terminated by sending a Kill message, which throws an ActorKilledException and is processed by the actor's supervisor. Assuming the default supervisor strategy (which stops the actor and then restarts it), what happens to the messages that were already in the actor's mailbox at the moment the Kill was processed? Are those m
When using Akka’s ask pattern, a Future is returned that completes with a Failure if the actor does not reply within the specified timeout. However, if the actor sends a reply after the timeout has elapsed, the Future is already failed and the reply is not observed by the caller. The documentation notes that such late replies are “dropped,” but it does not e
scala