Spring Boot Reviews

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. 

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. 

We have been using Spring Boot for two years. 

This is a stable solution. 

This is a scalable solution. 

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. 

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.

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

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. 

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

They should include tutorial videos for understanding new technologies.

I have been using the solution for three years.

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

I rate the solution's scalability a ten.

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.

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

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

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. 

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.