IT Central Station is now PeerSpot: Here's why
Buyer's Guide
Java Frameworks
July 2022
Get our free report covering VMware, VMware, Amazon, and other competitors of Jakarta EE. Updated: July 2022.
620,319 professionals have used our research since 2012.

Read reviews of Jakarta EE alternatives and competitors

Max Ramos - PeerSpot reviewer
Senior Java Developer at NTT Global Networks Incorporated
MSP
User friendly Java framework used to easily develop web applications at a fast pace
Pros and Cons
  • "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."
  • "This is a really good solution for me and I can't think of anything that can be improved."

What is our primary use case?

We use this solution for web applications and to handle data relevant to our customers. 

What is most valuable?

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.

What needs improvement?

This is a really good solution for me and I can't think of anything that can be improved.

For how long have I used the solution?

I have been using this solution for five years. 

What do I think about the stability of the solution?

This is a stable solution. We have not experienced any issues or bugs that we were not able to fix. 

What do I think about the scalability of the solution?

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. 

Which solution did I use previously and why did I switch?

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.

How was the initial setup?

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. 

What's my experience with pricing, setup cost, and licensing?

This solution is free unless you apply for support.

What other advice do I have?

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. 

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Buyer's Guide
Java Frameworks
July 2022
Get our free report covering VMware, VMware, Amazon, and other competitors of Jakarta EE. Updated: July 2022.
620,319 professionals have used our research since 2012.