You may also be eligible for lower rates. Contact our sales team and a Google Cloud expert will help you find the best solution. → goo.gle/39x5gFz Get $300 in free credits and try Google Clouds' messaging and ingestion service for event-driven systems and streaming analytics for free. → goo.gle/3nXLgV3
Hey ! I must be missing smt, why do you use Event Arc for the cases shown : Why not using native --trigger-event google.storage.object.finalize of google cloud functions ?
Why filter function is put inside Cloud Run while others are simple cloud functions? Couldn't all of them be implemented as serverless functions instead?
Appreciate the demo and great insight !. Because the workflow functions are executed in a sync process this will affect response time if there is a lag in one of the cloud functions (i.e lets say the resize takes longer than expected).This would result in a backlog of images waiting to be processed by the subsequent functions as the workflow would not progress because of the lag. Wouldn't the execution of this workflow to a async architecture be better here replacing cloud run workflow with cloud functions (2nd generation) + eventArc only ? cloud storage event arc trigger can be generated after the image is placed in gcs to a cloud function which can add watermark and create a new file in a gcs bucket and following same pattern rest of the processing can be made in a ASYNC fashion removing the need of creating a workflow + cloud run making it a complete event driven serverless architecture ?.
Hi, Can a GKE cluster creation trigger eventarc service ? I am able to see creation of compute engine triggers eventarc not the GKE. is there any service to be enables or is this feature currently disabled for GKE ?
You may also be eligible for lower rates. Contact our sales team and a Google Cloud expert will help you find the best solution. → goo.gle/39x5gFz
Get $300 in free credits and try Google Clouds' messaging and ingestion service for event-driven systems and streaming analytics for free. → goo.gle/3nXLgV3
Ay disculpen perola verdad voi adormir x keya veovoroso
Hey ! I must be missing smt, why do you use Event Arc for the cases shown : Why not using native --trigger-event google.storage.object.finalize of google cloud functions ?
Why filter function is put inside Cloud Run while others are simple cloud functions? Couldn't all of them be implemented as serverless functions instead?
It would be nice to know why they choose cloud functions vs run for each case
This might have changed, but at the time of this video's creation, Eventarc's event sink only supported Cloud Run.
Appreciate the demo and great insight !. Because the workflow functions are executed in a sync process this will affect response time if there is a lag in one of the cloud functions (i.e lets say the resize takes longer than expected).This would result in a backlog of images waiting to be processed by the subsequent functions as the workflow would not progress because of the lag. Wouldn't the execution of this workflow to a async architecture be better here replacing cloud run workflow with cloud functions (2nd generation) + eventArc only ? cloud storage event arc trigger can be generated after the image is placed in gcs to a cloud function which can add watermark and create a new file in a gcs bucket and following same pattern rest of the processing can be made in a ASYNC fashion removing the need of creating a workflow + cloud run making it a complete event driven serverless architecture ?.
Hi, Can a GKE cluster creation trigger eventarc service ? I am able to see creation of compute engine triggers eventarc not the GKE. is there any service to be enables or is this feature currently disabled for GKE ?