Here’s the Deal

ASP.NET MVC vs N2O

61 26

9 2

When comparing ASP.NET MVC vs N2O, the Slant community recommends ASP.NET MVC for most people. In the question“What are the best backend web frameworks?” ASP.NET MVC is ranked 19th while N2O is ranked 29th. The most important reason people chose ASP.NET MVC is:

The framework has many build-in tools, and many packages have been written targeting the framework.

Specs

No specs yet!

Default ORMKVS

Default Template EngineNITRO

EncodingsJSON, BERT/ETF, XML

HostsCOWBOY, EMQ

Initial Release0.4

PriceFREE

ProtocolsHEART, FTP, NITRO

SecurityHMAC AES/CBC-128

Ranked in these QuestionsQuestion Ranking

Common Questions

What are the best backend web frameworks?

Pros

Pro
Mature

The framework has many build-in tools, and many packages have been written targeting the framework.

Pro
Cross platform

.Net Core can work on any platform.

Pro
Widely used

It's pretty easy to find a job with it and there's plenty of documentation and tutorials around.

Pro
Extensive documentation

There are a lot of resources available to get help.

Pro
Fast

Asp.NET Core on Linux is fast accordingly to TechEmpower benchmarks.

Pro
Asp.NET core provides balance between magic/agility and craftsmanship

You can get ordinary details quickly but with complete freedom to make your craft, knowing everything that is happening underneath the cloths. The highly modular system makes it possible to scale small applications to large ones with ease.

Pro
It has more users than any other backend web framework

Getting your next contract is easy with this on your CV.

Pro
Fast binary data

Pro
Binary encoding and protocols

Here is a list of types of endpoints which are supported by EMQ and accesible to N2O apps: WebSockets, MQTT, MQTT-SN, TCP, UDP, CoAP. Normal use of N2O as a Web Framework or a Web Application Server is through WebSockets, but for IoT and MQTT applications it could be served through UDP or SCTP protocols providing application level message delivery consistency.

Ad
Cons

Con
Core and full ASP.NET are bit confusing sometimes

While not in feature parity (yet) they are still apart and support sometimes funky combinations of features - full ASP.NET has all the bells and whistles but doesn't offer cross platform so you may have to do some research what you really need. That being said, it got a lot better in 2.0.