Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing Queryable Part #11

Open
beachwalker opened this issue Apr 14, 2017 · 4 comments
Open

Missing Queryable Part #11

beachwalker opened this issue Apr 14, 2017 · 4 comments

Comments

@beachwalker
Copy link

beachwalker commented Apr 14, 2017

Hi,

I don't see the projection (building the read model) part of CQRS in the example. Do I missed some lines or is this not included?

I think this should propagate the event to some kind of EventBus in the AggregateRoot here
https://github.com/Horusiath/AkkaCQRS/blob/master/CSharp/Akkme.Shared/Infrastructure/Domain/AggregateRoot.cs#L37

@beachwalker beachwalker changed the title Missing queryable part Missing Queryable Part Apr 14, 2017
@Horusiath
Copy link
Owner

@beachwalker this example is far from complete and probably outdated at this moment. Unfortunately I didn't have enough time to finish it. I'll try to do that in the future.

@beachwalker
Copy link
Author

Thx for the reply. Do you know other resources to get and idea how to implement that part? I could create specific actors but so they are tightly coupled.
I have two things in my mind related to that topic: http://getakka.net/docs/persistence/persistence-query for the "event handlers" of the readmodel projection
and http://getakka.net/docs/clustering/distributed-publish-subscribe for the event bus.

@Horusiath
Copy link
Owner

Horusiath commented Apr 14, 2017

Persistence query would be a way to go here. I'm not even sure if you will need distributed pub/sub here, as you'd need to manually acknowledge incoming events (so you don't accidentally loose single event over the network). You could just spawn live query from read journal on each machine, that needs that data - while this introduces a little more burden on your database (i.e. SQL journals periodically send a query to pull new events from db), I think it's easier to sync that way.

@lessismore1
Copy link

lessismore1 commented Mar 6, 2018

I would appreciate a Query Side implementation as well - looking for a template to use.
Akka Streams implementation using Persistence Query as source seems intuitively correct.

Have found one "framework" - https://github.com/evendotnet/Even - so far, but he is not using Akka Persistence or Persistence Query...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants