When comparing Gin-gonic vs Iris, the Slant community recommends Gin-gonic for most people. In the question“What are the best web frameworks for Go?” Gin-gonic is ranked 1st while Iris is ranked 13th. The most important reason people chose Gin-gonic is:
The documentation for Gin is broad and comprehensive. Most tasks that you will need to do relating to the router can be found easily in the docs.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Extensive documentation
The documentation for Gin is broad and comprehensive. Most tasks that you will need to do relating to the router can be found easily in the docs.
Pro Good for building REST APIs
Gin is a pretty minimalistic framework. Only the most essential features and libraries are included, making Gin a great framework for developing high-performance REST APIs.
Pro Well-tested and numerous middlewares
The Gin community has created numerous well-tested middlewares that make developing for Gin a charm. Features include gzip, an authorization middleware, and sentry.
Pro High performance
Gin runs 40x faster than Martini, and runs comparatively well compared to other Golang frameworks.
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 Might not be suitable for large backend applications
Gin-gonic is great for building a REST API for the backend if you want to develop an SPA using a frontend framework. But for anything that requires more features on the server side, it would be better to use a more "batteries included" framework.
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.