Spring Boot Reviews

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

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.

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.

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.

I work for customers in several industries and I mainly develop API and support applications and innovation with them, depending on the customer needs. I work in healthcare, logistics, and manufacturing.

The interaction with the database is great. Configuration management is useful as well. There are several features and I use many of them. 

The setup is straightforward.

It is a stable product.

The product scales well. 

Technical support is good.

It is a free open-source product with an active community.

Spring Boot is based on convention over configuration. Therefore, sometimes it seems that everything happens magically. It's difficult to explain to junior developers what it does under the hood.

There are no missing features at this time.

I've been using the solution for eight to nine years. 

It's very stable. I use it for most of my projects, and I don't have many problems with it. If there are problems, is due to the application being misconfigured. It's a configuration problem that is usually easy to solve.

It is scalable. It is a cloud-native technology. Therefore, it fits with most cloud environments and container platforms. There are not many problems in scaling it. The only problem is if it's not compiled natively, it's slow. That said, this is a Java problem, not a framework problem, let's say.

Technical support is good. 

Positive

I implement solutions with this framework. It doesn't need to be installed. It's straightforward to get started. It helps if you are a little experienced. 

I'd rate the implementation process a five out of five in terms of ease of execution. 

I am an employee in a company that heavily invests in this technology, and it pays off. Customers are happy. We are productive and developers are happy when working with it compared to other technologies. Therefore, my company is happy with this solution.

It's an open-source product, so we don't have a real partnership with the framework vendor. It is free to use. 

The solution is deployed both in the cloud and on-premises, depending on the customer's needs.

We work with the solution on behalf of clients. 

80% of my projects in the last eight years have been made with Spring Boot.

I'd advise new users to stay in touch with the community and explore the very valuable community resources.

I'd rate the solution a nine out of ten. It's very popular. It has a very engaged and very active community. The conference and the material online is great and it's usually very high quality. Once you've learned the solution, it allows you to be very productive.

We are using this solution for various in-house applications and products.

Spring Boot is lightweight. The platform is easy for developers to download. It gives you a good framework and support for the different components they have.

This is not a tool for beginners. You need to know and understand it well.

It needs to be simplified, more user-friendly.

Spring Boot is only for lightweight components. You cannot have large applications on it.

If the binary size is large then you have to ensure that the services that are designed are very lightweight.  For example, if there are ten components, you have to divide them into ten and not into one. There needs to be a logical separation.

I would like to see the size of the code improved and the framework. We don't always realize how much we are loading into the microservice. There should be some limitations in place to indicate whether the code size should not exceed a certain amount and should not compile itself.

I have been using Spring Boot for approximately five years.

It's a stable product. We have not had any issues.

Spring Boot is scalable.

I have a team of 50, who are using this solution. The organization has approximately 120 users.

We plan to continue our usage with Spring Boot.

There is a very large community available online. We find enough material there.

The initial setup was straightforward.

There is a lot of documentation to get through, but there is help available online.

This is an open-source product.

Spring Boot is a good product to get started with, especially when there are services to be written, in particular, when in the new microservices area. 

They need to look for the unnecessary binary size that gets increased, otherwise, it's good.

I would recommend this solution

I would rate Spring Boot an eight out of ten.

My primary use case is to develop APIs used by single-page applications. It's almost exclusively for web applications and sometimes for communication between micro services, meaning two Spring Boot apps talking to each other. I develop API and the processes, using open API to define before developing them. With Spring Boot we generate the code and we serve the API's to this single-page application or other micro services. I use it almost every day. It's open source, so we don't have any partnership with them, we're a customer. I'm a software engineer. 

Once you know how to use this solution, it's very easy, especially when building APIs. It has easily understandable convention and is an opinionated framework because of its conventional configurations. It helps build apps very fast and in particular Spring Data JPA  and Maven plugins are very useful in generating code like open API plugin. I like all the features that help with monitoring and tracking network calls between several micro services. Usually when I develop with other tele frameworks or technologies, there are things that don't work but this is not case with Spring Boots. Almost everything works smoothly and upgrading from one version to the next is very easy.

I think that security is a delicate issue in this product. It's not as easy as in other technologies so unless you already have something configured it can't be done with a junior developer. You need some experience to do that properly and to understand how Spring security works.

In addition, as many developers say, sometimes you can see too much magic without really understanding what's happening under the hood. This is the main benefit of Spring Boot, but also a disadvantage in the event that the convention doesn't work and needs to be customized. 

An additional feature they could consider would be the ability to reload properties without having to restart the application. It's one of the things I miss most. There is a solution that requires cloud tools, but there's no way to do it with a simple configuration.

I've been using this solution for about seven years. 

Once you understand the solution, it's very stable and unless you have an error in Java, it's very stable. I don't have many crashes or bugs related to the stability of the product.

Scalability depends on how and what features you use. If you have to scale a stateless API application, it's easy because you can scale it horizontally, ensuring that all the shared resources are available and that if the nodes need to talk to each other, they can. Spring Cloud helps and it's well supported and documented.

In terms of support, the documentation they provide is one of the best around and the community is very helpful. It's a very big community, so you always find the resources that you need. I've never had to contact technical support, I just open any issues on GitHub Bird to get a better idea of some concepts or problems I might have. 

The difference between Spring Boot and other systems is the ecosystem and the  community which allows for testing. Other frameworks like Python, Django, have a much smaller community so it's more difficult to get information. I also use Liferay, which is a huge monolith but has a very small community. When you need help, you need to go to the forum and wait for someone to reply to your question. It can take weeks or even months to get a proper reply because the community is so small. It's an important and valuable feature of Spring. 

There is a website called data.spring.iu where you can choose modules and download the zip file where you can start to develop, so it's easy. Deployment is simple because it's just one configuration file . If you are not an expert in servers or cloud providers, you might have some work to do but it's only one file and a few steps.

For anyone wanting to implement Spring Boot, I would recommend watching the developer, Josh Long, on You Tube. He has a lot of explanation videos showing the basics of Spring Boot. It shows what you can do in few steps, and you can then go to start.spring.iu, download your first project and start working on it.

I would rate this solution a nine out of 10.