How to Choose between Tomcat and WildFly

Choose WildFly if:

  1. You plan to use Java EE APIs such as EJB, JAX-RS (REST), SOAP-based services, etc.
  2. You're using Spring, but parts of your project make use of other JEE APIs.
  3. You like the idea of having (or eventually having) commercial support through Red Hat. WildFly is free, so you would need to move to the commercial version (JBoss EAP) to get commercial support through Red Hat.
  4. Your organization uses JBoss EAP for production apps, your development group should either use JBoss EAP or WildFly, which is virtually identical to JBoss EAP, but doesn't come with the commercial support.
  5. You want to get new features sooner. WildFly has a faster release cycle than Tomcat, so new features are available earlier.

Choose Tomcat if:

  1. You don't need (and don't anticipate eventually needing) to use any of the Java EE APIs.
  2. You like the idea of going with an Apache project.
  3. You are familiar with Tomcat already, it meets your needs, and you don't want to learn something new.

Written by Nat Dunn. Follow Nat on Twitter.