Hi Ashley,
most of my response is already in my recent post, what you are describing are
topics that are not coupled to a persistenceId and the ability to consume them
in other actors as a stream of events since a given position in the log. One
thing below resonates with me, and that is that
Hello there,
as Patrik redirected – we’ve talked a lot about this and are aiming to provide
better views.
There already exists integration with Kafka
https://github.com/krasserm/akka-persistence-kafka#journal-topics developed by
Martin Krasser,
it adresses some of the points raised actually.
Hi Patrik,
Thanks for your post.
On 14 Aug 2014, at 10:31 pm, Patrik Nordwall wrote:
I think this might fit in rather well with the tag based PersistentView.
The Event Store journal plugin could interpret the tag as a projection
identifier.
Yes, I think that could easily even work now
On Thu, Aug 14, 2014 at 6:03 PM, Ashley Aitken amait...@gmail.com wrote:
Hi Patrik,
Thanks for your post.
On 14 Aug 2014, at 10:31 pm, Patrik Nordwall wrote:
I think this might fit in rather well with the tag based
PersistentView. The Event Store journal plugin could interpret the tag as
On 14.08.14 18:17, Ashley Aitken wrote:
Hi Konrad,
On Thursday, 14 August 2014 22:39:04 UTC+8, Konrad Malawski wrote:
There already exists integration with Kafka
https://github.com/krasserm/akka-persistence-kafka#journal-topics
I've been thinking about how Akka Persistence could possibly be improved
for CQRS and *persistent* stream or log processing more generally.
Here's my stream (no pun intended) of thought:
Currently, PersistentActor is focussed on persisting state changes for an
Actor (persistenceId) but why
