Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Goji vs Beego, the Slant community recommends Beego for most people. In the question“What are the best web frameworks for Go?” Beego is ranked 4th while Goji is ranked 10th. The most important reason people chose Beego is:
Beego 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.
Specs
Question Ranking
Pros
Pro Great performance
Goji is an abstraction layer over the standard Go library (which has support for HTTP) and added Einhorn support. There's probably very little you can do with Goji that you can't do with the standard library and a bit of elbow grease.
This makes Goji an extremely lightweight and fast framework.
Pro Socket manager integration
Goji integrates with Einhorn, which is a language agnostic socket manager. Making it possible to have websocket support in Goji.
Pro No need to find and install external libraries
Beego 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 Built-in tool which watches for changes
Beego has a built-in tool which watches the code for changes. This tool (called bee tool) can be configured to run any task once the code changes. It can run tests or reload and rebuild the whole project.
Pro Built in ORM
Beego's eloquent ORM is a simple and fast Object-Relational Mapping which helps with organizing the application's database. Beego examples and documentation all use the beego ORM. No need to learn to use and integrate another ORMs API.
Pro Captcha
Pro Auto testing
Cons
Con Doesn't add a lot of functionality on top of the standard library
Most of the tasks that Goji is used for can be completed with standard library support without adding the overhead of an additional external library and without having the risk of Goji development being abandoned one day.
Con Very opinionated
Con Very opinionated
Con Non-idiomatic code
Con Builds may fail silently
Sometimes even though a build has failed, the pages will still render. Apparently it caches a previous build when the current one has a problem. This can be a frustrating though because it leaves you wondering why the page you are working on stopped working out of the blue.
