Assigned
Status Update
No update yet.
Comments
pu...@google.com
pu...@google.com
Hello,
Thank you for reaching out to us with your request.
We have duly noted your feedback and will thoroughly validate it. While we cannot provide an estimated time of implementation or guarantee the fulfillment of the issue, please be assured that your input is highly valued. Your feedback enables us to enhance our products and services.
We appreciate your continued trust and support in improving our Google Cloud Platform products. In case you want to report a new issue, please do not hesitate to create a new issue on the
Once again, we sincerely appreciate your valuable feedback; Thank you for your understanding and collaboration.
Description
Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.
Problem you have encountered:
Currently, Pub/Sub delivers messages to subscribers immediately upon publication. While this behavior is desirable for many use cases, some scenarios benefit from delayed message consumption. Like Eventual Consistency: In distributed systems, introducing a delay can help ensure eventual consistency by allowing time for related updates to propagate.
What you expected to happen:
Proposing a new feature for Pub/Sub subscriptions: a configurable delay for message consumption. This feature would allow users to introduce a time buffer between when a message is published to a topic and when it becomes available to subscribers. This delay can be used for various purposes, including eventual consistency, retry mechanisms, and scheduled message delivery.
We propose adding a new configuration option to Pub/Sub subscriptions called consumptionDelay. This option would accept a duration value (e.g., "5s", "1m", "1h") that specifies the delay before a message is delivered to subscribers.
Steps to reproduce:
Other information (workarounds you have tried, documentation consulted, etc):