X
X
x5122016-01-10 12:55:12
Angular
x512, 2016-01-10 12:55:12

Node.js(+Express) or ASP.NET 5(.NET Core) to create WebAPI to PostgreSQL with authorization?

What is the best choice for creating WebAPI in terms of convenience and speed of development, reliability, availability of libraries (PostgreSQL, authorization), price and complexity of hosting. WebAPI will be used in conjunction with an Angular 2 application.
At the moment I have the following thoughts:
For Node.js: more common, hosting cheaper, should be installed anyway (Angular Serverside). ASP.NET is an extra dependency, stability is not yet known, how it works under Linux. Passport.js seems to be suitable for authorization. A single language between the client and the server, allowing you to write common logic once.
Behind ASP.NET WebAPI: C# language, static typing, great ORM (also with static typing) is much more convenient for development and subsequent support. In Node.js, you can screw TypeScript, but firstly, it is far from C # in terms of capabilities, and secondly, it also needs to be screwed, and this time and its own problems. For authorization, I found openiddict, but it is still in the Alpha version. To write common logic in one language, you can use Bridge.NET
In general, ASP.NET looks like a monolithic solution, but raw. Node.js looks like a set of proven solutions, each of which must first be looked for, and then integrated. Therefore, I am in the middle between them and do not know what to choose. I would like to hear the arguments I missed and criticism of my thoughts

Answer the question

In order to leave comments, you need to log in

1 answer(s)
B
beduin01, 2016-01-10
@beduin01

If I were you, I would take vibed.org and not bother. Recently just wrote authorization on it.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question