
I like the efficiency of Batch to handle job executions, standardizing the way of writing and executing the scripts by building docker images of the executable scripts and pusing to the artifact registry repositories, which is simple to set up and execute them.
Additionally, the batch automatically manages the infrastructure for us which becomes easy for us users.
It can run long running jobs which can be for adhoc process also very convenient to design them to execute daily ETL jobs.
The customer support of google cloud is good , we had to increase the quota request for batch jobs and they were prompt in responding and resolving the issue. On the integration, it can be integrated with the google services in our case we integrated with google workflow and also using the batch api you can integrate it easily. Review collected by and hosted on G2.com.
The thing i dislike about batch is that while we trigger the batch to run a dockerized script , it takes a few minutes to execute which is in sequence - the job goes to queued then to scheduled and then provisions the instance in which the executables will be running - this takes time which can be frustrating while you are in the development/ testing phase. Also , quota limitations - if say you are using compute engines as the resource type for running batch then the quota limit of the compute engine will effect if you are looking for the scalability , it can be resolved with the help of customer support. Review collected by and hosted on G2.com.
At G2, we prefer fresh reviews and we like to follow up with reviewers. They may not have updated their review text, but have updated their review.
The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user.
Validated through LinkedIn
This reviewer was offered a nominal gift card as thank you for completing this review.
Invitation from G2. This reviewer was offered a nominal gift card as thank you for completing this review.

