Spring Boot Reviews

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.

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

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.

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.