[smt88]

We need to know what you're trying to build to give you a good answer.

Like CmonDev, I'm wondering why you chose this stack. If time is an issue, I'd suggest using a stack you've already mastered, even if it isn't fashionable. As long as it's not something weird, you'll be able to find other people who can work on it with you (and Java isn't weird).

Node is commonly used in hybrid stacks where the backend is initially written in something like Python, and then the REST API is written in Node to speed up requests. That takes advantage of Python's strengths and Node's strengths.

Also, the question of "how strong/versatile/useful is this foundation" is a really hard one to answer without real-world trials, and those take lots of time. I'd suggest finding someone who has written a framework using the stack of your choice and piggyback on their work. No sense reinventing the wheel.

[cihanduruer]

First of all, thanks for your time.

I would like to build a single page application for one of my customer. Application is not very complex (nothing like a financial or manufacturing applications). It will be public application and possible traffic/load is completely unknown.

I choose that stack because of fashion. I would like to learn another way to develop. I am quite happy with my existing stack. If i use my stack, project can be also scale-able and asynchronous enough to create modern app.

My plan is also continue with the hybrid stack, so back-end is going to be a REST Api with ASP.Net Web Api secured with OWIN/Katana. I am planning to use new stack only for presentation layer so far.

I slightly disagree your find an existing framework and continue approach. Because in my opinion if i code everything i will learn more(i know with pain). Choosing framework/package will also take tremendous time for beginner of the stack.

Do you think learning a new stack because of a fashion is valid reason ?

[smt88]

> Do you think learning a new stack because of a fashion is valid reason ?

Yes!

> so back-end is going to be a REST Api with ASP.Net Web Api secured with OWIN/Katana

REST APIs are what Node is best at! You should definitely at least try to write your API in Node.

> I slightly disagree your find an existing framework and continue approach. Because in my opinion if i code everything i will learn more

You will learn more if you code everything, but you're also not learning from the wisdom of the community. Node is used in a very different way from ASP.NET, Python, PHP, etc. You should learn "the Node way". It's always better to learn how each language does things rather than trying to recreate another environment that you're already used to.

Since this is just for the presentation layer, your Node code would be absolutely tiny -- you're not going to learn very much anyway.

I'd suggest using Express. Most Node servers, especially small ones, are based on Express anyway.