Dear Hakkers,
I would be interested in using Google Cloud Platform for deploying Akka
clusters with persistent actors. I was wondering if there is a
possibility and if somebody did use the Google Data Store for Akka
persistency.
I understand that for that one would need to be able to implement
Thanks Konrad.
Well, I kinda get the "level of abstraction" but what about a cluster
node failure running my Akka streams stages? How would you cope with
it? Now, Is my only option to use Kafka and some kind of partition and
offset syncing? Please elaborate on that!
Are you suggesting that
Hi,
I'd like to better understand the relationship of Akka streams and Akka
cluster including persistency. What I mean by that is how would you
make an Akka streams resilient in a Akka cluster setup? How would I use
persistent actors with Akka streams? Is the use of `Source.actorRef`
and
terSystem@myhost:2551",
"akka.tcp://ClusterSystem@myhost:2552"
]
--8<---cut here---end--->8---
Even though the nodes was started they couldn't of course join the
cluster because they were talking to a different host on a diffe
ersistence.journal.leveldb
> # use the java one
> akka.persistence.journal.leveldb.native = off
> and add the following library
> "org.iq80.leveldb" % "leveldb" % "0.7",
> to your dependencies to add the storage implementation itself.
> On Thu
Hi,
I'm exploring the wonderful world of Akka cluster and sharding at the
moment. So far, I've setup just one persistent actor `PublicationActor`
and I start the cluster sharding as follows:
--8<---cut here---start->8---
ClusterSharding(system).start(
Hi hakkers,
I'm struggling with the same issue trying to port the spray code in
https://github.com/NET-A-PORTER/spray-actor-per-request to akka http. It
seems that the perRequest method in the PerRequest trait should return a
Future[RouteResult] which will be completed in the newly created
actor.
