Try our new research platform with insights from 80,000+ expert users
CEO at Modal Technologies Corporation
Real User
Good security and integration, and the autowiring feature saves on development time
Pros and Cons
  • "I have found the starter solutions valuable, as well as integration with other products."
  • "Perhaps an even lighter-weight, leaner version could be made available, to compete with alternative solutions, such as NodeJS."

What is our primary use case?

I primarily rely on Spring Boot as the core microservices framework, used for creating myriad solutions for health care and for the financial services industries. Environments change, depending on client commitments and budgets, but Spring Boot remains as the successful nexus for all development.

I have used it for both SQL and NoSQL solutions, including both caching and non-caching environments. With over 20 Spring modules to select for possible augmentation of the basic Spring Boot platform, there is nearly always a solution available.

In cases, where some additional, narrow functionality is still lacking, many existing solutions can be integrated into the Spring Boot Java framework, even if that functionality is not part of an official Spring Boot add-on module.

How has it helped my organization?

Spring Boot has sped time to market and has also improved testability, hence also improving the quality of deployed solutions. By eliminating the need for XML configuration, Spring Boot has also been instrumental in improving application performance, since this shift away from XML has provided an impetus to migrate from SOAP to RESTful services.

Also, Spring Boot has facilitated cloud migrations, since now the application can be deployed as a simple JAR file. Where Spring Boot has not helped has been with clients, who insist on moving away from Java (and .NET), towards lighter-weight solutions, such as NodeJS.

What is most valuable?

I have found the starter solutions valuable, as well as integration with other products.  For example, the MongoDB Repository feature is extremely helpful. Also, the integration with Spring Data JPA is valuable for accessing familiar JPA query functionality.

Spring Security facilitates the handling of standard security measures.

The Spring Boot annotations make it easy to handle routing for microservices and to access request and response objects.

Other annotations included with Spring Boot enable move away from XML configuration, and, of course, autowiring removes the necessity for creating objects in many scenarios.

What needs improvement?

Perhaps an even lighter-weight, leaner version could be made available, to compete with alternative solutions, such as NodeJS.

It would also be extremely helpful if hand-holding templates were provided, to quickly guide new developers through the entire end-to-end process of developing a solution with Spring Boot. These aids could be in question or checkbox answer format, which would then trigger the appropriate guides. The guides should be geared to developer tasks. For example, after the neophyte Spring Boot developer answers some questions, the guide might say, "OK, then, you will want to put your MongoDB queries in the MongoDB Repository that you have created. You can use this @Query format..."

Buyer's Guide
Spring Boot
October 2024
Learn what your peers think about Spring Boot. Get advice and tips from experienced pros sharing their opinions. Updated: October 2024.
814,649 professionals have used our research since 2012.

For how long have I used the solution?

I have been using Spring Boot for three years.

What do I think about the stability of the solution?

My impression is that Spring Boot is highly stable. In fact, I have not seen any stability problems, at all, since I have been using it.

What do I think about the scalability of the solution?

Spring Boot scales well. Care must be taken if any state is to be maintained since maximum scalability would be associated with a singleton instance of the application.

How are customer service and support?

A deep and wide community provides substantial support for the entire Spring Boot ecosystem.

Which solution did I use previously and why did I switch?

Previously, I used the traditional Spring and EJB. Performance, error-prone XML SOAP layer, XML-weak developer skillset, as well as increased ease of Cloud deployment were prime motivators for switching to Spring Boot.

How was the initial setup?

The initial setup is straightforward due to the extensive starter project support online. Also, there is vast community support online for Spring Boot.

What about the implementation team?

Developers implemented without any vendor team support.

What was our ROI?

Since Spring Boot, as well as the associated Eclipse IDE (with the Spring Tool Suite, STS, installed) are free, ROI is extremely high. The only investment is developer training, which is minimized, in part by having starter projects available online, and in part, by the simplicity of the design of the platform.

What's my experience with pricing, setup cost, and licensing?

Spring Boot is free; even the Spring Tools Suite for Eclipse is free.

I advise others to use the cost savings to invest in Postman Pro, and to use that product to create and run suites of integration testing, whenever changes are made to the code base. I even advise moving unit testing to Postman Pro test scripts, which can be run by testers, in addition to developers. In this way, zero-defect applications can be deployed and supported.

Which other solutions did I evaluate?

The closest competitor was a totally different option: NodeJS/React.

What other advice do I have?

Spring Boot is a great way to implement microservices in the Cloud. It is an especially good choice if the requirements include background processing and calculations, which make the application a poor candidate for a lighter-weight solution, such as NodeJS.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Erick  Karanja - PeerSpot reviewer
Technical Lead at Cellulant Kenya
Real User
Top 5Leaderboard
A highly scalable solution that has an easy configuration and out-of-the-box deployment
Pros and Cons
  • "Spring Boot's configuration is easy, and it has an out-of-the-box deployment."
  • "Spring Boot's cost could be cheaper."

What is our primary use case?

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.

What is most valuable?

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

What needs improvement?

Spring Boot's cost could be cheaper.

For how long have I used the solution?

I have been using Spring Boot for five years.

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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

Which solution did I use previously and why did I switch?

We previously used Apache Camel.

How was the initial setup?

Spring Boot's initial setup is straightforward.

What about the implementation team?

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.

What other advice do I have?

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.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Spring Boot
October 2024
Learn what your peers think about Spring Boot. Get advice and tips from experienced pros sharing their opinions. Updated: October 2024.
814,649 professionals have used our research since 2012.
Mehmet Bagci - PeerSpot reviewer
Board Member at Iota Bilgi Teknolojileri A.Åž.
Real User
Top 10
Easy to set up and extend but uses too much memory
Pros and Cons
  • "It is stable."
  • "The performance could be better."

What is our primary use case?

We primarily used the solution for web applications. 

What is most valuable?

The capabilities of the solution are very useful.

I personally am not a fan of the solution and don't like much of the tool.

It is easy to set up the solution.

The solution can scale. 

It is stable. 

What needs improvement?

The product uses up a lot of memory, which is an issue. We don't need such complicated frameworks. I don't use Java anymore. 

The performance could be better.

For how long have I used the solution?

I've used the solution for several years.

What do I think about the stability of the solution?

It is stable. 

The solution's performance isn't so good, and it uses up a lot of memory.

What do I think about the scalability of the solution?

The solution is scalable. It can extend well. 

We had about 4,000 or 5,000 users on the solution.

How are customer service and support?

I have never used technical support. I can't speak to how helpful they would be. 

Which solution did I use previously and why did I switch?

We are now using NodeJS. 

We were using Oracle Forms many years ago. Then we started using Java.

How was the initial setup?

The initial setup is pretty straightforward. 

It has a deployment tool that makes it simple to start projects. 

The people available to handle the deployment and maintenance depend on the project. 

What about the implementation team?

We were able to handle the initial setup ourselves in-house. It has a deployment tool that makes it very easy.

What's my experience with pricing, setup cost, and licensing?

We did not pay any licensing fees for the solution. 

What other advice do I have?

We have stopped using the solution as we stopped using Java.

I would not recommend the solution to others. I'd recommend NodeJS, however. I don't like Javan anymore.

I'd rate the solution five out of ten. 

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Jalal Hosseini - PeerSpot reviewer
Software developer at a wholesaler/distributor with 1,001-5,000 employees
Real User
Top 10
Creates projects easily with a few clicks, is stable, and has many features
Pros and Cons
  • "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."
  • "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."

What is our primary use case?

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.

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

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

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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

Which solution did I use previously and why did I switch?

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.

How was the initial setup?

The development phase is simple to install.

What's my experience with pricing, setup cost, and licensing?

Spring Boot is an open-source solution.

What other advice do I have?

For writing applications, Spring Boot is a practical option, and I would give it a ten out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Chiranjeev Sharma - PeerSpot reviewer
Founder at Seaswift Technologies
Real User
A simplified configuration setup that provides various interfaces
Pros and Cons
  • "The configuration setup in Spring Boot is pretty simplified compared to Hibernate ORM."
  • "When the dependencies within those starter packages clash, mismatch or have a hazard, it is hard to solve the issue."

What is our primary use case?

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.

How has it helped my organization?

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.

For how long have I used the solution?

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

What do I think about the stability of the solution?

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.

What do I think about the scalability of the solution?

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

How are customer service and support?

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.

How was the initial setup?

The setup process is simple.

What's my experience with pricing, setup cost, and licensing?

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.

Which other solutions did I evaluate?

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.

What other advice do I have?

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

Disclosure: My company has a business relationship with this vendor other than being a customer:
PeerSpot user
Real User
Checks logs and the health of applications; allows quicker monitoring and is also good for production support
Pros and Cons
  • "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."

What is our primary use case?

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

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

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

What do I think about the stability of the solution?

Overall, Spring Boot is a stable tool.

What do I think about the scalability of the solution?

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.

How are customer service and support?

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

How was the initial setup?

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

What about the implementation team?

We deployed Spring Boot in-house.

What's my experience with pricing, setup cost, and licensing?

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

Which other solutions did I evaluate?

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.

What other advice do I have?

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.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Max Ramos - PeerSpot reviewer
Senior Java Developer at NTT Global Networks Incorporated
MSP
User friendly Java framework used to easily develop web applications at a fast pace
Pros and Cons
  • "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."
  • "This is a really good solution for me and I can't think of anything that can be improved."

What is our primary use case?

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

What is most valuable?

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.

What needs improvement?

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

For how long have I used the solution?

I have been using this solution for five years. 

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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. 

Which solution did I use previously and why did I switch?

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.

How was the initial setup?

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. 

What's my experience with pricing, setup cost, and licensing?

This solution is free unless you apply for support.

What other advice do I have?

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. 

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Manager, Software Projects at a consultancy with 11-50 employees
Real User
Simplifies the development environment, is easy to set up, and is reliable
Pros and Cons
  • "The setup is straightforward."
  • "Nothing really comes to mind in terms of areas of improvement."

What is our primary use case?

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

What is most valuable?

It simplifies the development environment for developing web applications.

The setup is straightforward. 

We have found the product to be stable so far. 

What needs improvement?

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.

For how long have I used the solution?

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

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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. 

How are customer service and support?

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

How was the initial setup?

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

What's my experience with pricing, setup cost, and licensing?

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.

What other advice do I have?

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.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user