Spring Boot Reviews

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 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.

My team uses Spring Boot to build APIs. We're running Spring Boot for 90% to 95% of our ecosystem. When you talk about the Java system, Spring Boot is the only framework we're using right now.

Spring Boot's configuration is easy, and it has an out-of-the-box deployment.

Spring Boot's cost could be cheaper.

I have been using Spring Boot for five years.

Spring Boot is not too stable on the cloud, and it normally consumes a lot of memory and CPU.

Spring Boot is a highly scalable solution. Around 200 to 250 users are using Spring Boot in our organization.

We previously used Apache Camel.

Spring Boot's initial setup is straightforward.

We have an in-house deployment, where they restrict your deployments into the cloud so that we can do on-prem setups. Then, you can deploy applications into the back setup.

Spring Boot is a cloud-based solution. I highly recommend Spring Boot for users who do not process highly sensitive traffic.

Overall, I rate Spring Boot an eight out of ten.

We use a variety of actuators. We have also been working with a Spring MVC as a plugin, so we Hibernate ORM like the one where we connect to the database. We use it a lot, and Spring Boot provides interfaces like run command line runner replication. The configuration setup in Spring Boot is pretty simplified compared to Hibernate ORM.

They have starter POMs and starter configurations for different use cases. But sometimes, when the dependencies within those starter packages clash, mismatch or have a hazard, it is hard to solve the issue. The dependency management should be improved so there can be a configuration showing that it's clashing.

We have been using this solution for about two years. It is cloud-based.

Regarding stability, if we are making a REST API, I would rate the stability a nine out of ten, but if we want to make a full-fledged application, I rate it a seven out of ten.

It is scalable. We are currently serving around 10000 users.

If we have any issues with the technology, we can search it on the internet, go to Stack Overflow or talk to some experts that we have.

The setup process is simple.

We mostly try to use open-source components because we get the maximum support on the open source, and it's pretty flexible to work with our developers with open source. Mostly, we use open source. In terms of deployment, it's on the higher side compared to other stacks because the application footprint is a bit larger.

The other technology stack would be a notice-based solution which is handy to start with. But once the scope of the application rises, the number of use cases doesn't feel stable. It keeps breaking because of the lack of a type system in Java. So for an enterprise application, the initial amount of time it takes to build might be later while the application runs. On the other hand, it is much more stable than a JavaScript environment.

I rate this solution an eight out of ten. It would be great to have additional features to improve the technology.

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.

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.

I primarily use the solution for web applications. 

The solution has been very stable.

We like that the product is open-source. We have a lot of community support and a lot of help available in the market. It is widely being used and therefore I get a lot of information on the internet.

The initial setup is simple. 

The cloud packaging is not very straightforward, I would say. For example, integrating with Azure or a microservice architecture or cloud-based architecture is ard. If they could improve and provide a whole package at once would be great.

I've been using the solution for four to five years at this point. 

In terms of stability, the performance is good and it is a reliable product. There are no bugs or glitches and it doesn't crash or freeze. 

I'm not sure how many people use the solution within our organization, or how often. However, my understanding is that it is widely used. 

We have our own technical people on our team. We don't have any tech support as such, however, we do have support for our guys where we can ask for detailed support and information about the environment and all those things.

The implementation process is simple and straightforward. It's not overly complex or difficult. 

If we need to integrate it with third parties, we may get assistance, however, the process is pretty simple. 

The solution is open-source and free to use. We are not a premium member and therefore do not pay any licensing fees. 

I'm just an end-user of the solution.

I pretty much work on the open-source, like the Java Spring Boot. That's it.

I would recommend the solution to others. I'd rate the product at an eight out of ten.

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.