Criação de um sistema resiliente e assíncrono com o Cloud Run e o Pub/Sub avaliações

Manoj B. · Revisado há almost 2 years

Rasmiranjan S. · Revisado há almost 2 years

Rasmiranjan S. · Revisado há almost 2 years

rajesh r. · Revisado há almost 2 years

Smaranika Nayak G. · Revisado há almost 2 years

Jayesh P. · Revisado há almost 2 years

i like this

José Manuel R. · Revisado há almost 2 years

Iliyan P. · Revisado há almost 2 years

Nnamudi E. · Revisado há almost 2 years

Anish K. · Revisado há almost 2 years

SREENIVASULU B. · Revisado há almost 2 years

Damien C. · Revisado há almost 2 years

Hafizullah N. · Revisado há almost 2 years

Maqsood A. · Revisado há almost 2 years

Durga P. · Revisado há almost 2 years

Bibi P. · Revisado há almost 2 years

Binil R. · Revisado há almost 2 years

Kazutaka N. · Revisado há almost 2 years

Yusuke Y. · Revisado há almost 2 years

Eliud C. · Revisado há almost 2 years

Siarhei F. · Revisado há almost 2 years

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. · Revisado há almost 2 years

Subhajit G. · Revisado há almost 2 years

數野 雅. · Revisado há almost 2 years

Demisew M. · Revisado há almost 2 years