关于“使用 Cloud Run 和 Pub/Sub 构建弹性异步系统”的评价

Mahyuddin M. · 已于 over 4 years前审核

Andrei B. · 已于 over 4 years前审核

MAYBER I. · 已于 over 4 years前审核

CARLOS ANDRES P. · 已于 over 4 years前审核

Souptik D. · 已于 over 4 years前审核

Dingzhou W. · 已于 over 4 years前审核

Ganesh R. · 已于 over 4 years前审核

MAYBER I. · 已于 over 4 years前审核

Xin Z. · 已于 over 4 years前审核

Miłosz G. · 已于 over 4 years前审核

Excelente explicación.

ADRIAN S. · 已于 over 4 years前审核

Carl A. · 已于 over 4 years前审核

Jose Manuel G. · 已于 over 4 years前审核

Vladislav R. · 已于 over 4 years前审核

Yecid Andres H. · 已于 over 4 years前审核

JHAN CARLOS B. · 已于 over 4 years前审核

Moritz K. · 已于 over 4 years前审核

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. · 已于 over 4 years前审核

MUZAKKI A. · 已于 over 4 years前审核

Alice C. · 已于 over 4 years前审核

Bud B. · 已于 over 4 years前审核

Fathoni M. · 已于 over 4 years前审核

Godfrey M. · 已于 over 4 years前审核

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. · 已于 over 4 years前审核

Ricardo M. · 已于 over 4 years前审核