Комментарии:
I'm sure this marketing name won't ever be confusing. Couldn't you have called it BigBatch, BatchRun, or BatchFlow.
ОтветитьHi. Any comparison between Dataproc and Batch?
ОтветитьOptions I have on GCP that I find difficult to choose when it comes to pick one that is more cost effective than the other to run a batch (scheduled) job:
a. Cloud Run JOBs
b. GKE CronJob
c. Google BATCH
Any thought on this is appreciated.
Is batch serverless?
ОтветитьGood offering as a managed job scheduler. Wondering about the Principal, whether there is any service account that will run the Job or its the user itself. Can it be a substitute for Composer in certain scenarios?
ОтветитьAwesome 😀
Ответитьhow is Batch different from Airflow [Cloud Composer]?
ОтветитьI love the idea that i can run bash scripts in the cloud without a container as a wrapper! This is what i'm search for a long time.
What was missing in the video was the way the infrastructure knows: How many jobs do I need to run?
The JSON File seems not that flexible to define that dynamically, isn't it?
I also wonder about the pricing. When it comes to solutions which are promoted as "easy to use!" i often get the feeling, i don't want to see the price tag at the end.
OMG - BATCH. 😳😡🤬🤯🧐🤩🙂
ОтветитьOh look you are only 5 years away from aws
ОтветитьAren't there any free services like this for students, so we can be able to practice on it
ОтветитьWould have been nice to quickly go over parts of JSON file that defines the batch job.
ОтветитьNice!
ОтветитьThose services cost a worth
Ответить