feat: Add reply consumer to taskworker prototypes #79465
Draft
+568
−1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I wanted to see how using kafka to consume task results would behave in comparison grpc results. In this arrangement, consumers would consume from both a 'work' and 'result' topic. workers would receive tasks via grpc 'webhooks', execute the task and publish results over kafka. This allows consumers to not have a grpc interface which I think will make them easier to operate, and give us a centralized place to control ratelimiting and throughput to workers. There are several code-crimes that will need to be resolved before we could take this approach any further. Most important is that Arroyo does not support consuming from multiple topics in the way I have been thinking about this.
github-actions
bot
added
the
Scope: Backend
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I wanted to see how using kafka to consume task results would behave in comparison grpc results. In this arrangement, consumers would consume from both a 'work' and 'result' topic. workers would receive tasks via grpc 'webhooks', execute the task and publish results over kafka.
This allows consumers to not have a grpc interface which I think will make them easier to operate, and give us a centralized place to control ratelimiting and throughput to workers.
There are several code-crimes that will need to be resolved before we could take this approach any further. Most important is that Arroyo does not support consuming from multiple topics in the way I have been thinking about this.