Hi Hannes, consider using channels with an aggregating processor as destination (or, more generally, an actor that updates a database). If the source processors are eventsourced processors make sure to setup reliable event delivery<http://doc.akka.io/docs/akka/2.3.1/scala/persistence.html#reliable-event-delivery>. See also this discussion<https://groups.google.com/forum/#!topic/akka-user/ChVFU9-cKRk/discussion> .
Cheers, Martin Am Mittwoch, 26. März 2014 23:15:07 UTC+1 schrieb Hannes Stockner: > > Hi, > > I am using cluster sharding to distribute aggregate root instances and I > am struggling to figure out how best to derive new event streams. Below is > an example of the concept I have in mind specified in a given-when-then > format. > > Given Multiple Entries distributed over different nodes > When Event A or Event B > > Then Add Event A or Event B to the new stream > > I have looked at views, but a view operates on single streams (e.g. the > stream provided by a single entry) rather than per entry type. Relating to > the example, a view allows events to be consumed for a subset of aggregate > root instances, rather than all of the events for an aggregate root type. > It’s implied that the solution needs to be reliable and can recover missed > events. > > > Thank you in advance for your help > > -- >>>>>>>>>> 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 akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
