Op maandag 23 juni 2014 15:27:38 UTC+2 schreef Ashley Aitken: > > > Sorry to bring this thread up again but I am still trying to work out the > read model in CQRS with Akka Persistence. > > On Tuesday, 6 May 2014 15:18:29 UTC+8, Martin Krasser wrote: >> >> >> The availability of (new) events in the journal is also an event. Whether >> a view is actively notified about their availability (= push) or if the >> view tries to find out itself (= pull) is rather a technical detail. A >> pull-based view even allows to decouple a processor from its view(s) in the >> dimension of lifetime. Why do you see this in conflict with being reactive? >> > > Do you mean that an active View can subscribe to the Event Bus and be > notified of the arrival of (new) events in the journal for its > Processor(s)? > > If not I am beginning to feel that this would be very useful, if not > necessary, for efficient view models built with Akka Persistence. > > Of course, along with Views watching multiple Processors, which I don't > believe will be the same as the new Akka Streams. > Why do you need a view that watches multiple Processors? This can already be achieved. You create a child View for every Processor you would like to watch. The child simply forwards all messages to its parent.
Regards, Jeroen > Thanks, > Ashley. > > -- >>>>>>>>>> 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.
