Build a Resilient, Asynchronous System with Cloud Run and Pub/Sub Reviews

i like this

José Manuel R. · Reviewed over 1 year ago

Iliyan P. · Reviewed over 1 year ago

Nnamudi E. · Reviewed over 1 year ago

Anish K. · Reviewed over 1 year ago

SREENIVASULU B. · Reviewed over 1 year ago

Damien C. · Reviewed over 1 year ago

Hafizullah N. · Reviewed over 1 year ago

Maqsood A. · Reviewed over 1 year ago

Durga P. · Reviewed over 1 year ago

Bibi P. · Reviewed over 1 year ago

Binil R. · Reviewed over 1 year ago

Kazutaka N. · Reviewed over 1 year ago

Yusuke Y. · Reviewed over 1 year ago

Eliud C. · Reviewed over 1 year ago

Siarhei F. · Reviewed over 1 year ago

I'm loving event driven design. FYI, express now has its own built in body-parser, you just have to enable it. I would suggest you use node:#-alpine since those images are smaller and builds faster. You should have us assign REGION and ZONE to variables for use in deploy.sh. Before deployment, you should have us run npm start to verify we didn't mess things up. This would be a good time to introduce "gcloud run services logs read email-service --region=$REGION" and maybe add --log-filter for the 500 error; maybe add a ~/checklogs.sh and have deploy.sh or post-reports.sh run that after sleeping for 5 seconds.

Lucas S. · Reviewed over 1 year ago

Subhajit G. · Reviewed over 1 year ago

數野 雅. · Reviewed over 1 year ago

Demisew M. · Reviewed over 1 year ago

Guillermo A. · Reviewed over 1 year ago

Ryohei A. · Reviewed over 1 year ago

Chandan C. · Reviewed over 1 year ago

Sagar S. · Reviewed over 1 year ago

Ezio H. · Reviewed over 1 year ago

ok

Raj Kamal M. · Reviewed over 1 year ago