How to ease concerns about scalability and maintainability in Node/Express.

At work, we are starting to have discussions around a major product to build. We have been primarily an ASP.NET shop for a long time, but with the influx of new devs into the company (myself included), there is a push to change that. Currently, the architectural discussion is "What will we use on the back end?" Currently, the best cases right now are for PHP and ASP, this is mainly because we have a Senior Developer who knows ASP intimately, and another developer who's built out a tool we use a lot using PHP (and that our new tool might interact with his tool more often then not).But my boss, is giving us three days next week to have a hackathon using our desired tools to make a case against PHP or ASP. He's a former MSFT guy, but wants to get away from ASP (especially since he wants his Jr. Devs to have a good career trajectory) and, even though we have a few good reasons for PHP, he really doesn't want to use it.So, my coworker brought up Python with Flask. A project manager asked, "What about MEAN?" I immediately lit up since I've used Node before, but mainly on school projects and the pro bono work I've done. All small scale applications.While almost everyone was open to the idea, our C# dev asked about maintainability. Everyone responded with an uncomfortable shrug... but everyone hadn't used Node in at least 2 years (6 months for myself).So, next week, I have to build an application under the hackathon guidelines (TBD) and do a presentation about MEAN Stack. Really, Node.js in general because Angular is already a part of our main stack and we have all been leaning toward a NoSQL database at this point.With whatever I build and my presentation I have to show "Why Node?" I have to, mainly, convince them of maintainability and scalability. Other concerns that have been raised, but are smaller, are speed and modularity (it might be re-skinned on the front end on occasion).So, as for what my question actually is. I'm not as familiar with Node as I used to be, nor was my old self as familiar with Node as I'd like to be. What are some cases, arguments, and resources you would use to make a case for Node (especially on what could potentially be an enterprise level)?As a side note, I'm really fine with it either going the way of Flask or Node. As long as it's not PHP or ASP.NET, most of us are happy.

Submitted February 05, 2016 at 05:05PM by Formula7