-
Notifications
You must be signed in to change notification settings - Fork 31
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
Workers communication strategy #66
Comments
@TCMiranda in my opinion the right solution is the first. Sometimes you may want to reuse code between multiple workers.
|
@prdn thanks for your answer! So, if workers are connected to the "handlers broker" as clients, you would agree to allow them to "communicate" by messages without a separate layer like the second case? The second solution you mentioned would be that case when a worker posts another message as a client to finish its request, right? |
Hello guys,
I am using Pigato in some projects for now, but sometimes I still get confusing about allowing workers to communicate or even to use each others services.
In some scenarios, I prefer to not allow sub levels of workers, but in other scenarios, this gives me much duplicate code, which I solve creating shared modules.
To illustrate a little better:
So, what are your thoughts about it?
Does anyone knows some good reference on this subject?
The text was updated successfully, but these errors were encountered: