CODEWITHSUNDEEP
node.jsfirebasegoogle-cloud-functions
Renz M
Renz M

Reputation: 87

API that will continuously return data

Beginner here, I'm using Firebase real time database and I need my API to constantly return that value when something has been added see my code below. 

apiCalls.get('/api/getallusers',function(req,res){
  userFunc.getAllUsers(function(err,result){
    if (err) return res.status(500).send('internal server error!');
    res.status(200).write(JSON.stringify(result));
    res.end();
    return res;
  })
})

this will return the error

Error [ERR_STREAM_WRITE_AFTER_END]: write after end

but if i remove res.end it will show 1 record and constantly load until the page times out..

is what I'm doing possible or are there different ways to do it.

also I'm using firebase cloud functions for this api.

UPDATE:

Uploaded the API but it does not return anything...

here is the link https://us-central1-testproject-e6819.cloudfunctions.net/api1/api/getUser

tried axios and Event Source

Firebase functions logs the values but it does not return it..

Upvotes: 0

Views: 731

Answers (2)

Frank van Puffelen
Frank van Puffelen

Reputation: 599776

Operations in Cloud Functions must be relatively short-lived and end deterministically. There is no way to keep a connection open from Cloud Functions to the client.

Typically consider what triggers the need to send new data. For example, if it is triggered by the fact that a new user is registered, you can use trigger your Cloud Functions from Firebase Authentication. Then the function could for example write to the Realtime Database (or Cloud Firestore), and your client/app listens to the database for realtime updates. That way you're using all the pieces of Firebase in the way they're designed: Cloud Functions for short-lived updates triggered from events in the system, and the Realtime Database or Cloud Firestore for sending realtime updates.

If that doesn't work for your use-case, you'll need a runtime environment that allows you to keep processes alive. Something like App Engine flex, Kubernetes, or many other options come to mind for that.

Upvotes: 1

Brad
Brad

Reputation: 163488

If you're viewing the API response like a web page, your browser is buffering the data it's received until there's enough of it to form a more full page. Your browser is expecting content that ends, not some endless stream of data.

You should remove .end() if you expect to be able to continue to write to the output stream.

Also, I recommend using the Server-Sent Events (SSE) protocol for this. https://developer.mozilla.org/en-US/docs/Web/API/Server-sent_events It provides a nice standards-based abstraction that makes it very easy to handle event streams client-side.

const eventSource = new EventSource('https://api.example.com/someApi');
eventSource.addEventListener('userupdate', (e) => {
  console.log(e.data);
});

Server-side, there are a couple Express-based middlewares to make this even easier than it already is.

Upvotes: 2

Related Questions