backendlore VS nodebestpractices

Sure it's not for everyone. I learnt a lot doing cash strapped startups where there wasn't a devops person. AWS can get expensive, especially when you start using more and more services (lambda,dynamodb,rds,elasticache etc) although it can be easily scaled.

Note, you probably shouldn't do it by hand (setting up your own services). You'd use Ansible/Terraform.

For those that are interested but not quite ready, here's a great article [0].

[0] https://github.com/fpereiro/backendlore.

7. Backendlore

A good example of ASCII diagrams: https://github.com/fpereiro/backendlore

I have found this to be useful: https://github.com/fpereiro/backendlore

It is more about writing backends generally, but in it he uses Redis as a primary database and walks through durability and scalability.

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.