[akka-user] How to manage internal state of the system

Hi, I am building a system where I am receiving a request from the client and putting it into messaging queue. I only send the response to the client once I have an acknowledgment from the messaging queue that the message was placed into. The way I am doing it is using Akka-HTTP by passing

[akka-user] HTTP server performance

Hi everyone. AKKA 2.5.9 / HTTP 10.0.11 As part of prototyping architecture, I ran some benchmarks (including http) few months ago. A simple hello world (request handler is completed with result immediately) had nice performance ~2.7m requests/minute. with 1,6m r/m when response included ask

Re: [akka-user] [Akka Streams] Difference between KillSwitch and Materializer.shutdown()

First warning sign: Why would you have one stream per materializer? shutting down the materializer while things are running is very brutal. It’s like forcefully pulling the carpet from under someone’s feet, and the laughing as they spill their coffee upon themselves — don’t do this as the go-to

[akka-user] [Akka Streams] Difference between KillSwitch and Materializer.shutdown()

I came across 2 ways to terminate a stream 1. KillSwitch 2. Materializer.shutdown() I see one difference which is - Materializer.shutdown() is used to kill all streams materialized by that materializer whereas KillSwitch can be used to terminate one particular stream. In

Re: [akka-user] Getting a timeout error when testing a stream with mapAsync stage

Thank you. So I'll add the request(1) before the expectComplete(). I actually use the .runWih(TesSink.probe) in my test, I used the TestSubscriber.manualProbe just in the demonstration example to be able to print the intermediate results. Jakub On 19 February 2018 at 12:18, Patrik Nordwall

Re: [akka-user] Getting a timeout error when testing a stream with mapAsync stage

btw, probably easier to use .runWith(TestSink.probe) in that example, or .runWith(Sink.seq).futureValue On Mon, Feb 19, 2018 at 12:12 PM, Patrik Nordwall wrote: > Doc improvement is welcome. If you add request(1) before the > expectComplete it’s not undefined, then

Re: [akka-user] Getting a timeout error when testing a stream with mapAsync stage

Doc improvement is welcome. If you add request(1) before the expectComplete it’s not undefined, then you are supposed to get it. /Patrik mån 19 feb. 2018 kl. 07:40 skrev Jakub Kahovec : > I had another thought about this behaviour and two things came to my mind. > First,

Re: [akka-user] How to build the Akka API documentation for offline use?

Run the unidoc task in sbt. It comes from sbt-unidoc and aggregates the API docs from all sub-projects to ./target/unidoc/ On Mon, Feb 19, 2018 at 9:45 AM Thai wrote: > Hi All, > > I noticed that the Akka API doc is unavailable to download like Scala, so > I git-cloned

Re: [akka-user] Akka Actor usage in Apache Spark and Apache Flink

Another pretty big Akka based project (as in, really using Akka a lot) is Apache OpenWhisk, the open source "amazon lambda"; Check it out as well. https://github.com/apache?q=openwhisk On Mon, Feb 19, 2018 at 2:32 PM, Konrad “ktoso” Malawski < konrad.malaw...@lightbend.com> wrote: > Best to ask

Re: [akka-user] Akka Actor usage in Apache Spark and Apache Flink

Best to ask on a Flink forum ;-) -- Cheers, Konrad 'ktoso ' Malawski Akka @ Lightbend On February 19, 2018 at 14:32:15, Unmesh Joshi (unmeshjo...@gmail.com) wrote: Thanks Konrad. What I was interested in was what use cases both Spark and

[akka-user] Alpakka - Contribution ideas

Hi, I've always known that the Akka community is very welcoming to the contributors. And Enno proved that to me again. I just made a small contribution towards the self-contained example (789 ) in Alpakka and I am looking for ideas where I could learn