Good morning (east coast of usa 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). 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? 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. 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.
