使用 Cloud Run 和 Pub/Sub 建構高韌性的非同步系統 Reviews

Manoj B. · Reviewed almost 2 years ago

Rasmiranjan S. · Reviewed almost 2 years ago

Rasmiranjan S. · Reviewed almost 2 years ago

rajesh r. · Reviewed almost 2 years ago

Smaranika Nayak G. · Reviewed almost 2 years ago

Jayesh P. · Reviewed almost 2 years ago

i like this

José Manuel R. · Reviewed almost 2 years ago

Iliyan P. · Reviewed almost 2 years ago

Nnamudi E. · Reviewed almost 2 years ago

Anish K. · Reviewed almost 2 years ago

SREENIVASULU B. · Reviewed almost 2 years ago

Damien C. · Reviewed almost 2 years ago

Hafizullah N. · Reviewed almost 2 years ago

Maqsood A. · Reviewed almost 2 years ago

Durga P. · Reviewed almost 2 years ago

Bibi P. · Reviewed almost 2 years ago

Binil R. · Reviewed almost 2 years ago

Kazutaka N. · Reviewed almost 2 years ago

Yusuke Y. · Reviewed almost 2 years ago

Eliud C. · Reviewed almost 2 years ago

Siarhei F. · Reviewed almost 2 years 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 almost 2 years ago

Subhajit G. · Reviewed almost 2 years ago

數野 雅. · Reviewed almost 2 years ago

Demisew M. · Reviewed almost 2 years ago