Spring Boot Reviews

I use Spring Boot to develop microservices.

It's very easy to get started. It's very quick. Most of the configurations are already available. So not much time is spent on setting up things. One can quickly set up and then get rolling.

The cross framework compatibility has some shortcomings. With JUnit Test Runner and Spring Boot, it's really tedious to make them both work to write the test cases.

I have been using Spring for around ten years, but I haven't used Spring MVC much, though I have used the other parts of the solution's framework. Regarding the version, I am using Spring 5.1. I am a user of the solution.

Stability-wise, it's quite a mature product now.

The initial setup was easy.

It's an open-source solution.

I would recommend Spring Boot to others.

I found it tedious to write JUnit test cases for my code in Spring.

I rate the overall solution an eight out of ten.

I primarily use the solution at the point of sale. It covers inventory management at multiple locations and reports as well. 

The solution is easier to use than Jakarta. It's easier to get things set up. 

The simplicity is excellent. 

The stability is fine.

It is not hard to set up. 

The solution is free. It's open-source. 

The database connectivity could be better in terms of dealing with multi-tenant systems. If that could be simplified, that would be better. Currently, we have to use a customer's implementation. 

I'm not missing any features. 

I've been using the solution for about three years. 

It is stable and reliable. We've had a few issues. However, those were related to coding and refactoring to improve scalability. 

The solution is very scalable. 

I've never dealt with support. I can't speak to how helpful or responsive they would be. 

I'm also familiar with Jakarta. Spring Boot is easier in general. 

The initial setup is very easy. It's not difficult at all. 

I don't handle the deployment process. However, we do use Docker and Kubernetes during deployment. Usually, the deployment is automated, which makes it quick to get going.

The maintenance is easy and minimal. I have no trouble maintaining it. 

The solution is free to use and open-source. 

I'm a developer, not an end-user. 

I'm looking at the latest version of the solution. I'm not on it just yet. I need to move to version three, and right now, I am on version two. 

I would highly recommend the solution in general. I'd rate it eight out of ten. 

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.

We primarily use the solution for building websites and the backend.

It has been helpful in assisting us in the process of building websites. 

The simplicity is great. 

It's easy to set up the solution. 

The solution is mostly stable. 

It is great if you are using Java. 

We'd like to see them get better at securing apps. 

For example, when you want to do authentication, it would be ideal if there was a way to do two-step verification. 

We don't really need any new features.

When we change versions, we run into issues. 

I've been using the solution for two years. 

While the solution is stable, when we jump from one version to another, many things tend to go wrong. We'd like it to be more stable when we switch versions. Therefore, I'd rate the stability 6.5 or seven out of ten. 

I don't really use the solution to scale. I've never tried to expand it. 

I've never contacted technical support in the past. I can't speak to how helpful or responsive they would be.

I previously used Laravel. The main difference is the language used. However, Spring Boot is better if you are working in Java. 

The product is simple to set up. 

I use Docker to deploy Spring Boot.

Once it is up and running, there are many things that I can start creating. 

I'd rate the ease of deployment at an eight out of ten. It is not complex at all. 

I set up the solution myself. I did not need any outside help or assistance. 

I don't deal with the pricing aspect of the solution. 

I'm just a user.

I'd rate the solution eight out of ten. 

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. 

I have 12 developers using Spring Boot in my organization. There are currently two teams in my company: one for the web version, another for the desktop version.

Spring Boot has a very lightweight framework, and you can develop projects within a short time. It's open-source and customizable. It's easy to control, has a very interesting deployment policy, and a very interesting testing policy. It's sophisticated.

For data analysis and data mining, you can use a custom API and integrate your application. That's an advanced feature. For data managing and other things, you can get that custom from a third-party API. That is also a free license.

I would like to see more integration in this solution.

I have been using Spring Boot for four years. This is a cloud-based solution, deployed on AWS.

The solution is stable. I developed a project in hospital management for a big institute in our country, Bangladesh, called Company Limited Hospitals. Four thousand people use this application, and it can very smoothly handle this. There have been no problems with it.

The solution is scalable.

It is a big community, so if you have any problems you can get feedback within a fairly short time. There's also a big international community.

Installation was very easy. There are a few different ways that you can deploy the solution: through a Tomcat server, an Apache HTTP server, or deploy with Docker. We can deploy any policy by using Docker. It's totally hassle-free in deployment policy. You can control your memory and load balance.

I have two people on my technical team for deployment. A system engineer controls all of the deployments.

It's open-source software, so it's free. It's a community license.

I would rate this solution nine out of 10. Someone in any position can use this technology because there is very little code but gives you maximum output. 

Spring Boot is incrementally increasing its users daily. New companies are using Spring Boot because it's very controlled and has microarchitecture. It's a very mobile solution, and you can use it with any product.

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 primarily use the solution for building applications.

The cloud version is very scalable.

The product overall is quite stable.

The configuration moving down from a command key is difficult. If you are doing configurations and adding items, it can become a little challenging.

The security could be simplified.

I have been using Spring Boot for the last three or four years.

The scalability on-premises is limited as you are dealing with hardware. However, in the cloud, scalability is quite good. If a user needs to scale the solution they definitely need to consider deploying the cloud version.

We have about 400 users on the solution on the on-premises deployment model.

We have plans to increase the usage of the solution in the future.

The technical support is pretty good. We actually resolve a lot of issues via an independent contractor. They are quite knowledgable and responsive and we've been satisfied with the level of service that's been provided.

Before using Spring Boot, we actually used the original Spring solution.

The initial setup is pretty straightforward if you are using a simple setup. The environment can get complex though, and then the setup is a bit more difficult.

The deployment took a couple of months. It was quite a long time.

While we handled the cloud deployment ourselves, the on-premises deployment was handled by somebody else. I believe it wasn't too difficult for them to execute. They were quite knowledgeable in regards to the setup.

We're just a customer. We don't have a business relationship with the company.

We use both on-premises and cloud deployment models at this time.

I would highly recommend the solution. It's worked quite well for us and we've been really happy with it overall.

I'd rate the solution eight out of ten. In terms of the overall accommodations made by the product, it could be a bit better. If it was, I would rate it higher.

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.