Express callback delaying with setTimeout

Question

Express callback delaying with setTimeout

I'm working on a route that involves setting a data attribute called "active" to true initially, but then switching it to false after an hour. I'm curious if it's considered bad practice or feasible to use a setTimeout function within the express callback function like this:

app.get("/test", (req, res) => {

//Some code

SetTimeout(func, 3600);
});

I'm concerned about scalability - if this route is accessed frequently, will it become too costly? Appreciate any insights on this matter. Thanks!

javascript express web-development-server

Answer 1

Answer №1

When storing values in a database, it is not recommended to create a timer for each entry in the node that resets the value. This is especially true for long-lasting timers. Session-like or related data that needs to persist for longer periods should not be held in the memory of the node process.

If your site receives frequent visitors, there may be multiple timers running concurrently. Restarting the application can either result in losing these timers or require waiting until they finish before accepting any new ones.

Switching to clustered mode is not a viable solution as calling a route twice could lead to the requests being handled by different processes, causing inconsistencies with timeouts set by each process.

A more efficient approach would be to add a timestamp to the database and implement a cleanup timer that manages all entries.

Answer 2

When storing values in a database, it is not recommended to create a timer for each entry in the node that resets the value. This is especially true for long-lasting timers. Session-like or related data that needs to persist for longer periods should not be held in the memory of the node process.

If your site receives frequent visitors, there may be multiple timers running concurrently. Restarting the application can either result in losing these timers or require waiting until they finish before accepting any new ones.

Switching to clustered mode is not a viable solution as calling a route twice could lead to the requests being handled by different processes, causing inconsistencies with timeouts set by each process.

A more efficient approach would be to add a timestamp to the database and implement a cleanup timer that manages all entries.

Answer 3

Answer №2

It appears that setting one timer may be sufficient in this case, assuming the 'hour' begins with the initial request.

let timer = null
let data = true

app.get("/test", (req, res) => {

  //Some code
  if (!timer) {
    timer = setTimeout(() => {data=false}, 3600);
  }
});

Alternatively, for multiple users, it is possible to avoid setting numerous timers by utilizing a hash with timestamps and checking it for each request or using a separate interval timer.

// init
let timers = {}

// in request
if (!timers[user]) {
    timers[user] = new Date().getTime() / 1000 + 3600
}
else if (timers[user] <= new Date().getTime() / 1000)
{
    // update db, etc
}


// or poll for expirations in separate single timer routine
let now = new Date().getTime() / 1000
Object.keys(timers).forEach(user => {
  if (timers[user] <= now) {
    // update db, etc
  }
})

Answer 4

It appears that setting one timer may be sufficient in this case, assuming the 'hour' begins with the initial request.

let timer = null
let data = true

app.get("/test", (req, res) => {

  //Some code
  if (!timer) {
    timer = setTimeout(() => {data=false}, 3600);
  }
});

Alternatively, for multiple users, it is possible to avoid setting numerous timers by utilizing a hash with timestamps and checking it for each request or using a separate interval timer.

// init
let timers = {}

// in request
if (!timers[user]) {
    timers[user] = new Date().getTime() / 1000 + 3600
}
else if (timers[user] <= new Date().getTime() / 1000)
{
    // update db, etc
}


// or poll for expirations in separate single timer routine
let now = new Date().getTime() / 1000
Object.keys(timers).forEach(user => {
  if (timers[user] <= now) {
    // update db, etc
  }
})

Express callback delaying with setTimeout

Answer №1

Answer №2

Similar questions

Utilize npm to construct a Vue application and execute it on a Raspberry Pi device

The function this.$set is failing to update an array in VueJS

I am puzzled as to why my Details Modal keeps appearing whenever I click anywhere, even when I have specifically added it to only show up on the event of today. Additionally, I am encountering

Having trouble retrieving the Firebase data within the Node.js API

I am currently working on creating a system for displaying rating stars for products. The rating value, which ranges from 0 to 5, has already been provided

Issue encountered: Cannot locate module: Error message - Unable to find 'stream' in 'C:devjszip-test ode_modulesjsziplib' folder

The error message shows: "Unable to retrieve property 'opts' from an undefined source in google-auth-library"

How can I programmatically trigger a change event for a dropdown in Vue.js?

Building basic objects in TypeScript

AngularJS: steer clear of relying on the 'angular' global variable

Is there a way in Jquery to retrieve the id of the clicked element and modify its name?

Exploring Three.js on Cordova with WebGL

Guidelines for implementing drag and drop functionality for my specific scenario

Selecting a language by clicking on it

Guide to mocking the 'git-simple' branchLocal function using jest.mock

Transforming a JSON string into an object within a variable amount of nested JSON structures

"Optimize Your Data with PrimeNG's Table Filtering Feature

How can JavaScript be used to remove HTML tags from text while preserving a space between each line?

Having trouble with my ReactJS application where click interactions are functioning properly on the header but not on my content

JavaScript throws a "null is null or not an object" error when attempting to