node-mongo | mongo project archetype demonstrating how to use node | REST library

Connect to your database 1st and after that start your server.

You're trying to query the database without connecting to your database.

https://mongoosejs.com/docs/connections.html#buffering

Mongoose lets you start using your models immediately, without waiting for mongoose to establish a connection to MongoDB.

That's because mongoose buffers model function calls internally. This buffering is convenient, but also a common source of confusion. Mongoose will not throw any errors by default if you use a model without connecting.

your mongodb Client is running on your local machine you must make a cloud base mongodb cluster like Atlas and change your mongo URI with cloud base cluster URI.

After re-thinking it through and reading this solution here https://stackoverflow.com/a/36623117/8293176, I realized that I misunderstood the concept of routing in React.

What I did before was that I tried to apply the static re-routing within the reverse proxy conf file to the Nginx hosting react which was incorrect! It just brought me to another page.

I had to apply it to the Nginx hosting the React build itself. This way, the redirects are client-side.

I applied the Catch-all method proposed in the link referenced above and the links in the Question, and it worked nicely!

I hope this post can provide clarity to future readers.

You can try to define a network in the docker-compose.yml so that the services are in the same network and have access to each other:

First you need to wait a connection to be established to make sure it will be ok, see Error handling:

With mongoose model, you can use pipe functions like skip and limit for pagination.

I figured it out, the problem was that heroku wasn't reading this part in the mongoose.connect:

I don't think there is any option to do in project(), but you can try query builder approach,

You would need to configure mongoose and connect to MongoDB within a worker thread because Worker has isolated env ie its own event loop etc. If you are using a Worker to save data to MongoDB for just learning purposes then it's ok otherwise no use of a Worker here. Workers only useful when you have long-running synchronous tasks to perform for example encrypting a file, resizing an image or complex data processing, sorting large data, etc.

You can refer to this article for example code https://henrikgronvall.com/articles/nodejs-worker-threads/