Spring Boot Reviews

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.

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.

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.

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.

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.

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

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.

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

I have been using this solution for five years. 

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

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. 

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.

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. 

This solution is free unless you apply for support.

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. 

Spring Boot is a Java Framework, and it offers dependency management for Maven and Gradle, but we use it as a Maven project. We're a massive bank, and I estimate that 95 percent of Java projects use the Spring Boot Framework. It's upwards of 40,000 users.

Spring Boot provides an all-in-one solution for the libraries needed to create a Win app. It covers all the aspects, including validation, security, etc. It provides all those features out-of-the-box. You can do almost everything with Spring Boot. 

Spring Boot could improve its integration with the major cloud providers. Connectivity with cloud solutions isn't easy compared to other frameworks like Django and Python.

I need to connect to GCP, so I would like to have one simple dependency that I can include to immediately connect to GCP, so I don't need to go through all the configuration steps. 

I've used Spring Boot for three years.

Spring Boot is stable, but we can't use the latest version because we are a large bank, and banks have higher security standards. Our security people have to vet it for us. The version we get is usually six or seven months, so all the bugs have been fixed. I have used Spring Boot for my personal use, and I've noticed that the latest version may get unstable.

Spring Boot is highly scalable. It has scaled up a lot compared to the earlier versions. 

Installing Spring Boot is easy, and we can deploy it in three to four hours. 

Spring Boot is open-source.

I rate Spring Boot eight out of 10. Spring Boot provides so many enhanced tools. It's highly scalable and secure. If you are looking for a Java Framework, you won't find a better alternative to Spring Boot.

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.

The big thing in Spring Boot is that you don't need to make many manual configurations to set up some of the basic things I analyze. If you use Spring Core and want a JDBC connection, you need to consider a lot of XML files to have the JDBC connection done. In Spring Boots, it is simple to have the JDBC connection since the basic functions can be achieved with minimal codes or minimal configurations, making it a very powerful tool. There is not much custom configuration needed in Spring Boot.

With the boom of AI and machine learning, there is a need for a lot simpler integrations with them. The solution should have basic data models. There were regression and classification models before introducing data models back, and I feel we need some plugins to help to make it possible. In general, I want to see some integration in Spring Boot with artificial intelligence products.

I have been using Spring Boot for eight years. I am just a user of the product.

It is a stable solution. Stability-wise, I rate the solution a nine out of ten.

Considering that If we are using the correct microservices and architecture using Spring Boot, I rate the solution scalability a nine or ten out of ten.

If you are using a monolithic architecture with Java Spring Boot, then the tool will not provide enough scope for scalability. With microservices, you can deploy the tool with a lot of functions and make it scalable.

Around 50 people use the solution in my company, but there are a total of 80 people who know Spring Boot.

I was initially using Spring Core, the earlier version of Spring Boot.

The initial setup was not complex and was a simple process. If you want to have multiple integrations, the setup phase will become complex. There are not many complications during the setup phase in Spring Boot for basic functions or websites.

The solution is deployed on an embedded application server from Spring Boot, or we must deploy the tool using other application servers.

I use the free version of Spring Boot.

If you want a livelock, I think Flume and Spark are open for it, and it will be better than a custom Java application built by IBM Redbooks. In the fields of data management and data streaming, Java is flexible, while Spring Boot is more flexible than Java.

Overall, I rate the solution a nine out of ten.

I use Spring Boot to develop microservices.

It's very easy to get started. It's very quick. Most of the configurations are already available. So not much time is spent on setting up things. One can quickly set up and then get rolling.

The cross framework compatibility has some shortcomings. With JUnit Test Runner and Spring Boot, it's really tedious to make them both work to write the test cases.

I have been using Spring for around ten years, but I haven't used Spring MVC much, though I have used the other parts of the solution's framework. Regarding the version, I am using Spring 5.1. I am a user of the solution.

Stability-wise, it's quite a mature product now.

The initial setup was easy.

It's an open-source solution.

I would recommend Spring Boot to others.

I found it tedious to write JUnit test cases for my code in Spring.

I rate the overall solution an eight out of ten.