It is not possible to directly configure a pull subscription and a push subscription on the same Google Cloud Pub/Sub topic to operate at different times of the day. This limitation arises because pull and push subscriptions operate independently, and Pub/Sub does not offer built-in functionality to schedule or switch between them based on time. Additionally, push subscriptions require a continuously available HTTP/HTTPS endpoint, making it impractical to dynamically enable or disable the endpoint without introducing reliability challenges.
However, several alternative solutions can achieve this desired behavior:
1. Two Topics with Time-Based Routing
-
Create separate topics for daytime and nighttime processing.
-
Use a pull subscription for the daytime topic and a push subscription for the nighttime topic.
-
Schedule a Cloud Function or Cloud Run service to transfer messages between topics at specified times by pulling unprocessed messages from one topic and republishing them to the other.
2. Single Topic with Filtering
-
Use a single topic and assign a message attribute (e.g., processing_time) to indicate the intended processing period ("day" or "night").
-
Create:
-
This approach enables efficient message routing without requiring message republishing.
3. Single Pull Subscription with Custom Logic
This option keeps the Pub/Sub configuration simple but shifts complexity to the subscriber application.
Each approach has trade-offs in terms of complexity, cost, and operational overhead. A single pull subscription with custom logic is sufficient for simpler use cases, while message filtering or time-based routing is better suited for high-volume or complex scenarios. The best choice depends on your application's specific requirements and constraints.
LinkedIn
Twitter
