Spring Boot Reviews

We host a web app where we have different APIs of the e-commerce marketplace and we use Spring Boot on the backend.

The solution reduces our development time.

Spring Boot allows us to quickly develop what we need.

The solution has some vulnerabilities and fails our security audits, forcing us to keep fixing the solution.

I have been using the solution for three years.

I give the stability an eight out of ten.

I give the scalability an eight out of ten.

We have 20 people using the solution in our organization.

We previously used Django and switched to Spring Boot because my current client is more interested in Java.

The initial setup was straightforward. The deployment took a few days because we needed to get permission which requires going through a certain approval process.

I give the solution an eight out of ten.

We require around five engineers for maintenance.

I recommend the solution to others.

We are using Spring Boot for many use cases.

The most valuable feature of Spring Boot is the microservices and change information. Additionally, there are plenty of features.

The solution could improve its flexibility.

I have been using Spring Boot for approximately two years.

Spring Boot is stable.

The solution is scalable.

The support is good because of the online community, we receive a faster response.

I rate the support from Spring Boot a nine out of ten.

Positive

The initial setup of Spring Boot is easy.

I am using a free version of Spring Boot.

I would recommend this solution to others.

I rate Spring Boot a nine out of ten.

Our use of this solution is related to creating microservices, based on microservices architecture that we're implementing now.

Since microservices are totally linked to the business capabilities and, at the same time, it is a way or a style of handling the business functionality and the business processes, Spring Boot comes into the picture where you are just focusing on building microservices for one specific business function. So that has been really helpful. You can have both the UI part and the API part, so that the microservice can be utilized either with other applications or it can be used independently.

Spring Boot is much easier when it comes to the configuration, setup, installation, and deployment of your applications, compared to any kind of MVC framework. It has everything within a single framework, rather than having the hassle of installing, setting up, or even deploying a regular MVC framework.

I'm not one who is really obsessed with Spring Boot. It's a tool. But at the same time, I would rather use other things like a BPMN engine to do the work because Spring Boot is lacking visibility in terms of how that business process or business rule would look within your application. Because everything has been embedded within the code itself, it disables the visibility and the ability to maintain or even support a specific functionality in a user-friendly manner, where a developer can come up and just adjust that part of that process.

I'd rather go for a BPMN tool or engine that will reduce development time, rather than spending the whole time writing a tiny function for linking activities or tasks together.
I would rather use a BPMN engine just to focus on the business link and, at the same time, to have that type of visibility and agility, not to mention, of course, the consistency between consumer processes and the business ability.

It's a stable solution.

It's a scalable solution.

Spring Boot is an open-source tool, a framework.

You need to have that user-friendliness so that it's really easy for both business and even IT to use the same engine. When it comes to modeling, it shouldn't be like a foreign language between IT and the business. It should be very easy to manipulate, very easy to create, very easy to design.

My most important criteria when selecting a vendor depend on specific business requirements. The business is always looking to speed up the production of these services. So agility is number one. The second is going to be the productivity and effectiveness. The third is related to the user experience; and finally, the customer support side.

I would give Spring Boot a five out of 10. Spring, as a framework, is really complex. It's not really easy for a beginner or even an intermediate developer.

We use this solution for human resources applications. 

This solution could be improved if it offered greater integration and was more compatible with other solutions. For this reason, we have moved to Microsoft. 

We have used this solution for one year.

The complexity of the initial setup is moderate, not straightforward. It took approximately one week. 

I would rate this solution 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. 

The big thing in Spring Boot is that you don't need to make many manual configurations to set up some of the basic things I analyze. If you use Spring Core and want a JDBC connection, you need to consider a lot of XML files to have the JDBC connection done. In Spring Boots, it is simple to have the JDBC connection since the basic functions can be achieved with minimal codes or minimal configurations, making it a very powerful tool. There is not much custom configuration needed in Spring Boot.

With the boom of AI and machine learning, there is a need for a lot simpler integrations with them. The solution should have basic data models. There were regression and classification models before introducing data models back, and I feel we need some plugins to help to make it possible. In general, I want to see some integration in Spring Boot with artificial intelligence products.

I have been using Spring Boot for eight years. I am just a user of the product.

It is a stable solution. Stability-wise, I rate the solution a nine out of ten.

Considering that If we are using the correct microservices and architecture using Spring Boot, I rate the solution scalability a nine or ten out of ten.

If you are using a monolithic architecture with Java Spring Boot, then the tool will not provide enough scope for scalability. With microservices, you can deploy the tool with a lot of functions and make it scalable.

Around 50 people use the solution in my company, but there are a total of 80 people who know Spring Boot.

I was initially using Spring Core, the earlier version of Spring Boot.

The initial setup was not complex and was a simple process. If you want to have multiple integrations, the setup phase will become complex. There are not many complications during the setup phase in Spring Boot for basic functions or websites.

The solution is deployed on an embedded application server from Spring Boot, or we must deploy the tool using other application servers.

I use the free version of Spring Boot.

If you want a livelock, I think Flume and Spark are open for it, and it will be better than a custom Java application built by IBM Redbooks. In the fields of data management and data streaming, Java is flexible, while Spring Boot is more flexible than Java.

Overall, I rate the solution a nine out of ten.

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.

We are using the latest version of Java Spring Boot. We can just start with the application within a day. When we start developing we can just start up the application development immediately and work for like four or five hours. We are using it for logistics companies and will be logging thousands of users. Companies of three thousand to four thousand users are what we are using it for.

It doesn't take much time like most other applications. So I just do my business with Spring Boot. It gives you confidence in a readily available platform. You just have to implement your project and you don't have to worry about third parties and integrating all the jobs.

I feel like communication has to be increased. For example, communicating between different services from the third party layers or with the legacy applications. But, it's getting mature right now, but there are some communication patterns that are getting with Spring Boot.

We have been using Java Spring Boot for more than 3 and a half years.

Java Spring Boot is very stable. It's already proven and the market is moving towards this technology.

One of the best advantages of Spring Boot is the scalability. You don't have to worry about it. You can deploy an application like in a service. If I want to have a separate application, or if you want to go with a business logic application, I would tend to go with the single application for the instance. So when I just want to increase the business logic application resources I can just scale up the service. I don't have to scale the whole application. That's monolithic. You can deploy an application individually or have it as a single application.

We do not use their technical support.

The initial setup is very straightforward. The cloud deployment gives you the DevOps technology, continuous integration, and continuous deployment tools. We have Docker, and we can put the image on the container. And we can do it again very easily. We can just bring the application down and bring up the application within 30 minutes.

We did the initial setup in-house and we also maintain it in-house. We have a team of 30 people using Spring Boot.

We have used other frameworks and the scalability is not nearly as good.

I would recommend looking into logistics and buying a domain to use Spring Boot. I would rate Java Spring Boot at a nine on a scale of ten.