currency-api VS nodebestpractices

Let’s look at the docker below, this innocent-looking docker file is taken from a Node Js API. It has one major issue we will uncover as we proceed:

Once the above small pull request is merged and deployed you can start work on the enabler cement code. This cement code wires up the above code to a user action like viewing the rates. It will be possible with a route that will invoke the above getByToCurrency method. You can see how we exposed the code as a new route in this small pull request. You can see the main code below:

Repository: goldbergyoni/nodebestpractices

ah, but there is one more reason to return await. have a read.

View on GitHub

Flat structure: check out the structure recommended by node best practices, and check out how Nest.js does the structure. The more layers you add, the more complex navigation with the flat structure becomes. With the component structure, it stays easy to use no matter how many components and layers you have.

I am looking for a resource like https://github.com/goldbergyoni/nodebestpractices. I know Sql but I want to learn best practices. Can you recommend me resources for this?

Also, while learning nodejs + express, have a read on the best practices here.

Assuming you have fundamentals in place this repo of best practices can help line things up and link you to areas where you need improvement. https://github.com/goldbergyoni/nodebestpractices

Please don't call node.js single-threaded as this is not true and is annoying. To take advantage of CPUs, this could help.