awesome-backend VS practica

View on GitHub

6. Awesome Backend Engineer

🔖 Curious to see examples? We have a starter: Visit Practica.js, our application example and boilerplate (beta) to see some practices in action

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.

I found an interesting repo that seems to answer my questions and more. If a future developer stumbles across this thread, check it out here: https://github.com/practicajs/practica

If you don't mind, take a look at following example: https://github.com/practicajs/practica/tree/main/src/code-templates/services/order-service/entry-points/api

Have a look at practica.js