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 Spring Boot to create different microservices. The configuration is very easy. We also make use of the in-built server. Spring Boot Two has reactive programming and that is valuable for microservices development. We have more than 1,000 users supported by Spring Boot. 

We use this solution on-premise as well as on the public cloud.

The community surrounding Spring Boot is really good. If you face any issue with Spring Boot, you will get the answer from the community. Spring Boot also provides smooth integration with other solutions. A module is provided for each integration including for Kafka and DB.

Building a new product in Spring Boot can take a long time since the solution uses reflection. This is one area the solution could be improved. 

I have been using this solution for more than five years. 

This is a stable solution. 

This is a scalable solution. 

I have not needed to contact support because I rely on the documentation provided. 

We switched to using Spring Boot to make our application more scalable and to be able to make custom configurations. If you have deployed something and you want to customize it, you can easily adjust it with the Spring Boot application without doing any code changes.

The initial setup is very straightforward using the Spring Initializr. You can configure any project in a matter of seconds. It creates an executable JAR and with a single command, it will run automatically.

This is an open source solution. 

I would advise others that it is important to know Java well. I would also recommend getting to know how Spring Boot works internally to use you make use of the proper configuration. 

I would rate this solution a nine out of ten as 99% of our requirements are met. 

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. 

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.

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.

I used Spring Boot to create a prototype for a banking solution. I developed two microservices, one for ATMs and the other for the backend. I used Spring Boot with the microservices architecture. I also wrote an application to calculate discount strategies or sales systems for a backend website.

Spring Boot's main feature is that it's great for DevOps because you can write your own application. You don't need to install Apache Tomcat. You can create your project easily with a few clicks.

To monitor your application, you can use RESTful API in Spring Boot, which can help you write microservices applications. In the latest version of Spring Boot, there are many features for reactive programming as well.

If you want to create large microservices applications, you need to connect several applications and services to each other. It is very complicated, and Spring Boot does not have an integrated solution for it.

It would be good to have documentation on Spring Reactive to better understand it.

I've been using Spring Boot for the past two years.

Stability wise, I would rate Spring Boot at eight on a scale from one to ten.

Except for Spring Reactive, the other tools and technology stacks in Spring Boot don't offer scalability. 

Many years ago, I switched from JSF to Spring Boot because it is a good, general framework with many features. For example, Spring Boot has IoC, inversion of control, aspect-oriented programming, and Spring Reactive.

The development phase is simple to install.

Spring Boot is an open-source solution.

For writing applications, Spring Boot is a practical option, and I would give it a ten 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.

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.