Advice on Nestjs for a moderately large app. What's good and bad about Nestjs?

Background:I'm building an e-commerce api and was thinking of using Nest.js. I've been doing some prototyping in Nestjs and so far like it.This e-commerce api will have a react frontend and a react admin panel. This api is going to be used long-term and we won't be able to afford a rewrite in another framework/language if things go south. Since this is going to be something we're going to work on for next couple of years, I am looking for some advice here:What do you think about nestjs development over long term? What if it somehow stop getting developed (we all know how fast JS ecosystem moves).How complex is the internals? For eg; in express if I ever stumble upon something complex, I can look at its source code and understand what's going on. I did check out nestjs source but from a quick glance it seemed overly complicated and over engineered.This is more of a subjective question. I've been more of a functional programming guy. I prefer react over angular. I feel a little dirty writing all these classes and using so much OOP that it makes JS look like Java. Has anyone been in the same boat, did your opinions change?How's the scalability? We're hoping to use this e-commerce api in production where we could be getting several million requests per month.Asking people who are more experienced with similar frameworks, does the nestjs architecture seem optimal? What should I avoid using (interceptors? pipes? etc) for the time being?This is like our 3rd rewrite for this api, we want to get it right this time and avoid any kind of code smell. Most important things for us are long term maintainability, easy testing and faster turnaround time for features. I'd love to know opinion of people who have been using nest for a while now, and also from people who decided to not use it.

Submitted July 15, 2019 at 08:34PM by crazyfreak316