Hi Olger,
What if you keep the sharded event sourced actors (+10k), but let them also
send the events to one or a few processors. Then you can connect the
views/streams to these processors.
If you don't like storing the events twice you can instead store some meta-data
(processor-id,
Hi Patrick,
Sounds like an interesting approach, storing some meta-data at the view may
help to check / show the reliability of the system.
At this moment the events are sent to a processor per node that publishes
the event (distributed pub sub)
When you talk about view, that's the
On Sun, Apr 20, 2014 at 2:47 PM, Olger Warnier ol...@spectare.nl wrote:
Hi Patrick,
Sounds like an interesting approach, storing some meta-data at the view
may help to check / show the reliability of the system.
At this moment the events are sent to a processor per node that publishes
the
I'm using 2.3
I eventually stumbled across this
(more or less)
akka.persistence.journal.plugin = akka.persistence.journal.inmem
from the reference configuration file for snapshot 2.4
Is there any particular reason this is hidden away with no mention in the
docs?
--
Read the docs:
On Sunday, April 20, 2014 4:59:22 PM UTC+2, Patrik Nordwall wrote:
On Sun, Apr 20, 2014 at 2:47 PM, Olger Warnier ol...@spectare.nljavascript:
wrote:
Hi Patrick,
Sounds like an interesting approach, storing some meta-data at the view
may help to check / show the reliability of the
Curious how would you recommend accomplishing that in this example (getting
messages to /project/someactor containing ActorRefs for
actors /project/users/user-X, /project/users/user-Y, /project/users/user-Z)?
Chris
On Wednesday, April 16, 2014 12:15:15 PM UTC-7, √ wrote:
Hi Chanan,
I'd say
I don't believe it is hidden, well not completely at least. There is a
reference in the Akka
documentationhttp://doc.akka.io/docs/akka/snapshot/scala/persistence.htmlto
the Community
Contribution http://akka.io/community/ journals provided, which is where
the in-memory one is listed as well
I think a possible solution might look like this:
import scala.collection.mutable.Queue
import scala.concurrent.duration._
import akka.actor._
import akka.routing._
object State extends Enumeration {
val Unknown, Created, Sent = Value
}
trait Action
case class Unknown() extends
