Spring Boot Reviews

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.

I used Spring Boot to create a prototype for a banking solution. I developed two microservices, one for ATMs and the other for the backend. I used Spring Boot with the microservices architecture. I also wrote an application to calculate discount strategies or sales systems for a backend website.

Spring Boot's main feature is that it's great for DevOps because you can write your own application. You don't need to install Apache Tomcat. You can create your project easily with a few clicks.

To monitor your application, you can use RESTful API in Spring Boot, which can help you write microservices applications. In the latest version of Spring Boot, there are many features for reactive programming as well.

If you want to create large microservices applications, you need to connect several applications and services to each other. It is very complicated, and Spring Boot does not have an integrated solution for it.

It would be good to have documentation on Spring Reactive to better understand it.

I've been using Spring Boot for the past two years.

Stability wise, I would rate Spring Boot at eight on a scale from one to ten.

Except for Spring Reactive, the other tools and technology stacks in Spring Boot don't offer scalability. 

Many years ago, I switched from JSF to Spring Boot because it is a good, general framework with many features. For example, Spring Boot has IoC, inversion of control, aspect-oriented programming, and Spring Reactive.

The development phase is simple to install.

Spring Boot is an open-source solution.

For writing applications, Spring Boot is a practical option, and I would give it a ten 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. 

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.

Spring Boot is deployed on a Azure Kubernetes container.

If I have to interact with a core banking system or any other application, I use  Spring Boot.

The most valuable feature of Spring Boot is all the interactions to various applications happen using Spring Boot.

Spring Boot could improve the interface, error handling, and integration performance.

I have been using Spring Boot for approximately four years.

The stability of Spring Boot depends on the hardware being use. If you have good hardware the solution will be stable.

The scalability of Spring Boot is good.

We have more than 1,000 users using this solution.

I have not used the technical support from Spring Boot.

The intiial setup of Spring Boot is simple.

Spring Boot is an open source solution, it is free to use.

We compared Spring Boot to .NET and we found Spring Boot to be better.

I rate Spring Boot an eight out of ten.