What is the generally accepted mechanism for controlling a batch service? RRS feed

  • Question

  • Using a batch solution seems to me to need some form of controller to schedule work packages by adding jobs / tasks to batch pools in response to some form of data arriving.

    I thought to use a function App triggered on a timer, however the function does not accept the Microsoft.Azure.Batch namespace in a C# function.  Is there a way to import the batch client APIs that I am missing?

    Alternatively does anyone have thoughts on best practice for controlling batch service tasks?  One obvious way is through use of a client machine with the full .NET environment that could query data and spawn tasks in the cloud but the server-less 'App' function method would be a lot cleaner with less overhead, if it is possible.

    Monday, July 17, 2017 11:10 AM


All replies