I have a simple node.js express server that accepts simgle api and responds after 10 seconds.
If 2 apis requests arrives at nearly same time, server accepts the second api until the first api responds after 10 seconds.
I want to accept 2 requests at once and handle them simultaneously.

I have a simple node.js express server that accepts simgle api and responds after 10 seconds.
If 2 apis requests arrives at nearly same time, server accepts the second api until the first api responds after 10 seconds.
I want to accept 2 requests at once and handle them simultaneously.

I have a simple node.js express server that accepts simgle api and responds after 10 seconds.
If 2 apis requests arrives at nearly same time, server accepts the second api until the first api responds after 10 seconds.
I want to accept 2 requests at once and handle them simultaneously.

Hello and good morning from Nigeria… I have the following CORS error in Firefox: Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://localhost:3001/socket.io/?EIO=4&transport=polling&t=PGwfo3y. (Reason: CORS request did not succeed). Status code: (null).

Hello and good morning from Nigeria… I have the following CORS error in Firefox: Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://localhost:3001/socket.io/?EIO=4&transport=polling&t=PGwfo3y. (Reason: CORS request did not succeed). Status code: (null).

I am registering the following routes – one GET route and one PATCH route.

I have developed a nodejs api using express, mysql and prisma orm. Traffic will be very low. Around 100 requests an hour at peak usage. Most api calls involve a call to the db. Data returned will also be small. Maybe 10 to 20 rows at a time. The database will have around 30 tables, most of which will have very limited number of rows. Again, around 10 to 20 rows. There is however a transaction table that could over time become relatively big, lets say 3000 rows in a year.

I have developed a nodejs api using express, mysql and prisma orm. Traffic will be very low. Around 100 requests an hour at peak usage. Most api calls involve a call to the db. Data returned will also be small. Maybe 10 to 20 rows at a time. The database will have around 30 tables, most of which will have very limited number of rows. Again, around 10 to 20 rows. There is however a transaction table that could over time become relatively big, lets say 3000 rows in a year.

I have developed a nodejs api using express, mysql and prisma orm. Traffic will be very low. Around 100 requests an hour at peak usage. Most api calls involve a call to the db. Data returned will also be small. Maybe 10 to 20 rows at a time. The database will have around 30 tables, most of which will have very limited number of rows. Again, around 10 to 20 rows. There is however a transaction table that could over time become relatively big, lets say 3000 rows in a year.

I have developed a nodejs api using express, mysql and prisma orm. Traffic will be very low. Around 100 requests an hour at peak usage. Most api calls involve a call to the db. Data returned will also be small. Maybe 10 to 20 rows at a time. The database will have around 30 tables, most of which will have very limited number of rows. Again, around 10 to 20 rows. There is however a transaction table that could over time become relatively big, lets say 3000 rows in a year.