Re: [akka-user] Cancel Actor job

Have a look at "cluster sharding”, it’s smarter than just routers. -- Cheers, Konrad 'ktoso ' Malawski Akka @ Lightbend On February 2, 2018 at 11:09:19, Richard Gong (gong...@gmail.com) wrote: That works in a single machine. Now take a st

Re: [akka-user] Cancel Actor job

That works in a single machine. Now take a step forward to have the workers in a cluster. The master needs to dispatch jobs to workers. I'm looking at the document of router, https://doc.akka.io/docs/akka/current/cluster-usage.html?language=scala#router-with-pool-of-remote-deployed-routees. M

Re: [akka-user] Re: ANNOUNCE: Akka Multi-DC Persistence

Hi Igor, There are several reasons, such as: - we believe that it's useful to have the strong consistency with single-writer within one DC, and "only" have the asynchronous replication between DCs - failures and partitions within one DC can be handled by SBR, fits the model of Akka

[akka-user] Re: ANNOUNCE: Akka Multi-DC Persistence

Hello Patrik, excellent news! May I ask why you chose to have static topology over dynamic one? With the latter one, I mean lifting the "only one writer" requirement locally as well, thus enabling always-available operation --- even during netsplit, where you could have multiple writers. CRDT-

[akka-user] Re: Recommendations on a PoC for system migration from VB.NET to Scala/Akka stack

DId you see my note ? On Monday, January 29, 2018 at 12:22:01 AM UTC+5:30, Damian Blazejewski wrote: > > Generally, it sounds good. > > i. -> you don't say anything about the deployment but I would think about > Akka Cluster from the beginning. > iv. -> what data do you persist? You can do it as