jakarta ee - Why choose tomcat over a java EE compliant application server?

Question

Java EE application servers provide all the features of tomcat, so why use tomcat (instead of glassfish for example as it is the official one)?

Especially when Java EE features are needed like JPA, JAX-RS, JSF, and therefore more libraries have to be packaged with the application, while a EE-compliant application server would have provided it out of the box?

Answer 1

The question that was in our mind and the entire reason we created TomEE was, why should people have to choose?

The whole "Tomcat or JavaEE" thing is tired and old.

After 10 years it still comes up and people argue against each other as to which is better and why.

Here's the math in short form:

• In Java EE 6, we (JCP) created the Web Profile to formally acknowledge the need for smaller runtimes with a focused set of technologies.

Great, we're half-way there, but people are still arguing "Tomcat or JavaEE". The solution was clear, Tomcat needed to be Java EE certified. The Web Profile was created to allow for exactly that.

• In 2011 we (Apache) started doing the work to certify Apache Tomcat. Certification reached and announced at JavaOne 2011 as Apache TomEE. Final release announced in April.

Awesome, now we are there.

The new Status Quo

• There is a lighter version of JavaEE
• There is a JavaEE certified version of Tomcat

All this happened in the last 2 years. Things have changed.

If you want Tomcat and JavaEE, you can have it.