Spring Boot Reviews

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. 

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. 

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.

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. 

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

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. 

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

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.

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.

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

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.

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.