ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #akka
Learn how Akka Typed Actors enforce compile‑time message safety, see a counter example, and avoid common pitfalls like blocking calls or mixed APIs.
When streaming a large relational dataset through an Akka Streams Alpakka JDBC source, the goal is to bound memory and query cost while preserving back-pressure. Offset-based pagination is straightforward to express using .drop(offset).take(limit) , but deep offsets force the database to scan and discard preceding rows. Keyset pagination avoids that cost by
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
For a low-traffic Akka actor system, the choice between the default Java serialization and Protostuff often reduces to a trade-off between per-message CPU overhead and schema maintenance burden. Java serialization relies on runtime reflection and classloader traversal, adding CPU cycles and GC pressure that persist even at low message rates. Protostuff produ
Operators need to decide which Split Brain Resolver strategy to enable in their Akka Cluster to prevent divergent singletons while maintaining acceptable availability during network partitions. The decision is complicated by version‑specific availability of SBR, the trade‑offs among static‑quorum, keep‑majority, keep‑oldest, keep‑referee, lease‑majority and
Bind interface choice for Akka HTTP in containers Goal: expose an Akka HTTP server only to intended callers while allowing the container orchestrator or sidecar to reach it. `Http().newServerAt(interface, port)` binds to the supplied interface, so `127.0.0.1` keeps traffic local to the host, whereas `0.0.0.0` accepts IPv4 connections from every interface. Co
Goal: Ensure that when multiple Akka cluster nodes restore snapshots concurrently, the recovered actor state remains linearizable and all nodes observe the same event sequence. Constraints: File‑based snapshots require the actor system to be stopped before restore to avoid inconsistency, which prevents concurrent restores but yields faster recovery; JDBC‑bac
Licensing boundary between Akka 2.6 LTS and 2.8+ The Akka actor runtime (Classic and Typed) ships under Apache 2.0 through the 2.6 LTS line. Starting with Akka 2.8, the same runtime artifacts are distributed under Business Source License 1.1, which restricts certain production uses unless a commercial agreement is in place. The license converts to Apache 2.0
scala