title: How to dynamic deploy for standalone Spring batch using Spring Cloud Task
body: <p>We are planning to retire the existing legacy java batch applications and recreate it with the latest available batch framework. 
  Given that we have a large number of batch jobs to be modernised, we are looking for a framework or architecture that would allow us to </p>
  
  <ol>
  <li>Develop a batch solution that would allow us to dynamically deploy a new batch as and when they are created, without disturbing the existing deployed applications. - Does Spring cloud Task provide any of this feature. Note: We are looking only to deploy the apps to our local server, and has nothing to do with cloud.</li>
  <li>If Spring Batch/Boot can provide us the feature we typically expect from a batch application, what is the special value add to go for Spring Cloud Task? - I wasn't able to completely understand this from the Spring documentation available online.</li>
  <li>From the documentation of the Spring Cloud Task, I was able to understand that it allows an application to have many tasks within it. What should I do if each of the tasks have their own library dependencies, which might contradict with the dependencies of other Tasks? So in that case, should each of these tasks moved to a new application or this there a work around for that?</li>
  </ol>