Geek asks and answers

ASP.Net or Node.js in the following situation

Good morning,

I'm going to write a web service, and I'm not sure which structure is best for this situation. I understand that Node and .Net are good.

The client will call the services in the following steps:

Application Download - Log in through the Facebook API.

The user can create an “object”. This object will be stored in the database (SQL for the table. Net / Azure for Node), and also sent to the Facebook application (timeline material). The user can make changes to this at any time.

User can browse Facebook friends (Facebook API again).

Changes to the entity will be redirected to all users who have "joined" the same entity (SignalR.net/Socket.io Node).

This is the skeleton of web services, there may be more calls to Facebook or CRUD. What structure will handle this?

Many thanks.

+3
source share
3 answers

Any well-written code, regardless of structure, can handle this.

If you are a .NET developer, I personally believe that C # type safety is important, so I would not go the way of Azure node.js, as it will also force me to use Azure.

I would personally use the ASP.NET Web API.

+1
source

In addition to the WebAPI mentioned, also consider the excellent ServiceStack for creating a web service.

+2
source

, ( , , ). .NET Web API node.js - express/connect.

, node.js - , ASP.NET .

As a result, I don’t think you can say that “X is better than Y because of Z” in this scenario. This is a matter of personal preference, infrastructure and your technical skills.

+1
source

More articles:


All Articles