-
Notifications
You must be signed in to change notification settings - Fork 34
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
Comments
@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. |
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. |
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. |
I would appreciate a Query Side implementation as well - looking for a template to use. Have found one "framework" - https://github.com/evendotnet/Even - so far, but he is not using Akka Persistence or Persistence Query... |
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
The text was updated successfully, but these errors were encountered: