When comparing Bottle vs Beego, the Slant community recommends Bottle for most people. In the question“What are the best backend web frameworks?” Bottle is ranked 17th while Beego is ranked 19th. The most important reason people chose Bottle is:
Bottle works around the one-file approach, everything is done in a `bottle.py` file. This means that it's extremely easy to share and upload your application since it practically is just one python file.
Ranked in these QuestionsQuestion Ranking
Pro Single-file distribution
Bottle works around the one-file approach, everything is done in a
bottle.py file. This means that it's extremely easy to share and upload your application since it practically is just one python file.
Being a small one file distribution it includes almost every vital thing you need to support little websites (routing, templating). Everything else can be implemented using plugins.
Pro No need to install
It is so little there's no need to install, it is included in the standard libs python.
Pro Async, *let friendly
Using it with gevent is a breeze. It's a WSGI app so it's easy to make it work with anything.
Pro Truly magnificent
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 Auto testing
Con Small community. Difficult to find online docs and examples
Con Very hard to develop projects that are not smaller than 1000 lines
While Bottle is a great framework for building small applications (generally less than 1000 lines of code), it starts getting very hard to manage your application if you want to go even a bit larger than that.
The fact that it follows a single-file distribution model and that it's missing something like Flask's blueprints only make this problem worse.
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.