-
Notifications
You must be signed in to change notification settings - Fork 86
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
Consumer/processor component #42
Comments
Sounds good, I'll look into it. |
Hi, I'm reading more into this now and can't kinda understand what would make this "processor" component so unique. Right now, you can connect API component as a consumer, which can then send requests to another MQ, I don't see the differece. |
For example how could I build a 3 way connection as processor that consumes a queue as input, requests to other services to enrich and then pushes the result into another queue |
Current set of components are good to design simple web-based apps, but in practice there are more cases.
For example, almost immediately I missed “consumer” or “processor” - worker which consumes MQ messages and transforms them. In general they can do multiple requests, not just transformations, for example it can consume “crawling requests” which contains domain names, perform the crawling of the website (HTTP requests) and push results into another MQ queue.
The text was updated successfully, but these errors were encountered: