When comparing N2O vs Revel, the Slant community recommends N2O for most people. In the question“What are the best backend web frameworks?” N2O is ranked 29th while Revel is ranked 38th.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
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.
Pro Comes bundled with a code reload tool
Revel comes bundled with a code reload tool which rebuilds the project on every file change. This code reload tool is also used to run, build and deploy the Revel application that you are building.
Pro Good examples easy to understand with simple emulated MVC behavior
Pro No need to find and install external libraries
Revel is a "batteries included" web framework, which means that a lot of features already come out of the box. This way you don't have to spend time and find third-party libraries to integrate to the framework for most of the tasks you need to complete.
Pro Easy to learn for fast development
Cons
Con Unfriendly developer community
Developers are often rude and unfriendly to users.
Con Bad documentation
It has bad documentation, which leaves out crucial steps, making it hard to learn.
Con Non-idiomatic code
Con Outdated
The world has moved past its MVC obsession. It's not the way the web works anymore. The good thing about go is that it's trivial to write a server applications (literally takes minutes). relying on a bloated, archaic framework is missing the point
Con Dead
Thankfully, this abomination is no longer being developed
Con No official support for mongo
Revel does not come with any support for MongoDB, you can integrate third-party libraries but they have been reported to crash under heavy load.