WildFly

WildFly
Name	WildFly
Developer	Red Hat, JBoss community
Initial release	1999 (as JBoss)
Latest release	2025.xx (check project)
Programming language	Java
Operating system	Cross-platform
Platform	Java SE, Java EE / Jakarta EE
License	Apache License 2.0

WildFly is an open-source Java application server for building and running enterprise Java applications. Originally evolving from the JBoss Application Server project, it provides a modular, lightweight runtime supporting Jakarta EE specifications and microservices architectures. WildFly is developed by the JBoss community with stewardship from Red Hat and integrates with a wide ecosystem of middleware, container, and cloud platforms.

History

WildFly traces its lineage to the JBoss project founded by Marc Fleury and later stewarded by Red Hat after acquisition. The JBoss Application Server gained prominence alongside GlassFish and Apache Tomcat during the 2000s as enterprises adopted Java EE and EJB technologies. In 2013 the rebranding to WildFly marked a modular rearchitecture emphasizing JBoss Modules and faster release cadence to align with upstream projects like OpenJDK and evolving standards such as JSR 342 and JSR 354. Over successive releases the project coordinated with the Eclipse Foundation's Jakarta EE initiative after the transfer of Java EE stewardship from Oracle Corporation, interoperating with runtimes like Payara Server and Apache Geronimo. The community and corporate contributors incorporated features responding to cloud-native trends promoted by organizations including Cloud Native Computing Foundation and Docker, Inc..

Architecture and Components

WildFly's architecture centers on a modular classloading structure derived from JBoss Modules, separating subsystems such as the Undertow web server, the IronJacamar resource adapter, and the Infinispan data grid. The core uses the MicroProfile initiative patterns and integrates a management model based on Dmr (Dynamic Model Representation) and an extensible Management Model exposed via CLI and HTTP. Key components include an integrated web connector (Undertow), a messaging subsystem historically tied to HornetQ and later ActiveMQ Artemis, a persistence layer compatible with Hibernate ORM, and a security realm abstraction interoperable with PicketBox concepts and Keycloak for identity federation. The server supports modular deployment units (deployments), subsystems, and extensions that align with OSGi-like isolation without depending on the Eclipse Equinox runtime.

Features and Standards Compliance

WildFly implements many Jakarta EE specifications that evolved from Java EE, including Jakarta Servlet, Jakarta CDI, Jakarta EJB, Jakarta JAX-RS, and Jakarta JMS. It frequently aligns with Java SE releases via compatibility testing against OpenJDK builds and supports standards such as JACC for authorization, JAX-WS for SOAP-based services, and Bean Validation (JSR 380). WildFly also embraces microservices standards through Eclipse MicroProfile APIs like Config, Health, Metrics, and Fault Tolerance, interoperating with tools and libraries from Eclipse Foundation members such as Payara Micro and Thorntail. Integration with Hibernate ensures JPA compliance, while servlet handling uses Undertow which competes with servers like Jetty and Apache Tomcat.

Deployment and Administration

Administrators manage WildFly via a management console, a command-line interface derived from JBoss CLI, and a RESTful management API compatible with orchestration systems including Kubernetes, OpenShift, and Docker Swarm. WildFly supports domain mode for centralized management across clusters, aligning with deployment patterns used by Red Hat OpenShift and AWS deployments. Packaging options include standalone server distributions, container images coordinated with Podman and Docker, and Helm charts for Helm-based Kubernetes deployments. Typical operational integrations involve CI/CD pipelines using Jenkins, GitLab CI, or GitHub Actions and artifact repositories like Maven Central and Nexus Repository.

Performance and Security

WildFly leverages high-performance components such as Undertow and Infinispan to provide low-latency HTTP handling and distributed caching comparable to Hazelcast and Ehcache. Tuning JVMs like OpenJDK HotSpot and GraalVM impacts latency and throughput; benchmarking often compares WildFly to servers like GlassFish and Apache TomEE. Security features include pluggable authentication modules, TLS termination, and integration with identity providers such as Keycloak and Okta; role-based access control aligns with JBoss PicketLink concepts and OAuth 2.0 / OpenID Connect protocols. WildFly participates in vulnerability disclosure models supported by Red Hat and community CVE tracking coordinated with Mitre.

Community and Development

WildFly development is driven by the JBoss community with contributions from corporate sponsors including Red Hat, independent contributors, and partner organizations like IBM and Microsoft in cross-cloud interoperability efforts. Governance follows open-source collaboration practices promoted by the Apache Software Foundation and Eclipse Foundation communities, with development tracked on issue trackers and pull request systems similar to GitHub workflows. The project organizes mailing lists, IRC/Matrix channels, and periodic community meetings, and it participates in conferences such as Red Hat Summit, Devoxx, and JavaOne where maintainers present roadmaps and integration case studies.

Commercial Support and Ecosystem

Commercial support is offered primarily through Red Hat's Red Hat JBoss EAP product which provides long-term support, certifications, and integration with enterprise stacks like Red Hat OpenShift and Red Hat RHEL. Third-party vendors provide complementary services including monitoring (vendors similar to Datadog and New Relic), security scanning (firms akin to Fortify and Synopsys), and managed hosting providers comparable to AWS and Google Cloud Platform. An ecosystem of libraries, adapters, and developer tools from companies and open-source projects enriches WildFly deployments, ensuring interoperability with CI/CD tools, observability platforms, and identity providers widely used in enterprise Java landscapes.

Category:Java application servers