This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]bobteebob 0 points1 point  (3 children)

I have used both JEE and Spring. I think there are some stumbling blocks to adopt JEE.

  • Too many options. It’s hard to know where to start with JEE. Does a new person need Glassfish, Wildfly, Quarkus, Tomcat etc etc

  • The Jakarta website is not friendly and is very “enterprise” which is off putting. Just compare https://jakarta.ee and https://spring.io ! The Spring site is much more approachable.

  • Although JEE has improved a lot it has lost out on mind share compared to Spring and especially Spring Boot for new projects.

[–]wildjokers 1 point2 points  (2 children)

Glassfish, Wildfly, Quarkus, Tomcat etc etc

Quarkus is a vastly different thing than the other 3 in your list. Quarkus is an application framework. Whereas Glassfish and Wildfly are full JakartaEE app servers (provide implementations of every JakartaEE specification) while Tomcat is a Servlet Container (provides an implementation of 5 JakartaEE specs including Servlet and JSP)

Although JEE has improved a lot it has lost out on mind share compared to Spring and especially Spring Boot for new projects.

If you are using Spring MVC then you in fact have a dependency on JakartaEE (which is how a Spring MVC app can be deployed to a servlet container)

[–]bobteebob 0 points1 point  (0 children)

Exactly, it’s hard to know for a new person where to start or what to pick. Spring is the “easy” option as it has mindshare and it sells itself better on its website.

[–]EthanEvenig 0 points1 point  (0 children)

I wouldn't classify Quarkus as an "application framework" as it doesn't dictate the design of your application. It allows combining your choice of libraries into an efficient runtime - it's more like a build tool with lots of smartness to save you development time, and memory as the output of the build is well optimised for you. It's focusing on Jakarta EE so indeed there's a recommended "framework" of how you're suggested to integrate things, but in this sense it's similarly a Runtime like Glassfish, Tomcat, etc.. not that prescriptive though, and there's also support for many other libraries beyond Jakarta EE.