Hi Brice,
Sounds like you have found your way forward.
A few curious thoughts. Are you using an Akka Cluster? Then Cluster Sharding
http://doc.akka.io/docs/akka/2.3.6/contrib/index.html might help you
here. It would take the role of your SessionService and manages the session
actors for you
Hi,
I'm converting an homegrown (cassandra based) persistence system to the
akka-persistence system.
My system have clients connecting to it, creating a session in the
system. This session is implemented as SessionActor (which is now a
PersistentActor using the session id as persistenceId) and
I think I would make the sessions persistent actors, children of a
SessionManager that is not a persistent actor. The SessionManager can
always see if a child exists.
http://typesafe.com/activator/template/akka-persistence-event-sourcing
If you have a use case that involves checking for session existence without
sending a command to the session, you could publish a SessionCreated
*domain* event (not an Akka persistence event) to the read side by
publishing it to an Akka EventBus. The subscriber could then store some
Hi,
On Wed, 2014-10-22 at 08:46 -0700, Richard Rodseth wrote:
If you have a use case that involves checking for session existence
without sending a command to the session, you could publish a
SessionCreated *domain* event (not an Akka persistence event) to the
read side by publishing it to
