I believe Martin may have kindly answered, at least part of, this question
in another thread.
If I may paraphrase him: the way Akka Persistence Views work currently
(polling) is an implementation detail and later versions of Akka
Persistence may provide a push-based approach as well.
If jou
Sorry for the delay in responding - I had lots of work work to attend to.
Vaughn - thank you for your suggestion regarding the EventBus. To be
honest, as I am new to Akka I was not really aware that the EventBus even
existed. Now that I am, I still need to get my head around the use of
messa
Can someone share the link to Pet Helland's paper? I couldn't locate it.
--
>> 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/
On 06.05.14 08:59, Ashley Aitken wrote:
I believe Martin may have kindly answered, at least part of, this
question in another thread.
If I may paraphrase him: the way Akka Persistence Views work currently
(polling) is an implementation detail and later versions of Akka
Persistence may prov
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-b
On 06.05.14 09:31, Ashley Aitken wrote:
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 (= p
Thanks Martin.
On Tuesday, 6 May 2014 15:53:28 UTC+8, Martin Krasser wrote:
>
>
> On 06.05.14 09:31, Ashley Aitken wrote:
>
> Reactive I take to mean push, the events are driving action in the system,
> from GUI to GUI.
>
> From a user's (= API) perspective, a View will always receive Per
Why not use a business-level identity as a correlation id that travels
through the processing and view compositions that you describe? In the end
you could use an EventBus to tell a given presentation that its newly
composed view is available. You might find your answers using something
like th
On 06.05.14 19:10, Ashley Aitken wrote:
Thanks Martin.
On Tuesday, 6 May 2014 15:53:28 UTC+8, Martin Krasser wrote:
On 06.05.14 09:31, Ashley Aitken wrote:
Reactive I take to mean push, the events are driving action in
the system, from GUI to GUI.
From a user's (= API) per
Pat Helland: Life beyond Distributed Transactions
B/
On 12 May 2014 at 14:19:10, Chanan Braunstein (chanan.braunst...@pearson.com)
wrote:
Can someone share the link to Pet Helland's paper? I couldn't locate it.
--
>> Read the docs: http://akka.io/docs/
>> Check the FAQ:
>>>
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
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 i
Hi Jeroen,
On Friday, 27 June 2014 05:13:54 UTC+8, Jeroen Gordijn wrote:
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.
>
Ther
Hi Ashley,
Op vrijdag 27 juni 2014 06:57:17 UTC+2 schreef Ashley Aitken:
>
> Hi Jeroen,
>
> On Friday, 27 June 2014 05:13:54 UTC+8, Jeroen Gordijn wrote:
>
> Why do you need a view that watches multiple Processors? This can already
>> be achieved. You create a child View for every Processor you w
14 matches
Mail list logo
