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

Nanda K. · Reviewed מעל 4 שנים ago

Mahyuddin M. · Reviewed מעל 4 שנים ago

Andrei B. · Reviewed מעל 4 שנים ago

MAYBER I. · Reviewed מעל 4 שנים ago

CARLOS ANDRES P. · Reviewed מעל 4 שנים ago

Souptik D. · Reviewed מעל 4 שנים ago

Dingzhou W. · Reviewed מעל 4 שנים ago

Ganesh R. · Reviewed מעל 4 שנים ago

MAYBER I. · Reviewed מעל 4 שנים ago

Xin Z. · Reviewed מעל 4 שנים ago

Miłosz G. · Reviewed מעל 4 שנים ago

Excelente explicación.

ADRIAN S. · Reviewed מעל 4 שנים ago

Carl A. · Reviewed מעל 4 שנים ago

Jose Manuel G. · Reviewed מעל 4 שנים ago

Vladislav R. · Reviewed מעל 4 שנים ago

Yecid Andres H. · Reviewed מעל 4 שנים ago

JHAN CARLOS B. · Reviewed מעל 4 שנים ago

Moritz K. · Reviewed מעל 4 שנים ago

Instructions have errors. They are simple so I was able to correct them, but still, this is not a challenge lab so instructions should be perfect.

Ricardo M. · Reviewed מעל 4 שנים ago

MUZAKKI A. · Reviewed מעל 4 שנים ago

Alice C. · Reviewed מעל 4 שנים ago

Bud B. · Reviewed מעל 4 שנים ago

Fathoni M. · Reviewed מעל 4 שנים ago

Godfrey M. · Reviewed מעל 4 שנים ago

Would be good to talk about these 2 points with respect to Pub/Sub retries: 1. Cloud Pub/Sub does not have a limit to the number of times it will retry delivery of a message to a subscriber. If your subscriber never acknowledges the message within the ack deadline, it will be redelivered until the message expires 7 days later. 2. The dead letter queue feature for Cloud Pub/Sub is something else to consider. This feature allows one to set the maximum number of times delivery of a message should be attempted and then to specify a topic to which to publish messages that were delivered more than that number of times. When enabled, the feature also exposes the number of delivery attempts as a field. For example, it is exposed at the deliveryAttempt property on the message passed into the subscriber callback in Node.js.

David L. · Reviewed מעל 4 שנים ago