Horusiath/AkkaCQRS

Router Vs Coordinator

varghesep opened this issue · 1 comments

In the extension.cs, a router has been used for userindex actor. Is there a reason why the other coordinators like account and user have not been used in a router but as an actor only?

User index is used solely for fast finding user ids given user emails. It should be probably implemented more like separate persistent actor listening on event bus for registered users.

There is no particular reason for using routers here, but I don't think that it should be placed under one of the existing coordinators (mixing responsibilities doesn't seem to be a good idea).