Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Spring-boot vs Bottle, the Slant community recommends Spring-boot for most people. In the question“What are the best backend web frameworks?” Spring-boot is ranked 9th while Bottle is ranked 20th. The most important reason people chose Spring-boot is:
Boot is just a thin configuration layer over Spring Framework, as such it inherits all the strengths of Spring.
Specs
Question Ranking
Pros
Pro Inherits all of Spring's strengths
Boot is just a thin configuration layer over Spring Framework, as such it inherits all the strengths of Spring.
Pro Preconfigured starters
Pro Fast prototyping
Spring boot is built for fast prototyping.
Pro Kick down to Spring
Pro Flexible
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 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.
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
Cons
Con Lacking in UI development
While actually very good and with a very complete and rich feature set to develop and maintain code on the server side, it still doesn't provide any rich framework for building good user interfaces.
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.
