how to consume a web service in mule flow?

What architecture should I use so as not to accidentally create a DDoS on a web service?

• The system would serve as a middware between the client and the web service. The aim is to throttle the rate of web service requests that we are generating. Requirements: 1) Scalable to handle a large number of incoming requests from the client asynchronously. 2) Scalable for the number of different web services it can connect to. 3) Load balancing across nodes. 4) Throttling the rate of requests made to the web services. Possible solution: Gearman Problem: Requirement 4 is not solved by gearman as we cannot control the rate of requests made by a particular worker for a particular service. Use case: The client gives me a file containing URL's (6-7 million) from which some data is to be downloaded. I have a gearman cluster set up which provides this functionality. However, all workers start sending download request simultaneously to the web service, hence, creating a DDoS.

• Answer:

  Ddos is a very capital intensive operation. So until you are fb or yahoo, you should be pretty safe.