👀 Views: 866 💬 Answers: 1 📅 Created: 2025-07-23

gcp pubsub cloud-functions node.js async JavaScript

I'm building a feature where I'm migrating some code and I'm currently facing a challenge with Google Cloud Pub/Sub where messages aren't being processed in the order I expect when using Cloud Functions with Node.js..... I have set my subscription to be ordered, but it seems that messages are being processed out of order. Here's how I'm publishing the messages: ```javascript const {PubSub} = require('@google-cloud/pubsub'); const pubsub = new PubSub(); async function publishMessages(messages) { const topic = pubsub.topic('my-topic'); const messagePromises = messages.map(async (message) => { const dataBuffer = Buffer.from(message); await topic.publish(dataBuffer); }); await Promise.all(messagePromises); } ``` I'm publishing a sequence of messages like this: ```javascript const messages = ['message1', 'message2', 'message3']; publishMessages(messages); ``` On the subscriber side, I have a Cloud Function set up like this: ```javascript exports.processMessage = async (message, context) => { const data = Buffer.from(message.data, 'base64').toString(); console.log(`Processing: ${data}`); }; ``` Even though I enabled ordering on the subscription, I noticed that the logs show messages being processed out of order, for instance: - Processing: message2 - Processing: message1 - Processing: message3 I've tried adding a delay between messages in the publisher to see if that affects the order, but it hasn’t helped. I also verified that I'm using the correct subscription with ordering enabled. Is there something I'm missing in the configuration, or is there a known issue with ordered delivery in this setup? Any insights would be greatly appreciated! I'm working with Javascript in a Docker container on Ubuntu 20.04. Any ideas what could be causing this? The project is a service built with Javascript.