Spring Boot Reviews

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

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. 

I'm the CEO of our company and a user of Spring Boot. I use the product on a daily basis for business applications. It's great because it simplifies development. Together with MyBatis, they make a beautiful pair for Java development. I'll be developing with Spring Boot in the future.

The product could be improved by supporting and integrating Hadoop. A year ago Spring Boot announced that they were removing Hadoop support from the product but many software companies work with Hadoop and Cassandra, and I really think that Spring Boot should renew the Hadoop connection. 

I've been using Spring Boot since 2003 when the framework was created.

It's a very stable product. 

As a Java program, it's very scalable.

I haven't had any issues where I've required technical support. I know there is a blog and many forums where questions can be answered and Spring Boot is discussed. There are somewhere between five and 10 different software forums. 

Setup of the program is very simple, it takes about a minute. 

As a product that is a Java framework, it's better and a lot more simple than other similar frameworks. 

I would rate this product a nine out of 10. 

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.

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.