Hi, we would like to know: how to define the event receive order ?
Currently you add the IDistributedEventHandler interface to your receiving class - if it depends on the execution of another handler for the same event, the only solution we found so far is to create a new event so you always have a 1-to-1 relation between event and receiver.
So is there a better way than creating new events for each step ?
2 Answer(s)
-
0
There is no
event receive order. It is very much against the nature of async communication.If you have a process that needs to be done sequentially, you can use HTTP calls awaiting each other.
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post) -
0
well that would mean we have to do http calls from the repository to other services - which breaks the separation between domain and data access provider.
So how do you ensure all services have up to day data ? another approach ( beside events ) would be locking - you have DistributedLocking, but the documentation is very basic, it is possible to lock only for writes ? ( allow reads without locking if no write lock is aquired )
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
