Here’s the Deal

Spring MVC vs Bottle

103 34

46 2

When comparing Spring MVC vs Bottle, the Slant community recommends Spring MVC for most people. In the question“What are the best backend web frameworks?” Spring MVC is ranked 11th while Bottle is ranked 20th. The most important reason people chose Spring MVC is:

The official documentation covers virtually everything. The official website also has a series of great tutorials in video and text formats. There are links to Github repositories for Spring sample applications and there are also a lot of third-party tutorials out there for the fact that Spring MVC is so widely used by many experienced developers.

Ranked in these QuestionsQuestion Ranking

Common Questions

What are the best backend web frameworks?

Pros

Pro
Great documentation that covers almost everything

Pro
Spring MVC has a massive community

Being the oldest and most used JVM web framework, means that Spring MVC has a massive community of followers who are very helpful and have provided numerous tutorials and answers on SO.

Spring even holds an annual conference called SpringOne. The Spring forums and SO are great places to ask and get help about anything Spring related. The website blog and newsletter keep developers informed on every news related with the framework.

Pro
Spring apps are highly scalable

Applications are meant to scale as the framework is used in large-scale applications worldwide. Components like EhCache are used to scale memory cache and it also contains components used for parallel processing.
Batch enables processing of large volumes of records and job processing statistics.

Pro
Spring has an extensive ecosystem

It is based and is dependent on the Spring Framework, therefore it benefits from tools like for example Roo and Spring Tool Suite and many more tools included in the Spring Framework. All Maven dependencies are available in a public Maven repository.
There are also 3rd-party solutions for Spring, such as MyEclipse which includes scaffolding capability for Spring MVC.

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

Ad
Cons

Con
Updating and code maintenance can be a grueling task if you are a beginner

Updating your project is manageable if you’re already familiar with the framework and the project itself, but if you’re just diving in it can be a little overwhelming and hard.

Con
Bloated legacy DI API

Spring DI is bloated and rather complex in comparison to CDI.

Con
Complex and not newbie friendly

Spring MVC architecture although simple has a lot of layers and abstractions which can be hard to debug if problems arise. It is also highly dependant on the Spring core.
It's an old and mature framework that has numerous amount of ways to extend and configure it – and this actually makes it fairly complex.

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
Unnecessarily slow, bloated, complex, convoluted, wordy, and verbose

Spring is convoluted and XML-ridden. Deploying things on the JVM has always been a pain in the nipple and nothing has changed much since the 90s. All things Java-related are wordy, verbose, and a waste of developer time.

Con
Slow Prototyping

If you are looking to build a quick prototype fast and easy, Spring isn't going to help much. It's very large and quite hard to grasp if you are just beginning with it.

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.