When comparing Beego vs Buffalo, the Slant community recommends Beego for most people. In the question“What are the best web frameworks for Go?” Beego is ranked 4th while Buffalo is ranked 6th. 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
Ranked in these QuestionsQuestion Ranking
Pros
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
Pro Hot reloading
The dev command will watch your .go and .html files and the asset folder by default. It will rebuild and restart your binary for you automatically so you don't have to worry about such things.
Just run the buffalo dev command and go to localhost:3000/ to see all changes live!
Pro CLI project scaffolding
Buffalo aims to make building new web applications in Go as quick and simple as possible. buffalo new coke
That will generate a whole new Buffalo application that is ready to go. It'll even run go get for you to make sure you have all of the necessary dependencies needed to run your application.
Pro Database migration
Easily migrate database.
Pro Full web and api only generator for those not looking for full web templating
Pro Multi step Dockerfile included with scratch base for minimal size
Pro Embeded resources in binary for easy reference
Pro Great community channel when help is needed
Cons
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.