So we are at this point in time where we need to start working on a new web app with typical browser side and server side parts.
Our team is kinda split on the server side tech stack selection, specially the language. We have been handling server side in the past projects in all sorts of languages like php, python, go, java etc.
The primary problem here is, that a lot of application logic, gets duplicated across frontend and back end.
I will put the use case of two very common scenarios for reference, although there are many others too.
- validation
- user permissions
On the surface, the promise of code-reusability and no repetition of the business logic seems very promising. If we go for javascript all in all, our code theoretically will be (should be) very DRY.
I looked into the stackoverflow questions to see if I can find any help there but I was not very surprised to see this question popping up again and again and being closed immediately by the army of moderators before ever getting to a useful answer.
The only question that could get a useful answer is here, but that is also 7 years old, when node.js was in its infancy.
On the surface it all seems very promising, but I would like to know if you have already taken this path recently (specially after ES2015 and onwards), is the grass on the server side javascript side as green as it looks?
This is not a question about your opinion, rather this is a question about your experience with server side JS especially for removing the duplication in validation logic.
Does it work the way it sounds should be working? Are there any hidden pitfalls and bumps that will pop-up only after we are already halfway down that path?
any heads-up you can share are highly appreciated.