Batch Ready!
June 16, 2022

Batch Ready!

Alfred Brock | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User

Overall Satisfaction with Azure Batch

We use Azure Batch in order to compare our measurements with the measurement of other labs, organizations and farms.
It allows us to carry out analysis on all the separate data sets independently and then combine it all afterwards. We are also working on having it take the next step to visualize the data and then share it automatically.
  • Ease of scripting
  • Scheduling
  • Combination of Data Sets
  • It would be great to see it head right into the visualizations, but, of course, that requires, for us, a separate set of steps anyway
  • Some data preparation is necessary prior to computing and that can be klunky
  • More GUI
  • After setting things up we have reduced time in running all of the processing
  • It is promising in allowing us to concentrate on the data rather than the formatting and presentation that can all be automated after it has been processed
  • We have reduced the number of products we used before adopting Batch
Azure Batch proved superior for ease of use and cost.

We selected Azure Batch because it was an extension for skills we already had in house.
Azure Batch allowed us to work with our already existing tools and we were able to take advantage of various elements of those tools that heretofore we were unable to do.

Do you think Azure Batch delivers good value for the price?


Are you happy with Azure Batch's feature set?


Did Azure Batch live up to sales and marketing promises?


Did implementation of Azure Batch go as expected?


Would you buy Azure Batch again?


Microsoft Teams, AudioCodes Software-Defined Voice Network (SDvN), Yealink Conference Phones
It is well suited for computing against various data sets that may be similar in content but contained in different arrays and combinations.
It is well suited for scheduling the computing time.
It is well suited for working with teams of programmers or analysts at different locations.

It is less appropriate when the data sets have not been normalized beforehand - but this is more of a staging issue rather than anything about the software.