What is the difference between JBoss EAP, Wildfly, JBoss web, and JBoss server?

I'm new to JBoss, and have found a lot of different terminology - JBoss EAP, JBoss Server, Wildfly, Jboss Web, and a lot of documentation that is either not up to date or targeted at an older version.

Where do I start learning about JBoss as a Java EE application server, running against the most current build?

JBoss EAP is the name for the Java EE application server that Red Hat produces and supports. The latest version is 6 at the moment and this implements Java EE 6.

JBoss AS/WildFly is the name for the community project that you can test. This community project will eventually become JBoss EAP. "WildFly" is just the new name for "AS", which stood for Application Server. Version numbering is a bit more difficult here. WildFly 8, WildFly 9, WildFly 10 and possibly additional WildFly versions are all milestones on the path to what eventually will be called JBoss EAP 7. They all implement Java EE 7.

Even though they're milestones on that path and not supported, some releases are actually quite stable and could be run into production (but since they're not supported this is at your own risk).

JBoss Web was the name of the Tomcat based Servlet container that Red Hat used in JBoss EAP 6 and earlier. From EAP 7 on (and thus already in WildFly 8,9,10) this will be replaced by a new Servlet container/http engine called Undertow.

JBoss EAP is the JBoss Enterprise Application Platform that is a subscription based JavaEE application server; this is a Red Hat product; whereas Wildfly is the community product.

You can check link https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.2/ to get all the documentation related to JBoss EAP 7.2 version.

Developers can think of WildFly as an incubation ground for new JBoss features. WildFly employs a continuous delivery model, which means new WildFly releases happen more frequently than JBoss EAP releases.

This gives WildFly users the chance to use new features or provide feedback on the latest builds before the code is integrated into a JBoss EAP release. In comparison, JBoss EAP releases occur much more infrequently.

From an API standpoint, the biggest difference between WildFly vs. JBoss EAP is their MicroProfile support. The MicroProfile API is included as part of the WildFly distribution. JBoss EAP users will need to install the Eclipse MicroProfile expansion pack to obtain support.

Another key factor in the WildFly vs. JBoss EAP debate is that only EAP comes with subscription-based support from Red Hat. WildFly does not

Simply,

1. JBoss EAP is Enterprise Edition with RedHat support (with subscription,also JEE1.6+)
2. JBoss Wildfly like Developer Edition (also JEE1.7+)