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.

We use Spring Boot for microservices, but for the logistic version. We also use the solution for traditional banking purposes.

The most valuable features of Spring Boot include being able to check all the logs and doing health checks for applications. We can also do monitoring more quickly, and use Spring Boot for production support, so when production goes up or down, we can bring up the application very quickly through Spring Boot.

Spring Boot is okay right now, but my team is looking for some integration where you can make a call to the JMS messaging service and other types of third-party integrations. If the integration with Spring Boot is improved, that would make the tool better.

What I'd like to see in the next release of Spring Boot is its integration or tie-up with messaging servers and third-party EFPs, as that would make it very good and more competitive versus other new solutions in the market.

I've been using Spring Boot for three and a half years now.

Overall, Spring Boot is a stable tool.

Spring Boot is a scalable tool. For example, in some microservices, you can just scale down if not used in most cases. For other micro solutions, you can bring up in the RAM space or in cluster mode. If you need more people to use Spring Boot, you can scale it, with no issues.

My rating for the Spring Boot technical support team is five out of five.

The initial setup for Spring Boot was straightforward, and it was completed within ten minutes.

We deployed Spring Boot in-house.

As Spring Boot is an open-source tool, it's free.

As microservice is a new concept, Spring Boot is the first solution we've used that offers it. Before, we used a monolithic application, the Spring MVC. Now people are moving to microservices, with each service being broken down into a simple service.

My company deployed Spring Boot by embedding it on a Tomcat server.

In the company, twenty people use Spring Boot for different microservices such as logistic applications for invoice creations, booking logistic services, invoicing, login authentication, load management services for creating loads, creating roads on maps such as Google Maps, etc.

My company relies on Spring Boot and uses it extensively as it's an open-source tool and so much has been added to it in terms of Java. It's a platform with independent capabilities that you can just deploy in Windows or Linux, and that's a Spring Boot advantage.

My advice to anyone looking into implementing Spring Boot is to go for it. If you need microservices, this is the best solution to use.

My rating for Spring Boot is nine out of ten.

It's being used for the front-end web portion of our application.

It simplifies the development environment for developing web applications.

The setup is straightforward. 

We have found the product to be stable so far. 

Nothing really comes to mind in terms of areas of improvement. It works well. There's nothing that stands out that I would look to be improved with that software.

I have some experience with the solution. My teams have worked with it for a bit longer.

The solution seems stable. I haven't dealt with bugs or glitches. It doesn't crash or freeze. It's reliable. 

I haven't tried to scale the solution. I'm not sure how well it would scale, having never tried. 

We mostly have software developers using the solution. It's not meant for everyone in the company to access. We just have small teams on it. 

I've never needed to call technical support. I couldn't really comment on how helpful or responsive they would be.

The solution is very straightforward and easy to implement. It's not a complex deployment process. 

I can't speak to the exact pricing of the product. I don't handle licensing. 

My understanding is that it is comparable to what else is in the market. I don't know of many competitors for it in the Java environment. Everybody seems to use Spring Boot.

I would recommend potential users to try it, particularly if they're developing web-based applications. It would make sense for them to try and implement it as a Spring Boot application instead of just the base Java application.

I'd rate the product nine out of ten. It was easy to install, there wasn't any expense involved, and it seemed to work as designed.

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.

We use Spring Boot to create different microservices. The configuration is very easy. We also make use of the in-built server. Spring Boot Two has reactive programming and that is valuable for microservices development. We have more than 1,000 users supported by Spring Boot. 

We use this solution on-premise as well as on the public cloud.

The community surrounding Spring Boot is really good. If you face any issue with Spring Boot, you will get the answer from the community. Spring Boot also provides smooth integration with other solutions. A module is provided for each integration including for Kafka and DB.

Building a new product in Spring Boot can take a long time since the solution uses reflection. This is one area the solution could be improved. 

I have been using this solution for more than five years. 

This is a stable solution. 

This is a scalable solution. 

I have not needed to contact support because I rely on the documentation provided. 

We switched to using Spring Boot to make our application more scalable and to be able to make custom configurations. If you have deployed something and you want to customize it, you can easily adjust it with the Spring Boot application without doing any code changes.

The initial setup is very straightforward using the Spring Initializr. You can configure any project in a matter of seconds. It creates an executable JAR and with a single command, it will run automatically.

This is an open source solution. 

I would advise others that it is important to know Java well. I would also recommend getting to know how Spring Boot works internally to use you make use of the proper configuration. 

I would rate this solution a nine out of ten as 99% of our requirements are met. 

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.

I work for customers in several industries and I mainly develop API and support applications and innovation with them, depending on the customer needs. I work in healthcare, logistics, and manufacturing.

The interaction with the database is great. Configuration management is useful as well. There are several features and I use many of them. 

The setup is straightforward.

It is a stable product.

The product scales well. 

Technical support is good.

It is a free open-source product with an active community.

Spring Boot is based on convention over configuration. Therefore, sometimes it seems that everything happens magically. It's difficult to explain to junior developers what it does under the hood.

There are no missing features at this time.

I've been using the solution for eight to nine years. 

It's very stable. I use it for most of my projects, and I don't have many problems with it. If there are problems, is due to the application being misconfigured. It's a configuration problem that is usually easy to solve.

It is scalable. It is a cloud-native technology. Therefore, it fits with most cloud environments and container platforms. There are not many problems in scaling it. The only problem is if it's not compiled natively, it's slow. That said, this is a Java problem, not a framework problem, let's say.

Technical support is good. 

Positive

I implement solutions with this framework. It doesn't need to be installed. It's straightforward to get started. It helps if you are a little experienced. 

I'd rate the implementation process a five out of five in terms of ease of execution. 

I am an employee in a company that heavily invests in this technology, and it pays off. Customers are happy. We are productive and developers are happy when working with it compared to other technologies. Therefore, my company is happy with this solution.

It's an open-source product, so we don't have a real partnership with the framework vendor. It is free to use. 

The solution is deployed both in the cloud and on-premises, depending on the customer's needs.

We work with the solution on behalf of clients. 

80% of my projects in the last eight years have been made with Spring Boot.

I'd advise new users to stay in touch with the community and explore the very valuable community resources.

I'd rate the solution a nine out of ten. It's very popular. It has a very engaged and very active community. The conference and the material online is great and it's usually very high quality. Once you've learned the solution, it allows you to be very productive.

The big thing in Spring Boot is that you don't need to make many manual configurations to set up some of the basic things I analyze. If you use Spring Core and want a JDBC connection, you need to consider a lot of XML files to have the JDBC connection done. In Spring Boots, it is simple to have the JDBC connection since the basic functions can be achieved with minimal codes or minimal configurations, making it a very powerful tool. There is not much custom configuration needed in Spring Boot.

With the boom of AI and machine learning, there is a need for a lot simpler integrations with them. The solution should have basic data models. There were regression and classification models before introducing data models back, and I feel we need some plugins to help to make it possible. In general, I want to see some integration in Spring Boot with artificial intelligence products.

I have been using Spring Boot for eight years. I am just a user of the product.

It is a stable solution. Stability-wise, I rate the solution a nine out of ten.

Considering that If we are using the correct microservices and architecture using Spring Boot, I rate the solution scalability a nine or ten out of ten.

If you are using a monolithic architecture with Java Spring Boot, then the tool will not provide enough scope for scalability. With microservices, you can deploy the tool with a lot of functions and make it scalable.

Around 50 people use the solution in my company, but there are a total of 80 people who know Spring Boot.

I was initially using Spring Core, the earlier version of Spring Boot.

The initial setup was not complex and was a simple process. If you want to have multiple integrations, the setup phase will become complex. There are not many complications during the setup phase in Spring Boot for basic functions or websites.

The solution is deployed on an embedded application server from Spring Boot, or we must deploy the tool using other application servers.

I use the free version of Spring Boot.

If you want a livelock, I think Flume and Spark are open for it, and it will be better than a custom Java application built by IBM Redbooks. In the fields of data management and data streaming, Java is flexible, while Spring Boot is more flexible than Java.

Overall, I rate the solution a nine out of ten.