Actors may not be that cheap.
They are ~400 bytes for an Actor; plus whatever you put inside one of
course, but that’s your state, not the Actor’s fault ;)
I tried to create a worker actor every time the master actor received a
start job message and found out that it created a new thread to run
Actors may not be that cheap. I tried to create a worker actor every time
the master actor received a start job message and found out that it created
a new thread to run it. Seems to me that the default dispatcher is an
unbounded thread pool. It doesn't look good to me -- it falls back to the
Actors are cheap so you can start one actor (make them child actors if some
actor that manages the work things), so then you don’t have that
multiplexing issue at all.
Remember to put the blocking things onto a dedicated thread pool dispatcher
— read docs about dealing with blocking to see how
Do you have configuration that allows a Akka-Http client application to
specify the host and port of a certificate authority in addition to the
public internet one? Failing that, can you provide some guidance on custom
code that would alleviate much of the needs to go to Javax interface,
I'm newbie in Akka. Here's one thing I'm trying to achieve, a simple job
manager. There are jobs involving SQL queries and CPU intended computation.
The jobs should be cancellable while they're running. Here's my code to
simulate it. The worker actor sends "continue" message to itself if no
Hi,
in akka-stream, processing is usually run in a fused fashion, i.e. without
further configuration one stream will run in a single actor so all
operations are run sequentially. In such a synchronous scenario, there's
little room for elements to ever get dropped because the actorRef stage
I use RestartSource.withBackoff to recover from broker outages.
https://doc.akka.io/docs/akka/current/stream/stream-error.html#delayed-restarts-with-a-backoff-stage
Hope that helps.
Michał
On Friday, 12 January 2018 22:41:04 UTC, Sean Rohead wrote:
>
> I am using akka-stream-kafka 0.18. I have
I want some suggestions/recommendations on the following.
Today we have a legacy .NET system that gathers information from customers
environment and reports back to our backend.
Now this system is built the following way,
The client is a VB.Net application.(Usually running outside our
