-
backend-best-practices
Best practices, tools and guidelines for backend development. Code examples in TypeScript + NodeJS
-
practica
Node.js solution starter boilerplate that is production-ready, packed with โ best practices and built with simplicity in mind
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
Backend best practices - this is actually what you were looking for in this post and I'm suggesting against it - this is a tutorial on the "right" way with OOP flavor. Even though I do it differently, these reports are looking very well-done and interesting.
Good practices to me means being disciplined with good coding standards regardless of framework you'd work in. I've seen terrible codes in Spring, .NET just as I would see in any node.js project. Does framework like Spring enforce structure that your team could possibly have some guidelines to follow? Sure it does. Does spring make your team stick with best practices? I don't know about that. For example, using interface for places where you need (or at least java bean managed modules) is key to achieving good modularization in Spring, it's the same in Javascript. However, due to the nature of its language features, fewer places require using actual interface in Javascript. The underlying principles are not much different, it's just different ways of achieving the goal. That said, shooting yourself in the foot in express will give you much deeper learning experience than using something like nest to make you feel comfortable. At one point, I am sure you'd get hang of good and bad of Javascript. Meanwhile, you could use something like https://practica.dev/ as a reference to explore some of good/bad practices and build upon it.
If you are sound with TypeScript, give Nuxt a try. Or Next.js if you prefer React. Coming from SpringBoot, express will feel more like a library than framework. Nuxt or Next can be considered as frameworks, with their own ecosystem.
If you are sound with TypeScript, give Nuxt a try. Or Next.js if you prefer React. Coming from SpringBoot, express will feel more like a library than framework. Nuxt or Next can be considered as frameworks, with their own ecosystem.