orchid-orm-benchmarks VS nodebestpractices

Here are my tests for an example project. The logic is quite straightforward: create db records, make a request, check the response, and if it was a mutating request check how it affected the database.

And if you like to see a random example project here is mine, but my point is that a random project won't really help because each project has a unique set of frameworks/libs/practices and it changes almost everything.

Or you can clone this examples repo and play with the Blog API code.

I have an example app, and have written documentation based on it, and I'd appreciate it if you could look and give some feedback. Yes, the doc is about ORM, but imagine the ORM is just an implementation detail and instead look at how validations, controllers, repos, and especially tests are done. Source code, and long boring tutorial about it. Really, check the tests here, they are special. It doesn't have "service" because the app is too simple, but I usually have a service layer as a files with exported functions. Error handling is in app.ts.

I keep all routes in a separate file: routes.ts, in case of multiple API versions it could be "routes.v1.ts", "routes.v2.ts" and so on. v1 and v2 can reuse the same controllers.

I wrote some tests for sample app as well, maybe could be interesting for you to check it out: here, criticism is welcome, just as I like to criticize

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.