Spring Boot Reviews

We primarily used the solution for web applications. 

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. 

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.

I've used the solution for several years.

It is stable. 

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

The solution is scalable. It can extend well. 

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

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

We are now using NodeJS. 

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

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. 

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

We did not pay any licensing fees for the solution. 

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. 

The solution is mainly used for microservices. It's a Java solution. 

The solution is stable.

It has an easy initial setup. 

We can use the solution with Jenkins.

It is easy to set up. 

It's open-source and free to use. 

This is a pretty light solution. It's not too heavy.

There are lots of integrations already available. It's easy to integrate.

I'm not sure if there are any features that need to be added. 

We'd like to have fewer updates. 

We've been using the solution for five or six years. I've used it for a while now. 

The stability has been good. There are no bugs or glitches. It doesn't crash or freeze.

We have 16 banks with us, and we use Spring Boot in some capacity in them all. 

It's a scalable solution. 

We've never directly contacted technical support.

We are using other Java framework solutions. 

The initial setup is pretty straightforward to set up. It's not overly complex. The deployment is pretty fast. It doesn't take a long time to set up.

We use Jenkins tools to help with the deployment process. 

We had a different team that handled the initial setup for us. However, it was done in-house. 

The solution is open-source. 

I'm an end-user.

We are using the latest version of the solution. I'm not sure of the exact version number. 

The solution meets all of our requirements at this time. 

I'd recommend the solution to others. It's a very popular application.

I would rate the solution nine out of ten. 

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.

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.

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

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.

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

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.

The setup process is simple.

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.

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.

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

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.

We use the solution to manage our microservices. It helped us develop a web application portal for a financial company.

We are a financial technology company. We chose Spring Boot because it provides additional security layers, essential for the sector. Moreover, it offers powerful tools and technologies that enable us to focus on specific microservices. It is crucial because the banking industry and financial technology typically rely on a monolithic architecture, where the failure of one service affects the entire system. However, with Spring Boot, a cache in one microservice only impacts that particular service while the others remain unaffected. It is significant considering the large number of users who utilize banking applications.

The solution has the best security features. Thus, financial services providers use Spring Boot's framework incorporated with Java to add a security layer. Moreover, it works as a standalone framework to create applications that can run without relying on external web servers or being embedded within a web server like Apache Tomcat.

The solution needs more applicable control for large-scale application development. It is a time-consuming process to convert a framework to an application. Also, it requires integration with other platforms, making it even more complicated. We cannot use it directly in existing projects utilizing the framework. These particular areas need improvement.

We have been using the solution for more than three years.

It is a highly stable and valuable product when integrated with Java technologies.

We have more than 100 backend developers utilizing the solution. It is scalable, but it depends on the infrastructure that you are using. Also, it requires specific knowledge of managing loads and deployment of microservice applications.

We have yet to contact the solution's technical support team. There are times when we encounter problems. Fortunately, we have a subject matter expert in Spring Boot whom we consult. However, we will seek assistance if we experience any high-level technical difficulties.

The solution's initial setup process is simple. It is easy to learn, even for a beginner using it.

The solution is an open source tool.

The solution is a great technology to learn. It provides default configurations for codes, including dependency injection and inversion of control. It simplifies development, especially for Java developers, as it reduces the need for writing boilerplate code and configuring various aspects. Additionally, it enhances productivity and facilitates unit testing, integration, and test processes. Furthermore, it seamlessly integrates with its ecosystem, including Spring JDBC, Spring Data, Spring Security, etc.

Overall, I rate it a ten out of ten. It has many capabilities including ease of learning and use, and it reduces development time as well. 

The use cases depend on the domain I require it for. Sometimes its for the banking domain and sometimes for health.

The Spring Cloud Gateway, Load Balancer are the valuable features. Apart from them, handling a sync call, then multiple service communication through field clients are also useful features.

We have specific algorithms for our Load Balancer or API gateway. So those things, if they could make it more precise, that would be beneficial. Sometimes when we are under pressure or any new person who looks into that stuff, we'll get confused or scared because of some difficulties in understanding Which algorithm needs to be used to implement a Load Balancer. When when we Yeah. Because when we say circuit breaker, we need to use it, and then the user gets a blank circuit breaker. This means we are saying the circuit breaker needs to be moved, and then that circuit breaker needs to be elaborated more. What type of algorithm should I do, and what exactly do I need to get done so that this circuit breaker can help me to resolve my issue? Because, you know, because if you go for the circuit breaker, it will ask to open the new tab, you know, since it will check. If the service is not responding, it will wait and go for another connection. So in similar words, if they can explain it a bit more, that will be helpful. Everyone could do their own Google stuff, and they will get it, but they need help understanding how this could help them to resolve the issue. It will be good if Spring Boot provides information about real-time use cases.

I have been using the solution for five years.

It is a stable solution. The new version is compatible with JDK so there are no stability issues.

It is a scalable solution. I rate the stability nine out of ten.

I rate the overall solution a nine out of ten.