chakench commented on issue #4086: URL: https://github.com/apache/incubator-dolphinscheduler/issues/4086#issuecomment-730802740
> > > Hi, this doesn't look like a scheduler task, I think what you should think about is whether it is placed in DS? > > > > > > This should be a Scheduler Task and is used in a lot of situations. In the business process, there is an MQ node, and the subsequent nodes are the corresponding HTTP processing nodes. In this way, the business process can be dynamically choreographed in the way of DAG, without the need for hard coding。 > > hi, maybe I didn't understand what you mean. My question is: Since it can pass http, why use mq? There is no benefit in adding a layer of links, but the overall maintenance cost will increase, and the predictability of scheduling will be reduced. As for concurrency, I think this is not what DS needs to consider. DS calls A. If A cannot guarantee his throughput, then A should consider expansion or other methods. MQ is definitely not the best solution. The reason for using MQ is to act as an event trigger and then trigger subsequent HTTP nodes to take MQ messages for business processing, which is quite normal for scheduling ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
