Spring Boot Reviews

We are using Spring Boot to create services.

The most valuable feature of Spring Boot is it reduces the configuration needed. The configuration is handled by the solution. For example, if you're going to develop a web service, we needed to have a Tomcat web server and had to deploy the services and do tests. However, with Spring Boot, the default server comes with Spring Boot which reduces the task of doing all the configuration.

The solution is good for developing services in Spring Boot web and for batch services Spring Boot batch. You are able to use multiple cloud services to monitor your service production, such as Eureka

Spring Boot can improve the dependency tree that we use for libraries. It would be helpful if it was less complex.

I have been using Spring Boot for approximately one year.

Spring Boot is a highly stable solution.

Spring Boot is meant to be scalable. We use microservice architecture, which is tightly coupled with our Kubernetes cluster. You have your microservices with the default one or three ports, and based on the traffic, you can scale up your ports. The scalability of Spring Boot is very good.

Most of our whole company is using this solution, which is over 10,000 people.

This is an open-source solution and the support is not free. However, the documentation is readily available online.

The initial setup of Spring Boot was easy. The full deployment time can vary depending on the pipeline tests and if you have any other tasks, such as SonarQube checks which checks for everything. Typically, the process takes approximately 30 minutes. However, the time could increase if there are many complex elements, such as unit tests, and many modules.

If the deployment has a few services used and there are not any test cases, the deployment could take two minutes.

We did the implementation of the solution in-house.

If you want support there is paid enterprise version with support available.

If you develop in Java, 99 percent of people would use Spring Boot. There is a lot of framework support.

My advice to others is they should structure their directory classes properly or else the Spring Boot automatic configuration would not detect the components.

I would recommend this solution to others, there is not a more user-friendly tool available.

I rate Spring Boot a nine out of ten.

I gave my rating because the solution has open-source community support and it makes it easier by avoiding the need for us to do the configuration.

It's a framework that is very easy to access and easy to configure. It's inbuilt to the Apache Tomcat server, and it's very lightweight. 

We like that it is an open-source tool. 

The solution is very lightweight.

It's simple to access.

The design is great. I can easily access and just pull API if I want to trigger any URL in that application.

One of the best aspects is that it is cloud native. 

Even if I want to implement a microservice that's in it, I can design the microservices. 

In terms of transactions, I can do a bunch of different services and break them down into microservices. I can do that using the RESTful API if I need to send it from the front end to the back end. 

It works well with GitHub. It's a very flexible way to configure the JavaBeans, XML configurations, and databases. We can manage REST endpoints, and I can use RESTful API, which makes it easy to auto-configure. There is no manual configuration needed. 

In terms of the Spring Boot application, the application's startup time needs to be improved. We'd like to see more speed and better performance. 

We'd like them to develop more supporting testing. We'd like to see it be more flexible.

It would be ideal if they continued to prioritize security.

They should ensure that auto-configuration related to Spring MVC will be added into any new features.

It's stable and very easy to create a standalone application. The performance is good and it is reliable. There are no bugs or glitches. It doesn't crash or freeze. 

I've never had to contact support. I use a full-stack website. I can find many answers I'm looking for online. 

In terms of the initial setup, the basics are very important. If I know Java, for example, if I know Java, it will be easier. I have Java experience, and that's huge. I have more than seven years of experience, and I have worked in different frameworks. Therefore, for me, it's easy to understand the design of the architecture, which makes implementation simple. 

A cloud deployment won't take that much time. Every two weeks, I have the deployment using an Agile sprint. I can deploy within five minutes. It does, however, depend on the requirement. We tend to follow the documentation while moving into production. 

The solution is open-source and free to use. I'm not aware of the pricing of the commercial version. 

We are a customer and end-user.

If you plan to use this product for the first time, I suggest doing some research. It's easy to use and doesn't require that much configuration, however, it's simpler if you understand a little bit about it. 

I'd rate the solution eight out of ten.

We use this solution for web applications and to handle data relevant to our customers. 

This solution is really user friendly. In terms of prototyping, it's really fast to build the applications we want to test to complete a proof of concept. In this regard, Spring Boot is really a good framework compared to Java EE because it has less boilerplate codes, and we program conventions over configurations.

This is a really good solution for me and I can't think of anything that can be improved.

I have been using this solution for five years. 

This is a stable solution. We have not experienced any issues or bugs that we were not able to fix. 

This is a scalable solution. We have an application that consumes around 500,000 messages per second and it's handling it quite well. This does depend on the capabilities of your hardware. 

I have previously used Java EE. When using Java EE, you have to have a separate application server. For Spring Boot, it has an embedded server so from the get go, you can easily run your application. With Java EE, you have to set up the application server first to be able to run it.

There is also a difference in the amount of boilerplate code that you need to write when using each of the systems. Spring Boot favors convention over configuration so there are no big challenges when it comes to setting it up. When using Java EE, you have to make sure that your dependencies work together.

The initial setup is very easy. You just need to specify some of the basic dependencies and you're good to go. You can have a running application by writing one class. Setting this up took us less than five minutes. We currently have just over 20 people using this solution. 

This solution is free unless you apply for support.

I would advise others to read the Spring Boot documentation because it is by far the best that I've seen when it comes to Java frameworks. You don't need to pay for courses, tutorials or training. Spring Boot also has a large community. Anything that you might want to ask about Spring Boot or any issue that you might encounter, has answers provided for by the community. 

I would rate this solution a ten out of ten. 

The solution is stable and has a vast community. It works on Java-based language and has an efficient framework.

They should include tutorial videos for understanding new technologies.

I have been using the solution for three years.

The solution's framework is stable. I rate its stability a ten. 

I rate the solution's scalability a ten.

The solution's initial setup process is straightforward. I rate the process an eight. It requires specialized knowledge of Java. It takes one week for simple APIs. Whereas it might take a month or two for complex projects.

I rate the solution a nine. I advise others to know new ways of configuring it.

I primarily use the solution at the point of sale. It covers inventory management at multiple locations and reports as well. 

The solution is easier to use than Jakarta. It's easier to get things set up. 

The simplicity is excellent. 

The stability is fine.

It is not hard to set up. 

The solution is free. It's open-source. 

The database connectivity could be better in terms of dealing with multi-tenant systems. If that could be simplified, that would be better. Currently, we have to use a customer's implementation. 

I'm not missing any features. 

I've been using the solution for about three years. 

It is stable and reliable. We've had a few issues. However, those were related to coding and refactoring to improve scalability. 

The solution is very scalable. 

I've never dealt with support. I can't speak to how helpful or responsive they would be. 

I'm also familiar with Jakarta. Spring Boot is easier in general. 

The initial setup is very easy. It's not difficult at all. 

I don't handle the deployment process. However, we do use Docker and Kubernetes during deployment. Usually, the deployment is automated, which makes it quick to get going.

The maintenance is easy and minimal. I have no trouble maintaining it. 

The solution is free to use and open-source. 

I'm a developer, not an end-user. 

I'm looking at the latest version of the solution. I'm not on it just yet. I need to move to version three, and right now, I am on version two. 

I would highly recommend the solution in general. I'd rate it eight out of ten. 

We host a web app where we have different APIs of the e-commerce marketplace and we use Spring Boot on the backend.

The solution reduces our development time.

Spring Boot allows us to quickly develop what we need.

The solution has some vulnerabilities and fails our security audits, forcing us to keep fixing the solution.

I have been using the solution for three years.

I give the stability an eight out of ten.

I give the scalability an eight out of ten.

We have 20 people using the solution in our organization.

We previously used Django and switched to Spring Boot because my current client is more interested in Java.

The initial setup was straightforward. The deployment took a few days because we needed to get permission which requires going through a certain approval process.

I give the solution an eight out of ten.

We require around five engineers for maintenance.

I recommend the solution to others.

We are using Spring Boot for many use cases.

The most valuable feature of Spring Boot is the microservices and change information. Additionally, there are plenty of features.

The solution could improve its flexibility.

I have been using Spring Boot for approximately two years.

Spring Boot is stable.

The solution is scalable.

The support is good because of the online community, we receive a faster response.

I rate the support from Spring Boot a nine out of ten.

Positive

The initial setup of Spring Boot is easy.

I am using a free version of Spring Boot.

I would recommend this solution to others.

I rate Spring Boot a nine out of ten.

We use the solution to run microservices on an Azure platform. Our UI is on Angular, and Spring Boot is our backend. We have connections with Kafka Topics and some IBM backend tools, and Spring Boot is sufficient to play the part of the orchestration layer.

The solution is easy to use; I primarily employ integrated templates such as the REST template.

I like the containers as I can quickly boot up and run them in Apache Tomcat.

The product is also easy to deploy in a cloud-based infrastructure.

The tool's documentation could be improved, especially by tying it back to frequently asked questions and issues users have. A feedback loop in which the documentation targets the most commonly asked user questions would make using the solution easier. Essentially, I want a more user-centered approach to documentation rather than a purely technical focus.

The UI could be better, though, like many users, we don't use Spring Boot's UI functionality; we use an Angular front-end, and Spring is a backend layer. There are alternatives to using the solution's UI.

We've been using Spring Boot for around six years. 

Spring Boot is a very stable solution; I never had an issue with it. 

The product is scalable, providing the proper infrastructure is in place. If we have the resources, we could have 100 instances of the solution running, and that would be fine if the load were balanced. We use Spring Boot bank-wide, with about 300 developers in total.

The support is excellent. As Spring Boot is open source, help is always readily available, and we rarely need to go outside our organization to find it. The solution is not an off-the-shelf tool; it gives us a set of libraries where we can build, customize, and write our own tools. As we write our own software, the need for outside technical support is much less; we can support ourselves.

We integrate with third-party products in our ecosystem, including some IBM tools and Jakarta EE. The latter requires us to buy a license for a container, but Spring Boot comes with its own internal container called Docker.

The initial setup is straightforward and consists of going through a simple initializer process online by filling out a form with the project name and some requirements. Then, the form results will generate a shell project to download. This process takes under 15 minutes, especially if I know what features I want to include in my project. I rate the solution five out of five for ease of setup.

The solution is free. 

I rate the solution nine out of ten.

The tool is continually being improved, and when Java is upgraded, the Spring Boot update quickly follows. They're doing very well on that front.