Hey,
currently our lambda architecture is designed this way :
Tree based hierarchy of View Materializer Actors which is mostly done due
to Actor supervision. Each Materializer Actor triggers an akka-stream that
builds the resulting View. This design works but it leads to complex actors
because
Oh and I put garbage collection in the title because the only thing i can
think of is that this actor is somehow cleaned up? But I thought
registering it to the ActorSystem would prevent this.
On Wednesday, October 28, 2015 at 1:49:02 PM UTC-5, ryan walsh wrote:
>
> Hello,
>
> I have a UI Contro
Hello,
I have a UI Controller that listens to requests from the user, and uses
Akka to talk to some other back end services for request processing.
When I bootstrap my UI, I wire in an ActorSystem object.
When I receive a request from a user, I create an "actor-per-request" using
the wired in
>
>
> What's in the case of Akka the way to prevent threads (that is actors)
> from blocking when doing blocking IO (querying databases, doing REST calls,
> reading from files, etc.)? Go through NIO or is there some stuff provided
> for this?
>
> Thanks for any answers.
>
http://doc.akka.io/docs/a
For posterity, using Roland's advice, I encoded the state of the processing
into the flow itself, and it cleaned up all of my issues and got rid of any
stream-based state.
sealed trait HandlerEvent
case class Open(ctxt: Context) extends HandlerEvent
case class Handle(ctxt: Context, state: State)
Hi guys,
I was playing around with Akka Cluster trying to make work a Cluster with
two nodes using Cassandra for persistence.
This is a demo project I created to reproduce the case:
https://github.com/gvolpe/akka-cluster-demo
The rebalancing and the remember entities feature are working smooth
Hi,
Following is my app.conf. I am losing almost 50% of the messages. Is it
because of the ClusterRouterPool ?
Running it on 2 node cluster(each is m4.xlarge machine)
There are two actors-
akka {
loglevel = "INFO"
loggers = ["akka.event.slf4j.Slf4jLogger"]
log-dead-letters-during-shutdo