The New Spring Boot Initializr: the Good and the Not-So-Good!

DZone 's Guide to

The New Spring Boot Initializr: the Good and the Not-So-Good!

Check out the good and the not-so-good features of the newest Spring Boot Initializr.

· Java Zone ·
Free Resource

There has been a change to the Spring Boot Initializr. If you haven't used Spring Boot Initializr before, it is a web interface used to quickly create new Spring Boot projects.

In case you don't know, Spring Boot is one of the most popular Java-based frameworks for building enterprise applications and microservices. You can check out this intro to Spring Boot to get more details.

In this post, we will be looking at the new user interface to initialize Spring Boot applications that has replaced the old one.

Accessing the Spring Boot Initializr

You can still access the Spring Boot Initializr at the same location as before, that is https://start.spring.io

However, now you will be greeted with the following user interface:

For reference, below was the old look. We discussed this in greater detail in this post: Spring Boot - A Work of Art.

The Good Things

At a first glance, from an aesthetic point of view, the new intitializer does appear more intuitive in the new user interface.

On top of the page, we still have the option to choose between Maven and Gradle. The options are provided in the form of tabs instead of a dropdown.

Then, we also have the option to select our programming language. As usual, you can choose between options such as Java, Kotlin, and Groovy. Here, as well, preference has been given to the tabbed approach as compared to the dropdown.

In my view, this enhanced user interface is really good. Going for a tab-based approach enhances the look and feel of the site. It also makes it easier to switch options on the fly if you want.

The Neutral Things

When looking at the features where I don't have any particular view compared to the old one are the other project details.

You can still customize the various details such as Group Id, Artifact Name, Description of the Project, Type of Packaging, and Java version.

By default, you only see the Group Id and the Artifact Id. But on clicking the More Options button, you can see the other fields mentioned above.

The Not-So-Good Things

In my opinion, the most controversial change that has been made to the Spring Boot Initializr is with regards to the dependencies section.

The objective of this section is to let developers select dependencies for their project. And even with the new interface, that's the purpose of this section.

However, the traditional check-box driven approach where you can pick dependencies from a long list has been replaced with a search bar.

For example, if you need web-related dependencies, you need to enter "web" in the search-bar. The dependencies related to that particular topic will be listed below, which you can select the appropriate ones.

On face value, all of it works fine. The only downside is that there is no way to access the full list like earlier. Apart from the few suggestions mentioned in the search bar, there is no mention of the many other projects that form a part of the Spring Boot family. For instance, this includes Spring Cloud, Messaging, NoSQL databases, and so on.

Now, this is by no means a deal-breaker. Everything still works. You can still get those projects by searching for the relevant term in the search-bar. In fact, the new user interface is a lot more snappy when compared to the old one.

However, it does makes things a tad complicated if you aren't aware of what dependencies to pick or just want to see all the available options before choosing one.

Usually, new projects will also get added to the Spring Boot family, and with the old list-view, it was easier to get to know about them. With this new interface, one needs to rely a lot more on the official docs.


This was my short opinion on the new web-based Spring Boot Initializr. Even though it doesn't change the functionality, it does a few good things with the interface.

However, there are also a few design choices that might make the task of selecting dependencies a bit more confusing or time-consuming. Now, I don't know why this decision was made, and maybe, things will change in the future.

Nevertheless, Spring Boot remains as one of the best Java microservices frameworks.Building production-ready microservices using Spring Boot is fast and efficient.

So, what do you think about this change? Do you see any other issues? Or, have you already found an alternative way to handle things? Sound off your comments in the comments section below.

Java, Spring Boot initializr, dependencies, intitializer, java frameworks, microservices, spring boot

Published at DZone with permission of Saurabh Dashora . See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}