Patrik, you can do no wrong.
On Tuesday, 20 January 2015 22:15:39 UTC+11, Patrik Nordwall wrote:
Another alternative is to use akka-data-replication
https://github.com/patriknw/akka-data-replication.
/Patrik
On Tue, Jan 20, 2015 at 3:16 AM, Soumya Simanta soumya@gmail.com
, of course, I said a month ago).
On Sunday, January 4, 2015 6:42:21 PM UTC-7, Kane Rogers wrote:
Hi, hAkkers!
We're in the process of moving our distributed Akka service from the dark
ages of remoting and manual management of IPs (shudder) into the wonderful
new world of Akka Cluster
Hi, hAkkers!
We're in the process of moving our distributed Akka service from the dark
ages of remoting and manual management of IPs (shudder) into the wonderful
new world of Akka Cluster.
Currently, our project is split up something like this:
- spray-frontend
- worker-1
- worker-2
Thanks, Andrew! This was super helpful to me!
Sorry for the newbie question, but why do we define a companion object for
MainActor, and create the props that way? What benefit does this give us?
On Wednesday, 26 November 2014 01:23:40 UTC+11, Andrew James Ramirez wrote:
Hi,
What is the best
Yes, exactly! Think of it as an HTTP endpoint, you can only send messages
and see what it responds with, if you can observe the effect of the
previous message by sending it another message, then you can observe and
test the relationship.
*Gold.* Thank you.
On Thursday, 20 November
