ASP.NET MVC vs Iris
When comparing ASP.NET MVC vs Iris, 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 Iris is ranked 55th. 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.
Ranked in these QuestionsQuestion Ranking
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 No need to find and install external libraries
Iris 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 Efficiency
Efficiency by using a light engine.
Pro Development
Pro API
If you're familiar with expressjs or other modern web frameworks, Iris will make you feel at home.
Pro More than feature complete
Pro More than 250 examples
More than 250 examples for implementing web application.
Pro Low amount of bugs
Most issues are questions, few bug reports and if a bug is found it's quickly patched.
Pro Good for big projects
Iris is a good framework for big projects and the author helps solving problems.
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.
Con Expensive
You need to have the plate to maintain a site.
Con Previously experience with net/http
Previously experience with the Go's standard net/http package is necessary for you to move forward with Iris.
Con Author copies code
Alternative Products
