Try our new research platform with insights from 80,000+ expert users
Peter Nkomo - PeerSpot reviewer
Technical Lead at a tech services company with 11-50 employees
Reseller
Top 5
An easy-to-use solution with excellent native templates and containers
Pros and Cons
  • "The solution is easy to use; I primarily employ integrated templates such as the REST template."
  • "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."

What is our primary use case?

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.

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

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

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.

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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.

How are customer service and support?

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.

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

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.

How was the initial setup?

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.

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

The solution is free. 

What other advice do I have?

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.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Sameer AHAMED - PeerSpot reviewer
Senior Software Engineer at Huawei Technologies India
Real User
Lightweight, easy to understand, and is cloud-native
Pros and Cons
  • "We like that it is an open-source tool."
  • "We'd like them to develop more supporting testing."

What is our primary use case?

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. 

What is most valuable?

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. 

What needs improvement?

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.

What do I think about the stability of the solution?

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. 

How are customer service and support?

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

How was the initial setup?

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. 

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

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

What other advice do I have?

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.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Amazon Web Services (AWS)
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.
Senior Architect at Tecnics
Real User
Scalable framework used to build microservices based on specific platform requirements
Pros and Cons
  • "Spring Boot facilitates the use of Java which is open source. We use Github and other libraries that are available which assist in the building we need to do."
  • "This solution could be improved if there were more libraries available. We would also like more mobile platform functionality using low levels of code."

What is our primary use case?

We use Spring Boot to build our own microservices as per our platform requirements. We build everything from scratch. It is easy for developers to learn how to use and to start building. We have approximately 100 people in our team using it. 

What is most valuable?

Spring Boot facilitates the use of Java which is open source. We use Github and other libraries that are available which assist in the building we need to do.

What needs improvement?

This solution could be improved if there were more libraries available. We would also like more mobile platform functionality using low levels of code. 

For how long have I used the solution?

We have been using Spring Boot for two years. 

What do I think about the stability of the solution?

This is a stable solution. 

What do I think about the scalability of the solution?

This is a scalable solution. 

How are customer service and support?

Because Spring Boot operates using Java and is open source, there are a lot of artifacts available on the web. We have not needed to contact Spring Boot for customer support. 

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

We decided to use Spring Boot because it operates using Java which works on any platform including Windows, Linux, or Unix. It is easy to deploy in different environments.

How was the initial setup?

The initial setup is generally straightforward but can be more complex when trying to build enterprise apps. The setup takes approximately one week. 

What other advice do I have?

I would recommend this solution to those who have good Java knowledge and skills. 

I would rate this solution a nine out of ten. The reason is that generally less code needs to be written when using it. The Spring Boot framework eliminates the need to write code from scratch. If you wanted to build your own product or solution, Spring Boot offers many possibilities. 

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Amazon Web Services (AWS)
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
Luis Mario Ramos Santos - PeerSpot reviewer
Senior FullStack Developer/Engineer/Architect at Capitbrok
Real User
Top 5Leaderboard
Has good scalability and an easy initial setup process
Pros and Cons
  • "The solution's framework is stable."
  • "They should include tutorial videos for learning new features."

What is most valuable?

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

What needs improvement?

They should include tutorial videos for understanding new technologies.

For how long have I used the solution?

I have been using the solution for three years.

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

I rate the solution's scalability a ten.

How was the initial setup?

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.

What other advice do I have?

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

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Software Engineer 3 at a financial services firm with 10,001+ employees
Real User
Highly scalable, reduces configuration time, and helpful community support
Pros and Cons
  • "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."
  • "Spring Boot can improve the dependency tree that we use for libraries. It would be helpful if it was less complex."

What is our primary use case?

We are using Spring Boot to create services.

What is most valuable?

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

What needs improvement?

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

For how long have I used the solution?

I have been using Spring Boot for approximately one year.

What do I think about the stability of the solution?

Spring Boot is a highly stable solution.

What do I think about the scalability of the 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.

How are customer service and support?

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

How was the initial setup?

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.

What about the implementation team?

We did the implementation of the solution in-house.

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

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

What other advice do I have?

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.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Google
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Sachindra S - PeerSpot reviewer
Senior Software Engineer at a tech services company with 10,001+ employees
MSP
Top 20
Open-source with an easy initial setup and good reliability
Pros and Cons
  • "We like that the product is open-source."
  • "The cloud packaging is not very straightforward."

What is our primary use case?

I primarily use the solution for web applications. 

What is most valuable?

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. 

What needs improvement?

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.

For how long have I used the solution?

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

What do I think about the stability of the solution?

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. 

What do I think about the scalability of the solution?

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. 

How are customer service and support?

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.

How was the initial setup?

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

What about the implementation team?

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

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

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

What other advice do I have?

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.

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
Malumbo Sinkamba - PeerSpot reviewer
Java Software Developer at Chrilan Technology
Real User
Top 10
Open-source, easy to use, and straightforward to set up
Pros and Cons
  • "The simplicity is excellent."
  • "The database connectivity could be better in terms of dealing with multi-tenant systems."

What is our primary use case?

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

What is most valuable?

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. 

What needs improvement?

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. 

For how long have I used the solution?

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

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

The solution is very scalable. 

How are customer service and support?

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

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

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

How was the initial setup?

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. 

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

The solution is free to use and open-source. 

What other advice do I have?

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. 

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
Enrico Costanzi - PeerSpot reviewer
Senior Software Engineer at Intesys
Real User
Good support, great configuration management, and free to use
Pros and Cons
  • "The setup is straightforward."
  • "It's difficult to explain to junior developers what it does under the hood."

What is our primary use case?

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.

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

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

What do I think about the stability of the solution?

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.

What do I think about the scalability of the solution?

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.

How are customer service and support?

Technical support is good. 

How would you rate customer service and support?

Positive

How was the initial setup?

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. 

What was our ROI?

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.

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

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

What other advice do I have?

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.

Disclosure: My company has a business relationship with this vendor other than being a customer: Implementer
PeerSpot user