Hi Chanan,
On Wed, Apr 23, 2014 at 3:12 PM, Chanan Braunstein < [email protected]> wrote: > Good morning (east coast of usa at least), > > Good evening (Europe at least) > We are looking to build a fairly large system and considering > Akka-Persistence/CQRS/DDD for it but we are still unsure of a few things. > > If we have two different services (Play webapps). One is responsible for > reading off a queue and/or some rest end points and it inserts data into > the system via an Akka Persistence event source. The other system would be > the transactional one that actually does "stuff" - Can it have another > actor with the same processorId, that will be notified of the new data as > it comes in? (Yes, sounds like a view, but it will need to also have its > own events as stuff happens on the system). > A view is read-only, apart from that it can have its own snapshots (to speed up replay). You can have a view that forwards the messages to another processor, that can store other things. > If that doesn't make sense, is there another way of doing, short of making > one system and one actor? > > Similar question, can there be two actors in the one cluster with the same > processorId, will they get notified of new data that the other actor > changes? > No, it can only be one Processor instance per processorId. In a cluster you will use Cluster Singleton<http://doc.akka.io/docs/akka/2.3.2/contrib/cluster-singleton.html>or Cluster Sharding <http://doc.akka.io/docs/akka/2.3.2/contrib/cluster-sharding.html>. > I guess that is the same as above since its the processorId that matters > and not the cluster. > > Lastly, more general question, I guess since Akka-Persistence is still > somewhat new (if you don't count eventsourced) and clustering is newish, > but is there any guidance on how to build large system using those two > pieces? We are looking for some do's and don'ts, best practices, patterns, > etc. > You might find some useful bullets in these slides: http://www.slideshare.net/patriknw/akka-persistence-webinar Cheers, Patrik > > Thanks, > Chanan > > -- > >>>>>>>>>> Read the docs: http://akka.io/docs/ > >>>>>>>>>> Check the FAQ: > http://doc.akka.io/docs/akka/current/additional/faq.html > >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user > --- > You received this message because you are subscribed to the Google Groups > "Akka User List" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/akka-user. > For more options, visit https://groups.google.com/d/optout. > -- Patrik Nordwall Typesafe <http://typesafe.com/> - Reactive apps on the JVM Twitter: @patriknw JOIN US. REGISTER TODAY! <http://www.scaladays.org/> Scala <http://www.scaladays.org/> Days <http://www.scaladays.org/> June 16th-18th, <http://www.scaladays.org/> Berlin <http://www.scaladays.org/> -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
