We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Would be great to see a video on a performant way of taking one channel of events and then fanning those events from that channel to n channels.
Obviously would be important to cover how to gracefully handle the shutdown of those channels without losing a event that is in flight.
Something like the following
The text was updated successfully, but these errors were encountered:
So each message sent to the center is replicated and sent to each one of the consumers below?
Sorry, something went wrong.
@campoy Yes exactly that.
Edit: I guess in a way it's the reverse of the merge channels example you did.
@aranw he does this in his trace episode when he tries the "worker" approach.
https://youtu.be/ySy3sR1LFCQ?t=1450
No branches or pull requests
Would be great to see a video on a performant way of taking one channel of events and then fanning those events from that channel to n channels.
Obviously would be important to cover how to gracefully handle the shutdown of those channels without losing a event that is in flight.
Something like the following
The text was updated successfully, but these errors were encountered: