Spring Boot Reviews

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. 

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. 

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

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 the solution to run microservices on an Azure platform. Our UI is on Angular, and Spring Boot is our backend. We have connections with Kafka Topics and some IBM backend tools, and Spring Boot is sufficient to play the part of the orchestration layer.

The solution is easy to use; I primarily employ integrated templates such as the REST template.

I like the containers as I can quickly boot up and run them in Apache Tomcat.

The product is also easy to deploy in a cloud-based infrastructure.

The tool's documentation could be improved, especially by tying it back to frequently asked questions and issues users have. A feedback loop in which the documentation targets the most commonly asked user questions would make using the solution easier. Essentially, I want a more user-centered approach to documentation rather than a purely technical focus.

The UI could be better, though, like many users, we don't use Spring Boot's UI functionality; we use an Angular front-end, and Spring is a backend layer. There are alternatives to using the solution's UI.

We've been using Spring Boot for around six years. 

Spring Boot is a very stable solution; I never had an issue with it. 

The product is scalable, providing the proper infrastructure is in place. If we have the resources, we could have 100 instances of the solution running, and that would be fine if the load were balanced. We use Spring Boot bank-wide, with about 300 developers in total.

The support is excellent. As Spring Boot is open source, help is always readily available, and we rarely need to go outside our organization to find it. The solution is not an off-the-shelf tool; it gives us a set of libraries where we can build, customize, and write our own tools. As we write our own software, the need for outside technical support is much less; we can support ourselves.

We integrate with third-party products in our ecosystem, including some IBM tools and Jakarta EE. The latter requires us to buy a license for a container, but Spring Boot comes with its own internal container called Docker.

The initial setup is straightforward and consists of going through a simple initializer process online by filling out a form with the project name and some requirements. Then, the form results will generate a shell project to download. This process takes under 15 minutes, especially if I know what features I want to include in my project. I rate the solution five out of five for ease of setup.

The solution is free. 

I rate the solution nine out of ten.

The tool is continually being improved, and when Java is upgraded, the Spring Boot update quickly follows. They're doing very well on that front.

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.