# Wildfly (Formerly known as JBoss AS)

# Introduction

WildFly is a powerful, modular, and lightweight open-source application server written in Java. It implements the Java Platform, Enterprise Edition (Java EE) and Jakarta EE specifications, as well as Eclipse MicroProfile.

# Key characteristics of WildFly:

-   **Application Server:**

    WildFly functions as an application server, providing a runtime environment for deploying and executing enterprise Java applications, including web applications, enterprise JavaBeans (EJBs), and other Java EE/Jakarta EE components.

-   **Modular Architecture:**

    WildFly utilizes JBoss Modules for its modular architecture, which provides true application isolation and efficient resource utilization by only loading necessary components.

-   **Open Source:**

    WildFly is free and open-source software, licensed under the GNU Lesser General Public License (LGPL), version 2.1. 

-   **Community-Driven:**

    It is a community-driven project sponsored by Red Hat and serves as the foundation for building Red Hat's JBoss Enterprise Application Platform (JBoss EAP). 

-   **Standards Compliant:**

    WildFly adheres to the latest Java EE, Jakarta EE, and MicroProfile specifications, ensuring compatibility and interoperability with other compliant implementations.

**Strengths**
-------------

-   ✅ **Jakarta EE compliance** --- portable applications across compliant servers

-   ✅ **Mature enterprise features** (JTA transactions, clustering, JCA resource adapters, security realms)

-   ✅ **Centralized management** via admin console & CLI

-   ✅ **Rich support for legacy EJB and JMS workloads**

-   ✅ **Built-in scalability & clustering** for stateful workloads

-   ✅ **Standardized architecture**---easy for developers trained on EE specs

**Weaknesses**
--------------

-   ❌ **Heavier footprint** --- requires an app server runtime, slower startup

-   ❌ **More XML/config** unless using recent EE annotations

-   ❌ **Slower developer feedback loop** compared to Spring Boot hot reload

-   ❌ **More monolithic tendency** unless carefully modularized

-   ❌ **Declining popularity** in greenfield microservice projects

**Market Share & Popularity**
---------------------------------

    -   📉 Still strong in **legacy enterprise** Jakarta EE deployments

    -   Backed by Red Hat (same team behind Quarkus)

    -   Often found in telcos, banks, government systems with long-lived EE apps

    -   Market share lower than in the 2000s, with some moving to **Quarkus** or **Spring Boot**

# Conclusion

**WildFly** is still a **top choice for Jakarta EE-heavy, transaction-intensive, clustered enterprise systems** with strong operational tooling. However, **Spring Boot** is the **market leader for cloud-native, microservice, and modern application development**, with higher developer productivity and better adaptability to change.